A publishing history. Backed by evidence.

Preservation and verification methodology

For each eligible publication or material update, ContentLedger calculates a deterministic SHA-256 digest of the canonical WordPress content and immediately seals an immutable canonical JSON origin-evidence manifest. This process does not wait for Internet Archive.

Internet Archive submission and verification run as a separate preservation track. A Wayback snapshot is identified as verified only after its public URL resolves successfully; this confirms link availability at the recorded check time, not byte-for-byte identity or permanent retention.

Records migrated from an earlier release preserve their historical evidence-capture metadata while stating the later manifest sealing time. Cryptographic signatures and timestamps begin when those artifacts are actually created and are never backdated.

When OpenTimestamps is enabled, a privacy-protected commitment to the sealed manifest digest is submitted to redundant public calendar servers. Downloadable proofs begin as pending receipts and may later contain a Bitcoin block-header attestation. Independent Bitcoin verification remains a separate external check.

When digital signatures are enabled, the site signs each sealed manifest digest with an Ed25519 key and publishes a compact JWS artifact. The website identity's did:webvh JSONL log records the assertion method and its authorization intervals. This associates the recorded digest with a site-controlled key under separately reported authorization evidence; it does not by itself prove legal ownership, first publication, or trusted signing time.

The Internet Archive is an independent organization. Inclusion here does not imply endorsement, ownership, or a guarantee of future retention by the Internet Archive.