helloorigo.com/trust
Verification material
Chronicle's integrity evidence asks a reader to trust a signed root, not Origo. Checking that claim with the offline verifier bundled beside a Chronicle export means comparing what it found against material published here, independent of any single export or build. Three things are published on this page:
Publisher key registry
The keys Chronicle's witness publication signs with. A signed root statement attributed to a key not listed here is not accountable to anyone — see step 2 of the contract below. There is one key and no rotation has occurred yet; a retired key stays listed rather than being removed, per ADR-0026 §13.
| Key ID | Algorithm | Public key |
|---|---|---|
| origo-witness-alpha-1 | Ed25519 | bda03f42419746a33958f59561ea79de20d9e39d99c7c8b8f2a6e2b39a43cb8c |
Verifier build hashes
The SHA-256 of every published build of the offline verifier bundled beside a Chronicle export. Superseded builds stay listed, never removed, so an export delivered with an older build still has something to check it against.
| Status | SHA-256 | Published | Note |
|---|---|---|---|
| current | f407b45c17b02567504de8cb5cfe0ccef6a70608941b0db3dc10a4cbbcec5730 | 2026-09-04 | Points the verifier's own attribution note at the published registry (#575); no verification logic changed. |
| superseded | 6ae4fb8bc32a1c319e1418ffa9561f5fc4a02ba2575cff838b0469b64c0e0329 | 2026-09-03 – 2026-09-04 | First build bundled with the Chronicle operator export (#571/#573). |
The integrity-evidence-v1 contract
The full specification the verifier checks a bundle against: what each of its seven steps means, what counts as an accepted key or timestamp authority, and what the evidence proves and does not. Anyone building an independent verifier builds it from this document.