Environment Installation

This page is the dev environment checklist. Deep install and node configuration live in the network guides — follow those for production validators.

Prerequisites

Install terpd

Choose one:

1. Terp Installer — curl script with checksum verification
2. Node install guide — source, release binary, or Docker
3. Quick path — Quick start if you only need CLI + public RPC

Verify the binary:

terpd version
which terpd

Prefer comparing release checksums before you trust a downloaded binary: Verify.

Configure environment

Home directory

Default daemon home is typically under ~/.terp or ~/.terpd depending on build/flags. Override anytime:

terpd init my-moniker --chain-id morocco-1 --home $HOME/.terpd

See Configure for app.toml / config.toml layout and minimum-gas-prices.

Chain selection

Public genesis, peers, and snapshots: Public endpoints.

Keyring backend

# Interactive (default on many installs)
terpd keys add dev-key

# CI / headless (weaker security — never for mainnet funds)
terpd keys add ci-key --keyring-backend test

Verify installation

# Binary responds
terpd version

# Can reach a public node (mainnet example)
terpd status --node https://rpc.cosmos.directory/terpnetwork

# Key exists
terpd keys list

Next steps

Related concepts

• Hardware — operator sizing mindset
• Software — stack overview
• Trustlessness — verify binaries and state

Further reading

• Install
• Configure
• Genesis
• Libraries
• Integrity