Skip to content

Releases: maticnetwork/bor

v2.2.5

03 Jul 21:12
041ced5
Compare
Choose a tag to compare

This release fixes an issue where new milestone are not processed by bor on the start of the node, therefore delaying the finalization of blocks for the first few hours after the node is started.

What's Changed

  • Fix milestone whitelist delay on restart by @cffls in #1611

Full Changelog: v2.2.4...v2.2.5

v2.2.4

03 Jul 07:10
81caac8
Compare
Choose a tag to compare

This release includes various fixes for bugs encountered post Heimdall v1 -> v2 migration in Amoy network and Bhilai HF.

What's Changed

Full Changelog: v2.1.1...v2.2.4

v2.2.4-beta2

30 Jun 11:12
097a1ba
Compare
Choose a tag to compare
v2.2.4-beta2 Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release fixes a bug in heimdall(v2) gRPC client which fetches state sync data from heimdall-v2. If you have enabled Heimdall-gRPC then it is recommended to upgrade to this version.

What's Changed

Full Changelog: v2.2.4-beta...v2.2.4-beta2

v2.2.4-beta

27 Jun 10:08
e5b3a69
Compare
Choose a tag to compare
v2.2.4-beta Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release fixes a bug in committing state sync into bor. We now explicitly do not allow any state sync events into bor (AMOY) for a given block range from 23184305 to 23220127. 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, params: added OverrideStateSyncRecordsInRange to overwrite the state sync records for a range of blocks by @pratikspatil024 in #1597
  • amoy: added blocks in the OverrideStateSyncRecordsInRange for the outage after heimdall (v1 -> v2) migration by @pratikspatil024 in #1598

Full Changelog: v2.2.3-beta...v2.2.4-beta

v2.2.3-beta

26 Jun 07:07
80ee5b1
Compare
Choose a tag to compare
v2.2.3-beta Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release contains a fix for heimdall-v2 state syncs fetching.
The -beta suffix indicates that this version is intended solely for Amoy use and will not be deployed on mainnet.

What's Changed

Full Changelog: v2.2.2-beta...v2.2.3-beta

v2.2.2-beta

24 Jun 17:15
f4a3614
Compare
Choose a tag to compare
v2.2.2-beta Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release must be installed on all nodes in the Amoy network for the upcoming Heimdall v1 to v2 migration, scheduled on Tuesday, June 24th, 2025, between 7:00 PM and 9:00 PM UTC.
The -beta suffix indicates that this version is intended solely for Amoy use and will not be deployed on mainnet.

It contains the changes for bor to be independent from heimdall, during the expected downtime due to the migration, and the changes to make bor compatible with v1 and v2.

What's Changed

  • eth: fix canonical chain state inconsistency in checkpoint verifier by @cffls in #1591

Full Changelog: v2.2.1-beta...v2.2.2-beta

v2.2.1-beta

24 Jun 06:39
da97795
Compare
Choose a tag to compare
v2.2.1-beta Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release must be installed on all nodes in the Amoy network for the upcoming Heimdall v1 to v2 migration, scheduled on Tuesday, June 24th, 2025, between 7:00 PM and 9:00 PM UTC.
The -beta suffix indicates that this version is intended solely for Amoy use and will not be deployed on mainnet.

It contains the changes for bor to be independent from heimdall, during the expected downtime due to the migration, and the changes to make bor compatible with v1 and v2.

What's Changed

  • Allow peer sync recovery from a wrong fork by @cffls in #1588

Full Changelog: v2.2.0-beta...v2.2.1-beta

v2.2.0-beta

18 Jun 19:44
606fc34
Compare
Choose a tag to compare
v2.2.0-beta Pre-release
Pre-release

🚨 ⚠️ ONLY USE ON AMOY NETWORK ⚠️🚨

This release must be installed on all nodes in the Amoy network for the upcoming Heimdall v1 to v2 migration, scheduled on Tuesday, June 24th, 2025, between 7:00 PM and 9:00 PM UTC.
The -beta suffix indicates that this version is intended solely for Amoy use and will not be deployed on mainnet.

It contains the changes for bor to be independent from heimdall, during the expected downtime due to the migration, and the changes to make bor compatible with v1 and v2.

What's Changed

Full Changelog: v2.1.1...v2.2.0-beta

v2.1.1

17 Jun 09:49
c522a93
Compare
Choose a tag to compare

This release schedules the Bhilai Hard Fork for Mainnet.

The Bhilai Hard Fork on Mainnet is scheduled for block number 73440256. Which is expected to be mined on July-1-2025 at 9:10 AM UTC (2:40 pm IST). Make sure to update all your Mainnet nodes before this time.

Note: If you are updating to v2.1.x for the first time, make sure to check out the release notes of v2.1.0.


⚠️ Validator Configuration Update (Mandatory)

All validators are required to check their config.toml file.
If the gaslimit field under the [miner] section is uncommented, it must be updated to 45000000 (45M) to support PIP-60.

[miner]
  gaslimit = 45000000

If this section is not present or if gaslimit is commented, then you are all set. No actions needed from your end.


What's Changed

Full Changelog: v2.1.0...v2.1.1

v2.2.0-test

16 Jun 06:28
3c77074
Compare
Choose a tag to compare

🚨 ⚠️ DO NOT USE IN PRODUCTION FOR ANY NETWORK ⚠️🚨

This version provides the bor code for the heimdall v1 -> v2 migration.
It can be used for tests until made final.

What's Changed

Full Changelog: v2.1.0...v2.2.0-test