Ethereum Moves Toward ZK Proofs for Core Block Validation

• Ethereum plans to let validators verify blocks using zero knowledge proofs instead of re-executing every transaction.

• EIP 8025 introduces optional execution proofs so attesters can validate blocks with constant cost and lighter hardware.

• The L1 zkEVM roadmap depends on ePBS and zkVM teams already proving Ethereum blocks ahead of a 2026 rollout.

Ethereum is preparing a major validation overhaul that could change how blocks are confirmed on the network. Ethereum Foundation member ladislaus.eth said the shift replaces transaction re-execution with zero-knowledge proof verification. The plan, outlined under the L1-zkEVM 2026 roadmap, targets validators, developers, and home stakers across Ethereum’s global network.

From Transaction Re-Execution to Proof Verification

Currently, every Ethereum validator re-executes all transactions in each block to confirm validity. However, according to ladislaus.eth, this approach scales poorly as on-chain activity grows. More gas usage increases storage, bandwidth, and hardware demands for every node.

Under the proposed design, validators would instead verify cryptographic proofs. These proofs confirm correct execution without re-running transactions. Notably, verification time remains constant regardless of block complexity.

This shift relies on zkEVM technology, now moving into Ethereum’s core protocol. Importantly, the change does not replace current methods. Instead, it adds an optional validation path for attesters.

EIP-8025 Introduces Optional Execution Proofs

The roadmap centers on EIP-8025, known as Optional Execution Proofs. The proposal allows validators, called zkAttesters, to confirm blocks by checking zero-knowledge proofs. They would no longer need to run a full execution client.

According to the design, execution layer clients generate execution witnesses. These witnesses feed into zkVMs, which produce proofs of correct state transitions. Consensus layer clients then verify those proofs.

Proofs from different execution clients would circulate through a dedicated gossip network. Attesters would accept blocks after verifying a threshold, currently proposed as three of five proofs. This structure preserves client diversity while reducing validation costs.

Roadmap Timeline and Infrastructure Dependencies

The Ethereum Foundation has scheduled the first L1-zkEVM workshop for February 11, 2026, at 15:00 UTC. The session will cover six research tracks, including prover infrastructure and security verification.

Notably, the roadmap depends on enshrined proposer-builder separation, or ePBS. ePBS, targeted for the Glamsterdam hardfork, extends proof generation time windows. This change enables real-time proving within a single slot.

As development progresses, zkVM teams such as RISC Zero, ZisK, and openVM already prove Ethereum blocks. Meanwhile, EIP-8025 now sits in the consensus-specs features branch, pending further review.