Signed Snapshot Archive

Vorliq archives signed public snapshots so community members and future node operators can compare the latest signed state with recent historical signed states.

What Is Archived

Each archive item stores safe public metadata plus the signed public snapshot object: archive version, creation time, snapshot hash, signature status, public key id, chain height, latest block hash, confirmed transaction count, treasury balance, active node count, deployment commit, and the snapshot payload.

The archive does not contain private signing keys, admin tokens, environment dumps, raw logs, raw IP addresses, raw user agents, SSH keys, private wallet keys, or server paths.

Schedule And Retention

Production creates an archive during deploy after signed snapshot verification passes and installs a daily archive job for 04:00 Europe/London. The backend keeps the latest 30 archived snapshots.

Verify An Archive

node tools/verify_snapshot_archive.js https://vorliq.org
node tools/verify_snapshot_archive.js https://vorliq.org --list
node tools/verify_snapshot_archive.js https://vorliq.org --hash SNAPSHOT_HASH

The tool verifies the embedded signed snapshot, checks the archive hash, compares metadata against the embedded snapshot, scans for forbidden secret markers, and fails if the required signature is missing or invalid.

Key Rotation

If the signing key rotates, new archives should show the new public key id. Historical public keys should remain documented so older archived snapshots can still be verified.

Limits

Archived signed snapshots help prove public payload provenance and consistency over time. They do not prove legal status, financial value, banking status, investment quality, custody safety, or future network availability.