Open the walkthrough
Confirm the supported Linux host, storage, node role, and timing requirements in one guided place.
nodes.roko.network · testnet v2
Launch a ROKO node. Own your edge.
Run a private edge node for local RPC, LAN time, and mesh observation; or use the same path to prepare for validator authority with stronger evidence.
White-glove launch path
Let the guided installer do the careful work.
The installer collects every choice before it changes the host, shows a complete dry-run plan, installs the clock and verified node runtime, waits for synchronization, then writes a readiness report.
Review the dry run
The installer collects the role, runtime, clock path, timeout, and report location before making any change.
Approve once
One confirmed run prepares the clock, installs the verified node, creates the service, and waits for full synchronization.
Continue by evidence
Keep the readiness report. Validator candidates use it for the separate reviewed enrollment and activation process.
Live network status
Current participation.
Browser-side telemetry from the public ROKO RPC. Validator authority is derived from GRANDPA state; mesh peers are shown separately.
Checking public RPC…
Checking GRANDPA authority state…
Checking temporal mesh state…
https://rpc.roko.network
Faster bootstrap
Start from a verified snapshot—and help seed it.
Normal and archive snapshots are available through direct HTTPS, torrent files, and magnet URIs. The torrent includes an HTTPS web seed, so it can complete even when few community peers are online. Always verify the snapshot manifest and SHA-256 digest before restoring it.
# Download the profile manifest and payload together
jq -r '.archive.sha256 + " " + .archive.file' snapshot.json > SHA256SUMS
sha256sum --check SHA256SUMS
# Stop the node before restoring chain database files.
# Never restore keystores or node identity from a public snapshot.Why ROKO is different
Three layers interact on one host, but they do different jobs.
Node network
Full, archive, sentry, observer, and validator nodes exchange chain and P2P data.
Clock discipline
Chrony bootstraps test and edge hosts; partner validators use Timebeat for the production timing path.
Temporal layer
ROKO PTP² measures peer clock quality; Temporal RPC exposes time-aware data.
Why bootstrap the clock first?
The node consumes the host clock. Chrony provides a practical bootstrap for test and edge systems; Timebeat is the endorsed validator timing stack and maximum-payout eligibility path.
Why sentries?
Public RPC and Internet peer traffic are noisy. Sentries absorb that exposure so validator authority can stay isolated.
Why evidence?
Mainnet activation is easier to trust when a partner can show repeatable software, chain, clock, disk, peer, and monitoring checks.
Visual model
Keep public service exposure away from validator authority.
Internet clients + peers
Public full / sentry
Isolated validator
Verification
Do not proceed to validator work until these checks are boring.
Clock
chronyc trackingchronyc sources -vService
systemctl status roko-nodejournalctl -u roko-node --since todayRPC health
system_healthsystem_nodeRolesFinality
chain_getFinalizedHeadchain_getHeaderValidator candidate
Validator authority is an activation process, not a flag.
Starting with --validator does not make a node part of
the active validator set. Enrollment, session keys, bonding,
governance approval, and activation are separate steps.
- Full node provensync, finality, stable peer ID, restart evidence
- Clock readinessTimebeat PTP² Mesh for maximum-tier validators; Chrony for bootstrap and test evidence
- Custody reviewkey handling, encrypted storage, recovery path, no unsafe RPC exposure
- Hardware attestationCPU, RAM, NVMe, network, monitoring, recovery evidence
- Mainnet planningactivation timing, payment/reward terms, support channel
Production direction
Testnet can be flexible. Mainnet needs credible infrastructure.
CPU
8 modern physical cores minimum; 12-16 preferred.
Memory
32 GiB minimum; 64 GiB+ preferred.
Storage
Dedicated enterprise SSD/NVMe; 2 TB minimum, more for archive duties.
Network
Stable uplink with reviewed P2P reachability and firewall policy.
Clock
Timebeat partner profile for maximum-tier validators; monitored bootstrap sources for test and edge hosts.
Security
Full-disk encryption, TPM/secure boot where available, least privilege, recovery path.
Operator access + support
Want to run a ROKO node?
Submit the operator intake, or join the official ROKO Telegram or Discord and speak with the team. We distribute nightly node binaries through the downloads portal and container images through GHCR; public node onboarding does not require source-repository access.