Testnet operations

The chain repository supports a quick single-node shell testnet, managed Docker testnets, IBC testnets, and public testnet workflows.

Public partner path

If the goal is only to use the public network as a client:

1. Follow Getting started
2. Verify chain ID chain-1
3. Fund through the hosted faucet when available
4. Observe transfers in the explorer

To join the live validator set, follow Join the testnet as a validator for the current software boundary, bootstrap command, and reachability requirements.

Local paths

make sh-testnet

make docker-testnet-clean
make docker-testnet
make docker-testnet-stop

Use the repository’s current Makefile and release scripts for exact flags. Local defaults commonly use RPC http://localhost:26657, REST http://localhost:1317, gRPC localhost:9090, chain ID localchain-1, denom urp1, and prefix rp1.

Local development usually requires source or an internal operator environment. External partners should follow the validator join guide instead of building the private repository.

Public testnet

The public testnet is documented in the network reference. It is a live network, not a fixture: discover current pools, faucet state, validator readiness, bridge support, minimum gas price, and module parameters before claiming a flow works.

Testnet hygiene

• Never use production keys or mnemonics in a testnet home.
• Label demo and seeded transactions as demo data.
• Do not use synthetic benchmark modes as chain performance evidence.
• Reset local homes when a topology or genesis artifact no longer matches the plan.
• Keep public testnet endpoints separate from local environment variables.