Terp Network Docs

Hardware

Physical infrastructure for Terp Network — nodes, validators, sensors, relayers, HSMs

Hardware

Hardware is the physical layer of Terp Network. Every interaction — from validating blocks to broadcasting transactions — runs on some hardware device.

Node Hardware

Anyone running a Terp Network node needs:

Full Node (Minimum)

ComponentRequirement
CPU2+ cores (x86_64 or ARM64)
RAM8GB+
Storage500GB+ SSD (NVMe recommended)
Network100Mbps+ stable connection
OSLinux (Ubuntu 22.04+, Debian 12+, NixOS)
ComponentRequirement
CPU4+ cores, 3GHz+
RAM16GB+
Storage1TB+ NVMe SSD
Network1Gbps with redundant links
OSLinux, minimized
HSMOptional (YubiHSM2, Ledger)

Sentry Node

Same as full node, but with:

  • Public IP with DDoS protection
  • Higher bandwidth allocation
  • Rate limiting configured

Hardware Security Modules (HSMs)

Validators can use HSMs to protect their consensus key:

  • YubiHSM2 — USB-connected, supports Ed25519 signing
  • Ledger — Cosmos app for transaction signing
  • SGX/TEE — future support for trusted execution environments

Specialized Hardware

Terp Network extends beyond validators:

HardwareRole
Relayer serverRuns IBC relayer software (low resources)
IPFS/storage serverContent-addressed storage for chain data
Sensor nodeIoT/edge devices using light client proofs
Communication relayMesh network or LoRaWAN connectivity
Broadcast nodeTransaction submission gateway

Hardware topology diagram scaffold — a diagram showing different hardware types in the Terp Network ecosystem: validator, sentry, full node, relayer, storage server, sensor. Show connectivity between them.

Hardware Security Considerations

  1. Physical access — keep validator hardware in a secure, locked location
  2. Network isolation — validators should not face the public internet directly (use sentries)
  3. Key storage — consensus keys should use HSMs or encrypted storage
  4. Backup — maintain offline backups of validator state

Further Reading

On this page