Ethereum's Beacon Chain would store roughly 6 bytes per validator instead of 121 under a new design that shifts balance accounting off-chain using zero-knowledge proofs.
Ethereum's Beacon Chain would store roughly 6 bytes per validator instead of 121 under a new design that shifts balance accounting off-chain using zero-knowledge proofs.

Ethereum's Beacon Chain would store roughly 6 bytes per validator instead of 121 under a new design that shifts balance accounting off-chain using zero-knowledge proofs.
Ethereum co-founder Vitalik Buterin published a proposal July 6 to shrink the Beacon Chain's validator state by 95%, replacing on-chain accounting with daily STARK proofs.
"The goal is to reduce the amount of state the Beacon Chain needs to maintain, replacing much of today's on-chain accounting with zero-knowledge proofs," Buterin wrote in a research post titled "The Extremely Lean Chain."
The Beacon Chain currently stores public keys, withdrawal credentials, balances, slashing status and epoch counters for each validator — roughly 121 bytes per participant. Buterin's Phase 1 design cuts that to two fields: effective balance and a public key index. Validators would generate a daily STARK proof covering approximately 5,400 Merkle branches, a workload Buterin said modern laptops can complete within an hour.
The proposal is part of Ethereum's broader "Lean" roadmap, which Buterin described as the network's third major iteration after the Merge. If implemented across 6 to 7 forks through 2029, the design could allow Ethereum to support millions of validators while introducing daily validator identity rotation — making it harder to link deposits, staking activity and withdrawals.
Phase 2 introduces rotating validator identities generated through zero-knowledge proofs. Instead of using the same key indefinitely, validators would register a fresh public key each day, appearing as new participants while privately proving continuity through a chain of ZK proofs. The protocol would hide withdrawal addresses at deposit time using cryptographic commitments, revealing them only at withdrawal. The design also enables Single Secret Leader Election, preventing block proposers from being publicly identifiable before producing a block.
The "Extremely Lean Chain" is one of several proposals landing as part of Ethereum's updated strawman roadmap. EF researcher Toni Wahrstätter separately proposed native UTXOs on Ethereum, which could reduce permanent state for payment flows by 99.8% by borrowing Bitcoin's unspent transaction output model. Buterin has framed these changes as part of a multi-year transition where verification through recursive STARKs replaces re-execution. Missing a daily balance proof would not trigger slashing — validators would simply need to submit the required proof before attesting again.
This article is for informational purposes only and does not constitute investment advice.