Trust

Everything UnifyID records about a release of personal data, a staff read or a public fact goes into an append-only log. Once an hour that log is sealed under a single Merkle root and signed. The signed statements are published to anyone, with no account and no key.

This section is about what you can do with them. The first two pages are what exists; the third is a script you can run against the live service; the fourth is the proof a person downloads about one record. The fifth is the honest limit, and it is the page worth reading twice.

One fact that belongs here is already on a sign-in page because you meet it during an integration: every release of a person's data to your application is written as a disclosure in the same database transaction that reads the data. That is on Handling the callback.

Pages in this section

• What we publish

  One signed statement an hour, over combined roots only, with no personal data in it — and why the numbering is not one per hour.

• The public endpoints

  Seven unauthenticated endpoints, the exact fields they return, and the proof endpoints that are not public.

• Verify a checkpoint yourself

  Two unauthenticated requests, an ES256 check with any library, and a walk backwards through the chain. No tool of ours required.

• Proof bundles

  The file a person downloads about one record: what is in it, the chain of checks it supports, and the legitimate reasons the record itself is absent.

• What this does not yet prove

  The honest limit: you can confirm we signed a checkpoint and that the published history is consistent — you cannot yet confirm we did not sign a different one.

• AnchoringNot yet available

  Built and tested, rehearsed on a test network, and starting on Base mainnet at launch. What the two contracts do, what the second channel is for, and how to confirm for yourself whether it is on.