Chain Bootstrap Snapshots

Prebuilt chain state so a node can recover or start near the tip without a full P2P sync. Pick the snapshot that matches your node's database backend. Always check the manifest first - bootstrap only helps if it is fresher than your node's current lag.

LMDB snapshot

Default backend - all current releases

Height

273909

Size

893 MB

Generated

2026-11-12T20:03:29Z

SHA256ee87e23cf0904874368aeb005447c0f2fb6702802b33ff0907797c54ea70096f .sha256

Download lmdb.tar.gz

SQLite snapshot

SQLite backend - requires v1.1.4+ and XEQM_DB_BACKEND=sqlite

Height

Size

- MB

Generated

SHA256- .sha256

Download sqlite.tar.gz

Restore from the LMDB snapshot

Default for every current release.

# Stop your node
sudo systemctl stop xeqm-<unit>

# Download and verify
wget https://bootstrap.xeqmlabs.com/lmdb.tar.gz
wget https://bootstrap.xeqmlabs.com/lmdb.tar.gz.sha256
sha256sum -c lmdb.tar.gz.sha256

# Extract and restart (syncs only the tail)
tar -xzf lmdb.tar.gz -C /var/lib/xeqm/<node-dir>/
rm lmdb.tar.gz lmdb.tar.gz.sha256
sudo systemctl start xeqm-<unit>

Restore from the SQLite snapshot

For nodes on the SQLite blockchain backend (v1.1.4+, XEQM_DB_BACKEND=sqlite). Do not mix the two: a SQLite node needs xeqm.db, not lmdb/.

# Stop your node
sudo systemctl stop xeqm-<unit>

# Download and verify
wget https://bootstrap.xeqmlabs.com/sqlite.tar.gz
wget https://bootstrap.xeqmlabs.com/sqlite.tar.gz.sha256
sha256sum -c sqlite.tar.gz.sha256

# Extract (xeqm.db + sqlite.db + ons.db + p2pstate.bin) and restart
tar -xzf sqlite.tar.gz -C /var/lib/xeqm/<node-dir>/
rm sqlite.tar.gz sqlite.tar.gz.sha256
# ensure the unit has XEQM_DB_BACKEND=sqlite in its environment, then:
sudo systemctl start xeqm-<unit>