Vitalik Buterin Updates Ethereum Roadmap with Seven Previously Unattainable Priorities

The reordering deprioritizes Verifiable Delay Functions and parts of the earlier EVM roadmap. For engineers auditing or building on Ethereum and its rollup ecosystem, this changes the verification assumptions, execution surfaces, and trust models they must reason about.

The New Priority Stack

Quantum safety sits at the top. Post-quantum signatures are no longer optional research. Cryptographic agility moves into the base protocol rather than being retrofitted after deployment.

Native rollups receive explicit mention as a redefined priority. The verification logic moves into the protocol itself. The trust assumptions baked into current smart contract-based rollup bridges become replaceable. This is a meaningful upgrade from the older rollup-centric language.

STARKs anchor the new architecture. Succinct proofs and a leaner protocol are designed in from the start, not bolted on later.

Simpler execution environments — leanISA and RISC-V — open a path to more deterministic runtime. These can run alongside or beneath the current EVM, giving developers a cleaner execution surface for security-critical code paths.

Blob and gas futures reshape data availability pricing. Rollup operators get predictable cost planning. AI-assisted formal verification appears in the plan, positioning verification as a tool to harden new protocol components before they ship.

What the Audit Looks Like

The dropped items matter. VDFs never closed the research-to-implementation gap. Keeping them on the list consumed researcher attention indefinitely without producing a deployable primitive. Removing them is a realist engineering decision, not a retreat from ambition.

Privacy has also moved up the queue. It is no longer treated as secondary to scalability. For institutional participants, this shift changes what default transaction behavior looks like across Ethereum and its rollup ecosystems.

New state types signal deeper structural change. Multiple hard forks are likely required before any of this ships. The mention of a leaner architecture suggests the runtime surface itself is being redesigned, not extended incrementally.

Timing remains uncertain. Roadmap updates from researchers do not map cleanly to client dev timelines. No specific EIP has been tied to these items yet. Community consensus on directional changes moves slowly.

What to Watch

• Post-quantum signature scheme selection and integration path
• Native rollup verification specification
• leanISA and RISC-V runtime coexistence with the EVM
• AI-assisted formal verification toolchain maturity
• Mapping of each new priority item to a concrete EIP

The broader crypto economy is contracting in parallel — even esports circuits are recalibrating around shifting sponsorship dynamics as crypto capital retreats. Ethereum's core researchers are choosing the opposite direction: deeper protocol commitment, not retrenchment.