Skip to content

Releases: celestiaorg/celestia-node

v0.21.3-mocha

28 Jan 10:08
5a5d450
Compare
Choose a tag to compare
v0.21.3-mocha Pre-release
Pre-release

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.3-mocha...v0.21.3-mocha

v0.21.3-arabica

23 Jan 13:31
396b45a
Compare
Choose a tag to compare
v0.21.3-arabica Pre-release
Pre-release

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 (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

Full Changelog: v0.21.2-arabica...v0.21.3-arabica

v0.21.2-arabica

21 Jan 11:44
5707592
Compare
Choose a tag to compare
v0.21.2-arabica Pre-release
Pre-release

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 (v3.3.0-arabica) core endpoint, passing the port via the --core.grpc.port flag.

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

Full Changelog: v0.21.1-arabica...v0.21.2-arabica

v0.21.1-arabica

20 Jan 11:58
bb68a13
Compare
Choose a tag to compare
v0.21.1-arabica Pre-release
Pre-release

What's Changed

  • fix(share/shwap/p2p/bitswap): set archivalPool ctx by @renaynay in #4052

Full Changelog: v0.21.0-arabica...v0.21.1-arabica

v0.21.0-arabica

20 Jan 10:28
cec0abe
Compare
Choose a tag to compare
v0.21.0-arabica Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.20.4-arabica...v0.21.0-arabica

v0.20.4

27 Nov 21:16
51b7943
Compare
Choose a tag to compare

This is a security patch release, please upgrade as soon as possible.

What's Changed

Full Changelog: v0.20.3...v0.20.4

v0.20.4-mocha

27 Nov 21:13
51b7943
Compare
Choose a tag to compare
v0.20.4-mocha Pre-release
Pre-release

This is a security patch release for the mocha network, please upgrade as soon as possible.

What's Changed

Full Changelog: v0.20.3-mocha...v0.20.4-mocha

v0.20.4-arabica

27 Nov 21:12
51b7943
Compare
Choose a tag to compare
v0.20.4-arabica Pre-release
Pre-release

This is a security patch release for the arabica network, please upgrade as soon as possible.

What's Changed

Full Changelog: v0.20.3-arabica...v0.20.4-arabica

v0.20.3

27 Nov 11:21
f5d9b32
Compare
Choose a tag to compare

This patch release fixes a JSON serialisation error with libshare.Blob via #3958, fixing the state.SubmitPayForBlob endpoint.

What's Changed

Full Changelog: v0.20.2...v0.20.3

v0.20.3-mocha

26 Nov 10:44
f019e10
Compare
Choose a tag to compare
v0.20.3-mocha Pre-release
Pre-release

This patch release fixes a JSON serialisation error with libshare.Blob via #3958.

What's Changed

Full Changelog: v0.20.2-mocha...v0.20.3-mocha