Every seal below is recomputed here, on your machine, from the raw chain data. We do not ask you to believe our integrity flag — this page ignores it and does the arithmetic itself. If a single entry had been altered, the recomputed seal would stop matching and the row would turn red.
Fetching the chain and recomputing every seal locally.
| # | ID | Label | Sealed | Fingerprint | Seal | Link | Artifact |
|---|---|---|---|---|---|---|---|
| Loading chain… | |||||||
curl -s https://aurorapathways.xyz/proof/runs/2026-09-17.json | shasum -a 256
curl -s "https://aurorapathways.xyz/api/proof?verify=PF-72705281"
# the fingerprints match, or something is wrong
It does prove that a file with this exact fingerprint existed at the sealed time, and that no earlier entry has been edited since — changing any one of them breaks every seal that follows, in public.
It does not prove the contents are true. Someone can seal a file containing a false claim. What becomes impossible is backdating — quietly revising the past to look better. So treat this as protection against rewriting history, not as a guarantee about any single document.
Runs where our tests failed are sealed here too. A registry that only holds good news would prove nothing at all.