Ethereum's roadmap is entering a critical transition phase where zero-knowledge proofs move from Layer 2 scaling solutions back to the mainnet itself. ConsenSys CEO and Ethereum co-founder Joe Lubin recently outlined a 3-to-5-year timeline for Ethereum to become a fully zero-knowledge proof-based protocol, anchoring this prediction to the Lean Ethereum proposal from Ethereum Foundation researcher Justin Drake. This shift would enable the network to process over 10,000 transactions per second on mainnet through native ZK verification at Layer 1, directly addressing the throughput pressure that has plagued Ethereum's base layer.

What Are Zero-Knowledge Proofs and Why Does Ethereum Need Them?

Zero-knowledge proofs, or ZK proofs, are cryptographic tools that allow one party to prove a statement is true without revealing any underlying details. In blockchain terms, a ZK proof (specifically a zk-SNARK, or zero-knowledge Succinct Non-Interactive Argument of Knowledge) can verify that a batch of transactions is valid without exposing the transaction data itself. This technology enables Layer 2 networks like Scroll and Linea to bundle transactions off-chain, submit a single proof to Ethereum for verification, and dramatically reduce fees and confirmation times.

The reason Ethereum needs this technology is straightforward: the network currently processes roughly 15 transactions per second on mainnet, creating congestion and high gas fees. Layer 2 solutions have grown to handle much of the transaction volume, but they introduce fragmentation. Assets and liquidity are scattered across different chains, requiring bridges to move value between them. Lubin's vision collapses this fragmentation by bringing ZK verification directly to Layer 1, creating what he calls "synchronous composability" where assets move atomically without bridges.

How Does Ethereum's ZK Convergence Strategy Work?

Lubin frames Ethereum's evolution in two phases: divergence and convergence. During the divergence phase, which began around 2020-2021, the network deliberately pushed execution off-chain to Layer 2 networks, allowing zero-knowledge proving technology to mature in production environments before being reintegrated at Layer 1. This strategy gave ZK technology time to develop, be audited, and prove itself in real-world conditions. Now, the convergence phase is beginning, in which ZK proving already running on Layer 2s migrates upward to mainnet, ultimately creating a single atomic execution context.

The Lean Ethereum proposal operationalizes this convergence target with specific technical goals:

• Throughput Target: 10,000+ transactions per second on mainnet, representing an order-of-magnitude improvement over current capacity and a direct competitive response to other Layer 1 architectures like Solana's Alpenglow upgrade
• Validator Rollout: An opt-in validator phase in 2026 followed by a mandatory transition by 2027, though this timeline has not been independently confirmed by the Ethereum Foundation
• Client Implementation: The Ethereum Foundation has published plans for an optional Layer 1 zkEVM (zero-knowledge Ethereum Virtual Machine) client as a first step toward full-stack ZK integration

What Challenges Could Delay Ethereum's ZK Transition?

While Lubin's vision is ambitious, significant technical hurdles remain. Making zkEVM verification mandatory at the consensus layer requires extensive auditing, formal verification, and client diversity work. Some protocol developers assess these timelines as longer than Lubin's 3-to-5-year window implies, creating uncertainty about whether the convergence phase can proceed on schedule.

Additionally, Vitalik Buterin, Ethereum's creator, has publicly pulled back from characterizing rollups as a permanent architectural destination. Earlier in 2026, Buterin stated that most Layer 2s had become "branded shards" rather than genuinely differentiated execution environments, suggesting skepticism about whether the current rollup ecosystem represents the network's long-term direction.

How Are Layer 2 Networks Already Using Zero-Knowledge Proofs?

Several Ethereum Layer 2 networks are already running ZK proofs in production, providing a testing ground for the convergence strategy. Scroll, for example, is a zk-rollup that batches transactions off-chain and submits a single cryptographic proof to Ethereum for verification. As a zkEVM, Scroll maintains full compatibility with the Ethereum Virtual Machine, allowing developers to deploy existing smart contracts and tools with minimal changes. The SCR token enables decentralized governance through the Scroll DAO, with token holders able to propose and vote on protocol upgrades and treasury management.

ConsenSys's own Linea network is also running ZK proofs in production, including experiments in synchronous composability that Lubin has previously described as "the holy grail of our ecosystem." Gnosis's Ethereum Economic Zone pursues similar integration, creating a shared execution context between Layer 1 and Layer 2 with tighter composability and shared security.

What Does Ethereum Foundation Restructuring Mean for ZK Development?

Lubin indicated that the Ethereum Foundation itself is undergoing significant restructuring to support the ZK transition. Rather than maintaining a single foundation, at least three groups will spin out of the Ethereum Foundation, each focused on discrete mandates: core protocol development, usability and scalability, and institutional outreach. The EF itself will narrow to what Lubin called its "CROPs" components. Lubin stated categorically: "There won't be a second foundation." This organizational segmentation is positioned not as instability but as preparation for the coordination demands of a ZK-heavy protocol transition.

Lubin

The analytical question now is not whether Ethereum will eventually integrate ZK proofs, but whether Lubin's reframing of the rollup era as a deliberate strategic phase reflects a coherent long-run plan or a retroactive narrative applied to a roadmap that drifted further than intended. The next 12 to 18 months will be critical in determining whether the technical and organizational groundwork can support the convergence timeline Lubin has outlined.