Run a node

Run a node. Secure the network

Operate a validator on the network that secures the infrastructure of nations. Permissionless, with clear requirements and honest economics.

Requirements Quickstart

Requirements

Requirements.

What it takes to run a validator: CPU, memory, disk, bandwidth, OS, and a supported client. Indicative testnet figures — the confirmed matrix lives in the docs.

CPU8 cores// indicative — confirm

RAM32 GB// indicative — confirm

Disk2 TB NVMe// indicative — confirm

Bandwidth100 Mbps symmetric// indicative — confirm

Full node requirements

Security economics

Economics.

Rewards exist to fund the network's security, not to advertise a return. Slashing and jailing protect the network from faulty or dishonest operators; uptime is a duty, not a bonus.

Rewardssecurity-budget funded// indicative — confirm

Slashingfor equivocation / faults// indicative — confirm

Uptime target—// indicative — confirm

Epoch length—// indicative — confirm

Node economics — rewards, slashing, uptime

Quickstart

Quickstart.

A single command brings up a testnet node. The full, confirmed guide lives in the docs — read it before running anything beyond testnet.

# Start a testnet validator node (testnet)
docker run --name oss-node oss/node:testnet \
  --network testnet --rpc-url $OSS_RPC_URL

Open the quickstart Full node guide

Client diversity

Client diversity.

No single client should secure the network alone. Running independent implementations means a bug in one cannot halt or split the chain — neutrality and resilience depend on it.

Why it matters

A monoculture is a single point of failure. The supported clients are listed in the requirements; choosing a minority client strengthens the whole network. Confirmed, versioned client builds live in the docs.

Supported clients

Run a node. Secure the network.

Clear requirements, honest economics, and a one-command testnet start.

Run a node Open the explorer