VERIFY · LIVE
Check it yourself
This whole property rests on one claim: you do not have to trust us. Here it is in one screen, for a stranger with no account — verify a real settlement, then prove a real leaf is in the log. Nothing is submitted, nothing is installed.
1 · Verify a settlement in your own browser
Every cross-organisation collaboration is published as frozen canonical JSON plus its sha256. The server hands your browser that feed unchecked, and the hashing happens on your machine — so the verification is yours, not a claim of ours.
It is the only page here that runs a script, and that is the point: a server-rendered “we checked it” is exactly the thing this page exists to stop us saying.
2 · Prove a real leaf is in the transparency log
The log holds 8523 hashes across 13 sources, append-only. Here is its most recent leaf — a real one, sealed just now:
| Kind | checkpoint/1 |
|---|---|
| Source | flashynetwork |
| Sealed (UTC) | 2026-10-04T08:21:21.610Z |
| Leaf hash | 0x53ea4f495d599e6fe73c32c6d7f960dd501d2acb5556c82477d8849cf9639337 |
That opens /verify-leaf/ with the hash pre-filled. You get the audit path against the current head, the four fields of context the leaf carries — never who or how much — and the exact steps to re-check the proof in any RFC 6962 verifier, ours or not.
No account, nothing installed
Neither step asks you to sign in or submit anything, and nothing here is privileged. The same two checks run from a shell against the same public feed:
npx @flashyos/verifyA verifier you have to ask us to run is not one. That is the whole claim, and this page is the shortest way to see it is true. Why this matters →