Skip to content

Releases: maticnetwork/bor

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

v1.3.4-beta2

21 Jun 15:34
b228a47
Compare
Choose a tag to compare
v1.3.4-beta2 Pre-release
Pre-release

Bor v1.3.4-beta2 includes fix to an issue which caused eth_getLogs rpc calls to fail

What's Changed

  • cmd/utils: use defined filter api instance instead of a new one by @manav2401 in #1270

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

v1.3.4-beta

19 Jun 05:58
c551b41
Compare
Choose a tag to compare
v1.3.4-beta Pre-release
Pre-release

Bor v1.3.4-beta is a maintenance release containing some improvements and bug fixes. It implements PIP-35 which increases the minimum gas price to 30 gwei in transaction pool, miner and gpo (by @marcello33 in #1264). It also contains an upstream geth merge till v1.13.6 along with a few cherry-picked commits related to p2p.

Upstream Geth Merge

Misc

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

v1.3.3

12 Jun 08:15
625774f
Compare
Choose a tag to compare

Bor v1.3.3 introduces PIP-32 - Ability to prune ancient block data along with a few bug fixes and observability improvements.

Ancient block pruning

This version of bor enables node operators to prune the ancient/historical block data if required. Note that this is different from state pruning, which prunes unused/inactive state from the db. The aim is to remove historical block data (headers, body, and receipts) from the freezer database as they are no longer used for chain verification. This also means that your node will no longer be able to serve RPC queries for those blocks (RPC operators shouldn't ideally use this).

It is available as a sub-command bor snapshot prune-block [options...] and the number of blocks to keep (post pruning) is configurable via block-amount-reserved flag. More details and usage info can be found in the PR itself (#1216).

Important points to note:

  • This version is backwards in-compatible if pruning is performed (at least once) on the node.
  • This feature is only enabled in hash based storage scheme for now and won't work for path based scheme.

Huge shout-out to @jsvisa who initiated the efforts and did most of the implementation in bor.

Bug fixes

Observability / P2P

  • eth/internal: add debug.peerStats for stats related to all connected peers by @manav2401 in #1252
  • eth: broadcast block to static and trusted peers as well by @pratikspatil024 in #1258
  • eth/fetcher: modify queue limits for improving sync near chain tip by @manav2401 in #1260

Misc

New Contributors

Full Changelog: v1.3.2...v1.3.3

v1.3.3-beta3

10 Jun 07:06
Compare
Choose a tag to compare
v1.3.3-beta3 Pre-release
Pre-release

Bor v1.3.3-beta3 is a maintenance release containing fixes related to ongoing sync issues.

What's Changed

  • eth/fetcher: modify queue limits for improving sync near chain tip by @manav2401 in #1260
  • eth/gasprice: fix percentile validation in eth_feeHistory by @marcello33 in #1235

Full Changelog: v1.3.3-beta2...v1.3.3-beta3

v1.3.3-beta2

06 Jun 05:37
5b0805d
Compare
Choose a tag to compare
v1.3.3-beta2 Pre-release
Pre-release

The following fixes has been made on top of v1.3.3-beta.

What's Changed

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

v1.3.3-beta

30 May 09:10
Compare
Choose a tag to compare
v1.3.3-beta Pre-release
Pre-release

Bor v1.3.3-beta introduces PIP-32 - Ability to prune ancient block data along with a few bug fixes and observability improvements.

Ancient block pruning

This version of bor enables node operators to prune the ancient/historical block data if required. Note that this is different from state pruning, which prunes unused/inactive state from the db. The aim is to remove historical block data (headers, body, and receipts) from the freezer database as they are no longer used for chain verification. This also means that your node will no longer be able to serve RPC queries for those blocks (RPC operators shouldn't ideally use this).

It is available as a sub-command bor snapshot prune-block [options...] and the number of blocks to keep (post pruning) is configurable via block-amount-reserved flag. More details and usage info can be found in the PR itself (#1216).

Important points to note:

  • This version is backwards in-compatible if pruning is performed (at least once) on the node.
  • This feature is only enabled in hash based storage scheme for now and won't work for path based scheme.

Huge shout-out to @jsvisa who initiated the efforts and did most of the implementation in bor.

Bug fixes

  • eth/tracers: avoid data race when tracing block with bor tx by @easyfold in #1214
  • eth: explicitly commented the code were bor could get into snap-sync mode by @pratikspatil024 in #1243
  • ethstats: added error handeling in ethstats.go which prevents node to panic by @pratikspatil024 in #1249
  • eth: explicitly commented the code were bor could get into snap-sync mode 2.0 by @pratikspatil024 in #1247

Observability

  • eth/internal: add debug.peerStats for stats related to all connected peers by @manav2401 in #1252

Misc

New Contributors

Full Changelog: v1.3.2...v1.3.3-beta

v1.3.2

10 May 10:48
bade7f5
Compare
Choose a tag to compare

This is a maintenance release and fixes few bugs. It's advisable to upgrade bor to this version at the earliest.

Fixes

  • Hashing of state-sync transactions during rpc calls by @anshalshukla in #1207
  • Cancel pending downloader tasks before rewinding due to milestone mismatch by @anshalshukla in #1245
  • Cancel pending downloader tasks before rewinding by @cffls
  • core/rawdb: add sanity-limit to header accessor by @marcello33

Full Changelog: v1.3.1...v1.3.2

v1.3.2-beta-2

06 May 15:30
9e03209
Compare
Choose a tag to compare
v1.3.2-beta-2 Pre-release
Pre-release

Fixes:

Full Changelog: v1.3.1...v1.3.2-beta-2