Juno Validator Node Snapshot

Block Height
Chain ID
Snapshot Timestamp
Indexer Mode
Prune Mode
3112022 juno-1 11 GB 24 minutes ago lz4 null 100/0/10 Custom Pruning Frankfurt juno_3112022.tar.lz4
3098267 juno-1 8 GB 1 day ago lz4 null 100/0/10 Custom Pruning Frankfurt juno_3098267.tar.lz4

Our Juno Snapshot Server Setup

We take a node snapshot every day. We then delete all the previous snapshots to free up the space on the file server.

The snapshot is designed for node opeartors to run an efficient validator service on Juno chain. To make the snapshot as small as possible while still viable as a validator, we use the following setting to save on the disk space. We suggest you make the same adjustment on your node too. Please notice that your node will have very limited functionality beyond signing blocks with the efficient disk space utilization. For example, your node will not be able to serve as a RPC endpoint (which is not suggested to run on a validator node anyway).

Since we periodically state-sync our snapshot nodes, you might notice that sometimes the size of our snapshot is surprisingly small.


pruning = "custom"
pruning-keep-recent = "100"
pruning-keep-every = "0"
pruning-interval = "10"


indexer = "null"

How To Process Juno Snapshot

Install lz4 if needed

sudo apt update
sudo apt install snapd
sudo snap install lz4

Download the snapshot

wget -O juno_3112022.tar.lz4 https://snapshots2.polkachu.com/snapshots/juno/juno_3112022.tar.lz4

Stop your node

sudo service cosmovisor stop

Reset your node. WARNING: This will erase your node database. If you are already running validator, be sure you backed up your priv_validator_key.json prior to running the the command. The command does not wipe the file. However, you should have a backup of it already in a safe location.

# On some tendermint chains
cosmovisor unsafe-reset-all

# On other tendermint chains
cosmovisor tendermint unsafe-reset-all --home $HOME/.juno

Decompress the snapshot to your database location. You database location will be something to the effect of ~/.juno depending on your node implemention

lz4 -c -d juno_3112022.tar.lz4  | tar -x -C YOUR_DATABASE_LOCATION

Restart your node

sudo service cosmovisor start

Remove downloaded snapshot to free up space

rm -v juno_3112022.tar.lz4

Make sure that your node is running

sudo service cosmovisor status
sudo journalctl -u cosmovisor -f

ADVANCED ROUTE: The above solution requires you to download the compressed file, uncompressed it and then delete the original file. This requires extra storage space on your server. You can run the following combo command to stream the snapshot into your database location. For advanced users only:

curl -o - -L https://snapshots2.polkachu.com/snapshots/juno/juno_3112022.tar.lz4 | lz4 -c -d - | tar -x -C YOUR_DATABASE_LOCATION

ALTERNATIVE ROUTE: We also have Juno state-sync service to help you bootstrap a node.