Skip to content

Releases: maticnetwork/bor

v1.2.1

19 Dec 03:49
2ee3919
Compare
Choose a tag to compare
v1.2.1 Pre-release
Pre-release

Hotfix for pruning issue

What's Changed

Full Changelog: v1.2.0...v1.2.1

v1.2.1-beta

18 Dec 10:17
Compare
Choose a tag to compare
v1.2.1-beta Pre-release
Pre-release

This release fixes pruning bug

Full Changelog: v1.2.0...v1.2.1-beta

v1.2.0

29 Nov 16:03
e0671d5
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.1.0...v1.2.0

v1.2.0-beta2

24 Nov 07:55
3c4e9cd
Compare
Choose a tag to compare
v1.2.0-beta2 Pre-release
Pre-release

Hot fix for Memory leak on top of v1.2.0-beta

What's Changed

Full Changelog: v1.2.0-beta...v1.2.0-beta2

v1.2.0-beta

22 Nov 06:50
11969b0
Compare
Choose a tag to compare
v1.2.0-beta Pre-release
Pre-release

Update bor with upstream geth merge till v1.12.2

What's Changed

New Contributors

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

v1.1.0-amoy

22 Nov 06:07
c52f8df
Compare
Choose a tag to compare
v1.1.0-amoy Pre-release
Pre-release

This contains the new Amoy testnet config and packages to deploy a node on the Amoy chainspecs.

What's Changed

New Contributors

Full Changelog: v1.1.0...v1.1.0-amoy

v1.1.0

09 Nov 13:05
cf18ecc
Compare
Choose a tag to compare

In this version, we implement changes for Agra Hardfork for mainnet. 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

New Contributors

Full Changelog: v1.0.6...v1.1.0

v1.1.0-beta4

31 Oct 19:23
b3f4b0b
Compare
Choose a tag to compare
v1.1.0-beta4 Pre-release
Pre-release

Disable prevrandao instruction set in bor

What's Changed

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

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