Polygon zkEVM Mainnet Beta will cease operations on July 1, 2026, concluding one of the earlier production deployments of a zero-knowledge Ethereum Virtual Machine. The shutdown, communicated roughly twelve months in advance in June 2025, gives users and developers a defined window to migrate assets and applications.
What Is Being Retired
The zkEVM Mainnet Beta was Polygon's attempt to bring an EVM-equivalent chain secured by validity proofs into live production. As a Layer 2, it settled to Ethereum while using zero-knowledge proofs to attest to the correctness of its state transitions. With the beta reaching end of life, Polygon is consolidating its scaling efforts around a different architectural direction.
The AggLayer Pivot
Polygon has increasingly oriented its roadmap around the AggLayer, a coordination layer designed to unify liquidity and state across many connected chains rather than relying on a single monolithic rollup. In that framing, the standalone zkEVM beta becomes less central, and resources shift toward interoperability infrastructure that can bind multiple chains into a shared environment.
- zkEVM Mainnet Beta reaches end of life on July 1, 2026
- Shutdown was announced about a year ahead, in June 2025
- Strategic focus moves to the AggLayer interoperability architecture
What Users Need to Consider
Anyone holding assets or operating contracts on the zkEVM beta must plan an orderly exit before the deadline. That typically means bridging funds back to Ethereum or to an alternative chain, redeploying any dependent applications, and updating integrations that point at the retiring network. Teams that delay risk complications once support and infrastructure around the chain are withdrawn.
A Signal for the zkEVM Field
The retirement underscores how quickly the zero-knowledge scaling landscape is evolving. Multiple zkEVM implementations are reaching production maturity, and the performance gap between validity-proof chains and native EVM execution has narrowed. In that environment, projects are reassessing which architectures merit long-term investment, and consolidation is a natural outcome.
- Migration typically involves bridging assets and redeploying contracts
- Delayed action risks reduced tooling and support near the deadline
- The move reflects broader consolidation across zkEVM designs
Reading the Roadmap
For Polygon, sunsetting the beta is less a retreat from zero-knowledge technology than a reallocation. Validity proofs remain central to its longer-term vision, but delivered through an aggregated, multi-chain model rather than a single rollup. Ethereum's own roadmap has also moved toward integrating zkEVM proofs at the protocol level, which reshapes how third-party scaling projects position themselves.
The practical takeaway for developers is straightforward: treat the July 1 date as firm, complete migrations early, and evaluate whether the AggLayer-connected ecosystem or an alternative Layer 2 best fits their needs going forward. Early movers will have the widest choice of destination chains and the calmest bridging conditions, since congestion and support gaps tend to worsen as a deadline nears. Teams should also audit any external dependencies, such as oracles, indexers and wallet integrations, that assume the zkEVM beta remains live, and confirm those services support their chosen migration target before committing user funds.