NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1863 by repository stars
Latest stable
v0.36.0
Last release 3 days ago
19 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
1265 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
The --core.grpc.port flag is now deprecated.
This release introduces two notable features:
:warning: ⚠️ ⚠️ In this release, bridge nodes (BNs) will no longer use RPC for syncing against the given core endpoint. It will now use gRPC via https://github.com/celestiaorg/celestia-node/pull/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.
:warning: ⚠️ ⚠️
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.
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 https://github.com/celestiaorg/celestia-node/pull/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.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.4...v0.21.5
Your coding agent can read these notes before it upgrades. Set up the MCP server →
feat(store): Add HasQ4ByHash method on store by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4035
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.3-mocha...v0.21.5-mocha
fix(test/swamp): fix TestConvertFromArchivalToPruned by @vgonkivs in https://github.com/celestiaorg/celestia-node/pull/4097
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.4-arabica...v0.21.5-arabica
Nothing published for this version
test(swamp/share): cover share module with swamp tests by @vgonkivs in https://github.com/celestiaorg/celestia-node/pull/4036
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.3-arabica...v0.21.4-arabica
Nothing published for this version
The --core.grpc.port flag is now deprecated.
This release introduces two notable features:
:warning: ⚠️ ⚠️ In this release, bridge nodes (BNs) will no longer use RPC for syncing against the given core endpoint. It will now use gRPC via https://github.com/celestiaorg/celestia-node/pull/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.
:warning: ⚠️ ⚠️
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.
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 https://github.com/celestiaorg/celestia-node/pull/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.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.3-mocha...v0.21.3-mocha
Nothing published for this version
The --core.grpc.port flag is now deprecated.
This release introduces two notable features:
:warning: ⚠️ ⚠️ In this release, bridge nodes (BNs) will no longer use RPC for syncing against the given core endpoint. It will now use gRPC via https://github.com/celestiaorg/celestia-node/pull/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.
:warning: ⚠️ ⚠️
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.
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 https://github.com/celestiaorg/celestia-node/pull/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.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.2-arabica...v0.21.3-arabica
This release introduces two notable features:
This release introduces two notable features:
:warning: ⚠️ ⚠️
In this release, bridge nodes (BNs) will no longer use RPC for syncing against the given core endpoint. It will now use gRPC via https://github.com/celestiaorg/celestia-node/pull/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.
:warning: ⚠️ ⚠️
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.
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 https://github.com/celestiaorg/celestia-node/pull/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.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.1-arabica...v0.21.2-arabica
fix(share/shwap/p2p/bitswap): set archivalPool ctx by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4052
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.21.0-arabica...v0.21.1-arabica
fix(goreleaser): tag_sort by @cristaloleg in https://github.com/celestiaorg/celestia-node/pull/3972
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.4-arabica...v0.21.0-arabica
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is a security patch release, please upgrade as soon as possible.
This is a security patch release, please upgrade as soon as possible.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.3...v0.20.4
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is a security patch release for the mocha network, please upgrade as soon as possible.
This is a security patch release for the mocha network, please upgrade as soon as possible.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.3-mocha...v0.20.4-mocha
Nothing published for this version
This is a security patch release for the arabica network, please upgrade as soon as possible.
This is a security patch release for the arabica network, please upgrade as soon as possible.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.3-arabica...v0.20.4-arabica
Nothing published for this version
Nothing published for this version
Nothing published for this version
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958, fixing the state.Su
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958, fixing the state.SubmitPayForBlob endpoint.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.2...v0.20.3
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958.
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.2-mocha...v0.20.3-mocha
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958.
This patch release fixes a JSON serialisation error with libshare.Blob via https://github.com/celestiaorg/celestia-node/pull/3958.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.20.2-arabica...v0.20.3-arabica
Nothing published for this version
Nothing published for this version
the -experimental-pruning flag will soon be deprecated in favour of pruning becoming the default mode for all node types, requiring users to pass `-ar…
NOTE: v0.18 and v0.19 are skipped for mainnet
Hey everyone, this is quite a mammoth of a release, so please hang tight. We have two major changes packaged in this release:
The migration period for this release is quite tight (a bit longer than 2 weeks), so we urge all node operators to upgrade to this version and re-sync against the network by December 2nd.
As this release is API-breaking, we also urge all integrations to migrate to this new version by December 2nd. (The list of API breaks can be found below).
This release features Shwap(CIP-19), a protocol-breaking feature that brings massive optimizations to disk usage(16x) and data access latencies. The new protocol is not backwards compatible with the currently deployed protocol and software.
Both protocols will run side-by-side for about a two-week transition period, from November 20 to December 2. During this period, node operators should migrate to the new version. At the end of the period, posted historical and recent data will no longer be available on the old protocol.
Migration requires resyncing the node from scratch, as it now contains a new storage format.
Migration Steps over the old node:
.celestia-<type>) => rm -rf inverted_index index data transients blockskeys directory to preserve peer and chain identity keys in placeBlockstoreCacheSize entry from [Share.EDSStoreParams] section to just [Share]and remove GCInterval, RoutingTableRefreshPeriodcelestia initcelestia startIf the old node has to be kept running - initiate and start the new version in a different directory:
celestia init --node.store <new_path>celestia start --node.store <new_path>This release contains an upgrade to the celestia-app version (to v3). v3 will only be live on the mainnet in mid-December, but this release contains the requirements for compatibility with the upgrade.
Notable API breaks include:
blob share and state modules via the deduplication of types (via [#3782](https://github.com/celestiaorg/celestia-node/pull/3782))share module now takes height instead of the full ExtendedHeader (via [#3870](https://github.com/celestiaorg/celestia-node/pull/3870))Comprehensive list of API breaks:
GetSharesByNamespace renamed to GetNamespaceDatashare module returns shwap.NamespaceData for the GetNamespaceData methodshare module now takes height (uint64) instead of the full ExtendedHeader for all methodsshare and blob modules now use the go-square v2 libshare.Namespace (from https://github.com/celestiaorg/go-square/tree/v2.0.0) instead of the old share.Namespace for all methodsstate module now uses the go-square v2 libshare.Blob type (from https://github.com/celestiaorg/go-square/tree/v2.0.0) instead of the old one from the state moduleblob package now embeds the new go-square v2 libshare.Blob type mentioned above in the blob.Blob struct instead of the old v1 type.What to look out for in the following releases:
-experimental-pruning flag will soon be deprecated in favour of pruning becoming the default mode for all node types, requiring users to pass -archival to retain block history beyond the sampling windowGetRangeByHeight call by @renaynay in https://github.com/celestiaorg/celestia-node/pull/3828v by @renaynay in https://github.com/celestiaorg/celestia-node/pull/3787Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.17.2...v0.20.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.