Ethereum Prague Fork Priorities and Execution-Layer Roadmap
Summary
The document presents the Reth team’s evolving view of Ethereum execution-layer priorities after Cancun. It favors staking-related changes and isolated EVM upgrades, particularly proposals for contract-controlled validator actions, deposit handling, BLS12-381 precompiles, and a scoped EVM Object Format. The proposed format adds structure and validation to bytecode, with potential gains in analysis, execution, and tooling, while legacy contracts would still need support.
The authors also consider increasing blob capacity, but call for impact analysis on transaction pools and propagation. They defer Verkle tries to a later fork, citing migration and ecosystem preparation needs, and do not recommend raising the L1 gas limit without stronger evidence. For account abstraction, they want comparative testing of user experience and developer tooling before choosing among proposals. This is a client-team roadmap rather than a settled Ethereum-wide plan; its timelines and priorities are explicitly provisional, and several decisions depend on further testing and coordination with consensus-layer teams.
Key ideas
- The Reth team favors execution-layer changes that can be implemented and tested in isolation.
- A scoped EVM Object Format could improve bytecode validation, analysis, and support for tooling while legacy bytecode remains relevant.
- Increasing blob capacity may help scaling, but its effects on transaction pools and network propagation require study.
- The authors recommend postponing Verkle tries until client teams and ecosystem tooling are better prepared.
- Gas-limit and account-abstraction decisions should follow more evidence and comparative testing.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.