All news is rigorously fact-checked and reviewed by leading blockchain experts and seasoned industry insiders.
- The Ethereum Foundation has officially announced the beginning of Ethereum’s transition to full zero-knowledge proof integration.
- This means that Validators will verify proofs of state transitions instead of re-executing every transaction, and Ethereum L1 becomes proof-centric.
In the recently published blog post by the Ethereum Foundation, the core development team outlined a phased strategy to bring zero-knowledge technology directly into Ethereum’s base layer. The foundation explained how they plan to achieve this in less than a year.
“The fastest and safest way to ship an L1 zkEVM is to start by giving validators the option to run clients that, rather than re-executing execution payloads, statelessly verify multiple (let’s say three) proofs generated by different zkVMs each proving different EVM implementations,” the blog explains.
Rather than fully replacing the current execution model, this approach introduces parallel zk verification alongside existing execution clients. Each Zero-Knowledge Virtual Machine (zkVM) would prove the correctness of a specific Ethereum implementation, and validators would verify all of them, increasing redundancy and resilience.
Because ZK proofs are small and fast to verify, the burden on validators remains minimal, even when checking multiple proofs per block. This mirrors the Ethereum client diversity philosophy, applied now to zkVMs.
To accommodate this plan, Ethereum’s protocol requires relatively modest changes. The primary ask is pipelining in the upcoming Glamsterdam upgrade that is expected in 2026, which would give zkVMs more time to generate proofs off-chain, enable validators to proceed with other tasks while waiting for proof completion, and avoid execution delays while improving security.
What are the advantages of this?
The team stated,
Our greatest advantage in executing this plan is the ability to harness the entire zkVM industry towards making Ethereum by far the largest ZK application in the world. Many zkVMs are already proving Ethereum blocks, and performance breakthroughs are being announced on a weekly basis.
Ethereum has a powerful head start in its transition to a zero-knowledge future, thanks to a vibrant and competitive zkVM ecosystem already generating valid execution proofs for mainnet blocks. Projects like Scroll, zkSync, Polygon zkEVM, and others are consistently pushing the boundaries of what’s possible, delivering faster proving times, smaller proof sizes, and more efficient hardware usage.
To harness this and guide the ecosystem toward a unified vision, the Ethereum Foundation is encouraging zkVM teams to align on a shared set of technical goals for real-time L1 proving. These standards are designed to preserve Ethereum’s core principles, security, decentralization, and censorship resistance, while making proof verification fast and scalable.
The long-term target is 128-bit cryptographic security, though a temporary minimum of 100 bits is acceptable during early deployment to accommodate engineering limitations. Proofs must be under 300 KiB in size, avoiding any reliance on trusted setups or recursive schemes that depend on them.
And when it comes to performance, the bar is clear: zkVMs should aim to prove 99% of Ethereum blocks within 10 seconds, factoring in the 12-second block slot and the time needed for network propagation.
Edge cases, such as rare slow proofs or denial-of-service attempts, will be addressed through future protocol upgrades. By rallying the zkVM ecosystem around these clear technical targets, Ethereum is laying the groundwork for a base layer secured not by trust in computation, but by fast, verifiable cryptographic proofs.
This update follows a recent report from Crypto News Flash, highlighting a new proposal by Ethereum co-founder Vitalik Buterin and researcher Toni Wahrstätter from the Ethereum Foundation’s Applied Research Group.
Together, they introduced Ethereum Improvement Proposal (EIP) 7983, which suggests placing a hard cap on how much gas a single transaction can use. The proposed limit, 16,777,216 gas units, or 2²⁴, is designed to prevent individual transactions from monopolizing block space and improve network efficiency.
