mainnet snapshots

Node snapshots and the full-history archive of the mainnet network, at snapshots.gno.land. Chain id: ….

Other networks: Testnet (latest).

Latest snapshot

A pruned node's database (db/), cut every 30 minutes and kept 24 hours. It holds no key and no configuration.

Restore a node from it

Stop the node, move its db/ aside, then unpack the snapshot into the node's data directory, the directory that holds db/:

curl -fL <snapshot URL> | zstd -d | tar -x -C <data directory>

Or fetch it resumably over 8 connections, check it, then unpack it:

aria2c -x 8 -s 8 -c <snapshot URL>
curl -fLO <snapshot URL>.sha256
sha256sum -c <file>.sha256    # or: shasum -a 256 -c <file>.sha256
zstd -d -c <file> | tar -x -C <data directory>

Then start the node: it syncs the blocks since the snapshot's height from its peers.

Genesis

Full-history archive

The database of a node that keeps every height's state, synced every 6 hours. It is published as its files, each listed with its size and sha256 in archive/manifest.json, so a copy is brought up to date by fetching only the files that changed.

Fetch it, or bring a copy up to date (needs bash, curl, python3, and sha256sum or shasum):

curl -fsSLO https://snapshots.gno.land/fetch-archive.sh && bash fetch-archive.sh https://snapshots.gno.land <dir>

Run it again to update: only new or changed files are downloaded, an interrupted download resumes, and files the archive dropped are removed from <dir>/db. Stop the node that uses <dir> first.