Bor Release v0.2.10

In this release, we have included all changes that are part of geth v1.10.10 (Release Sytau (v1.10.10) · ethereum/go-ethereum · GitHub).

In order to ensure nodes in our network are not vulnerable to the DoS attack as mentioned in https://twitter.com/go_ethereum/status/1462717778830540803?s=20, please upgrade bor on all your validator and sentry nodes on both mumbai and miannet networks to the latest release: Release Upstream Changes from Geth v1.10.10 · maticnetwork/bor · GitHub

Instructions to Upgrade

  1. SSH to your sentry and validator nodes and upgrade golang to version 1.17 (if it is not already done):
wget https://gist.githubusercontent.com/ssandeep/a6c7197811c83c71e5fead841bab396c/raw/5866fbd95fe3d9eae7bae08a842240d2edbe489e/go-install.sh
bash go-install.sh --remove
bash go-install.sh
  1. Ensure go version is 1.17:
$ go version

# you should see go1.17 in the output:
go version go1.17 linux/amd64
  1. Navigate to the bor directory:
cd ~/bor
  1. Fetch the latest changes and switch to v0.2.10:
git fetch
git checkout v0.2.10
  1. Stop bor and build the latest code:
sudo service bor stop
make bor-all
  1. Check bor version:
bor version

and ensure it is as below:

Bor
Version: 0.2.10-stable
  1. Start bor:
sudo service bor start

Docker Image

https://hub.docker.com/layers/maticnetwork/bor/v0.2.10/images/sha256-81e7341b2df99068925aa46eeb9201b5e18ff67e42c9d8839e1d98a7679057ef?context=explore

Let us know if you have any questions.

Thank you.

1 Like

The following problems were encountered after upgrading:
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: ########## BAD BLOCK #########
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: Chain config: {ChainID: 137 Homestead: 0 DAO: DAOSupport: false EIP150: 0 EIP155: 0 EIP158: 0 Byzantium: 0 Constantinople: 0 Petersburg: 0 Istanbul: 3395000, Muir Glacier: 3395000, Berlin: 14750000, London: , Engine: bor}
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: Number: 22156660
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: Hash: 0x7922f041cf1f33d3947ce2629a9a9c3004a6130f1c7b29c4852b6207515fa061
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: 0: cumulative: 327191 gas: 327191 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x7eb1e495f067d98f32285bfd7620345d80a40383874c7b5a4a75e198adb399e8 logs: [0xc0845184d0 0xc084518580 0xc084518630 0xc0845186e0 0xc084518790 0xc084518840 0xc0845188f0 0xc0845189a0 0xc084518a50 0xc084518b00 0xc084518bb0 0xc084518c60 0xc084518d10 0xc084518dc0] bloom: 00000000001000000000200000020000400021000800000000000000000000000000000000000008000000100008000000008000104000000000000800202200000000000000000000010008000001800000000000002000001100000008000000020000020000000000000004000020004000000000000080000030010100001000000000000040011000000000000000010100011000100000040000000000220000000000000000000040000000000000000000000000000000000010004000000002400000000001000000000000000000000008800000108000000000020010000000000000000008000000000084042028000000000000080000300000 state:
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: 1: cumulative: 348191 gas: 21000 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x721d9ce635e9f1c66b7cf555c95a930cebd46e90123e174150d5f8ecb4b41aa0 logs: [0xc084518f20] bloom: 00000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000008000000020000000000000000000000000000000000000000000000001800000000000000000000100000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000100000000000000000200000000000000000000040000000000000000000000000000000000000004000000000000000000001000000000000000000000000000000100000000000000000000002000000000000000000000000000000000000000000000000100000 state:
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: 2: cumulative: 369191 gas: 21000 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x5a5712a15ed830ff3cb8624a064857beed25f1683238c385eaa5fe6533e77339 logs: [0xc084518fd0] bloom: 00000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000008000000020000000000000000000000000000000000000000000000001800000000000000000000100000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000100000000000000000200000000000000000000040000000000000000000000000000000000000004000000000000000000001000000000000000000000000000000100000000000000000000002000000000000000000000000000000000000000000000000100000 state:
Dec 06 07:17:51 ip-172-31-3-133 bash[1000276]: 3: cumulative: 390191 gas: 21000 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0xc25d54d6d1e747c2c58e66fb68dfdad62a03970665308e00d45d3850aabcd54a logs: [0xc084519080] bloom: 00000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000008000000020000000000000000000000000000000000000000000000001800000000000000000000100000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000100000000

Hi @adam ,

Please follow these instructions to get your node back in sync.
https://www.notion.so/v0-2-12-beta3-Bor-Upgrade-6c94ac47a5ac41b88bb5f3bf72cdb949

The node has been synchronized again. Thank you!

1 Like