Snapshots

To help node runners get their Radix node up and running faster, StakeSafe provides regularly updated ledger snapshots. Instead of syncing your node from genesis, you can restore from a recent snapshot and catch up to the network tip in a fraction of the time.

Snapshots are available at:

https://snapshots.stakesafe.net/

Benefits of Using Our Snapshots

• Faster Sync Times: Skip the lengthy process of syncing from genesis by restoring your node from a recent snapshot.
• Regularly Updated: Snapshots are refreshed on a regular basis, so you can start close to the current network tip.
• Reduced Load on the Network: Restoring from a snapshot reduces the load on public seed and full nodes during your initial sync.

How to Unlock a Download

Downloads are unlocked with a small XRD donation that supports StakeSafe's infrastructure costs. The process is fully automated and verified on-chain:

1. Click Download on the snapshot you want.
2. Send any amount of XRD to the donation account shown, using the exact message provided as the transaction message. This message is unique to your download request, so make sure to copy it exactly - it's how we match your donation to your request.
3. The page watches the Radix ledger live and polls automatically every 8 seconds. Once your transaction is confirmed on-chain (CommittedSuccess), your download link appears without needing to refresh - thanks to Radix's fast finality, this typically takes 10-30 seconds after your transaction is confirmed in your wallet.
4. Your download link stays valid for 7 days, and includes a SHA256 checksum so you can verify the integrity of the file after downloading.

tip

No need to keep refreshing the page - it checks for your donation automatically and reveals the link as soon as it's confirmed.

caution

Always verify the SHA256 checksum of the downloaded snapshot before restoring it, and only use it to bootstrap a node you fully control.

Thank you for contributing to the robustness and efficiency of the Radix network.

How to Restore a Snapshot

Once your download link works, here's how to put the archive to use on your own node.

1. Verify the checksum. Run sha256sum your-snapshot.tar.gz and compare it against the SHA256 value shown on the snapshot's card. Don't skip this on a multi-hour download.
2. Stop your node. sudo service babylon-node stop
3. Set your current data aside instead of deleting it, e.g. mv data data.bak, so you can roll back if anything goes wrong.
4. Extract into your node's home directory. tar -xzf your-snapshot.tar.gz -C /path/to/babylon-node. The archive unpacks into a data/ folder holding address_book, consensus_safety_store, executed_genesis, and state_manager - extract it there and nowhere else.
5. Check ownership. Make sure the new data/ directory is owned by the same user your node runs as.
6. Start your node. sudo service babylon-node start. It resumes syncing from the snapshot's epoch instead of genesis.

caution

A snapshot only ever contains ledger data - never your default.config or keystore (.ks) file. Leave those where they are; don't copy anything from the archive over them.

Choosing an Index Configuration

Every snapshot is built with one of two index configurations. Picking the right one now saves a full resync later.

A Radix node can maintain two optional indexes on its Core API as it syncs: local_transaction_execution_index, which answers transaction-status lookups by intent hash, and account_change_index, which answers "which transactions touched this account" history queries. Both are enabled by default on a stock node.

These indexes are built into the ledger data while it syncs - flipping the setting on an already-synced node does nothing until you resync from genesis, or restore a snapshot that was already built with the setting you want. That's why we publish both variants side by side instead of just one.

Which variant to download

Variant	Pick this if…
indexes enabled	You query Core API transaction status or account history - exchanges, wallet backends, explorers.
indexes disabled	You're running a validator or a plain full node and don't call those endpoints. Smaller archive, faster to build.

tip

Each snapshot card on snapshots.stakesafe.net shows both index states as pills, read straight from the archive itself - check those before downloading rather than assuming.

Running your own node and want to set this for future syncs yourself? The config keys go in default.config:

db.local_transaction_execution_index.enable = true | false (default: true)
db.account_change_index.enable = true | false (default: true)