Gnoland
- installation guide
- links
- snapshots
- contributions
Gnoland Topaz Snapshot
POSTHUMAN publishes a verified LZ4 snapshot from a dedicated non-signing Topaz RPC node.
- Latest archive: https://snapshots-gnoland.posthuman.digital/gnoland_topaz-1-latest.tar.lz4
- SHA-256: https://snapshots-gnoland.posthuman.digital/SHA256SUMS
- Metadata: https://snapshots-gnoland.posthuman.digital/snapshot.json
The archive contains only db/ and wal/. It never contains secrets/,
configuration, genesis, or validator signer state.
Restore
Set the data directory used by your service:
Stop the service and back up identity, configuration, and genesis:
Download and verify the archive before replacing data:
After successful verification, preserve the old database and restore the new one:
Verify chain, progress, and service health:
Keep the old db/ and wal/ until the restored node is synced and stable.
For a validator, independently verify recent signatures before deleting the
rollback copy.
AppHash mismatch recovery
If the node crashes with an AppHash mismatch, preserve logs and the current
db/ + wal/ for forensics. Restore only those directories from a known
healthy backup or this verified snapshot. Never overwrite validator keys,
node identity, configuration, genesis, or signer state.