Arweave Archive Policy

Purpose

Arweave archive is a mirror/backup layer for the record-chain.

Boundary

Modes

Dry-run (default)

Live (implemented)

The public archive index currently records historical daily archives as well as the newer weekly policy. Historical entries remain evidence of prior live uploads; they do not re-enable daily paid uploads.

Recovery access paths

An Arweave TXID and expected SHA-256 identify the payload. A gateway URL is only an access path and is never treated as the identity of the archive.

Quarterly Weekly Continuity recovery attempts and cross-checks:

Successful gateways must return byte-identical content, and the consensus bytes must equal the repository-preserved expected SHA-256. One operator or one URL being unavailable therefore does not by itself make the archive unrecoverable. A disagreement is a hard failure, not a majority vote.

Idempotency

Archive ID is deterministic from included batch manifest SHA256s. If the same archive already exists in the public index, no new archive is created.

Terminology

Use: Arweave, Arweave archive, Arweave TXID, Arweave wallet, Arweave wallet JWK, Arweave archive index.

Do not use: ARV5, LV5, IVV5, IPFS, Pinata, Lighthouse, Web3.Storage.

Exception: Legacy/evidence/historical archive pages may mention IPFS, 4EVERLAND, arseeding, or older storage routes when clearly marked as historical.