Bor v2.1.0-beta Release

Announcements
1

Hi all, we have released a new version of bor, v2.1.0-beta

Note: This is a beta release and is not intended for mainnet deployments. It includes preparatory changes for the upcoming Bhilai Hard Fork. Final activation parameters (e.g., fork block for Amoy) will be provided in a follow-up release.

This release contains some breaking changes to the database. Downgrading to previous versions requires re-syncing the chain.

Bhilai Hard Fork Preparation

  • This release includes all protocol changes for the Bhilai Hard Fork.
  • The fork is not yet active. A future release will specify the Amoy fork block and finalize the activation parameters.

Database Format Change

  • The database version has been increased from v8 to v9.
  • This is a backward-incompatible change. After upgrading to this version, rolling back to a previous version will require a resync from genesis.

Chain Rewind Behavior

  • On upgrade, the node will enter a head-state missing state and will rewind several hundred thousand blocks. This is expected and part of the upgrade path.
  • If operating a network of connected nodes:
    • Upgrade the nodes one by one.
    • This allows each rewound node to sync from its still-synced peers, reducing load on external RPCs.

Note: It would be best to upgrade Bor in the validator node when the validator is not in the current selected_producers set by referring to one span before https://heimdall-api-amoy.polygon.technology/bor/latest-span
Eg if the latest span has "span_id": 3516 , , then check https://heimdall-api-amoy.polygon.technology/bor/span/3515 and then upgrade.

Gas Limit Adjustment

  • The block gas limit will be increased to 45 million after deploying this version.
  • This is a non-hard-fork change and will apply immediately upon deployment of this release.

Steps for upgrading Bor node

  1. Stop bor service

    sudo service bor stop

  2. Install Bor with a version tag, network name (amoy), and node type (sentry, validator, or archive).

    # Replace the node type
curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- v2.1.0-beta amoy <node_type>

  3. Check bor version

    /usr/bin/bor version

# It should print 
# v2.1.0-beta

  4. Restart bor service

    sudo service bor start

What’s Changed

Full Changelog: v2.0.4-beta…v2.1.0-beta

2 Likes
2

Thanks for the update. Good to know about the database version bump and the rewind behavior, that part caught me off guard initially until I read through the details. The step-by-step upgrade notes are helpful too. Looking forward to the follow-up with the finalized Bhilai fork parameters for Amoy.

3

Bor v2.1.0-beta is out with prep for the Bhilai Hard Fork on Amoy. Note: it’s a beta release, not for mainnet yet, and includes a database upgrade from v8 to v9 — downgrades require full resync. Nodes will rewind blocks on upgrade; upgrade validators off selected_producers to reduce sync load. Gas limit increases to 45M immediately after deployment (non-hard-fork). Follow the usual steps: stop service, install with the script, check version, and restart. Check the full changelog for details. Stay tuned for the final fork block and activation info in upcoming releases.

4

This update looks solid. The increased gas limit and protocol changes for the Bhilai Hard Fork are promising. Appreciate the heads-up about the database format change and chain rewind, really helpful for planning the upgrade smoothly. Looking forward to testing it out!