Polygon Hard Fork corrects the bug that dropped offline nodes – online network

Polygon has restored the full network stability after a software bug temporarily disrupted the purpose of the milestones and forced certain offline nodes, according to an official report of incident published on the project state page.

The problem began early Wednesday when a bug affecting Bor, the producer of Polygon and Erigon blocks, his data access layer, caused disturbances in the parts of the ecosystem.

While the blockchain itself continued to produce blocks, certain remote procedure services (RPC) and the validators stopped, forcing suppliers to return to the last finalized block and to resynchronization.

Polygon performs an emergency fork to solve the finality bug

Polygon engineers confirmed that the bug prevented the progress of nodes under certain configurations, although the restarting of the assigned nodes has solved the problem for several validators and suppliers of RPC.

At the time, PolygonScan, the network explorer of the network, did not show any block update for more than five hours. Polygon later explained that the polygonse nodes had stopped after a defective step produced by Heimdall, the consensual engine of the project.

A representative of the company said that the team worked with Polygonscan to go to the functional nodes that had not stopped, stressing that the production of blocks remained live.

“The purpose of the checkpoint operates as planned within 15 minutes,” the team said in an update at 08:52 UTC, sharing an alternative link where the production of blocks in real time could be followed.

The analysis revealed that the problem came from Heimdall’s finality gadget, which is responsible for the production of milestones every second.

Although the control points in Ethereum are always displayed every 20 minutes, the milestones, which provide a faster and deterministic purpose, were not treated. This has left the local quick purpose delayed even if the main channel continued to add blocks.

To solve the problem, Polygon has deployed emergency updates: Bor version 2.2.11-Beta2 and Heimdall version 0.3.1, the latter requiring a hard fork. The upgrade, executed at 3 p.m. UTC, deleted the defective milestone and served it from node databases.

Polygon confirmed shortly after the fork has been successfully completed and the milestones and the control points again finalized normally.

“The hard fork has been successfully completed and the milestones now treat normally with the synchronization of the state.

The co-founder and CEO of the Polygon Sandeep Nailwal Foundation later explained that the disturbance came from a defective milestone proposal which pushed certain Bor nodes on divergent forks. This triggered short -term instability not explained in the system.

He stressed that, although the purpose of the control points on Ethereum has remained active throughout, the purpose of the local stages was delayed.

“Milestones are a light alternative to control points, allowing a faster deterministic purpose for transactions, even before a checkpoint is subject to Ethereum,” said Nailwal. “The deep cause came from a proposal for a defective milestone. We have deployed fixes both on Heimdall and Bor.

With these live fixes, the nodes are not trapped and the consensus normally finalizes. »»

Nailwal has described the event as part of the growing pain in scaling Polygon’s evidence, but said that each challenge strengthens its resilience. “There will be growing pain with an ambitious upgrade.

But everyone makes the Polgo stronger on our way to Gigagas flow, “he said, adding that more upgrades are planned to increase capacity and reliability.

Polygon engineers continue to monitor the network to ensure stability and study how the defective milestone was introduced.

Despite the temporary setback, the network has taken up normal operations, with blocks, milestones and treatment of real -time control points

The reliability of Polygon is questioned after the finality bug, TVL dropped by 87% compared to the peak

Polygons developers have deployed a hard fork to correct a bug which temporarily stopped the production of blocks on its chain of evidence, restaurant the network after several hours of disruption.

The problem, linked to the purpose of transactions, left -wing exchanges and challenge protocols, unable to process deposits or withdrawals when they were waiting for confirmation guarantees.

The breakdown aroused criticism from Polymarket traders, which argued that a blockchain hosting one of the largest prediction markets in the sector should not face such problems. “It could have gone unnoticed because no one used it, but it has been going on for about two hours,” said a merchant, showing the risk of overthrows during downtime.

Tokenpocket, a Stablecoin multi -hole wallet, also interrupted polygon transactions after observing that no new block had been finalized for more than an hour.

The incident occurs just a few weeks after HEIMDALL V2 upgrade from Polygon, designed to reduce the end times to five seconds and improve the coordination of the validator.

This update followed the Fork Hard Bhilai on July 1, which increased the flow to 1,000 transactions per second and integrated Pectra Eips d’Ethereum. Despite these efforts, network reliability remains a concern, because the total value of Polygon has increased from a peak of $ 9.43 billion in 2021 to $ 1.2 billion today, by Defillama.

The native token of the channel, POL, dropped by 3.4% during the day and is down 30% for the start of the year, negotiating $ 0.27.

Meanwhile, another layer 2 Ethereum, Linea, was confronted with a separate breakdown earlier during the day when its main sequencer stuck, causing a 67 -minute break in the production of blocks.

While Linea has already deployed a fix, the developers wonder if the two disturbances are linked. Linea did not disclose the cause of her downtime.

The two events highlight the fragility of scaling networks which have become essential to the wider ecosystem of Ethereum.

The post Post Polygon Hard Forks bug which dropped offline nodes – the online network appeared first on Cryptonews.

Source link