Polygon Encounters Finality Issue Due to Node Software Bug
Polygon is facing a temporary disruption in block finality following a software bug affecting both Bor and Erigon nodes. The issue, which surfaced early on Wednesday, led to delays in consensus and caused some decentralized applications and Remote Procedure Call (RPC) services to experience access problems. Despite the disruption, the Polygon blockchain remains active and continues to produce blocks.
Incident Details and Immediate Impact
The incident forced several RPC service providers and validators to rewind to the last finalized block and resynchronize their nodes. Polygons team confirmed that the bug prevents node progress in certain configurations. Some validators and providers reported resolution after restarting their nodes. "We see that a restart of nodes has fixed the issues for many validators and RPC providers," the Polygon team stated in an official update.
Ongoing Response and Status Updates
Developers at Polygon are working with infrastructure partners to isolate and resolve the problem. The team assured the community that the chains core operations are secure and users can expect a recovery soon. As of the latest statement, a fix has been identified and is in the process of being distributed to all validators and service operators. Polygon emphasized, "Checkpoint finality is working as expected within 15 mins." The company redirected users to an alternative block explorer showing that real-time block production is ongoing.
Technical Overview: Bor and Erigon Nodes
- Bor: The essential node client responsible for producing and organizing new blocks on the Polygon network.
- Erigon: A tool that allows infrastructure providers efficient access, storage, and retrieval of blockchain data, optimized for speed and stability.
Recovery Outlook
The team continues to monitor the situation and collaborate with ecosystem partners to enable a full network recovery. Polygon Labs reiterated that block production never stopped and that a solution is being rolled out network-wide. Further updates are expected as the patch reaches wider deployment.
Related content
Comments
