Skip to main content
Bootstrap a GenLayer Bradbury node in ~5 minutes instead of a multi-day full sync.

​
What’s inside

genlayer.db/ (PebbleDB) only - no keys, no logs, no operator data. ~320 MB compressed / ~850 MB extracted. Download: snapshots.unitynodes.com/bradbury/latest.tar.gz - refreshed every 6 hours. Full archive listing (all retained snapshots): snapshots.unitynodes.com/bradbury/

​
Restore

1

Stop your node

systemctl stop genlayer-node
2

Back up your existing chain DB

mv /opt/genlayer-node/data/node/genlayer.db \
   /opt/genlayer-node/data/node/genlayer.db.bak-$(date +%Y%m%d-%H%M%S)
Do not skip this - if anything goes wrong you can restore your original DB from the .bak-* folder.
3

Replace the chain DB

curl -fL https://snapshots.unitynodes.com/bradbury/latest.tar.gz \
  | tar -xzf - -C /opt/genlayer-node/data/node/
Your keystore/ and .env stay untouched - only chain state is replaced.
4

Start your node

systemctl start genlayer-node
You should see Node is synced!!! in journalctl -u genlayer-node -f within a few minutes.
5

Clean up the backup (once synced)

rm -rf /opt/genlayer-node/data/node/genlayer.db.bak-*

​
FAQ

On a node that has been running before, expect 1-5 minutes for the process to complete and Node is synced!!! to appear in the logs.On the very first run after a fresh installation, GenVM’s WASM runtime is precompiled and cached on disk - this one-time step adds 5-10 minutes to the first sync. Every subsequent restore reuses the cache and is fast.
If the new snapshot causes any problem, stop the service and swap the backup back in place:
systemctl stop genlayer-node
rm -rf /opt/genlayer-node/data/node/genlayer.db
mv /opt/genlayer-node/data/node/genlayer.db.bak-* \
   /opt/genlayer-node/data/node/genlayer.db
systemctl start genlayer-node
Your node will resume from the exact state it was in before the restore.
Every archive is published with a matching .sha256 file. Download both and check:
curl -fLO https://snapshots.unitynodes.com/bradbury/latest.tar.gz
curl -fLO https://snapshots.unitynodes.com/bradbury/latest.tar.gz.sha256
sha256sum -c latest.tar.gz.sha256
Expected output: latest.tar.gz: OK. If it prints anything else, delete the file and download again.
A new snapshot is created every 6 hours at 00:00, 06:00, 12:00, and 18:00 UTC. Only the last 4 versions are kept; older ones are removed automatically. The latest.tar.gz link always points to the newest one.
The archive contains only the genlayer.db/ directory (public chain state, PebbleDB LSM files). It does not contain any keys, wallets, .env, logs, hostnames, IPs, or operator identity.The restore procedure replaces only the genlayer.db/ folder inside your data directory. Everything else on your node - keystore/, operator-keystore.json, .env, configs/, logs/, systemd unit, running processes - is left completely untouched.