While the bug caused certain nodes to fall out of sync, block production on the network continued uninterrupted.
The Polygon Foundation, which oversees the protocol’s development, confirmed on Wednesday that consensus and finality functions have returned to normal.
What Happened and How It Was Fixed
The issue stemmed from a faulty proposal by one validator, which caused some Bor nodes—responsible for transaction ordering and block production—to diverge onto separate forks. RPC nodes, which help applications communicate with the blockchain, relayed inconsistent data during this time.
Polygon co-founder Sandeep Nailwal explained that the team deployed fixes on Heimdall v0.3.1 and Bor 2.2.11 beta2, removing the problematic milestone from the database. According to Nailwal, “With these fixes now live, nodes are not stuck, checkpoints and milestones are finalizing normally.”
UPDATE:
The hard fork has been successfully completed, and milestones are now processing normally along with state sync. Checkpoints are going through and consensus finalization has been fully restored on Polygon PoS.
We will continue to monitor the network closely to ensure… https://t.co/UwiAYdcKXu
— Polygon Foundation (@0xPolygonFdn) September 10, 2025
To address the issue, Polygon executed a hard fork. This update corrected node communication, ensuring that all nodes are now aligned with the main chain. While users may have noticed delays in transaction confirmations or discrepancies in node responses, the underlying blockchain remained operational, and new blocks continued to be added without interruption.
UPDATE: Milestone fixes rolled out
We identified the cause of the finality issue and have rolled out v2.2.11-beta2 for Bor and v0.3.1 for Heimdall, the latter a hardfork to be implemented at 3PM UTC.
We will continue to monitor the network to ensure all issues all resolved.… https://t.co/NSiS19cd5C
— Polygon Foundation (@0xPolygonFdn) September 10, 2025
Why This Matters for Users and Investors
RPC nodes are a critical part of blockchain infrastructure because they act as bridges between applications and the blockchain. When nodes fall out of sync, applications may display outdated data or experience temporary transaction delays. However, because Polygon’s block production continued, no on-chain transactions were lost. This is what the Founder and CEO of Polygon said about this:
Earlier today, Polygon PoS experienced a disruption where checkpoint finality on Ethereum was still active, but local fast finality on the chain (i.e. milestones) were delayed.
For context: milestones are a lightweight alternative to checkpoints, enabling faster, deterministic… https://t.co/ulINLtlurV
— Sandeep | CEO, Polygon Foundation (※,※) (@sandeepnailwal) September 10, 2025
This incident highlights a growing trend in blockchain networks. As smart contracts, file storage, and cross-chain interoperability increase in complexity, software bugs have become more common. In July, Polygon faced a similar event when the Heimdall mainnet halted for an hour. These incidents emphasize the importance of robust node monitoring, rapid bug fixes, and coordinated updates to maintain trust in blockchain systems.
Disclaimer
The information discussed by Altcoin Buzz is not financial advice. This is for educational, entertainment, and informational purposes only. Any information or strategies presented are the thoughts and opinions of the writer/reviewers, and their risk tolerance may differ from yours. We are not responsible for any losses you may incur due to any investments directly or indirectly related to the information provided. Bitcoin and other cryptocurrencies are high-risk investments; therefore, please conduct your due diligence. Copyright Altcoin Buzz Pte Ltd.
The post Polygon Fixes RPC Node Bug, Restores Consensus to Normal appeared first on Altcoin Buzz.
