#VitalikUnveilsLeanEthereum Vitalik Buterin introduced Lean Ethereum during the All Core Developers research call on September 3, 2026 and the proposal now defines the technical agenda for client teams, protocol researchers, and application builders across the ecosystem. The document sets a clear direction toward reduced complexity, lower maintenance cost, and a base layer focused on a small group of strong guarantees. The timing matches the completion of the Verge upgrade in Q2 2026 and the arrival of broader client diversity that makes major refactors realistic. Lean Ethereum addresses concerns that accumulated features increase consensus risk and raise barriers for new teams that want to build clients or audit the specification.

The foundation of Lean Ethereum rests on three principles. First, limit the number of consensus critical functions that every client must implement. Second, shift specialized functionality to rollups or to the application layer. Third, strengthen the base layer around data availability, settlement, and a minimal execution environment that supports validity proofs. The objective is a protocol that remains simple to verify, simple to implement, and simple to reason about. The approach accepts that the base layer should avoid attempting every use case. Trying to cover all requirements creates fragility. Choosing a narrow scope lets the network deliver stronger guarantees where decentralization and neutrality matter most.

State management receives the largest change under Lean Ethereum. The plan establishes stateless execution as the default for clients. Block producers attach witnesses that allow validators to execute a block without storing the complete state trie. Execution clients retain only the state needed for the applications they support. The base layer continues to guarantee data availability and to enforce correct state transitions through succinct proofs. Verkle trees, activated with the Verge upgrade, provide the cryptographic structure for witnesses. Standardized witness formats let light clients and rollups interoperate without custom adapters. Performance data shared on the call showed that a stateless client can verify mainnet blocks in under 175 milliseconds on a laptop with four cores. That speed reduces hardware requirements and helps home staking remain viable. Lower state storage also decreases bandwidth and disk input output, which supports nodes operating in constrained environments.

The Ethereum Virtual Machine roadmap changes as well. Lean Ethereum proposes freezing the legacy EVM at a defined feature set after the next network upgrade and introducing a minimal VM optimized for zero knowledge proofs. The legacy EVM will continue to support existing contracts, tooling, and developer workflows. The new VM uses a compact instruction set that maps directly to arithmetic circuits. The separation allows innovation to continue at the application layer while keeping consensus logic stable. Client teams would maintain the legacy EVM for backward compatibility, yet consensus changes to that VM would stop after a defined sunset date. The Solidity and Vyper teams expressed support because a stable target reduces testing cost and simplifies long term maintenance. Application developers can select the legacy EVM for compatibility or the new VM for performance inside validity rollups.

Data availability remains a core responsibility of the base layer. Lean Ethereum confirms the commitment to proto danksharding and full danksharding. The bandwidth target for blobs rises to 32 megabytes per slot by late 2027 and to 128 megabytes per slot once data availability sampling reaches production readiness. The increase supports thousands of rollups and permits large data submissions without congesting execution. The proposal defines a service level objective for data availability. The network must ensure that 99.95 percent of blobs remain retrievable by any node within two slots. To meet that objective, the protocol adds distributed blob repair. Nodes reconstruct missing chunks using erasure coding and a gossip protocol. Testing on the Holesky testnet achieved repair success above 99.99 percent under simulated network partitions and targeted node outages. The repair mechanism operates alongside the existing peer to peer layer and uses bandwidth efficiently by prioritizing missing indices.

Validator economics become simpler under Lean Ethereum. The proposal replaces the current variable reward curve with a fixed base reward per validator and a straightforward penalty for offline time. The change removes parameters that link issuance to total stake, participation rate, and other dynamic factors. The new model makes yield predictable for stakers and easier to model for custodians, funds, and regulatory reporting. Simulations presented by the research group indicate that issuance would remain between 0.24 percent and 0.56 percent of total supply per year, depending on the staking ratio. The range maintains security incentives while limiting dilution. The penalty for missed attestations stays proportional to downtime, which preserves liveness incentives. The simplification also reduces edge cases that audit teams must check during each upgrade cycle.

Client diversity stands as a primary objective. Lean Ethereum includes a specification for a minimal consensus client that can be written in under ten thousand lines of code. The minimal client verifies proofs, follows the fork choice rule, and participates in sync committees. The client omits peer discovery, RPC servers, metrics, and other non consensus features. The purpose is to give new teams a fast path to build alternative implementations and to provide a reference that auditors can review end to end. Nimbus and Grandine already produced prototypes that sync to the chain head on a standard laptop in under five minutes. The specification adds a common test harness that generates edge cases and consensus vectors. The harness lets teams discover bugs before code reaches public testnets.

Rollups receive clearer guarantees from the base layer. Ethereum commits to providing secure data availability and settlement. Execution and user experience migrate to layer two. Lean Ethereum introduces a standard for cross rollup communication that uses shared validity proofs and a common bridge interface. The standard allows assets and messages to move between rollups without trusted intermediaries and without long challenge periods. A working group with members from Arbitrum, Optimism, Base, Starknet, and Scroll will finalize the interface. Wallets can route transactions automatically and display a unified balance to the user. The standard uses recursive proofs so that a single proof can attest to state across many rollups. That method reduces verification cost on the base layer and keeps latency low for end users.

Security assumptions receive precise restatement. Lean Ethereum assumes an honest majority of stake for liveness and a synchronous network for performance, yet safety holds under asynchronous conditions because of the finality gadget. The proposal removes features that rely on complex economic games or that give advantages to large stakers. One example is the deprecation of in protocol MEV auctions. In place of auctions, the protocol supports a neutral encrypted mempool with threshold decryption at the block level. Flashbots and several university groups published simulations that show encrypted mempools reduce harmful MEV by more than seventy percent while preserving competitive block value. The change lowers the barrier for independent builders and reduces dependence on private order flow.

Governance and upgrade cadence become predictable. Lean Ethereum adopts a train model with one consensus upgrade per year in Q2 and one maintenance release for the execution layer in Q4. The schedule gives client teams time to plan and gives application developers a stable target. Each upgrade must include a deprecation plan for any feature being removed. The process requires a formal security review and a public testnet that runs for at least three months. The Ethereum Foundation committed funding for continuous fuzzing, for a bug bounty program that pays in ETH and stablecoins, and for grants that support alternative client teams. Bounty tiers increase for bugs that affect the minimal client, which aligns incentives with the goal of a lean base layer.

Community response arrived quickly after the call. Core developers welcomed the clarity and the reduction in scope. Application teams asked for assurance that the legacy EVM would remain usable for at least five years. The proposal sets a sunset date of 2032 with an option to extend based on usage metrics and ecosystem demand. Rollup teams supported the data availability commitments and the cross rollup standard because those changes lower costs and improve composability. Staking providers favored the simpler reward curve because it reduces accounting complexity and audit work. Some participants raised concerns about ossification and about moving too much functionality to layer two, which could affect users with limited access to rollups. The authors replied that the base layer would keep a minimal execution environment for emergency transactions and for use cases that require direct settlement without bridges.

Implementation steps are already in motion. The minimal client specification will be published in October 2026. A devnet that implements stateless execution and the new VM will launch in November 2026. The first external audit round begins in January 2027. The feature set for the first Lean Ethereum upgrade targets a freeze in mid 2027. Mainnet activation is planned for Q2 2028 if testing meets the defined criteria. The cross rollup communication standard aims for a version one release in December 2026, with reference code in the major software development kits shortly after. The Ethereum Foundation and several layer two teams allocated engineering resources to complete the work on schedule.

Lean Ethereum signals a shift from expansion to consolidation. The network demonstrated that it can upgrade without downtime and that it can support a large ecosystem of rollups and applications. The new direction focuses on making the core protocol robust, understandable, and durable. The changes trade flexibility at the base layer for simplicity and predictability. The strategy bets that a stable foundation enables more innovation at the edges and that developers will build advanced functionality where it belongs. The base layer will continue to provide censorship resistance, credible neutrality, and global settlement. Everything else can live on layer two, where experimentation is faster and failure carries less systemic risk.

The discussion will continue through the rest of 2026 and into 2027. The research community, client teams, and application developers now share a common reference point for design choices. Lean Ethereum does remove ambition from the roadmap. It channels ambition toward areas where decentralization and neutrality matter most and it trusts the broader ecosystem to deliver user experience, scalability, and domain specific features. The proposal acknowledges that the base layer must do a few things perfectly rather than many things adequately. By choosing a smaller scope and executing with discipline, Ethereum aims to remain the settlement layer for the internet of value for decades to come.