Trust
Check our work
You should not have to take our word for anything. These checks need no account and no key.
1
A claim on a record
Every figure on a record or a receipt links to the transaction it came from, with the hash printed in full. Open it in a block explorer and compare the amount, the time and the addresses with what we wrote.
Receipts also list their sources and queries, so you can re-run the result.
If something does not match, tell us through the support page.
2
A deployer record that says there is not enough evidence
On a deployer record page, when we have not checked something or the evidence is too thin, the page says so in words instead of showing a clean result.
What we have never measured is listed on the methodology page.
3
The Proof Board
Each flag is written to a hash-chained log when the launch happens, before anyone knows how it ends.
The rules were written down and frozen before any day is counted. The board shows when that document’s hash entered the log, and the hash itself is in SHA256SUMS. Each day’s last hash is published, and the board shows how many copies of the page the Internet Archive lists.
To check it yourself: You need Python 3.10 or newer and about ten minutes. No account, no key.
- Download proofkit.py, the pre-registration, one day's log, and SHA256SUMS. Check the file's SHA-256 against SHA256SUMS.
- Run: python proofkit.py verify radar-YYYYMMDD.jsonl.gz --prev <the previous day's root>. It checks every line's hash, the link to the previous day, and that the last hash equals the root published for that day.
- Run: python proofkit-<kit>.py board --day YYYYMMDD with that day's file and the eight after it, using the verifier named in the board's kit_version. The output must match board-YYYYMMDD-<kit>.json byte for byte.
- Open any flag: /api/proof/event/<seq> shows the line, its hash recomputed, and its day's root.
- Save today's root somewhere we do not control. That copy is what makes a later rewrite detectable.
4
What these checks do not prove
Matching hashes prove a page came from our log. They do not prove the rule is right.
A transaction proves money moved; it does not prove who controls a wallet. An address is a lead, not an identity.
5
Verify an evidence pack
Every paid case pack carries its own manifest.json, the packed raw RPC responses, and the standalone Python script verify_exhibit.py using Python’s standard library alone so you or opposing counsel can verify it offline or against any chain endpoint you choose:
python3 verify_exhibit.py --pack manifest.json --rpc solana=https://your-rpc.example
Without an RPC endpoint, neither script prints PASS — it checks only the local file SHA-256 digests and packed JSON hashes, and marks every transaction as not compared.
Everything below runs inside your own browser tab using Web Crypto SHA-256. No file or JSON leaves your machine unless you enter your own RPC URL to compare packed raw transactions against a chain node.