Verify
Nothing here has to be taken on trust. The record is a public repository and this site only renders it. Three checks establish that the figures are what they claim to be, and a fourth establishes who produced them.
- 1
The pages say what the files say
Each document page prints the hash of the file it renders and links to that file at a named commit. Hash the file yourself and compare.
git clone https://github.com/reouthq/track sha256sum METHODOLOGY.md DISCLOSURE.md KILL_CRITERIA.md - 2
The day's files match the day's manifest
Every day the workflow writes a manifest listing the hash of every file of that day, published and unpublished.
sha256sum -c --ignore-missing attest/2026-09-30.sha256 - 3
The manifest existed when it says it did
The manifest is timestamped on the Bitcoin blockchain with OpenTimestamps. A proof is complete once the transaction carrying it is confirmed, which takes some hours.
ots verify attest/2026-09-30.sha256.ots - 4
The figures came from the exchange, not from us
The workflow that reads the exchange is public and so are its execution logs. Its commits are made by the GitHub Actions service account; a commit by any other author would be visible in the history.
Recent anchors
The first anchor is written when the daily workflow starts. The rules themselves are anchored before the first monthly report, in the pre-registration manifest.
What these checks do not establish, and what an independent verifier may examine under a non-disclosure agreement instead, is set out in the Disclosure.