Use the ROKO Network
This is the public entry point for ROKO users, node operators, time-service operators, and application developers.
ROKO is currently a testnet. Chain state, endpoints, and enrollment rules can change before mainnet. Read the checked network-manifest.1356891f0708.json before following an operational guide.
The September 10 network update explains the latest managed correction, public package availability and maintenance checks. The public RPC node runs 3.0.0-dev-764f8c18114; the public download selector still serves the September 8 nightly. Runtime spec 286 remains active on the configured testnet. Select software using the upgrade guide and verified artifact metadata rather than treating these three states as one release. The v1.1.0 package and v1.0.22 validator notice remain historical references.
Choose a path
| I want to… | Start here |
|---|---|
| set up a wallet and claim test ROKO | Wallets and faucet |
| review proposals, conversations, votes, and stake | Governance and Agora |
| use public RPC, WebSocket, boot, or NTP services | Public services |
| choose a full, archive, validator, or observer role | Node roles |
| install a full, archive, observer, or candidate node | Guided node install |
| upgrade an existing native or Docker node | Upgrade a node |
| help distribute snapshots and releases | BitTorrent seeding |
| prepare an isolated validator | Run a validator |
| choose affordable validator key protection | Validator key custody |
| join the PTP² mesh without authoring blocks | PTP² observer |
| serve time to computers on my private LAN | Private NTP server |
| query and use nanosecond temporal data | Temporal RPC quickstart |
| read committed ROKO time from Solidity | Temporal EVM precompile |
Three protocols, three jobs
- NTP disciplines a computer's system clock. ROKO provides a public NTPv4 source at
time.roko.network. - ROKO PTP² measures and exchanges clock observations between ROKO libp2p peers. It is not IEEE 1588 PTP.
- Temporal JSON-RPC exposes mesh quality and canonical on-chain nanosecond timestamps to applications.
Joining one does not silently enable the others.
Public-document boundary
These guides intentionally contain only public DNS names, public ports, public chain identity, public peer identity, released software references, and generic topologies. They do not describe ROKO's origin addresses, internal hosts, private peer layout, management network, tunnels, credentials, or secret-store layout.
Never post a seed phrase, private key, node-key file, credential, private topology, or unredacted service log in a support issue.
Validation status
The public RPC identity, finalized runtime, package metadata and governance availability were rechecked on 2026-09-10. See the dated manifest and update for the package/deployment gap and remaining qualification limits. Bootstrap, test, and edge commands target Linux with systemd and Chrony. Timebeat is the endorsed official validator timing partner, and maximum-tier validator payout eligibility requires a licensed Timebeat deployment plus participation in the Timebeat PTP² Mesh. Install the node from the public GHCR image or from the checksum-verified native binary distributed by HTTPS or BitTorrent. Public node operation never requires access to the private source repository. The current chain-spec bootstrap is testnet-only.
Recheck the public RPC identity against the manifest:
node scripts/validate-public-network.mjs