Skip to content

Releases: celestiaorg/celestia-node

v0.22.0-beefy.bn.5

26 Feb 09:23
0a15bdf
Compare
Choose a tag to compare
v0.22.0-beefy.bn.5 Pre-release
Pre-release

v0.22.0-beefy.bn.4

26 Feb 09:21
2155ecb
Compare
Choose a tag to compare
v0.22.0-beefy.bn.4 Pre-release
Pre-release

v0.21.6-mocha

27 Feb 16:17
d60dda8
Compare
Choose a tag to compare
v0.21.6-mocha Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.21.5-mocha...v0.21.6-mocha

v0.21.6-arabica

25 Feb 14:07
5aed92c
Compare
Choose a tag to compare
v0.21.6-arabica Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.21.5-arabica...v0.21.6-arabica

v0.22.0-beefy.bn.3

21 Feb 15:31
1d3f6ff
Compare
Choose a tag to compare
v0.22.0-beefy.bn.3 Pre-release
Pre-release

v0.22.0-beefy.bn.2

21 Feb 12:12
d9cf345
Compare
Choose a tag to compare
v0.22.0-beefy.bn.2 Pre-release
Pre-release

v0.22.0-beefy.bn.1

17 Feb 15:14
6297a34
Compare
Choose a tag to compare
v0.22.0-beefy.bn.1 Pre-release
Pre-release

v0.22.0-beefy.bn

12 Feb 09:45
f58a189
Compare
Choose a tag to compare
v0.22.0-beefy.bn Pre-release
Pre-release

Changelog

v0.21.5

07 Feb 17:01
d571074
Compare
Choose a tag to compare

This release introduces two notable features:

  • Bridge node <> core endpoint sync over gRPC
  • Archival trimming of historic block files

Bridge node sync over gRPC

⚠️ ⚠️ ⚠️
In this release, bridge nodes (BNs) will no longer use RPC for syncing against the given core endpoint. It will now use gRPC via #3998.

Please make sure to pass a gRPC compatible (at least v3.3.0-arabica) core endpoint, passing the port via the new --core.port flag. The --core.grpc.port flag is now deprecated.

This also means there is no longer a RPCPort field in the core config. Instead, it is just Port which refers to the gRPC port of the core node.
⚠️ ⚠️ ⚠️

Additionally, it's possible to configure TLS for the gRPC connection via the following new flags:

      --core.tls                    Specifies whether TLS is enabled or not. Default: false
      --core.xtoken.path string     specifies the file path to the JSON file containing the X-Token for gRPC authentication. The JSON file should have a key-value pair where the key is 'x-token' and the value is the authentication token. NOTE: the path is parsed only if coreTLS enabled.If left empty, the client will not include the X-Token in its requests.

Archival trimming of historic block files

For archival node runners (both full node and bridge node), archival trimming will now be enabled by default, cutting archival node disk use for historic blocks in roughly half via #4028.

Note that the previous shwap release contains a condition to prevent nodes freshly syncing from storing the fourth quadrant files (.q4 files) for historic blocks that are outside the sampling window, but did not contain the functionality to clean up .q4 files once a block becomes freshly outdated, so disk use reductions are noticed only for the period between the completed full sync --> now.

What's Changed

New Contributors

Full Changelog: v0.20.4...v0.21.5

v0.21.5-mocha

07 Feb 16:46
4bdd1db
Compare
Choose a tag to compare
v0.21.5-mocha Pre-release
Pre-release

What's Changed

Full Changelog: v0.21.3-mocha...v0.21.5-mocha