github maticnetwork/bor v1.3.3

latest releases: v1.3.4-beta2, v1.3.4-beta
18 days ago

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

Don't miss a new bor release

NewReleases is sending notifications on new releases.