The Polygon Foundation, the organization that administers the Layer-2 scaling network development in the Ecosystem, said Wednesday that consensus and end functions were restored, following a software bug that caused several nodes to disappear with blockchain sync.
Polygon successfully conducted a hard fork Following the software bug That interferes with some remote call methods (RPC) node, used to restore information between applications and the blockchain layer, the polygon team Says Upon updating Wednesday.
The bug was caused by a “faulty” proposal from a validator, which pushed some of the Bor nodes, used for ordering a transaction and blocking labor, onto the fork network of diverse, according to polygon co-founder Sandeep Nailwal. Nail Says:
“We launched the arrangements in the same Heimdall V0.3.1 – a new version with a hard fork to delete the identified milestone – and bor 2.2.11 beta2, cleaning the milestone from the database. In these arrangements are already alive, the nodes are not stuck, the checkpoints and the milestones end normally.”
Software bugs Continue to cause blockchain outages. While cryptographic protocols are becoming more complicated by hosting smart contract function, file storage and cross-chain interoperability, bugs can be more frequent, interrupting the onchain user experience.
Related: The launch of USDT0 and xaut0 stablecoins on the Polygon Network
Polygon is experiencing second software bug since July
Wednesday’s software bug did not stop polygon production; Instead, the issue affects the communication of the node, causing a difference between the block making and what the affected nodes affected.
Polygon faces a similar issue in July when Hemidall Mainnet, the Consensus Client that returns communication between nodes for polygon (POS) consent mechanism, is quit for one hour.
As with the Wednesday incident, the network’s block production has not stopped, and new blocks are continuously added to the chain via Bor Mainnet.
https://www.youtube.com/watch?v=1TFG-Yg6LPS
The partial flow of the consensus layer was due to a validator that came out of the network, a polygon spokesman told cointelegraph at that time.
Following the unnamed Validator exit, many RPC nodes need to berenchronize with the blockchain and re-establish communication to continue normal functionality in the network-2 network.
Magazine: Polygon never set to defeat Ethereum: Anurag Arjun, X Hall of Flame
