Important Bor Sync Update for Mainnet
We've released a crucial update to address a persistent syncing issue encountered by some Bor Validator nodes on Mainnet.
Previously, nodes attempting to sync from blocks predating the recent Heimdall v1 to v2 migration would sometimes encounter a "bad block error." This prevented successful synchronization and impacted network stability for these nodes.
This update resolves the issue by explicitly disallowing problematic state sync events from being committed into Bor for a specific block range: from 73812433 to 73826700. This targeted exclusion ensures that Bor can now seamlessly sync from blocks prior to the Heimdall migration without encountering any errors.
The fix significantly enhances the reliability of node synchronization and overall network health.
This release fixes a bug in committing state sync into bor. We now explicitly do not allow any state sync events into bor (Mainnet) for a given block range from `73812433 ` to `73826700 `. This is to allow syncing bor from a block which was prior to the heimdall (v1 to v2) migration. Without this, bor cannot sync as it will reject blocks with bad block error. ## What's Changed * [consensus/bor/heimdall: increased the internalFetchWithTimeout to 30 seconds](https://github.com/maticnetwork/bor/pull/1626/commits/b46b6bd0b3283fb0bcf690f960205984a4678090) by @pratikspatil024. * [consensus/bor: skipping override state sync if value is 0](https://github.com/maticnetwork/bor/pull/1626/commits/52c28621f5a6c276c87e1bc22168844947c3695a) by @pratikspatil024. * [mainnet: added blocks in the OverrideStateSyncRecordsInRange for heimdall (v1 -> v2) migration](https://github.com/maticnetwork/bor/pull/1626/commits/1d39d8c3a28a6d1efa5bf82326baafac49d41dd4) by @pratikspatil024. * [mainnet: updated the OverrideStateSyncRecordsInRange for mainnet](https://github.com/maticnetwork/bor/pull/1627/commits/2601edc24de9a56de42fa2f92825b4d4b0193ee4) by @pratikspatil024. **Full Changelog**: https://github.com/maticnetwork/bor/compare/v2.2.5...v2.2.8