Polygon network conducts emergency Hard Fork to fix Node synchronization bug.

robot
Abstract generation in progress

The Polygon Foundation has officially reported a consensus failure that occurred on the Ethereum Layer 2 network.

What happened?

Bugs in the Bor node and Erigon node interfered with the RPC (Remote Procedure Call) service, disrupting communication between the application and the blockchain. Although the network itself was operational, there was a delay in finality of 10 to 15 minutes. Malicious proposals from validators caused the Bor node to split into multiple forks, halting block generation.

Countermeasure

According to Polygon co-founder Sandeep Nailwal, the following update is being distributed urgently:

  • Heimdall v0.3.1: Hard fork implemented to remove invalid milestones
  • Bor 2.2.11 beta2: Completely eliminate issues from the database

After the update, the full operation of the node was confirmed, and the checkpoint milestone function has been normalized.

Background

In July, the Heimdall V2 mainnet was offline for about 1 hour. At that time, it was due to a consensus bug, but slight synchronization issues occurred with multiple RPC providers. The Polygon side has established a continuous monitoring system and is committed to ensuring future stability.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pinned