Intelligence Brief
Ethereum’s latest working roadmap gives greater weight to protocol privacy, defence against quantum computing and execution beyond the Ethereum Virtual Machine. Vitalik Buterin identified those areas while comparing the current Ethereum Foundation Strawmap with the network’s 2023 roadmap.
The draft also includes native rollups, markets for future blob capacity and gas, and broader use of formal verification. Buterin argued that modern AI tools could make verification of a much larger portion of the protocol feasible. That is a development method, not a plan to delegate protocol control to an AI system.
The Strawmap is maintained by Ethereum Foundation Architecture as a work in progress. It organises research and engineering priorities but does not guarantee deployment dates. Ethereum’s separate post-quantum programme targets core infrastructure around 2029, while full migration would extend beyond that.
I updated my 2023 roadmap diagram to overlay where the items that were there sit in the current Strawmap ( https://t.co/9deLIQWG24 ).
In general, a lot of overlap, but:
* Some things got reshuffled in order (eg. quantum safety up-prioritized)
* Some things deprioritized (eg.… pic.twitter.com/XLdIt4kAgT— vitalik.eth (@VitalikButerin) August 10, 2026
Strategic Assessment
Quantum resistance matters because Ethereum still relies on cryptographic systems that a sufficiently capable quantum computer could eventually break. No current machine can execute that attack at the required scale. The risk is migration time: wallets, validators and applications may need years to adopt replacement signatures and proof systems.
Protocol-level privacy could reduce dependence on optional application layers, but it creates design and policy trade-offs. More private transfers protect users while making compliance and abuse monitoring harder. Native rollups may improve verification, yet deeper base-layer support also increases the cost of specification errors.
Developers and security researchers benefit from clearer priorities. Users benefit only when the work becomes stable software. A roadmap can coordinate research; it cannot substitute for audited implementations, client diversity or staged testing.
