The Ethereum ecosystem is gearing up for a groundbreaking shift in its verification process, aimed at eliminating the need to re-execute every transaction on the blockchain. This innovative approach hinges on the validation of zero-knowledge (ZK) proofs instead of manually reprocessing transactions, promising substantial changes to the network’s architecture.
New Verification Model and Roadmap
A draft proposal titled “Optional Execution Proofs” under EIP-8025 outlines the core logic and technical specifics of this transformation. Under the new model, validators will be able to verify compact proofs without rerunning blocks, thus moving the network toward proof verification instead of traditional transaction re-execution. This is actively being tested as part of Ethereum’s advancement.
The Ethereum Foundation’s ZK-based virtual machine (zkEVM) team’s 2026 roadmap focuses on setting execution witness and program standards, ensuring API compatibility, layer integration, proof infrastructure, measurement, and security. The overarching goal of these endeavors is to make verification costs accessible and practical for everyone involved.
Technical Challenges and Centralization Risk
A key element of the new design involves generating an “Execution Witness” to verify transactions. A standard program then utilizes this data to monitor state changes and create a zero-knowledge proof. Validators use these proofs to confirm the blocks. Another critical innovation is the Enshrined Proposer-Builder Separation (ePBS) update, aimed at extending the allocated time for block verification.
Nevertheless, the approach raises concerns about potential centralization, largely because the process requires high-performance hardware, such as multiple GPU cards. Recent analyses indicate that an average of 12 GPUs is necessary to verify an Ethereum block. The project’s security assumption rests on the verification of three independent proofs from diverse software clients.
Layer 1 Scalability and Impact on Layer 2
Ethereum’s updated roadmap emphasizes “statelessness,” allowing blocks to be verified without carrying their main weight. This development is expected to enable home validators to fully experience network participation and dramatically reduce synchronization times. Even with rising gas limits, the stabilized verification costs could facilitate more transactions.
Regarding Layer 2 solutions, if the base chain’s verification costs decrease and infrastructure is shared, Layer 2 projects might struggle to stand out focusing solely on scalability. Consequently, features like specialized virtual machines, ultra-low latency, and novel interaction models are anticipated to become differentiators.
Future Possibilities and Scenarios
Three potential paths loom in the medium and long term. First, the widespread adoption of proof verification could ease the participation of home users in the system. Second, the high hardware requirements for proof production may accelerate centralization, favoring large providers. Third, sharing Layer 1 proof verification infrastructure could push Layer 2 projects to explore new avenues for differentiation.
Achieving success in this process hinges on harmonizing technical standards, reducing hardware requirements, and stabilizing measurement criteria. Moreover, significant updates like ePBS and Glamsterdam might widen the verification window, enhancing the network’s comprehensive effectiveness.
This model, still in its draft phase, is unlikely to be fully implemented in the short term. Priorities include testing updates, maturing the approach, and transparently comprehending the workings of the new architecture.
