Vitalik Buterin shared three short-term technical initiatives for Ethereum native privacy. The work covers account abstraction with FOCIL, keyed nonces, and access-layer projects. EIP-8250 formalizes the keyed nonces design with support for 500 billion privacy records. Vitalik Buterin shared three short-term technical initiatives aimed at pushing Ethereum toward stronger native privacy in a post on X. The Ethereum co-founder called the work a set of live engineering tracks already underway across the protocol, rather than a fresh roadmap or future research agenda. The post followed a comment from analyst Millie, who argued that native privacy is the missing component that could give the asset true moneyness qualities and drive higher Layer 1 transaction fees. The three areas Buterin pointed to are account abstraction paired with FOCIL, the keyed nonces proposal under EIP-8250, and a set of access layer projects, including Kohaku and private read capabilities. The post sits alongside the privacy roadmap Buterin published in April 2025 and the four-track quantum resistance plan announced by the Ethereum Foundation earlier this year. AA Plus FOCIL Targets Censorship of Private Transactions on Ethereum The first item in Buterin’s short list pairs account abstraction with FOCIL, the Fork-Choice Enforced Inclusion Lists framework. The combination targets the censorship and relay problems that have weighed on Ethereum privacy tools for the past several years. Account abstraction allows wallets and protocols to verify signatures natively at the protocol level. The change removes a long-standing dependency on external relayers for privacy protocols such as Privacy Pools and Railgun. Both have so far required third-party relayers to broadcast user transactions on-chain, with the relay model adding cost, a single point of failure, and a separate trust assumption that users have to accept on top of the underlying cryptography. FOCIL works on the censorship side of the problem. The mechanism gives validators a way to force the inclusion of transactions that block builders might otherwise leave out. The Buterin post framed the pair as a way to make privacy-focused transactions first-class on Ethereum, with strong inclusion guarantees that protect users against block-level filtering by builders or by infrastructure providers. Together, the two changes target the cost side and the censorship side of the privacy stack at the same time. Privacy tools become cheaper to operate without external relayers, and the transactions they produce become harder to block once submitted to the network. Keyed Nonces and EIP-8250 Tackle Replay and Linkability The second item on Buterin’s list is the keyed nonces proposal, now formalized under EIP-8250. The change replaces Ethereum’s single sender nonce with a two-part system that gives frame transactions independent replay domains. The single-nonce model has been a long-standing source of transaction linkability. Observers can connect transactions that originate from the same account but belong to different application contexts, since the nonce is a sequential counter tied to the sender address. The EIP-8250 specification targets support for up to 500 billion privacy-related records across an eight-year horizon. The records are stored as nullifiers, with the design taking advantage of the simple structure of the data to use sharding and bloom filters to keep storage costs bounded. Buterin argued in his post that storing 500 billion nullifiers is actually easier on the network than storing the equivalent volume of regular state data, with the simple structure of nullifier records the main reason for the difference. The proposal addresses one of the practical bottlenecks for scaling privacy on Ethereum. Existing privacy protocols have run into limits on the number of records the network can maintain without compromising decentralization. The keyed nonces design extends the headroom for these records by several orders of magnitude. Access-Layer Work Tackles Metadata Leakage on Ethereum The third area in Buterin’s short list covers access-layer work, with Kohaku named as the main project alongside private read capabilities. The access layer covers everything that happens when a wallet, decentralized application, or RPC provider queries the chain for data. The metadata problem at this layer has been a long-running concern for Ethereum privacy researchers. Even when on-chain transactions are private, the queries a wallet sends to its RPC provider can reveal a large amount of information about the user. A provider can see which addresses a wallet checks, which token balances a user looks up, and which decentralized application a user is interacting with. The leakage runs alongside the on-chain layer and undermines the privacy gains from protocol-level changes. Kohaku targets this category of leakage directly. The project sits alongside private read efforts that aim to let users query the chain without revealing the specifics of what they are reading. The Ethereum Foundation has flagged this layer of work as one of the four tracks within the broader privacy roadmap, alongside changes at the wallet, protocol, and cryptographic layers. The April 2025 nine-step roadmap from Buterin includes related changes. These include migrating wallets to a one-address-per-application model and replacing trusted execution environments with cryptographic private information retrieval for RPC calls. The access-layer track sits within this wider plan and provides the near-term entry points for users. Privacy and Quantum Resistance Tracks Run in Parallel The privacy work runs alongside the quantum resistance efforts the Ethereum Foundation announced earlier this year. The Foundation has split the quantum resistance work across four tracks: consensus signatures, data availability commitments, account signatures, and application-layer zero-knowledge proofs. The two roadmaps overlap at several points. Account abstraction is a central building block for both, with the same protocol-level changes that allow privacy protocols to verify signatures natively also allowing individual accounts to adopt quantum-safe signature schemes. EIP-8141 is one of the proposals in the queue for the Hegotá hard fork in the second half of 2026. The EIP would let individual accounts adopt quantum-safe signature schemes without requiring a network-wide change. The split between privacy and quantum resistance has been a feature of Ethereum protocol planning for several years. The Foundation has argued that the two tracks need to advance at the same pace to keep the network ahead of both surveillance threats and the longer-term risk of quantum computers breaking current cryptographic assumptions. Millie’s response to Buterin’s post added another framing for the privacy work. The analyst argued that adding native privacy at the Layer 1 level would lift Ethereum’s utility value and drive higher mainnet transaction fees, with privacy treated as a core moneyness property for the asset. The case rests on the idea that payments and decentralized finance applications become more usable for regular users when the underlying network supports private transactions by default. The Buterin post does not commit to specific timelines for each of the three short-term items. AA plus FOCIL, keyed nonces, and access-layer work are all live engineering tracks across the Ethereum protocol developer community, with the Hegotá hard fork providing the next major coordination point for protocol-level changes.
