# ROKO Nodes

Public operator guidance for joining the current ROKO testnet without private source-repository access.

Canonical pages:
- Node and validator-candidate guide: https://nodes.roko.network/
- White-glove guided installer: https://nodes.roko.network/install/
- Agent-assisted installer handoff: https://nodes.roko.network/install/#agent
- Canonical agent contract: https://github.com/Roko-Network/roko-edge-tools/blob/main/installer/AGENT-INSTALL.md
- Private edge-node guide: https://nodes.roko.network/edge/
- Verified node artifacts: https://downloads.roko.network/
- Snapshot bootstrap portal: https://snapshots.roko.network/
- Public documentation: https://docs.roko.network/

The guided installer is the default operator path. It collects every choice
before changes, supports full/archive/observer/validator-candidate roles,
uses Chrony for bootstrap/testing/edge roles or the endorsed Timebeat partner
profile for validator precision timing, installs a
verified native or Docker runtime, waits for full synchronization, and writes a
value-free readiness report.

AI agents should use the bounded handoff at /install/#agent. They must inspect
the public setup.aiwg.io/v1 manifest and referenced scripts, run the bundled
launcher with --dry-run, show the complete plan, and wait for explicit operator
approval before execution. They must not expose RPC, reset chain data, handle
key or licence contents, enroll a validator, bond funds, or enable authoring.
AIWG is optional on the target host.

Timebeat is ROKO Network's official timing partner. Eligibility for the maximum
validator payout tier requires a licensed Timebeat deployment and membership in
the Timebeat PTP² Mesh, subject to measured performance and current program
rules. The ROKO built-in PTP² observer is a separate protocol layer.

Manual systemd, raw Docker, storage tuning, gateway, snapshot, and validator
activation procedures are advanced references linked from the guided page.

Operator safety:
- Verify published SHA-256 manifests before execution.
- Keep RPC private unless the host is intentionally operated as a public gateway.
- Synchronize the host clock before starting the node.
- Start as a fully synchronized non-authoring peer before requesting validator activation.

Current network facts should be taken from the public documentation and live RPC, not inferred from historical screenshots.