Download together
Keep the binary archive and SHA256SUMS file together.
Nightly distribution · ROKO testnet
Official node binaries and multi-architecture container images for full nodes, archives, observers, and approved validator candidates. No private source-repository access is required.
Nightly artifacts can change without notice and may require a chain reset. Keep validator keys and chain data separate from the OS disk.
Recommended installation
The public guided installer walks through role and runtime choices, detects x86_64 or ARM64, installs and verifies the clock stack, downloads the correct build, bootstraps the chain specification, creates a hardened non-authoring service, and waits for full sync. No private source-repository access is required.
Native Linux · architecture selected automatically
guided setup
$ git clone https://github.com/Roko-Network/roko-edge-tools.git
$ cd roko-edge-tools
$ ./bin/roko-guided-install --time-stack chrony --dry-run
$ ./bin/roko-guided-install --time-stack chrony
The Chrony command above is the bootstrap/testing/edge path. Validator candidates targeting eligibility for the maximum payout tier should use the endorsed Timebeat partner profile below and join the Timebeat PTP² Mesh.
The launcher collects all choices before changing the host. It offers native and Docker runtimes and full, archive, observer, and validator-candidate roles. Validator candidates remain non-authoring until the separate reviewed enrollment process.
Using an AI coding or operations agent? Copy the bounded agent handoff. It requires manifest and script inspection, a visible dry run, explicit operator approval, and the full readiness gate.
Advanced installation
Most operators should use the installer above. Open the manual downloads only for offline systems, image mirroring, or managed deployment tooling. The lower-level verified setup scripts remain available for operators who need to assemble their own workflow.
The torrent includes native and offline Docker artifacts for both architectures and uses this HTTPS service as a web seed. Verify the published SHA-256 checksums before execution.
Container images
Images are publicly readable without a registry login. Select the
tag matching the host architecture and record the resolved digest.
If registry access is unavailable, verify and download the offline
archive above, then run
bash install-roko-docker.sh --archive FILE.
shell
$ docker pull ghcr.io/roko-network/roko-node:testnet-latest-amd64
$ docker pull ghcr.io/roko-network/roko-node:testnet-latest-arm64
$ docker image inspect ghcr.io/roko-network/roko-node:testnet-latest-amd64 --format '{{index .RepoDigests 0}}'
$ docker run --rm ghcr.io/roko-network/roko-node:testnet-latest-amd64 --version
Integrity first
Keep the binary archive and SHA256SUMS file together.
sha256sum --check SHA256SUMS./roko-node --versionBootstrap the clock and fully join P2P before authoring.
Operator access + support
Submit the operator intake, or join the official ROKO Telegram or Discord and speak with the team. These channels provide onboarding and nightly artifact guidance; public access does not require source-repository membership. The public ROKO edge tools repository contains the public guided installer and optional diagnostics rather than node source. The guided installer prepares full, archive, observer, or non-authoring validator-candidate nodes. It does not generate validator/session/PTP² keys as a bundle, enroll a validator, or enable authoring; an observer key is inserted only through its separate interactive step. Approved candidates should complete the validator preparation and PTP² observer procedures separately.