Subscribe to updates

Snapshots

Download pre-built snapshots to sync an Injective node faster. Pruned snapshots for validators, archival segments for indexers.

Pruned Snapshots · Mainnet

EU (OVH)

Pruned, lz4 compressed, ~2-3 GB

# Check latest
curl -s http://injective-mainnet-snapshots.s3-website.gra.io.cloud.ovh.net/status.json | jq
Browse files ↗

Asia (GCS)

Pruned, lz4 compressed, ~2-3 GB

# Check latest
curl -s https://storage.googleapis.com/injective-mainnet-snapshots-asia/status.json | jq
Browse files ↗
Archival Segments · Mainnet

Archival data is stored in S3 segments by block height range. Deploy segment nodes behind a gateway proxy that routes queries to the correct node.

aws s3 ls --no-sign-request s3://injective-snapshots/mainnet/subnode/
SegmentHeight RangeVersionDisk
00730 -73Mv1.12.142 TiB
738073M -80Mv1.12.17 TiB
808880M -88Mv1.13.37 TiB
889888M -98Mv1.13.37 TiB
9810798M -107Mv1.14.07.5 TiB
105116105M -116Mv1.15.07.5 TiB
119143119M -143Mv1.17.016 TiB
138150138M -150Mv1.17.25.8 TiB
150181150M - 181M-Coming soon
Usage
Read first: Before restoring a snapshot during a chain upgrade, follow the Coordinated Upgrades Guide for binary verification, cosmovisor setup, and rollback procedures.
# Stop the node
sudo systemctl stop injectived

# Back up validator state
cp ~/.injectived/data/priv_validator_state.json ~/priv_validator_state.json.bak

# Remove old data and extract snapshot
rm -rf ~/.injectived/data
wget -O snapshot.lz4 <SNAPSHOT_URL>
lz4 -d snapshot.lz4 | tar xf - -C ~/.injectived/

# Restore validator state and restart
cp ~/priv_validator_state.json.bak ~/.injectived/data/priv_validator_state.json
sudo systemctl start injectived

Note: Snapshots are not backend-agnostic. A goleveldb snapshot will not work on a pebbledb node. Chain data grows ~10-15 GB/day; pruning is recommended every 300-400 GB.