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 11204 of 11632, 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.

Kindinitiative/1
Sourceflashyos
Sealed (UTC)2026-10-19T16:33:33.131Z
Refhttps://api.flashyos.com/api/v1/public/initiatives/cmvfh4dsb0089oo4iw6j85l1k/status
Leaf hash0x7d4791720b5807a852c94ed18d2a26838a38de97adac4ff27c94b0ce51ff0c2d

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 size11632
Head root0x9a55a3dd7b7a4890198df487a73ca8d4b4ec2ab9bea87610623f242d6548c0f4
Audit path
  1. R · 0x9da96c8ecaf960d78896…
  2. R · 0x48c0273aaa2ff4d51432…
  3. L · 0x53574e3a20a98196f4ad…
  4. R · 0x6dca8f2e9f7b1ed04754…
  5. R · 0x591d0e6aebf45f341ec8…
  6. R · 0x2052f23bfe97590a0420…
  7. L · 0xc3e0a7d02a997b30b5bd…
  8. L · 0xc5c0042f7ae3f5aab6f5…
  9. L · 0x9b988a54d3969e830743…
  10. L · 0xab141b429539e68a9a2b…
  11. R · 0xa7c0c5f37b43a3e2adda…
  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=0x7d4791720b5807a852c94ed18d2a26838a38de97adac4ff27c94b0ce51ff0c2d. 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.