celestiaorg/celestia-app v10.2.0-mocha on GitHub

Upgrade Notice

This minor release is for Mocha (mocha-5). It adds features and fixes on top of v10.1.0-mocha.
Validators are recommended to run the following command with the new binary to add missing fields and their documentation to config.toml:

celestia-appd config sync --home ~/.celestia-app

Use your node's home directory if it differs. Existing values are preserved, and a backup is created before changes. Add --dry-run to preview additions. Synchronization does not run automatically on startup.

For nodes already running v10, stop the node, replace the binary, and restart using the existing home and database. If upgrading from v9, follow the coordinated v10 activation process in the v10 upgrade notes; use the multiplexer build while the chain is on v9. Source builds require Go 1.26.6.

Upgrade from v9

Download the celestia-app archive for your platform from this release and verify it against checksums.txt. Use the multiplexer build, not celestia-app-standalone, while Mocha is on v9. Source builds require Go 1.26.6; use make install from this release tag.
Stop your node, replace celestia-appd, and restart with the same node home and database. Check that celestia-appd version reports v10.2.0-mocha and the node resumes syncing and, for validators, signing.
Leave the node running. The multiplexer switches to v10 and runs migrations automatically at activation. Do not use Cosmovisor for this upgrade.

Follow the Mocha upgrade announcement for timing. Check signalling progress and the pending activation height on your Mocha node:

celestia-appd query signal tally 10
celestia-appd query signal upgrade

Validators should signal only after completing their preparation:

celestia-appd tx signal signal 10 --from <validator-account-key> --chain-id mocha-5

Add your usual fee, node, and home flags.

RPC and storage

Heavy RPC requests share a limit of 20 concurrent requests, configurable through [rpc] max_concurrent_heavy_requests in config.toml. Clients should retry busy responses with backoff: HTTP GET 503, JSON-RPC errors, or gRPC ResourceExhausted.
Blockstore compaction is optional and disabled by default. Set [storage] compact = true to reclaim space after pruning; compaction_interval defaults to 10000 blocks. Archival nodes must keep min-retain-blocks = 0 in app.toml.
The multiplexer now exits if an embedded app fails. Check that your service manager restarts the node and alerts on repeated failures.

Supported operating systems

See the release README.

Tested in CI: Ubuntu 24.04 LTS on x86_64.
Prebuilt binaries: Linux and macOS, amd64 and arm64. 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.
Changes since the previous release: none.

What's Changed

Add the Cosmos gRPC reflection service (#7860).
Allow Fibre downloads without a keyring; uploads still require one (#7863).
Use go-square v4.0.1 for canonical BlobTx validation, removing duplicate app checks while preserving consensus acceptance rules (#7879).
Fix compilation on 32-bit targets and add a MIPS build check (#7872).
Add the explicit config sync command and upgrade celestia-core to v0.42.1 (#7880).

Full Changelog: v10.1.0-mocha...v10.2.0-mocha