Polygon Restores Stability After Hard Fork Fixes Finality Bug

By José Oramas September 11, 2025 In Cryptocurrency, Polygon

Source:AdobeStock

Polygon has completed a hard fork to restore finality on its proof-of-stake network after a bug caused transaction finality to lag by 10-15 minutes.
The fix was implemented by deploying software updates, Bor v2.2.11-beta2 and Heimdall v0.3.1, which resolved the bug and restored normal checkpointing and consensus finalisation.
This is the second significant software issue for Polygon since July, but the team emphasised that the upgrades are part of a roadmap to make the chain more resilient for the long run.

Polygon has completed a hard fork to restore finality on its proof-of-stake network after a disruption earlier this week.

The Polygon Foundation confirmed on Wednesday that the upgrade “has been successfully completed”, with checkpoints and consensus finalisation now operating normally. Transactions and state synchronisation are also proceeding without issues, the team said, while adding that it will continue to monitor the network.

According to Sandeep Nailwal, CEO of the Polygon Foundation, the fix involved deploying Bor v2.2.11-beta2, Polygon’s block production client, and Heimdall v0.3.1, the consensus coordination layer.

Moreover, the fork was executed at 3 p.m. UTC, resolving a bug that had caused local fast finality to lag by 10–15 minutes. While checkpoint finality to Ethereum mainnet remained intact, validators on Polygon PoS were delayed in reaching milestones, slowing down confirmations.

As we’ve seen before, there will be growing pains with any ambitious upgrade. But each one makes Polygon PoS stronger on our road to GigaGas throughput, making the chain more resilient for the long run. More upgrades are on the way to strengthen capacity and reliability further. We’re working around the clock to ensure all will be rolled out smoothly and without disruption.

Sandeep Nailwal, CEO of the Polygon Foundation.

Validator Synchronisation Impacted, Not Block Production

Finality marks the stage when a transaction becomes irreversible, ensuring that no chain reorganisation can roll back the state. During the incident, Polygon continued producing blocks and processing transactions, though validator synchronisation was impaired.

This is the second significant software issue for Polygon since July. Then, Heimdall, the consensus client linking validator communication, suffered a one-hour halt after a validator exited, forcing several RPC nodes to resynchronise. In both cases, block creation via Bor was unaffected.