v0.14.0

Pruning

This release introduces block (or sample) pruning via the --experimental-pruning flag. When --experimental-pruning is enabled, light nodes will prune samples, while full and bridge nodes will prune blocks older than 30 days ( the availability window defined in https://github.com/celestiaorg/CIPs/blob/main/cips/cip-4.md).

Full and bridge nodes that run with pruning enabled will support serving samples and blocks within the availability window, and will continue to advertise on the full topic, whereas full and bridge nodes that upgrade to this version and do not enable pruning will retain all blocks and begin to advertise themselves on the new archival topic, signalling to the network that they are an "archival" node.

⚠️ Please note that this is an experimental feature. Once --experimental-pruning is enabled, it is not possible to go back to running as an "archival" node without resyncing from scratch or restoring from a snapshot. ⚠️

As a part of the pruning feature, it is now default behaviour for light, full and bridge nodes to additionally discover "archival" nodes in the network in order to maintain the ability to request blobs and blocks older than the availability window.

Discovery metrics

There are now two sets of discovery processes running simultaneously: one for archival peers and one for full. Discovery metrics have been broken to reflect that change, so now, full discovery-related metrics will have full_ prepended to the string.

E.g. discovery_amount_of_peers is now full_discovery_amount_of_peers for full peers and archival_discovery_amount_of_peers for archival peers.

State access via gRPC only

Via https://github.com/celestiaorg/celestia-node/pull/3359, it is now possible to perform all state-related queries over a gRPC connection to a core consensus node only. This means that it is no longer required to pass a --core.rpc.port when configuring celestia-node for state access. Instead, only the gRPC port is necessary (which is still configured to default to 9090).

This does not yet apply for bridge nodes!!! Bridge nodes still require the same core configuration setup as before (RPC port for block sync and gRPC port for state access).

What's Changed

BREAKING

FEATURES

BUG FIXES

MISCELLANEOUS

New Contributors

Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.13.7...v0.14.0