ROKO edge nodes

Private local infrastructure for time-aware systems.

Run a ROKO edge node when you want your home, lab, robot fleet, or sensing environment to observe the mesh, use local RPC, and keep time-sensitive data anchored to infrastructure you control.

Launch with the guided installer See operator cases Peer-assisted downloads

ROKO edge node

Local RPC

LAN NTP

PTP² observer

Sensor ingest

Mesh watch

Privacy use case

Your devices should not need a third-party endpoint for every query.

An edge node lets wallets, automation, dashboards, and scripts query local infrastructure first. Public RPC remains useful for backup and comparison, but the default path becomes your own node.

Local RPC

Reduce metadata leakage.

Keep routine chain reads on loopback or a private LAN address. Avoid exposing unsafe RPC methods to the Internet.

Mesh observation

Verify from your vantage point.

Compare local peer health, finalized heads, and temporal quality against public status without depending on public status alone.

Private time

Serve LAN time locally.

Chrony can use approved upstreams, including ROKO public NTP, and provide a private NTP source for home or lab devices.

Data custody

Keep observations close.

Store local telemetry, robot events, and sensor readings where you can define retention, access, and publication rules.

Robotics, sensing, data gathering

Edge nodes are useful wherever local events need trustworthy ordering.

Robotics labs

Coordinate logs from controllers, cameras, lidar, test rigs, and operators against a common local time source before publishing selected data upstream.

Sensor networks

Timestamp field observations at the edge, preserve source identity, and periodically compare against ROKO temporal state.

Data acquisition

Keep raw measurements local while exporting signed summaries, hashes, or selected windows when the operation requires proof.

Home and lab automation

Give local systems a consistent private clock and a local chain vantage point without turning the edge node into a public service.

Private time model

Observe globally. Serve locally. Publish selectively.

Robots Sensors Laptops Gateways

Private LAN NTP + local RPC

ROKO edge node

P2P mesh + ntp01.roko.network

ROKO public time network

Edge launch commands

Start private, then add capabilities.

Install the node first from the public GHCR image or a checksum-verified native binary from direct download or torrent. Run it with local RPC first. Add LAN NTP only after Chrony is healthy. Add PTP² observer behavior only after the node is synced and you have a dedicated observer key workflow.

# Installation choices (no private repository required):
# https://downloads.roko.network/ — native HTTPS download or GHCR image
# https://downloads.roko.network/torrent — native binary torrent

# Chrony upstreams for the edge host
sudo tee /etc/chrony/sources.d/roko-edge.sources >/dev/null <<'CONF'
server ntp01.roko.network iburst
pool pool.ntp.org iburst maxsources 3
minsources 2
makestep 0.1 3
rtcsync
CONF

sudo systemctl restart chrony
chronyc waitsync 60 0.01
chronyc tracking

# Run the node with RPC kept local
/usr/local/bin/roko-node \
  --chain /etc/roko/roko-testnet-v2.json \
  --base-path /var/lib/roko \
  --name "<YOUR_EDGE_NODE_NAME>" \
  --rpc-methods Safe

Helper tools

Inspect node health without building a monitoring stack first.

The public ROKO edge tools repository includes quick diagnostics for local RPC, Chrony, systemd service state, disk usage, listeners, and sanitized support reports.

Open helper tools

git clone https://github.com/Roko-Network/roko-edge-tools.git
cd roko-edge-tools

./bin/roko-edge-doctor
./bin/roko-rpc-health --rpc http://127.0.0.1:9944
./bin/roko-time-health
./bin/roko-edge-report

Optional LAN time

Let approved devices use your edge node for NTP.

Replace the subnet and bind address with your actual LAN. Keep UDP/123 closed on public interfaces. Do not expose chrony control commands to the network.

# Add to the edge node Chrony config
allow 192.168.1.0/24
bindaddress 192.168.1.10
cmdport 0
ratelimit interval 3 burst 8 leak 2

sudo systemctl restart chrony
chronyc clients

# Linux LAN client
sudo tee /etc/chrony/sources.d/roko-edge.sources >/dev/null <<'CONF'
server 192.168.1.10 iburst prefer
CONF
sudo systemctl restart chrony
chronyc sources -v

Boundary

Edge nodes are not automatically validators.

An edge node can be private infrastructure, a PTP² observer, or a candidate on the path to validator readiness. Validator authority, payment, rewards, custody, and production hardware are separate enrollment steps. To run a node, submit the operator form or speak with the team in the official Telegram or Discord.

Fill out the operator form Join Telegram Join Discord Get nightly builds Peer-assisted downloads