beats.bitwrap.io · archive

Every track shared on beats.bitwrap.io is preserved in dated signed snapshots. Browse a moment in time, listen to what was on the catalogue then, or download the tarball for a permanent local copy. Each manifest is signed by the operator's Ed25519 key so you can independently verify the bundle hasn't been tampered with.

Snapshots

…

What's in a snapshot, and how do I verify it?

Each persisted snapshot is a content-addressed bundle of every share envelope at a moment in time, optionally including the cached audio renders and the SQLite track index. The sidecar JSON manifest carries:

archiveSha256 — sha256 of the .tgz bytes. Run shasum -a 256 file.tgz locally to compare.
signer + signature — Ed25519 signature over the canonical-JSON manifest (with signature stripped). Verify against /api/operator-pubkey.
envelopes.cids — every CID inside. Each envelope is itself content-addressed; signed envelopes inside are independently verifiable.

Restore against any beats-bitwrap server (yours or this one):

./scripts/process-rebuild-queue.py --restore beats-snapshot-YYYYMMDD-HHMMSS.tgz

Tracks reappear at ?cid=…; audio re-renders the first time a listener opens each one.

Archive policy

We may archive (purge from the live store) at any time and for any reason — usually to roll forward with changes that need older shares to be up-converted or re-rendered. Archived shares are not lost: they stay downloadable in the snapshots above, and visiting an archived ?cid=… URL surfaces a one-click recovery prompt that re-seals it from the latest snapshot.