secret-4 · mainnet · snapshot

Pruned chain data for a new node.

Pruned secret-4 snapshot (app state + Comet, compacted — same job as cosmprund). Cosmprund cannot open Secret 1.26, so this file is from our prune tool. Replace ~/.secretd/data (and .compute if present). Keep Cosmos keys and the enclave. First join or a node that was behind: extract and start. Not an archive.

Paste this

curl -fsSL -H 'Cache-Control: no-cache' -o restore.sh "https://mainnet-secret-snapshot.secret3.dev/restore.sh?t=$(date +%s)" && bash restore.sh

That one line replaces ./restore.sh and runs it. It verifies the snapshot, then replaces ~/.secretd/data. Your validator key and config.toml stay. It will not run on archive-00 or archive-01.

chain: secret-4
height: …
created: …
size: …
sha256: …

Files

The tarball does not contain the network seed. If this node is already above the snapshot, the script stops and leaves your data in place. An enclave that has executed a higher block has to be reset and registered again (secretd reset-enclave, then tx register auth) before an older snapshot can start. Same Cosmos keys. Need history? Use archive RPC/LCD, not this tarball.