Skip to content

Releases: maticnetwork/bor

v1.5.0-beta

03 Oct 17:47
b35b0e0
Compare
Choose a tag to compare
v1.5.0-beta Pre-release
Pre-release

The major change in this release is the commits merged from go-ethereum up to geth 1.14.6.

What's Changed

Full Changelog: v1.4.1...v1.5.0-beta

v1.4.1

18 Sep 15:51
0b28bb5
Compare
Choose a tag to compare

What's Changed

  • Fixed a bug in parallel executor. The bug could possibly cause parallel executor to compute a different block hash from a regular (serial) executor in some rare scenarios.

Full Changelog: v1.4.0...v1.4.1

v1.4.0

13 Sep 13:24
e69e4c8
Compare
Choose a tag to compare

This version includes a hard fork named Ahmedabad fork. Please upgrade your mainnet nodes before block number 62,278,656 (https://polygonscan.com/block/countdown/62278656) which is expected to be mined on Thu Sep 26 2024 around 9 AM UTC.

For more information about Ahmedabad HardFork, please refer to [PIP-37].

What's Changed

Misc

Full Changelog: v1.3.7...v1.4.0

v1.4.0-beta2

13 Sep 17:23
f9ba824
Compare
Choose a tag to compare
v1.4.0-beta2 Pre-release
Pre-release

The Ahmedabad hardfork on Amoy Testnet went through pretty smoothly on Sept 12th. However, the upgrade to WMatic did not go as expected. The changes that were made to the bytecode did not have any effect, thus making the deployment not effective.

Please note, the issue is present only on Amoy Testnet and hence, we only need to execute this additional hardfork on Amoy only.

Please upgrade your Amoy nodes before block number 12,121,856 (https://amoy.polygonscan.com/block/countdown/12121856) which is expected to be mined on Wed, Sept 18 2024 around 10 AM UTC. Announcement for Erigon with the new release will follow on Mon, Sept 16.

What's Changed

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

v1.4.0-beta

05 Sep 15:45
da611cd
Compare
Choose a tag to compare
v1.4.0-beta Pre-release
Pre-release

This version includes a hard fork named Ahmedabad fork. Please upgrade your amoy nodes before block number 11,865,856.
For more information about Ahmedabad HardFork, please refer to PIP-37.

What's Changed

Misc

Full Changelog: v1.3.7...v1.4.0-beta

v1.3.7

12 Aug 06:39
d903330
Compare
Choose a tag to compare

Compared to the last stable release (v1.3.6), this version includes a few bug fixes.

What's Changed

Upstream Geth Merge

Misc

New Contributors

Full Changelog: v1.3.6...v1.3.7

v1.3.6

07 Aug 13:57
2cdef71
Compare
Choose a tag to compare

This release contains an important security fix on top of v1.3.4. It is recommended for everyone to upgrade their nodes to v1.3.6

What's Changed

Full Changelog: v1.3.4...v1.3.6

v1.3.5-beta

30 Jul 04:36
369a59e
Compare
Choose a tag to compare
v1.3.5-beta Pre-release
Pre-release

This release contains some minor bug fixes compared to the last stable release v1.3.4.

What's Changed

Upstream Geth Merge

Misc

New Contributors

Full Changelog: v1.3.4...v1.3.5-beta

v1.3.4

25 Jul 12:18
29840e2
Compare
Choose a tag to compare

This release of bor contains the updated implementation of PIP-35 which enforces the min gas values to 25 gwei. These values are applicable to all networks (i.e. mainnet and amoy). Irrespective of the values set by the cli flags, they will be enforced to 25 gwei. This version also contains changes from upstream (v1.13.6) geth.

What's Changed

  • core, eth, internal, miner, params: enforce 30gwei for gas related configs in bor by @marcello33 in #1264
  • cmd/utils: use defined filter api instance instead of a new one by @manav2401 in #1270
  • PIP-35 for amoy: enforce gas related configs by @manav2401 in #1285
  • miner: log last tx hash before commit interrupt by @manav2401 in #1289
  • PIP-35: enforce gas related configs for mainnet by @manav2401 in #1290

Upstream Geth Merge

Misc

Full Changelog: v1.3.3...v1.3.4

v1.3.4-beta3

11 Jul 11:35
31545e5
Compare
Choose a tag to compare
v1.3.4-beta3 Pre-release
Pre-release

This release of bor contains the updated implementation of PIP-35 which enforces the min gas values to 25 gwei. The previous enforcements which were applied to all the networks are removed and the enforcements are only applicable to Amoy network.

Note: If you've deployed previous beta releases (i.e. v1.3.4-beta or v1.3.4-beta2 which applied the values for all networks) on mainnet, the values will now fall back to default (unless explicitly overwritten).

Heads up: A new stable release with these enforcement for mainnet will follow soon in coming weeks with appropriate announcements.

Until then, kindly deploy this version only on amoy.

What's Changed

Full Changelog: v1.3.4-beta2...1.3.4-beta3