VERIFY · LIVE

Notary

One append-only log of hashes — never content — from across the estate. Every figure below is recomputed from the leaf stream a stranger can download; none is a number we typed.

The log holds 6813 leaves from 12 sources. Each leaf is a 0x… sha256 and four fields of context — a sealed head, a certificate, a receipt — and nothing about who or how much. The head below is the RFC 6962 root over all of them, recomputed here; fetch the leaf stream and rebuild it yourself.

Head size6813
Head root0x444709eef00880d916c916179e2b0818816f7ea62f8d55d0a1c3511bd780a133
Most recent leaf2026-09-19T11:57:28.806Z
Stream regenerated2026-09-19T11:57:29.207Z

Per-event coverage

The fine-grained sources — one leaf per real event, not per commit or sealed head. A source is folding once the log holds a leaf of its own kind, and awaiting when its emitter is wired and correct but the property has not produced that event yet. Awaiting is the honest middle state, not a failure: a record only speaks when there is something true to seal.

SourceEventStatus
academycertificate/1✓ folding
claimyourgoldreceipt/1✓ folding
flashyidverification/1◇ awaiting first event
flashynetworksettlement/1✓ folding
flashyoscountersignature/1◇ awaiting first event
gdagroupintent/1✓ folding
goldholdingsintent/1✓ folding
intentmeshintent/1◇ awaiting first event
magicianintroduction/1◇ awaiting first event

Growth

Measured from the leaves’ own seal-times — not asserted. A leaf counts in a week because the work it seals happened that week, so the figures below cannot move unless the estate’s real activity does.

This week321-73.9% vs last week
This month4613+239.7% vs the month before

Leaves sealed per week — the last 8 weeks, oldest to newest.

Who is in the log

Each property folds its own hashes in. A checkpoint/1 leaf is a property’s whole sealed record in one root; the finer kinds — certificate/1, receipt/1 — are one leaf per event.

SourceLeavesKinds
flashynetwork3944checkpoint/1, settlement/1
claimyourgold921checkpoint/1, receipt/1, ship/1
flashyos872checkpoint/1, ship/1
gdagroup233checkpoint/1, intent/1, ship/1
academy187certificate/1, checkpoint/1, ship/1
flashygroup170checkpoint/1, ship/1
goldholdings151checkpoint/1, intent/1, ship/1
flashyid132checkpoint/1, ship/1
flashygold94checkpoint/1, ship/1
mlgblockchain79checkpoint/1, ship/1
intentmesh24checkpoint/1, ship/1
rites6checkpoint/1, ship/1

Browse the log

Every leaf, newest first — the same stream served at /.well-known/notary-log.json, one screen at a time. Each row is a 0x… sha256 and four fields of context; there is nothing here about who or how much, because there is nothing like that in the log.

5601–5625 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-31 00:43flashyidship/10x0f0e76499166fb99ship/flashyid/e02d038da563
2026-08-31 00:50flashyidship/10xbfcdbedc1b400935ship/flashyid/cd795a3261bf
2026-08-31 01:00flashyidship/10x46dda237527c1da0ship/flashyid/27d4096d4b34
2026-08-31 01:00flashyidship/10x34a6a9950eb31859ship/flashyid/14d87f825142
2026-08-31 01:01flashyidship/10x94a46572961a8b1dship/flashyid/9ce26ba3c7e1
2026-08-31 01:45flashyidship/10x4bf8eac50531036cship/flashyid/e79c4ee87b23
2026-08-31 02:19flashyidship/10x3fa5d96fb7f9e6b5ship/flashyid/ad3e5305bc26
2026-08-31 02:19flashyidship/10x1ac9d8a4592c826aship/flashyid/ededd2f1a7da
2026-08-31 03:01flashyidship/10x6c22dc7e04abfda8ship/flashyid/46e9011577bf
2026-08-31 03:01flashyidship/10x5aea4abf84fe3bdbship/flashyid/3598a9f1c586
2026-08-31 13:09flashyidship/10x8c3605f8c929f4bfship/flashyid/3e297f122136
2026-08-31 14:26flashyidship/10x36c83b264d139d16ship/flashyid/dfa7211a76da
2026-08-31 14:28flashyidship/10xda213bfd2cc6b377ship/flashyid/a46cf09132ec
2026-08-31 10:55flashyidship/10x81e24c7b03dadfefship/flashyid/56f0c979a7a2
2026-08-31 15:53flashyidship/10x7b107cbceee8a99bship/flashyid/ad00f95568bd
2026-08-31 12:27flashyidship/10x1ce89a69a518b9e2ship/flashyid/a839b932dd76
2026-08-31 14:26flashyidship/10x0cf804bbdb13c698ship/flashyid/3543d7eb0229
2026-08-31 15:53flashyidship/10x2e0e6bd16b1bc91bship/flashyid/9e94cb102fc0
2026-08-31 16:19flashyidship/10xdca18463e29668f7ship/flashyid/3cfbe1589110
2026-08-31 20:22flashyidship/10xcb753547a14e30c0ship/flashyid/d10114a0371a
2026-08-31 16:43flashyidship/10x7065e3289fff873cship/flashyid/a44be41f8ee3
2026-08-31 17:00flashyidship/10x1b9491fa67dd7924ship/flashyid/95aaf035e7e6
2026-08-31 17:55flashyidship/10x786465ec93af0afcship/flashyid/8b66c575c3f7
2026-08-31 19:38flashyidship/10xf69bdc71abb26bc4ship/flashyid/b5abbec5c1d2
2026-08-31 20:54flashyidship/10x18e8ed9e39080a72ship/flashyid/c4ac1bc06fee

What the log proves, and what it does not

The head is reproducible: anyone can rebuild it from the leaf stream, and a consistency proof shows the log only ever grew. It is not yet tamper-evident — that needs a cosignature from a party that is not the estate, and until one exists the log says so rather than implying more. See the checkpoint for the per-property root and verify to hash a record in your own browser.

Served at /api/v1/public/notary (head + proofs) and /.well-known/notary-log.json (the full stream). This page is derived from that stream — the estate’s fan-in runs every six hours, and a fold that changes the log deploys this page with it, so a new hash appears here on its own without anyone pushing.