A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗

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 12083 of 12230, 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.

Kinddevlog/1
Sourceflashytools
Sealed (UTC)2026-10-04T18:51:33Z
Refhttps://github.com/FlashyLabs/flashy-tools/commit/3ba484d2d49a5ffa49df1d64266a6cc0d4a7560f
Leaf hash0x0a23bb81c04bfffd990691572d9fc7acf746f0171739e26f490a9a3d129b28a1

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 size12230
Head root0x7d43d673300b9a0f0787b2fdb28997101ee7f9597a25f07d4f52e6cf448989aa
Audit path
  1. L · 0x7c82cd55cd75e58125f0…
  2. L · 0x5122c8d9ce50543d887d…
  3. R · 0x321e2ad5eb7aadb99324…
  4. R · 0x1290c39ba41eacc2472c…
  5. L · 0x68a929c564a21a6bfac8…
  6. L · 0xf777427784e15118af0f…
  7. R · 0xc60b602221a70d97090f…
  8. R · 0x67fa9ee1b49a3e3a623e…
  9. L · 0x890f6c3915b7e4d5cc71…
  10. L · 0x5bb3782ff416ffb8298d…
  11. L · 0x8d278d89ea03b60e7d14…
  12. L · 0x23f521a3b1825fb91298…
  13. L · 0x88058579d205b88ffec4…

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:

  1. Re-request the machine form and compare: https://flashynetwork.com/api/v1/public/notary?proof=inclusion&hash=0x0a23bb81c04bfffd990691572d9fc7acf746f0171739e26f490a9a3d129b28a1. The root it returns must equal the head root above.
  2. 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.
  3. 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.