VERIFY · LIVE
Verify a leaf
Paste a leaf hash. This returns its inclusion proof against the current head — and the exact steps to check that proof yourself, in any verifier that speaks RFC 6962.
A leaf hash is the 0x… sha256 in any row of the log. This page carries out the same request a machine makes to /api/v1/public/notary?proof=inclusion&hash=….
Included ✓
This leaf is in the log at position 6808 of 9392, and the audit path below proves it against the head root. You do not have to take that on faith — the steps to check it yourself are below.
| Kind | intent/1 |
|---|---|
| Source | gdagroup |
| Sealed (UTC) | 2026-08-31T00:00:00Z |
| Ref | imx/26a8f6b8064f |
| Leaf hash | 0x26a8f6b8064fec183d0d9277f02d3a1e480b6e26b96a1e33205c67517ae6fc7c |
Four fields of context and a hash — nothing about who or how much. The ref is where a holder re-fetches the full record and re-hashes it to this same leaf; the log never saw those bytes.
The proof
| Head size | 9392 |
|---|---|
| Head root | 0x12ba93239373bc50830955db1fc0aaee6a3b16560de611cad7e3d563c4d019b3 |
| Audit path |
|
Check it yourself
The proof is RFC 6962 — Certificate Transparency, byte for byte — so any CT verifier in any language checks it without reading our code. Three ways, from least to most independent:
- Re-request the machine form and compare: https://flashynetwork.com/api/v1/public/notary?proof=inclusion&hash=0x26a8f6b8064fec183d0d9277f02d3a1e480b6e26b96a1e33205c67517ae6fc7c. The
rootit returns must equal the head root above. - Fetch the whole leaf stream, rebuild the tree, and confirm the root — the head is a number you recompute, never one we ask you to trust.
- Keep the head. Later, fetch the new head and a consistency proof between the two; if it passes, the log only grew — nothing was rewritten or removed.
An unsigned head is reproducible, not tamper-evident: recomputing our root checks our arithmetic, not our honesty. Only a cosignature from a party that is not the estate closes that gap, and until one exists the head endpoint says so, with the witness ratio published at zero. See the log for the whole picture.