Quickstart
Three short paths. Pick one.
1. Talk to a public node
No local binary required. Public RPC is https://rpc.terp.network (cosmos.directory is stale — do not use it).
curl -s https://rpc.terp.network/status | jq .result.node_info.networkYou should see morocco-1 (mainnet). Public testnet is 120u-1:
curl -s https://testnet-rpc.terp.network/status | jq .result.node_info.networkMore queries: API playground and public endpoints.
2. Install terpd with the get script
The supported install path is the script at https://terp.network/get. It downloads a release binary for your platform (Linux/macOS, amd64/arm64) and can run the interactive bootstrap wizard (terpd bootstrap: init, genesis, state-sync, pruning, Cosmovisor, process supervisor).
# Interactive wizard (mainnet by default)
curl -sL https://terp.network/get | bash
# Public testnet (120u-1)
curl -sL https://terp.network/get | bash -s -- --network 120u-1
# Download the binary only — skip bootstrap
curl -sL https://terp.network/get | bash -s -- --setup-onlyPin a binary version with TERPD_VERSION (the script default is the current release, e.g. 5.2.0):
TERPD_VERSION=5.2.0 curl -sL https://terp.network/get | bash -s -- --setup-onlyVerify, then point the client at public RPC:
terpd version
terpd config set client chain-id morocco-1
terpd config set client node https://rpc.terp.network:443
terpd statusIntegrity notes for the installer: verify checksums. Build-from-source and Docker: Install.
3. Run your own node
- Prerequisites
- Prepare the node — or stay in the get-script wizard
- Catch up with state sync or a snapshot
- Keep it running with a process supervisor (systemd, pm2, or Cosmovisor)
Local disposable chains (not public testnet): Local network. Promoting a synced node to a validator: validator setup.
Mission and architecture.
Onramps, ZK-VM, composability.
Mainnet vs testnet connection.