L1-zkEVM First Official Call: L1-zkEVM Breakout #001 Key Summary Article X On February 11th, the first official breakout call was held to introduce ZK proofs to Ethereum L1. This marks the beginning of a roadmap to transition from re-execution to ZK Proof verification. Five Key Takeaways from the Call 1. Seven Dedicated Teams Completed We are entering the engineering phase, not research, in the areas of Execution Witness, consensus unification, zkVM standardization, proof infrastructure, benchmarking, and security verification. Each area has a dedicated lead. 2. Block Verification Time Under 16 Seconds With ZK verification of one Ethereum block under 16 seconds, we are nearing the mainnet level, achieving an "Alpha stage" evaluation. The remaining task is to verify security, not performance. 3. Confirmation of PeerDAS Synergy When combined with PeerDAS, introduced in Fusaka, synergies are achieved: maximizing block verification efficiency, reducing the hardware burden on validators, and strengthening decentralization. 4. Potential Requirement of 12 GPUs There is discussion that 12 GPUs may be required for new challenge proof verification. This could conflict with the goal of lowering the entry barrier for validators, and hardware optimization has emerged as a key challenge. 5. Setting a 128-bit Security Target The goal is to ensure provable security under current-generation cryptographic assumptions. Formal verification and cryptographic research will be conducted in parallel. Implications • Validator: In the long term, block verification will be possible without a full EL client. This could fundamentally change the node operation structure. • Infrastructure: Proof generation (Prover) infrastructure is emerging as a new layer. A Prover market, such as zkboost and pandaOps, is forming. • L2: If L1 itself performs ZK verification, the role and economic model of L2 rollups could be redefined. This is also expected to have a direct impact on L2's DA cost structure. Timeline: BAL (Parallel Execution) and ePBS will be implemented in Glamsterdam (second half of 2026), followed by L1-zkEVM implementation after 2027.