Important update for network participants! A critical issue preventing Bor nodes from syncing on Mainnet has been resolved.
Previously, attempts to sync Bor encountered "bad block" errors, particularly for blocks around the Heimdall v1 to v2 migration. This was due to state sync events being incorrectly processed during that specific period, making it impossible for nodes to catch up.
To address this, Bor will now explicitly ignore state sync events on Mainnet within the specific block range of 73812433 to 73822500. This crucial fix enables Bor to successfully synchronize data from blocks predating the Heimdall migration, ensuring network stability and node operability.
Additionally, this release includes minor improvements such as an increased internal fetch timeout to 30 seconds and refinements in how state sync overrides are managed.
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 `73822500 `. 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. **Full Changelog**: https://github.com/maticnetwork/bor/compare/v2.2.5...v2.2.6