Polygon software bug caused some RPC and Bor nodes to fall out of sync, but block production continued. The Polygon Foundation executed a hard fork and released Heimdall v0.3.1 and Bor 2.2.11 beta2 to purge the faulty milestone and restore consensus and finality.
RPC nodes and Bor forks were temporarily divergent
Consensus and finality were restored after a coordinated hard fork and database purge
Node operators should update Heimdall and Bor and resync affected RPCs
Polygon software bug disrupted RPC nodes but not block production — check fixes, steps for node operators, and latest status from Polygon Foundation. Read now.
The bug impacted some remote procedure call (RPC) nodes, causing them to fall out of sync, but did not impact onchain block production.
‘,
‘
🚀 Advanced Trading Tools Await You!
Maximize your potential. Join now and start trading!
‘,
‘
📈 Professional Trading Platform
Leverage advanced tools and a wide range of coins to boost your investments. Sign up now!
‘
];
var adplace = document.getElementById(“ads-bitget”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBitget”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBitget.length) : sessperindex;
adplace.innerHTML = adscodesBitget[adsindex];
sessperindex = adsindex === adscodesBitget.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBitget”, sessperindex);
}
})();
What caused the Polygon software bug?
The Polygon software bug originated from a faulty proposal by a validator that pushed certain Bor nodes onto divergent forks. This discrepancy affected RPC relays and node synchronization, while Bor continued producing blocks and onchain block production remained uninterrupted.
How did Polygon restore consensus and finality?
Polygon Foundation executed a coordinated hard fork, deploying Heimdall v0.3.1 and Bor 2.2.11 beta2 to remove the problematic milestone from node databases. Polygon co-founder Sandeep Nailwal confirmed the rollout and stated that checkpoints and milestones are now finalizing normally.
Source: Polygon Foundation
‘,
‘
🔒 Secure and Fast Transactions
Diversify your investments with a wide range of coins. Join now!
‘,
‘
💎 The Easiest Way to Invest in Crypto
Dont wait to get started. Click now and discover the advantages!
‘
];
var adplace = document.getElementById(“ads-binance”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBinance”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBinance.length) : sessperindex;
adplace.innerHTML = adscodesBinance[adsindex];
sessperindex = adsindex === adscodesBinance.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBinance”, sessperindex);
}
})();
The issue primarily affected RPC nodes, which relay blockchain state to wallets and dApps. Because Bor continued producing blocks, onchain transaction ordering and block production were not halted, preventing broader network stoppage.
Polygon’s response focused on purging the malformed milestone from Heimdall and Bor databases. Heimdall v0.3.1 includes the hard fork that deletes the identified milestone, while Bor 2.2.11 beta2 purges the same record to bring nodes back into consensus.
Polygon experienced a comparable incident in July when Heimdall mainnet halted for about an hour after a validator exited the network. Like the recent bug, block production on Bor never stopped; affected RPCs needed to resynchronize to reflect the live chain state.