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
-
Stop bor service
sudo service bor stop -
Install Bor with a version tag, network name (mainnet or mumbai), and node type (sentry, validator, or archive).
# Replace the node type curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- v1.1.0-beta2 mumbai <node_type> -
Check bor version
/usr/bin/bor version # It should print # v1.1.0-beta2 -
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:
- If set in cli args, use that value
- If not set in cli args and set in config, use that value
- If not set in any of them, use default value
Example:
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
- Backport master to develop after v1.0.4 by @pratikspatil024 in https://github.com/maticnetwork/bor/pull/1013
- internal/cli: add support to overwrite config.toml values via cli flags by @manav2401 in https://github.com/maticnetwork/bor/pull/1008
- update discord links by @anshalshukla in https://github.com/maticnetwork/bor/pull/1015
- backport-master-to-develop by @marcello33 in https://github.com/maticnetwork/bor/pull/1029
- backport/master-to-develop by @marcello33 in https://github.com/maticnetwork/bor/pull/1032
- mainnet recommended peer settings by @marcello33 in https://github.com/maticnetwork/bor/pull/1034
- mardizzone/master-to-develop by @marcello33 in https://github.com/maticnetwork/bor/pull/1035
- worker: (Block-STM) Do not hardcode EnableMVHashMap as false by @pratikspatil024 in https://github.com/maticnetwork/bor/pull/1039
- Fix Codecov and add integration tests coverage by @0xsharma in https://github.com/maticnetwork/bor/pull/1020
- Add CodeQL by @marcello33 in https://github.com/maticnetwork/bor/pull/1037
- add : agra HF mumbai block by @0xsharma in https://github.com/maticnetwork/bor/pull/1044
- bump peppermint and cosmos-sdk to latest polygon releases by @marcello33 in https://github.com/maticnetwork/bor/pull/1045
- chg : withdrawals check in bor consensus by @0xsharma in https://github.com/maticnetwork/bor/pull/1049
- Shanghai/Agra HF by @0xsharma in https://github.com/maticnetwork/bor/pull/1025
Full Changelog: https://github.com/maticnetwork/bor/compare/v1.0.6...v1.1.0-beta
Docker Images
You can find the latest docker images here:
Bor: https://hub.docker.com/r/0xpolygon/bor/tags
Thanks,
Polygon Team