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 week353-72.3% vs last week
This month4673+254.3% 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.

5401–5425 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-31 18:49flashyosship/10x4df59afd0f2f4455ship/flashyos/d305fa61ac18
2026-08-31 19:36flashyosship/10x4f3ad414d8b1fd32ship/flashyos/e32b566fe959
2026-08-31 19:42flashyosship/10x9479669da8a16d86ship/flashyos/ccef38dd7ac9
2026-08-31 19:44flashyosship/10xba8d13871cb94a48ship/flashyos/fef0bf8e2d12
2026-08-31 19:49flashyosship/10x2dc2ba690ade6c79ship/flashyos/2da1ed0010f7
2026-08-31 20:25flashyosship/10x1754a91dd6c11835ship/flashyos/5025aeed726c
2026-08-31 20:31flashyosship/10x21494aeeff2b9379ship/flashyos/5f4968be0d9f
2026-08-31 20:35flashyosship/10x9a1287a5026aba52ship/flashyos/c1bb699217d5
2026-08-31 20:42flashyosship/10x6fd28b2a925c05a2ship/flashyos/ca51c819aee2
2026-08-31 20:45flashyosship/10xa0fd7401260b997dship/flashyos/802d820c48ee
2026-08-31 20:47flashyosship/10x1a662a44bb439f09ship/flashyos/22d3c3a64178
2026-08-31 20:49flashyosship/10xd03747a5da463776ship/flashyos/99d09bb9679e
2026-08-31 21:02flashyosship/10x83ec5e42fae5e0d1ship/flashyos/99aa5bbf4961
2026-08-31 21:05flashyosship/10x9ec72cd95e347dc0ship/flashyos/bef64ae0318a
2026-08-31 21:07flashyosship/10x993843b3d3c768c5ship/flashyos/9853bd9aa159
2026-08-31 21:10flashyosship/10xeec7c486b7b6245fship/flashyos/52fc794214b8
2026-08-31 21:23flashyosship/10x8a194460bcd189c6ship/flashyos/77a092aa113e
2026-08-31 21:39flashyosship/10x4ea8f77711d2ed17ship/flashyos/ef77a9118c8d
2026-08-31 21:57flashyosship/10x1d83700dbbed2732ship/flashyos/3a6690363975
2026-08-31 22:24flashyosship/10xb14913fb3b94de95ship/flashyos/c64198c4bee8
2026-09-01 08:18flashyosship/10x38dac22998a4cc12ship/flashyos/f6412c3d0d76
2026-09-01 08:19flashyosship/10x3ad6f8c2d0c6b029ship/flashyos/afbb72a28ea5
2026-09-01 08:32flashyosship/10x9a57e516bb71207fship/flashyos/9f85e5c2f088
2026-09-01 08:36flashyosship/10xaef5018d60137ec4ship/flashyos/b4dcdf3a27b8
2026-09-01 10:24flashyosship/10x1fa7575e1c58ccd0ship/flashyos/8e5627dd07a6

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.