Skip to content
LogoLogo

Terp Network operates multiple network instances, each serving a distinct purpose in the development and production lifecycle.

Mainnet (morocco-1)

The production network. Real assets, real validators, real applications.

  • Chain ID: morocco-1
  • Consensus: CometBFT with bonded proof-of-stake
  • Validators: Decentralized set securing the network
  • Governance: On-chain proposals control parameters, upgrades, treasury
  • Asset: uthiol (native fee token), IBC-connected assets

Connect via: Network guide

Testnet (120u-1)

Public testnet. Used for:

  • Smart contract testing before mainnet deployment

  • Validator dry-runs

  • Integration testing with IBC partners

  • Application prototyping

  • Chain ID: 120u-1 (there is no 90u-4 network)

  • RPC: https://testnet-rpc.terp.network

  • Faucet: Faucet

  • Genesis: https://s3.terp.network/snapshots/testnet/120u-1/genesis.json

  • Install: curl -sL https://terp.network/get | bash -s -- --network 120u-1

Localnet

A single-node or multi-node network running entirely on your machine. Used for:

  • Development and debugging
  • CI/CD pipelines
  • Smart contract integration tests
  • Relayer configuration testing

Quick Start

# Using terpd
terpd init my-local --chain-id localterp
terpd start
 
# Or with O-Line (ephemeral deployment)
oline deploy --profile localnet

Localnet with faucet scaffold — guide in progress. See network guides for current instructions.

O-Line Deployments

The O-Line tool automates ephemeral node deployment for CI/CD and testing workflows, supporting all three network types with profile-based configuration.

Network Comparison

FeatureMainnetTestnetLocalnet
Real valueYesNoNo
Validator setLivePermissionedSingle node
FaucetN/AAvailableConfigurable
IBC peersLive channelsTest channelsNone by default
State syncAvailableAvailableN/A
SnapshotsAvailableAvailableN/A
GasReal uthiolFaucet uthiolSimulated

Network topology diagram scaffold — a visual showing how mainnet, testnet, localnet relate, with IBC connections to counterparty chains. Arrows for relayers, boxes for validators.

Running a Node

Anyone can run a node on any of these networks. See the node guides for:

  • Hardware requirements
  • Installation from source
  • State sync configuration
  • Validator setup
  • Snapshot restoration

Network Parameters

Key parameters shared across networks:

ParameterMainnet ValueNotes
Min gas fee0.05uthiolConfigurable per validator
Block time~6 secondsCometBFT default
Max validators100Governance-adjustable
Unbonding period21 daysSecurity parameter
Governance period7 daysProposal voting window