Buterin Argues for an Extremely Lean Ethereum Base Layer

Vitalik Buterin published a post titled "The Extremely Lean Chain" on the ethresear.ch forum on July 6, setting out how Ethereum's consensus layer could be stripped down to almost no permanent state. The post is an update to the Lean Ethereum strawmap he first published in February 2026, and it proposes two phases: replacing the per-epoch accounting of every validator's balance with a single daily proof submitted by each validator, and then rotating validator keys daily so the network's participant list becomes anonymous. Buterin's claim is that the result would be a near-stateless beacon chain able to "scale to millions of validators," clearing the path to single-slot finality and post-quantum cryptography. He put the timeline at three to four years. The direction drew broad agreement from other researchers within hours; the timeline did not.

Validator State: What the Chain Currently Has to Remember

Validator state is the record every Ethereum node keeps of who is staking and how much: each validator's balance and status, plus the bookkeeping that adjusts those balances as rewards and penalties accrue. That accounting currently runs every epoch, so the chain rewrites a large table of numbers on a fixed cycle whether or not much has changed. The cost scales with the number of validators rather than with the work they do, which is one reason the consensus layer is hard to grow. Shrinking it is the object of the proposal.

The first phase replaces that per-epoch update with one daily ZK-STARK proof from each validator. A ZK-STARK is a cryptographic proof that lets one party demonstrate a computation was performed correctly without the verifier redoing it, and without revealing the inputs; here, each validator would prove its own day's worth of duties and rewards and hand the chain the result. The chain would then need to store roughly 6 bytes per validator — a pointer to a proven position rather than a full balance record. At that size the validator set stops being a scaling constraint, which is what makes millions of validators arithmetically conceivable rather than just desirable.

The Second Phase: Daily Key Rotation and Unlinkable Identities

The second phase applies daily rotation to validator keys, producing what Buterin described as "a daily rotating, unlinkable list" of anonymous validator identities. Today a validator's public key is a stable identifier that can be watched across time and, in some cases, tied to an operator or an IP address, which is a censorship and targeting surface as much as a privacy one. Rotating keys each day breaks the link between one day's participation and the next. Buterin frames Hegotá, an upgrade still being assembled, as likely the last fork that is thematically "pre-Lean" — the work after it would be aimed at this architecture rather than at extending the current one.

The Response: Agreement on Direction, Objection to Pace

The pushback that followed was about speed rather than substance. Eli Ben-Sasson of StarkWare said "'3-4 years' as the timeline is way too long." Dankrad Feist, a former Ethereum Foundation researcher, called the vision "really cool" but said "3-4 years is very slow," arguing the work could be done in roughly a year. Barnabé Monnot of the Ethereum Foundation took a different tack and published a diff showing what had changed between the February strawmap and this version, the sort of artifact that makes a research proposal reviewable. Nobody prominent argued the chain should keep its current validator accounting.

What Is Unresolved: A Post, Not a Specification

What was published is a research post, not an EIP or a client specification, and neither phase has a proving system, a testnet or an implementation attached. The timing also puts it against an unusual organizational backdrop: the essay arrived days after ecosystem work moved outside the Foundation into a separate nonprofit, itself a consequence of the Foundation narrowing its focus in late June. Long-horizon protocol research is one of the functions the Foundation kept, and a three-to-four-year roadmap is a claim on those resources. The gap between Buterin's timeline and the one-year alternative Feist proposed is the concrete thing to watch, because it determines whether Hegotá is followed by incremental forks or by the first Lean one.