Skip to content

Releases: maticnetwork/bor

v1.0.6-beta-txpool

31 Oct 00:08
0fecaa5
Compare
Choose a tag to compare
v1.0.6-beta-txpool Pre-release
Pre-release

This patch restores majority part of txpool implementation from Geth.
Only for testing purpose. Do not use.

v1.1.0-beta3

25 Oct 10:24
Compare
Choose a tag to compare
v1.1.0-beta3 Pre-release
Pre-release

This release contains some patch fixes on top of previously released versions for the Agra Hardfork for the Mumbai testnet. Note that this is an optional release and doesn't affect the underlying changes for the hard fork. Those running on old v1.1.0-beta or v1.1.0-beta2 version will also support the hard fork.

The changes for Mumbai Agra hard fork includes 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. The hard fork will kick in at block 41874000 and is expected to mine on 31st October, 2023.

Patch notes

  • Handle nil blocks and state access when RPC called using 'pending' tag (#1053)
  • Better error and withdrawals handling for Shanghai hard fork (#1054, #1056)
  • Fix key value lookup while reading bor config (#1055)
  • Selectively log message execution failed on contract on bor (b88d00c)

Breaking changes (for those upgrading from v1.0.6)

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

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.

What's Changed

New Contributors

Full Changelog: v1.0.6...v1.1.0-beta3

v1.1.0-beta2

18 Oct 06:57
Compare
Choose a tag to compare
v1.1.0-beta2 Pre-release
Pre-release

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.

Patch notes

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

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

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.

What's Changed

Full Changelog: v1.0.6...v1.1.0-beta2

v1.1.0-beta

17 Oct 09:15
Compare
Choose a tag to compare
v1.1.0-beta Pre-release
Pre-release

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

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.

What's Changed

Full Changelog: v1.0.6...v1.1.0-beta

v1.0.6

06 Oct 08:29
d521b8e
Compare
Choose a tag to compare

This patch version apply some minor fixes compared to the previous v1.0.5 release

What's Changed

  • fix : wrong chainID on rpc by @0xsharma in #1030
  • build(deps): bump github.com/consensys/gnark-crypto from 0.9.1-0.20230105202408-1a7a29904a7c to 0.12.0 by @dependabot in #1028
  • build(deps): bump github.com/supranational/blst from 0.3.8-0.20220526154634-513d2456b344 to 0.3.11 by @dependabot in #953
  • bump version by @marcello33 in #1031

Full Changelog: v1.0.5...v1.0.6

v1.0.5

05 Oct 15:56
2e896e2
Compare
Choose a tag to compare

This patch release addresses some minor fixes encountered with latest v1.0.4 version, and implement some new small features.

What's Changed

Full Changelog: v1.0.4...v1.0.5

v1.0.4

20 Sep 13:12
2943db9
Compare
Choose a tag to compare

This version introduces several new features and fixes compared to the previous stable version v0.4.0. The changes include (but are not limited to):

  • Upstream merge from go-ethereum/v1.11.6
  • A new feature called milestone which will bring faster and deterministic finality. Refer to PIP-11 for more information.

What's Changed

New Contributors

Full Changelog: v0.4.0...v1.0.4

v1.0.4-beta

19 Sep 06:28
Compare
Choose a tag to compare
v1.0.4-beta Pre-release
Pre-release

This version introduces several new features and fixes compared to the previous stable version v0.4.0. The changes include (but are not limited to):

  • Upstream merge from go-ethereum/v1.11.6
  • A new feature called milestone which will bring faster and deterministic finality. Refer to PIP-11 for more information.

Patch Notes

Compared to the last beta release (v1.0.2-beta) this version includes patches for (and some additional improvements):

  • Panic caused by concurrent map read and map write (introduced during the upstream merge). PR#1007.
  • Potential goroutine leak caused by metric goutine created by each execution pool. PR#1005.
  • Simplify the contents of the readme and remove unnecessary details. PR#979.

What's Changed

New Contributors

Full Changelog: v0.4.0...v1.0.4-beta

v1.0.3-beta

14 Sep 06:52
Compare
Choose a tag to compare
v1.0.3-beta Pre-release
Pre-release

This version introduces several new features and fixes compared to the previous stable version v0.4.0. The changes include (but are not limited to):

  • Upstream merge from go-ethereum/v1.11.6
  • A new feature called milestone which will bring faster and deterministic finality. Refer to PIP-11 for more information.

Patch Notes

Compared to the last beta release (v1.0.2-beta) this version includes patches for:

  • Fixing eth_getLogs for state-sync txns
  • Panic caused by concurrent map read and map write (introduced during the upstream merge).

What's Changed

New Contributors

Full Changelog: v0.4.0...v1.0.3-beta

v1.0.2-beta

13 Sep 10:24
Compare
Choose a tag to compare
v1.0.2-beta Pre-release
Pre-release

This version introduces several new features and fixes compared to the previous stable version v0.5.0.

Patch Notes

Compared to last beta release (v1.0.1-beta) this version includes one more PR which adds new RPC endpoint (bor_sendRawTransactionConditional) to support EIP-4337 Bundled Transactions. Refer to PIP-15 for more information.

What's Changed

New Contributors

  • @ForwardSlashBack made their first contribution in #960
  • @rroblak made their first contribution in #981

Full Changelog: v0.5.0...v1.0.2-beta