Normal node
Move fast.
Keep it lean.
Pruned chain state for validators, RPC services, and most production nodes.
- Finalized block
- —
- Package size
- —
- Created
- —
- State pruning
- —
Loading…
Mainnet distribution
Trusted starting points for ROKO operators. Download a verified snapshot, restore the chain database, and continue from a finalized block.
01 / SELECT
Choose the database profile your node will keep. Each package is published with a SHA-256 digest and excludes node identity, keystores, and secret material.
Normal node
Pruned chain state for validators, RPC services, and most production nodes.
Loading…
Archive node
Unpruned chain state for explorers, indexing, analytics, and historical queries.
Loading…
02 / SEED
ROKO torrents are public snapshots and release bundles. Seeding them helps other operators bootstrap faster; it does not expose validator keys, node identity, wallet material, or private RPC.
Start with the normal snapshot. Add archive snapshots only when you have spare disk and bandwidth.
BitTorrent checks transport pieces. Operators still verify the manifest SHA-256 before restoring a snapshot or running a binary.
Read the full seeding guideUse the public tools repo to check current torrent metadata every 30 minutes and add new artifacts to Transmission.
Get roko-edge-toolsgit clone https://github.com/Roko-Network/roko-edge-tools.git
cd roko-edge-tools
ROKO_SEED_PROFILES="normal releases" ./bin/roko-seed-refresh
03 / RESTORE
The archive contains the chain database only. Your node identity and keys remain yours.
Choose the normal or archive package above.
Compare the file against its published SHA-256 digest.
Stop the node and extract into its chain data directory.
Start the node and let it synchronize from the finalized block.
sha256sum -c <snapshot-file>.sha256