mocha-5 testnet node in ~5 minutes instead of a multi-hour full sync.
What’s inside
data/folder from a livecelestia-appd v9.0.6-mochanode running on PebbleDB with aggressive pruning (custom/keep-recent=100/interval=19,indexer=null).snapshots/sub-dir included so your node can immediately serve state-sync to peers.
genesis.json · addrbook.json
Restore
celestia-appd on a partial data/. Your signing state then stays in
~/.celestia-app/priv_validator_state.json.backup: fix the cause and run the command again starting
from the rm -rf line.
Verify (optional)
.sha256 file is fetched first: it names the dated archive it belongs to, so the file you download is
always the one the checksum is for, even if a new snapshot is published during a long download. The last line should read <archive name>: OK.
FAQ
How often is the snapshot updated?
How often is the snapshot updated?
Every 4 hours. The last 2 snapshots are kept online.
What db backend?
What db backend?
pebbledb - Celestia’s default since v9.Can I use this to bootstrap a validator?
Can I use this to bootstrap a validator?
Yes. The snapshot contains only chain state - no keys. Your existing
config/priv_validator_key.json and data/priv_validator_state.json stay yours.Does the snapshot include state-sync chunks?
Does the snapshot include state-sync chunks?
Yes. After restore, your node can also serve
state-sync to downstream peers (snapshot-interval=1500).