- installation guide
- bridge node setup
- full node setup
- operating boundaries
- multiplexer
- fibre
- skill
- light node setup
- monitoring
- keys
- validator signaling
- blobstream orchestrator
- storage optimization
- snapshots
Celestia Testnet (Mocha-5) — Installation Guide
For a new non-running Mocha-5 app node. Existing nodes must follow App upgrade and multiplexer, not reinitialize their home.
Reviewed 2026-09-23: target v10.2.0-mocha, commit
3b77dc2f5b00e1a646a2e9dd98b5c024a0d9ad8a, app v10 activation 1082619.
Before activation the multiplexer runs app v9; binary version is not protocol
version. The upgrade guide defines RPC-first order, verification and the
pre-fork/pre-migration-only rollback boundary. Mainnet and Mocha-4 are separate.
POSTHUMAN operates app nodes, not Bridge/Light. DA v0.34.2-mocha and its Fibre
namespace are documented in the Bridge and
Light informational guides; Fibre/escrow activation
requires a separate decision.
Prerequisites
For Validator/Consensus Node (official requirements):
- Hardware: 32 cores, 32 GB RAM, 12 TiB NVMe planning envelope, 1 Gbps bandwidth; see capacity assumptions
- OS: Ubuntu 24.04 or equivalent with glibc >= 2.38; Ubuntu 22.04 and older unsupported
- Network: Stable internet connection
Note: These are official requirements for validators. For non-validator full nodes, lower specs may work but are not recommended for production.
1. Update System and Install Build Tools
2. Select the verified multiplexer artifact or toolchain
Prefer the checksum-verified official multiplexer archive and staging commands
in App upgrade and multiplexer. Do not select standalone
while Mocha-5 is still on app v9. Do not use Cosmovisor for this upgrade.
If building from source, install Go 1.26.6 through trusted distribution
channels and verify go version. Do not reuse the old v9 toolchain assumption.
3. Build from the pinned source (alternative to the official archive)
Use a new staging directory without deleting or replacing another checkout:
Require 10.2.0-mocha, the pinned commit and the multiplexer build tag.
Review the embedded historical assets as described in the upgrade guide.
Only after review, install the binary for this new non-running node;
existing nodes use the controlled upgrade workflow instead of this command:
Verify the effective installed binary path before creating a service. Avoid sharing an executable path with a mainnet or any running node.
4. Initialize the Node
Initialize with your node name and testnet chain ID:
This creates: ~/.celestia-app-mocha-5/
5. Download Genesis and Address Book
Important: Use the official Mocha-5 genesis and the listed community addrbook; verify chain identity before use:
6. Configure Node Settings
6.1 Set Minimum Gas Price
6.2 Configure Pruning (Recommended for testnet)
6.3 Disable Indexer (Saves disk space)
6.4 Enable Prometheus
6.5 Add Peers
The old POSTHUMAN endpoint ending in :28756 belonged to the retired
Mocha-5 source and must not be used. Select a current public peer, verify its
Mocha-5 identity and reachability, and replace every placeholder before use.
6.6 v10 configuration preflight
Before startup, follow Configuration preflight:
ensure the top-level app ABCI address matches proxy_app, preserve loopback
binds and keep priv_validator_grpc_laddr = "" when Fibre is not operated.
Do not blindly apply config sync or change ports to resolve a mismatch.
7. Create Systemd Service
Note: Service name is celestia-appd-testnet to distinguish from mainnet if running both.
8. Download and Apply Snapshot
POSTHUMAN does not currently publish a Mocha-5 snapshot. Use the verified
ITRocket feed at https://server-6.itrocket.net/testnet/celestia/. Check
.current_state.json, verify the live RPC identifies as mocha-5, download
the exact listed file before stopping the node, and validate the complete
archive with lz4 -t.
Before replacing validator data, preserve the local consensus key and newest
priv_validator_state.json. Never use signer state from a snapshot. Keep the
old data directory as rollback material until the restored node is synced and
verified.
9. Start the Node
10. Verify Node Status
Check Sync Status
Look for "catching_up": false when fully synced.
Check Block Height
11. Create or Restore Wallet
Optional operator-controlled onboarding, not part of an app upgrade. Keep wallet recovery material out of chat, logs and agent context. Never import or copy a consensus key through these wallet steps.
Create New Wallet
Save the mnemonic securely!
Restore Existing Wallet
Save Wallet Address
12. Get Testnet Tokens
Request testnet TIA from the faucet:
- Celestia Discord: https://discord.com/invite/celestiacommunity
- Go to #mocha-faucet channel
- Request tokens with your address
Check Balance
13. Create Validator
Optional new-validator transaction, requiring a separate operator decision; never repeat it for an existing validator upgrade. After sync and funding:
Useful Commands
Service Status
Stop Node
Node Info
Security
-
Firewall Configuration
-
Signer custody: Follow Keys and signer boundaries; preserve the existing key and newest signer state without exposing or moving them.
-
SSH Key Auth: Disable password authentication
-
Monitoring: Setup Prometheus/Grafana
Retirement boundary
There is no copy-paste validator uninstall procedure here. Decommissioning, data deletion, key handling or signer migration requires a separately reviewed plan with verified recovery evidence and duplicate-signer fencing. Never use installation or retirement steps as a database or signer-state rollback.
Resources
- Mocha-5 snapshots (ITRocket): https://server-6.itrocket.net/testnet/celestia/
- Mocha-5 RPC (ITRocket): https://celestia-testnet-rpc.itrocket.net
- Discord Faucet: https://discord.com/invite/celestiacommunity
- Official Testnet Docs: https://docs.celestia.org/nodes/mocha-testnet
Last Updated: 2026-09-23 | v10.2.0-mocha | App v10 height: 1082619 | Chain ID: mocha-5