Ethereum Strawmap Shifts: Privacy, Quantum Defense, and Native Rollups Reshape L1 Priorities

Woofun AI reports that Vitalik Buterin, co-founder of Ethereum, released a comparative analysis on August 10, contrasting the 2023 technical roadmap with the current Strawmap. This update, documented by ChandlerZ of Foresight News, reveals a fundamental restructuring of Ethereum's development priorities. While significant overlap remains between the two timelines, the new framework elevates quantum security and strong privacy protection to top-tier status, while deprioritizing Verifiable Delay Functions (VDF) and various EVM improvements. Several legacy solutions have been entirely replaced by superior alternatives, signaling a decisive shift in the protocol's architectural direction.

The structural evolution of the roadmap is characterized by the replacement of outdated mechanisms with more efficient designs. The Verkle Tree, once a central state management proposal, was first superseded by unified binary trees and subsequently replaced by Partitioned Binary Trees (PBT). Similarly, state expiration mechanisms have been abandoned in favor of new state types. The current Strawmap introduces several entirely new directions not present in the 2023 version. Strong privacy protection is now listed as a primary objective, alongside aggressive scaling efforts tailored to post-quantum threats. Protocol specifications are being simplified to facilitate formal verification, a process Vitalik Buterin argues is now feasible due to the advent of AI.

Additionally, the roadmap incorporates block and gas futures, native Rollups, and increased design flexibility for the future of the EVM, potentially including non-EVM instruction set architectures.

Three specific proposals aim to enhance the capabilities of private transactions, marking the most significant change in the roadmap. Strong privacy protection, previously absent from the 2023 plan, is now elevated to the protocol level. Vitalik Buterin identified keyed nonces, recent roots, streamlined privacy pools, and wormholes as critical components to address concurrency, proof verification, shared anonymity sets, and fund linkage. EIP-8250, submitted in April, allows a single shared sending address to utilize multiple independent nonces. This mechanism prevents pending transactions from one user from blocking others within the same privacy protocol, thereby improving concurrency. EIP-8272, submitted in May, enables private expenditure proofs to reference recent commitment tree roots. This innovation eliminates the need to read continuously changing application states during verification, streamlining the proof process.

Further privacy enhancements are proposed through EIP-8182, which aims to establish an in-protocol privacy pool for ETH and ERC-20 tokens. This proposal utilizes system contracts, shared masking pools, and a separate proof architecture to consolidate multiple assets into a single in-protocol anonymity set. Currently, various privacy applications maintain fragmented funds pools, resulting in small anonymity sets due to dispersed users and liquidity. EIP-8182 seeks to reduce the need to re-separate users during upgrades by introducing new verification methods through an extensible approval mechanism.

All three proposals—EIP-8250, EIP-8272, and EIP-8182—are currently in the Draft stage, with EIP-8182 also under Review. None have a fixed activation hard fork date yet. Wormholes, corresponding to the zero-knowledge destruction proof of EIP-7503, allow users to transfer ETH to a cryptographically unspendable address and then use zero-knowledge proofs to recreate an equivalent amount. This makes it difficult for public chains to link the original transaction to the new address.

However, this proposal is stuck in the Stagnant stage, with standards and reference implementations needing refinement, alongside risks of implementation errors and double-spending.

Quantum migration affects four distinct areas of cryptography, prompting a rise in the priority of quantum security. Vitalik Buterin has proposed continuing scaling efforts under post-quantum conditions to mitigate future threats. The affected cryptographic areas include ECDSA signatures used by regular accounts, BLS signatures used by validators, KZG commitments used for Blob data availability, and zero-knowledge proof systems adopted by some Rollups and privacy applications.

Although current quantum computers are not powerful enough to break these methods, replacing keys for accounts and validators across the global network will require years of preparation. The latest roadmap includes directions such as leanSPHINCS signature aggregation and zkzk frames. Recursive STARK is intended for use across the execution layer, consensus layer, and data layer. STARK relies primarily on hash functions, allowing it to circumvent some quantum risks associated with elliptic curve cryptography and compressing complex computations into easier-to-verify proofs.

The Ethereum Foundation has established a dedicated post-quantum team to manage this transition. An estimated timeline suggests that L1 protocol upgrades might be completed by 2029, while full execution layer migration could take several more years, with no fixed completion date. STARK is also linked to protocol simplification and formal verification. Vitalik Buterin's concept of the Extremely Lean Chain, proposed in July, aims to reduce the state size per validator to 6 bytes in the first phase, further down to 1 byte in the second phase. This reduction would enable validators to update balances and rotate public keys using zero-knowledge proofs. Vitalik Buterin believes that modern AI tools make full protocol formal verification feasible. In this context, AI is used to write and verify mathematically sound proofs that can be checked by machines, without participating in block creation, voting, or consensus decisions.

Native Rollups allow L2s to reuse mainnet verification, although the timeline for implementation may still change. EIP-8079, submitted in November 2025, provides a draft for native Rollups. Ethereum introduces an EXECUTE precompiled function to expose mainnet state transition functions to the execution layer. This enables EVM-equivalent Rollups to reuse L1's verification infrastructure. Currently, Rollups need to maintain their own proof systems, bridge contracts, and upgrade mechanisms.

Nativization can reduce the need for custom verification code and pave the way for removing security committees. The proofs in EIP-8079, which include transaction handling, ZK verification, and certain security designs, are still marked as pending and not part of any confirmed mainnet upgrades. In March, the Ethereum Foundation provided further clarification on the division between L1 and L2. It stated that L2s aiming to inherit maximum mainnet security can adopt native Rollups, Stage 2, and synchronous composability.

Meanwhile, those offering privacy, application-specific efficiency, or other differentiated features will continue to exist. Native Rollups adjust the verification relationship between L2s and the mainnet but do not eliminate the multi-chain scaling structure.

State design is also evolving, with Vitalik Buterin noting that the Verkle Tree will first be replaced by unified binary trees, followed by partitioned binary trees (PBT). State expiration is giving way to new state types. EIP-8347, submitted in July, proposes an offline migration to PBT, but the activation hard fork and anchor block dates remain undetermined. Non-EVM instruction sets such as Blob and Gas futures, leanISA, and RISC-V are also under long-term discussion.

However, deeper EVM reforms are not yet mature enough to be included in the Strawmap.

Woofun AI data shows that the integration of these diverse technical tracks requires careful coordination to avoid fragmentation. The inclusion of non-EVM architectures suggests a broader vision for the protocol's future, where flexibility in instruction set design may become a key differentiator for specialized applications.

The Strawmap currently outlines seven potential upgrades up to 2029, scheduled at roughly half-year intervals. The Ethereum Foundation revealed in May that core developers believe specifying exact hard fork dates after 2026 is too definitive and may be less emphasized in the future. This uncertainty reflects the complexity of coordinating global network upgrades. The nearest nodes to watch are Glamsterdam in the fourth quarter of 2026 and Hegotá in 2027, where proposal scopes are still being determined. The shift towards a more flexible timeline allows for greater adaptability in response to emerging technological challenges and opportunities.

However, it also introduces ambiguity for developers and users who rely on predictable upgrade schedules.

Vitalik Buterin's updates highlight changes in Ethereum's technical priorities: privacy, post-quantum security, and formal verification are now integrated into the core protocol design. Native Rollups and new state types push scaling discussions toward verification mechanisms and state structures. Many of these proposals are still in the Draft, Review, or early research stages. Strawmap provides dependencies and long-term directions but should not be considered as guarantees of deployment. Whether related EIPs will make it into actual hard forks, whether post-quantum account and validator migration plans will develop into complete standards, and whether native Rollup designs for transaction-containing proofs and ZK verification will be finalized remain to be seen. This marks a period of significant experimentation and refinement for the Ethereum ecosystem.