Polygon zkEVM halted after an Ethereum reorganization

Polygon zkEVM Mainnet Beta stopped sequencing new blocks on March 23, 2024, after an Ethereum layer-one reorganization exposed a failure in the rollup’s synchronization logic. Polygon’s event-day update said the problem was confined to zkEVM: Polygon PoS and chains built with Polygon’s development kit were not affected.

The interruption mattered beyond one beta network’s availability. Polygon zkEVM depended on a trusted sequencer to order layer-two transactions, an aggregator to assemble proofs and Ethereum to anchor the resulting batches. A routine change in Ethereum’s recent block history was enough to leave those components with inconsistent information, showing how a scaling network could inherit layer-one events while adding its own operational failure modes.

What Polygon knew on March 23

Polygon’s contemporaneous forum update traced the trigger to 19:39:35 Central European Time on March 22, when an Ethereum reorganization affected a transaction updating the Global Exit Root. That root summarizes information used by Polygon zkEVM’s bridge. The trusted synchronizer did not handle the reorganization correctly, so block production proceeded using an incorrect timestamp and Global Exit Root.

The same update said the aggregator later reached a state in which it could not prove batches because it could not construct the correct L1 information tree. At 10:02 Central European Time on March 23, engineers resynchronized a permissionless node, detected a different Global Exit Root and decided to rebuild the network state from data sequenced on Ethereum.

Those were Polygon’s own preliminary findings. The March 23 notice contained apparent date-label errors for two later timeline entries, so its sequence is more reliable than every printed timestamp. Polygon said engineers had identified bugs and were preparing a new executor version, but it did not declare a complete recovery in that first update.

Contemporaneous reporting from The Block independently observed a gap of more than ten hours between successfully sequenced blocks and reported Polygon’s attribution of the outage to a layer-one reorganization. That explorer observation measured the visible break in block sequencing; it was not a complete audit of user balances, failed transactions or bridge exposure.

Why a layer-one reorganization became a layer-two outage

An Ethereum reorganization replaces one recent chain tip with another valid history. Rollup software is expected to reconcile such changes before treating layer-one inputs as canonical. In this incident, Polygon’s synchronizer retained information associated with the displaced Ethereum block. The sequencer then used that stale input, while the proving pipeline could not reconcile the resulting layer-two state with Ethereum.

The distinction is important. Available evidence did not show Ethereum itself had stopped, nor did it establish an attack on Polygon zkEVM. The verified event was a software-handling failure triggered by a layer-one reorganization. On March 23, the immediate institutional question was whether a centrally operated sequencing and recovery path could restore consistent state without invalidating users’ expectations about confirmed activity.

The outage also illustrated the limits of the “mainnet beta” label. It warned users that the system was still maturing, but applications and bridges were nevertheless handling real transactions. A beta designation did not remove the need for precise incident reporting, transaction reconciliation and clear withdrawal status.

Later clarification

Polygon’s March 28 postmortem, which was not available on March 23, reported 14 hours of total downtime and estimated that approximately 4,000 March 22–23 transactions may have moved to different blocks or not been processed. It said RPC service and sequencing resumed at 00:03 UTC on March 24 with withdrawals still halted, followed by an emergency verifier upgrade later on March 24 and final normalization on March 25.

That later account clarified impact and recovery but does not change the event-day conclusion: on March 23, Polygon zkEVM suffered a prolonged sequencing failure after its software mishandled an Ethereum reorganization, while the extent of transaction disruption and the full remedy remained uncertain.