Bor update for Mainnet release

This release contains some bug fixes and also a hardfork, please refer the instructions in https://forum.polygon.technology/t/v0-2-12-beta3-upgrade-for-bor-mainnet-post-block-22156660/369 to upgrade.

Bor Update for Mumbai Testnet

This release contains some bug fixes that we are testing on Mumbai Testnet.

Fix for writing bor receipts to ancient db

This release fixes a bug that was introduced in the previous version where the bor receipts were being written as an array of arrays instead of the expected flattened array inside an array.

There was no impact of this bug in our network since all the nodes use --syncmode=full and this bug only affects nodes running with --syncmode=fast.

Upstream Changes from Geth v1.10.10

In this release, we have included all changes that are part of geth v1.10.10: https://github.com/ethereum/go-ethereum/releases/tag/v1.10.10

PS: This tag has not been created from master but from another branch geth-v1.10.10 as master contains few new features that are currently being tested.

Upstream Changes from Geth v1.10.10

In this release, we have included all changes that are part of https://github.com/ethereum/go-ethereum/releases/tag/v1.10.10

PS: This tag has not been created from master but from another branch geth-v1.10.10 as master contains few new features that are currently being tested.

Fixed Memory Leak, Added Network Flags for Mumbai and Mainnet

In this release, we have fixed the memory leak issue in bor, added network flags that can be used while invoking bor and few other minor changes. Major changes are listed below:

• Memory Leak Fixed: The root cause for the memory leak was identified and fixed in #201. We had already fixed the memory bloat issue that was causing few nodes to consume the entire memory within minutes of starting bor in https://github.com/maticnetwork/bor/releases/tag/v0.2.9-beta1
• Network Flags: You can now start bor using bor --bor-mainnet and bor --bor-mumbai flags to connect to mainnet and mumbai networks respectively. The defaults can be found here: https://github.com/maticnetwork/bor/blob/6c7a9e1c410992486ce610ed3836cec35ba546e6/cmd/geth/config.go#L342-L386 and any params that need to be overridden can be passed separately.

Pre-requisites

Please upgrade the go version to v1.16 or above before updating.

Hot Fix for Memory Bloat

Some of the bor nodes have been facing memory bloat resulting in the process getting killed by the OS. This is a hot fix for the issue.

We are also working with the geth team to include the change in geth if this is the agreed long term fix or discuss and come up with the long term fix.

Latest Updates from Geth

The major change in the release is this revert PR from Geth: ethereum/go-ethereum#23466

Updates from Geth v1.10.8

This release implements the latest changes from upstream geth v1.10.8 (https://github.com/ethereum/go-ethereum/releases/tag/v1.10.8 - hotfix release to patch a vulnerability in the EVM CVE-2021-39137). Below is the exhaustive list of changes in this release:

• Geth v1.10.8 updates
• Implemented new rpc/ipc method: GetTransactionReceiptsByBlock returns the transaction receipts for a given block number or hash
• Optimizing bor tx query

Please note that this release does not activate the London hard fork in bor.

Geth Update v1.10.3

Bor v0.2.6 is a maintenance release. Major changes are as follows:

• Latest changes from geth v1.10.3
• Added overrideStateSyncRecords to genesis
• Added flag for disabling bor logs