TL;DR
- Node Issue Impact: A software flaw within Polygon’s Bor and Erigon node systems created problems with transaction confirmation and desynchronized RPC services, ultimately hindering application performance.
- Validator Action: To restore accurate network data, infrastructure operators were required to revert to the previously confirmed block and re-establish synchronization.
- Network Resilience: Even with the disruption, Polygon’s underlying blockchain maintained its block production and continuous operation.
Polygon, a prominent Layer 2 blockchain solution, experienced a temporary interruption in its transaction confirmation process on Wednesday because of a software problem affecting its Bor and Erigon nodes. While the primary blockchain remained active and continued generating blocks, this event led to noteworthy issues for Remote Procedure Call (RPC) services and the synchronization of validators.
This disruption prompted several infrastructure providers to roll back to the last secure block and re-synchronize their systems, which had an impact on accessibility for applications operating on the network.
Node Software Flaw Causes Confirmation Delay
The confirmation delay arose from a software flaw found within the Bor and Erigon node configurations, which interrupted operations for specific validators and RPC providers. Polygon’s official status page reported the issue early Wednesday, clarifying that the blockchain itself remained active but certain services struggled to maintain correct synchronization. This resulted in reduced performance and limited accessibility for decentralized applications that depend on real-time network data.
RPC Providers and Validators Required to Revert
As a direct outcome of the software flaw, a substantial number of RPC providers and validators had to revert to the last finalized block and begin a resynchronization process. This action was crucial to reinstating correct data and guaranteeing consistency throughout the network. Polygon’s technical experts indicated that restarting the affected nodes resolved the issue for many users, however, the debugging process is ongoing. The team is diligently working with infrastructure partners to accelerate the recovery and restore all functions.
Core Chain Operations Remain Intact
Despite the disruption, Polygon emphasized that the incident did not jeopardize the operation of its core blockchain system. Block creation continued and the network was fully operational during the event. The team assured users that the finality delay was specifically related to the specific node configurations and had no bearing on the overall consensus mechanism. This distinction reduced worries regarding possible downtime or data loss.
Engineers Work Toward Full Recovery
Polygon’s technical team is working in coordination with infrastructure providers to locate the underlying source of the software flaw and implement a lasting solution. While restarting nodes is proving beneficial for many, the aim is to secure long-term stability and prevent reoccurrences. News organizations have contacted Polygon Labs seeking additional details, yet a response was not received by the publication deadline. The situation remains changeable, and updates are anticipated as the investigation advances.