Skip to content

The integrity log

Receipts you can verify, without taking our word for it.

What this proves, and what it does not

• It proves order and content. Each logged record’s fingerprint covers the exact quote, the resolution criteria and resolver sources, the verdict text and its sources and evidence grade. If a file on the Ledger no longer matches, the check fails and names the record.
• The date rests on Bitcoin only where an anchor is confirmed. The head is stamped with OpenTimestamps: 4 heads stamped, 4 confirmed in a Bitcoin block, 0 still pending. A pending proof is a receipt from the public calendar servers, not yet a block, so it is a promise and not yet a proof. A confirmed anchor means those entries existed no later than that block. Entries before the first anchor are dated by the repository’s history alone. The table below lists every anchor.
• It does not cover the time before it began. The log started on 2026-10-15. Entries dated earlier were rebuilt from the claim files that day (entry 0 says so). Before that, the git history is the evidence.
• It is not signed yet. The signing tool is built (ML-DSA-65, the post-quantum signature this site teaches, verified here in your browser by the same library), but the key has to be created and kept by the owner outside this repository, and that has not been done, so no signature exists and nobody has vouched for this head by name. Do not read the anchor as an endorsement: it dates the record, it does not say who wrote it.

Checking it by hand

Each entry’s fingerprint is the SHA-256 of that entry written in a fixed form: keys sorted at every level, no spaces, UTF-8, every field except hash itself. In Python:

import json, hashlib
doc = json.load(open("integrity-log.json", encoding="utf-8"))
prev = doc["genesis"]
for e in doc["entries"]:
    body = {k: v for k, v in e.items() if k != "hash"}
    text = json.dumps(body, sort_keys=True, separators=(",", ":"), ensure_ascii=False)
    assert e["prev"] == prev and e["hash"] == hashlib.sha256(text.encode("utf-8")).hexdigest(), e["n"]
    prev = e["hash"]
print("chain holds", prev == doc["head"])

To timestamp a head yourself, install opentimestamps-client and run ots stamp integrity-head.txt; anyone can later run ots verify on the result. This site does the same for every new head, and keeps the proofs in data/anchors/.

Bitcoin anchors and the signature

Each anchor is an OpenTimestamps proof for a copy of the head file. Stamping and upgrading run in this site’s own repository (a workflow that holds no secrets); the signature is made only on the owner’s machine.

To check one yourself: download its head file and proof, then upload both at opentimestamps.org, or run ots verify from the opentimestamps-client. The button at the top of this page also checks every anchor against the chain and every signature against the published key, in your browser.

Every entry

An entry dated earlier than the day it was recorded was reconstructed when the log began. The full file, with each entry’s recorded date and the fingerprints of what it covers, is integrity-log.json. How the Ledger works is on How we check.