Every claim on this site is a claim about what a document used to say. The regulator does not keep the earlier version: that is the whole reason the claim is worth making, and it is also the reason you have no obvious way to check it. So here is the way.
Nothing on this page asks you to trust us. The arithmetic below runs in your browser, on your machine, using the Web Crypto API your browser already ships. It will tell you plainly if our own numbers do not add up, and we cannot reach it to stop it.
What is actually being checked
Every day we take a SHA-256 fingerprint of every campaign we hold, built only from fields we already publish, and hash them together into a single value, a Merkle root. Each day’s entry then commits to the day before it:
link(n) = sha256( link(n-1) + root(n) )That is what makes the chain useful to somebody who was not paying attention last week. Changing what we said about one campaign changes its fingerprint, which changes that day’s root, which breaks every link published since. We cannot quietly revise our own history, and you do not have to have kept a copy of anything to know it.
The leaf, exactly
So that anybody can rebuild this from scratch, in any language, the fingerprint for one campaign is the SHA-256 of these five published fields joined by the ASCII record separator, 0x1e, in this order and no other:
campaign defect consequence remedy first_readPairs are combined by hashing the two lowercase hex strings written one after the other, with nothing between them. A node left alone at the end of a level is carried up unchanged rather than paired with itself. Every value comes from the public register index, so you can rebuild every leaf, every level and the root yourself and compare it with ours.
The endpoints
- The whole chain: every day, its root, and the link binding it to the day before.
- Today’s root: the head, on its own.
- An inclusion proof: one campaign’s leaf and the handful of sibling hashes needed to walk it up to the root. A few dozen bytes instead of fifteen thousand rows.
- The dated wording manifest: the fingerprints themselves, as a file you can keep.
What this does not prove
That we read the notice correctly on the day. A chain proves we have not changed our own record since we published a root; it cannot prove the record was right when it was written. Nothing cryptographic can. Closing that gap needs a timestamp from somebody who is not us, and until one is in place this page claims exactly what it can support and nothing beyond it.
The head of the chain
| Day | 2026-08-24 |
|---|---|
| Campaigns | 15,199 |
| Root | 5a48e4eadc85112d61578a7dfced2fe6b6c30c65c97d37493fb1c2c87aff6c0b |
| Link | af86859eff0f2a5d9b90602e57c003f5f8e0bff09dcba184ffb3e8cc8a3c2d22 |
| Entries | 1 |
What changed after publication · How we work · Corrections · Take the data