celestiaorg/celestia-app v10.4.0

on GitHub

Upgrade Notice

This release is intended for Mainnet (celestia). It introduces app version 10, including Fibre, and includes celestia-core v0.42.3 and Cosmos SDK v0.52.12.

All consensus node operators must install the v10 multiplexer binary before the v10 activation height. Read the major-version release notes and the operator instructions below before upgrading.

Upgrade existing mainnet nodes

Download the celestia-app archive for your platform and verify it against checksums.txt. Validators should also download the matching fibre archive. Source builds require Go 1.26.6; make install builds the multiplexer and make build-fibre-server builds Fibre.

While mainnet is still on v9, stop your node service, replace celestia-appd with the multiplexer build, and restart with your existing home and database. Confirm the node resumes syncing and, for validators, signing. The multiplexer embeds v9.0.8 and switches to v10 automatically at activation. Do not use the celestia-app-standalone build for the v9-to-v10 transition, and do not use Cosmovisor to perform it.

Coordinated activation

Activation is coordinated through x/signal; publishing or installing this release does not activate v10. Validators should signal app version 10 only after installing and checking their upgrade setup, following the network's upgrade coordination:

celestia-appd tx signal signal 10 --from <validator-account-key> --chain-id celestia <transaction-flags>

Once at least 5/6 of voting power has signalled and a MsgTryUpgrade succeeds, the mainnet upgrade is scheduled 232,616 blocks later (approximately seven days).

Review configuration before restarting

Use the new binary to preview and add missing configuration settings:

celestia-appd config sync --home ~/.celestia-app --fibre-home ~/.celestia-fibre --dry-run
celestia-appd config sync --home ~/.celestia-app --fibre-home ~/.celestia-fibre

Use your actual home directories. This updates the node's config/config.toml and Fibre's config/server_config.toml, preserves existing values, and creates backups before changes. Missing files are skipped. It does not run automatically at startup, update app.toml, or replace saved values with newer defaults. Review the additions and update deployment-managed configuration templates too.

Validators: prepare Fibre before activation

Fibre runs as a separate service. Follow the Fibre server guide to install and configure it before activation. Start the service and register its host only after the chain reaches app version 10.

• Enable the node's application gRPC endpoint (normally port 9090) and privval gRPC endpoint (normally 26669), and point Fibre at the correct validator node. Fibre connects to the node for signatures; it does not connect directly to an external KMS.
• Make the Fibre client-facing port (default 7980) publicly reachable. Application gRPC remains plaintext and should stay on the same host or a trusted private network.
• Store Fibre data and consensus node data ideally on separate disks. Review max_connections and max_concurrent_streams for the available RAM. See the capacity guidance.

KMS and signer transport

Any KMS may be used if it supports the privval SignRawBytes message and meets the median signing latency of 10 ms or less requirement. Monitor cometbft_privval_signing_latency_*; a node using a remote signer logs a warning when the median of its last 50 signatures exceeds 10 ms.

Remote Fibre-to-node signer connections require mutual TLS by default. Configure the node's server certificate, key, and client CA, plus Fibre's client certificate, key, and server CA. All three TLS fields must be set together on each side; incomplete node TLS settings fail startup. See the privval TLS guide and Fibre signing guide.

For a same-host plaintext signer connection, use a loopback IP literal, such as 127.0.0.1:26669, on both sides. The node does not accept localhost as a loopback exemption. Retain a working custom port if needed, but ensure the node listener and Fibre's signer address match. The Fibre client-facing TLS identity is automatically endorsed by the validator's consensus key and requires no operator-managed public certificate.

Validators: start and register Fibre after activation

Once the chain runs app version 10, start Fibre and confirm it is reachable before registering its public host. Sign registration with your validator's account key:

celestia-appd tx valaddr set-host <public-host>:7980 --from <validator-account-key> --chain-id celestia <transaction-flags>
celestia-appd query valaddr provider <celestiavalcons-address>
celestia-appd query valaddr providers

The host must be host:port, without a URL scheme or path. Clients discover servers through this registry; an unregistered server receives no Fibre traffic. Registration persists, so submit it again only when the address changes or its entry has been removed after leaving the validator set. See the registry guide.

RPC and storage operators

• Heavy RPC requests retain the shared default limit of 20 concurrent requests across HTTP, WebSocket, and gRPC. Configure [rpc].max_concurrent_heavy_requests as needed; clients should retry busy responses with backoff and backfill missed gRPC height notifications.
• Archival nodes must retain min-retain-blocks = 0. A nonzero value enables block pruning. New explicit blockstore compaction settings default off; review disk space and I/O capacity before enabling them.
• Fibre supports local and object shard storage. Changing backends does not move existing shards: retain access to the original data and object namespace until those shards are pruned. See the storage migration instructions.

Supported operating systems

See the canonical matrix in the release README.

• Tested in CI: Ubuntu 24.04 LTS (Noble Numbat) on x86_64.
• Prebuilt binaries provided: Linux (amd64, arm64), macOS (amd64, arm64), including the separate Fibre server. arm64 binaries are cross-compiled and are not executed in CI.
• Minimum glibc: 2.38 for Linux multiplexer builds. Ubuntu 22.04 and older are unsupported for these builds and fail with a glibc version mismatch. The separate Fibre binary requires glibc 2.34, which does not lower the consensus multiplexer requirement.
• Changes since v9.0.8: the celestia-app OS matrix is unchanged; Fibre archives are added for the same four platforms.

What's Changed

New Contributors

• @reflecttypefor made their first contribution in #7431
• @wangjingshuiku made their first contribution in #7733

Full Changelog: v9.0.8...v10.4.0