Bor v1.1.0-beta2 Mumbai Release

Hello All,

We are releasing a new version of Bor v1.1.0-beta2 for Mumbai. This release contains Agra Hardfork(details below). This will hardfork the Bor Mumbai network at block #41874000 which will be mined on 31st October 2023 (approx). A new release of Erigon that supports the hardfork changes will be released in a few days.

Instructions to Upgrade Bor

  1. Stop bor service

    sudo service bor stop
  2. Install Bor with a version tag, network name (mainnet or mumbai), and node type (sentry, validator, or archive).

    # Replace the node type
    curl -L | bash -s -- v1.1.0-beta2 mumbai <node_type>
  3. Check bor version

    /usr/bin/bor version
    # It should print 
    # v1.1.0-beta2
  4. Restart bor service

    sudo service bor start

Change log

In this version, we implement changes for Agra Hardfork. The changes include selected Shanghai EIPs (EIP-3651: Warm COINBASE, EIP-3855: PUSH0 instruction, EIP-3860: Limit and meter initcode, EIP-6049: Deprecate SELFDESTRUCT), StateSyncReceiver Contract Bytecode changes, New EIP1559 burn contract address change.

Breaking changes

Bor will now overwrite the config.toml flag values if the flag is explicitly set via cli arguments. This is a breaking change only for those using a combination of both as flags provided by cli arguments will be prioritised above config.toml values. Earlier config.toml flag values were prioritised.

The order of flag will now be as follows:

  1. If set in cli args, use that value
  2. If not set in cli args and set in config, use that value
  3. If not set in any of them, use default value

If the toml config looks something like this:

chain = "mainnet"
identity = "Anon"
datadir = "config_datadir"
### More values

and the user runs the following command

bor server --config=config.toml --datadir=cli_datadir

Until now, bor would set the datadir the value mentioned in config i.e. config_datadir.

With this version onwards, the value set for datadir would be cli_datadir.

Patch notes

  • Contains fix to an issue which caused empty value usage of the keystore directory flag (#1051)

What’s Changed

Full Changelog: Comparing v1.0.6...v1.1.0-beta · maticnetwork/bor · GitHub

Docker Images

You can find the latest docker images here:

Bor: Docker


Polygon Team