Vitalik Buterin releases the EIP-8250 proposal, aiming to support 500 billion private records

According to an X post by Ethereum co-founder Vitalik Buterin on May 6, the EIP-8250 proposal has been formally put forward. Its core mechanism is a “keyed nonce” system, aiming to enable large-scale parallel private transactions on Ethereum. According to the EIP-8250 proposal document, the system’s design goal is to support up to 500B (8B) privacy-related records within eight years.

EIP-8250 Core Mechanism: Keyed Nonce System

According to the EIP-8250 proposal document, current Ethereum transactions rely on a single sender nonce for replay-attack protection, but this structure limits the execution capacity of privacy systems and parallel transactions. The core change in EIP-8250 is to replace a single nonce with (nonce_key, nonce_seq), creating separate replay-protection domains for different types of transactions.

As described in the proposal, the keys derived from nullifiers can allow multiple privacy transactions to execute simultaneously without conflict; once a nullifier is used, it will be permanently marked as spent. Vitalik Buterin directly stated in the proposal: “Keyed nonces are not just about providing stronger protocol support for privacy solutions.”

Ethereum State Storage Challenges and Dedicated Nullifier Storage Architecture

According to the EIP-8250 proposal content, if Ethereum privacy transactions reach 2,000 transactions per second (2,000 TPS) within eight years, about 500B (500B) non-prunable nullifiers would need to be stored. The EIP-8250 proposal estimates that under the existing general state architecture, the storage requirement would reach dozens to hundreds of TB.

To solve this problem, the EIP-8250 proposal introduces dedicated nullifier storage, managing it separately from Ethereum’s existing general state. The reason is that nullifiers follow fixed and predictable rules, making them suitable for handling with a dedicated architecture.

Technical Specifications: Sharding, Bloom Filters, and a Dedicated Verification Layer

According to the EIP-8250 proposal document, dedicated nullifier storage will use the following three technologies:

Sharding: distribute stored data across different segments to reduce the storage burden on a single node

Bloom Filter: used for efficiently checking whether a nullifier has already been used, reducing the need for full state scanning

Dedicated verification layer: optimize verification based on the fixed rules for nullifiers, lowering verification computation costs

According to the proposal description, the design goal of combining the above technologies is to keep Ethereum node storage size manageable even as transaction volume increases significantly.

Common Questions

Who proposed the EIP-8250 proposal, and when was it published?

According to a public post on the X platform, EIP-8250 was formally proposed by Ethereum co-founder Vitalik Buterin on May 6, 2026.

How does the keyed nonce system work?

According to the EIP-8250 proposal document, keyed nonces replace a single nonce with (nonce_key, nonce_seq), establishing independent replay-protection domains for different transaction types. This allows multiple privacy transactions to execute at the same time without conflicts; once a nullifier is used, it is permanently marked as spent.

How does EIP-8250 solve Ethereum’s large-scale storage problem?

According to the EIP-8250 proposal content, the proposal introduces dedicated nullifier storage and uses sharding, Bloom Filter, and a dedicated verification layer to separate private transaction data from Ethereum’s general state, thereby controlling the storage size of nodes under high transaction volume.