• Vitalik Buterin says he is doubling down on Ethereum privacy: it is only dead if you give up.

• EIP-7805 FOCIL remains in draft, with no Ethereum network upgrade scheduling its inclusion.

• Ethereum's privacy roadmap, updated August 24, 2026, covers private reads, writes and proving.

Buterin Doubles Down on Privacy

Vitalik Buterin has publicly recommitted to privacy as a first-class goal for Ethereum (ETH), writing in an X post that the cause is “only dead if you give up” and that he is “doubling down.” The statement we pulled directly from his own account lands at a moment when privacy has become a formal engineering priority across the network, with active work spanning wallets, transaction inclusion, private blockchain queries and shielded transfers. It is also not an isolated remark. Buterin has long insisted the chain must not compromise on four core properties — censorship resistance, open source, privacy and security — which he bundles under the acronym “CROPS.” In March he argued the Ethereum ecosystem should see itself as part of a family of “sanctuary technologies,” open-source infrastructure that lets people transact and communicate without government pressure, with privacy and individual autonomy as the pillars. On May 20 he sketched a path toward “native privacy” built on account abstraction, keyed nonces and access-layer work, while urging the Ethereum Foundation to concentrate resources on keeping the network censorship-resistant, private and secure. By August he was comparing the current development “Strawmap” against his 2023 roadmap and singling out one decisive change: first-class attention to strong privacy. The commitment also predates this week’s post. In a Bankless interview in August 2025 he described privacy as fundamental to the cypherpunk roots of Web3 — “Privacy is freedom,” he said — and argued that embedding privacy into existing wallets was a more realistic medium-term goal than shipping standalone privacy wallets.

FOCIL and the EIP Pipeline

The technical substance behind the rhetoric sits in Ethereum’s official privacy roadmap, last updated on August 24, 2026, which organizes the effort into three axes: private reads, private writes and private proving. Private reads aim to stop infrastructure providers from learning which address or smart contract a user is inspecting, cutting the metadata exposure — IP address, lookup target, access time — that wallets currently leak to RPC providers. Private writes address the moment a transaction is actually sent, reducing the risk that it is censored or traced while waiting in the mempool and during block construction. That is where FOCIL (EIP-7805) enters: the proposal, described in the EIP-7805 document itself, has validators assemble transaction-inclusion lists that a block proposer must honor, and a block that ignores those lists can be disapproved in fork choice, raising the cost of arbitrarily excluding privacy-protocol transactions. The design remains at draft stage, and no network upgrade has finalized its inclusion. Alongside it, developers are reviewing EIP-8141 on frame transactions, EIP-8250 on keyed nonces and EIP-8182 on private ETH and ERC-20 transfers — proposals meant to make transaction formats and gas fee handling more flexible, weaken cross-transaction linkability and implement a protocol-level shielded pool. None of the four has been scheduled into a hard fork, though the wider upgrade pipeline keeps moving, with the Glamsterdam Sepolia testnet fork locked for Oct 6 on the calendar. The work is significant for validator economics too, since inclusion-list enforcement shifts censorship costs onto honest consensus participants rather than leaving them with block builders.

Draft Status, No Vote Yet

Our reading: the post is signaling, but signaling that matches the paperwork. The authoritative record here is the proposal set itself — EIP-7805 is still labeled a draft, and no upgrade inclusion, mainnet date or recorded consensus decision exists for any of the four privacy EIPs. COINOTAG flags what is not disclosed: no ship timeline, no confirmed mainnet scope, and unresolved questions around zero-knowledge proof costs, wallet usability and anti-money-laundering compliance before privacy becomes a true network default.