Clone the public tools
No private repository or registry login is required.
White-glove testnet setup
One guided path. A node you can trust.
The installer asks every question first, shows the complete plan, makes only the approved changes, waits for synchronization, and produces a readiness report. No private source access is required.
Start here
Review first. Install second.
Use a supported Linux host with systemd, a dedicated data volume,
outbound Internet access, and git. Run the dry run
first; it does not change the machine.
git clone https://github.com/Roko-Network/roko-edge-tools.git
cd roko-edge-tools
./bin/roko-guided-install --time-stack timebeat --dry-run
# After reviewing the plan:
./bin/roko-guided-install --time-stack timebeatRead the plan
Confirm the role, runtime, clock owner, timeout, and report path.
Approve once
The installer performs the same reviewed steps shown in the dry run.
Agent-assisted setup
Give your agent one bounded job.
Copy this model-neutral handoff into your preferred coding or operations agent. It directs the agent to the same public installer and machine-readable manifests, requires a dry run, and keeps you in control of every system change.
Install a ROKO testnet node using the public, audited installer.
1. Clone or update https://github.com/Roko-Network/roko-edge-tools
2. Start at docs/time-authority/README.md and read docs/time-authority/docset.yaml. Follow only the Pagenbar route matching my role, then read installer/AGENT-INSTALL.md and the selected setup.aiwg.io/v1 manifest.
3. Ask me for every required choice first: hobbyist or professional scope, geography, node name, role, runtime, whether NTP will be served, Chrony or Timebeat, sync timeout, and report path.
4. Help me select at least two sources: ntp01.roko.network may be one; another must be a geographically close Stratum 1 or 2 authority in a different failure domain.
5. Inspect the referenced scripts. Do not improvise replacement commands.
6. Run bin/roko-guided-install with the chosen time stack and --dry-run.
7. Show me the complete plan and wait for my explicit approval before running it without --dry-run.
8. Report success only after the docset acceptance gate passes, including source strata, selectable source count, leap state, matching genesis, peers > 0, isSyncing false, stable peer identity, and advancing finality. Include the readiness-report path.
Do not expose RPC, open firewall ports, reset chain data, handle or reveal keys/licences, enroll a validator, bond funds, or enable authoring. A validator-candidate must remain non-authoring. Stop and ask before any action outside the printed plan.
For Timebeat, ask only for local package, licence, and reviewed configuration paths. Never request or print their contents. The configuration must use public or operator-owned authorities and must not depend on private ROKO timing topology.
Required policy: establish independent time authority before joining, keep at least two selectable sources, inspect their stratum and root distance, and never lower the ROKO two-source gate.Inspect, plan, install, verify
The agent may inspect the public manifests and scripts, run the dry run, execute the approved plan, and report evidence.
Choices and approval stay yours
All parameters are collected before execution. The agent must show the plan and receive explicit approval.
No keys, exposure, resets, or authoring
Private material and destructive or authority-changing work remain outside this installer.
Agent execution contractCanonical, model-neutral instructions.
Time authority docsetAIWG/Pagenbar routes for hobbyists, professionals, and agents.
Mainnet physical clocksHardware selection, mandatory active GNSS, installation, and acceptance.
Chrony manifestBootstrap, testing, and edge setup.
Timebeat manifestOfficial partner precision-time setup.
One question at a time
Choose the role that matches your goal.
The interactive installer offers these four roles and a native or Docker runtime.
Full node
Synchronizes and verifies the chain without retaining every historical state.
Plan for 200 GiBArchive node
Retains archive state for deep history, indexing, and public infrastructure.
Plan for 1 TiBObserver
Adds an interactive ROKO PTP² observer key after the full-node base is ready.
Plan for 200 GiBValidator candidate
Builds a fully synchronized, non-authoring peer ready for separate enrollment.
Plan for 200 GiBClock before chain
Use two independent sources and one clock owner.
The installer brings the clock into a known state before starting the node. Never run multiple clock-steering daemons together.
Bootstrap · testing · edge
Chrony
Chrony is the no-licence bootstrap path for testnet evaluation, edge nodes, labs, and initial synchronization. The installer configures diverse sources and waits for synchronization before starting the node.
./bin/roko-guided-install \
--time-stack chrony
ROKO official timing partner
Timebeat is ROKO Network's endorsed precision-time partner. Validator operators targeting eligibility for the maximum payout tier must run a licensed Timebeat deployment and join the Timebeat PTP² Mesh. The installer pins and verifies Timebeat 2.3.5 and installs an operator-reviewed profile using public or self-operated timing authorities.
./bin/roko-guided-install \
--time-stack timebeatGlobal bootstrap sources
Start close to home, then prove diversity.
National timing laboratories provide traceable Stratum 1 service
in several regions. Regional NTP Pool zones add network diversity,
but individual pool server strata vary. Use at least two selected
sources and inspect the result with chronyc sources -v.
Americas
time-a-g.nist.govtime-d-b.nist.govEurope
ptbtime1.ptb.deptbtime4.ptb.deAsia-Pacific
ntp.nict.jpasia.pool.ntp.orgAfrica/Oceania
africa.pool.ntp.orgoceania.pool.ntp.orgThe installer does not stop at “service active”
Finish only when the node proves readiness.
The final gate checks each condition and writes a report containing no keys or licence values.
Correct chain
Genesis must equal the published testnet identity.
Connected
At least one network peer must be visible.
Fully synced
isSyncing must be false before completion.
Stable identity
The local peer ID must remain stable.
Advancing finality
The finalized head must advance during verification.
Ready after reboot
Re-run the installer if a later reboot exposes a failed clock or mount gate.
Expected ROKO testnet genesis
0x0a2296f8f036f71437e8f6f2028ccbf0dc3dd6b3de9120fc15e43789c794e8bb
Need to customize?
Keep the guided path; open advanced references only when needed.
Storage layout, manual systemd construction, public gateways, snapshots, key custody, and validator activation are deliberately separate from the default install.
Advanced node operationsManual runtimes, storage, services, and diagnostics.
Upgrade an existing nodeCurrent immutable release, native and Docker rollouts, agentic upgrades, and rollback.
Validator enrollmentGenerate a public node package, self-submit permissionless staking calls, and verify finalized operation.
Agora self-joinImport the public package and review lock, bond, session, intent, maintenance, and exit calls.
Validator key custodyPractical HSM and protected-key guidance.
Snapshot bootstrapVerified normal and archive snapshots.
Installer source and manifestsAudit the scripts, AIWG manifests, and implementation notes.
Ready to join?
Install as a peer. Self-declare validator candidacy when ready.
Full, archive, and observer nodes can join immediately. Validator candidates complete the guided readiness gate, generate a public enrollment package on the node, and use Agora with their own wallet. Election and active operation remain finalized on-chain outcomes.