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 week517-57% vs last week
This month4766+286.9% 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.

5101–5125 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-26 19:29flashyosship/10x41a4f61f69e41ca4ship/flashyos/926642b7d6a5
2026-08-27 14:07flashyosship/10x3848d45b95ef0c25ship/flashyos/9b2587f51fda
2026-08-27 14:25flashyosship/10x8568cd7393ba857dship/flashyos/4b911a202e21
2026-08-27 14:36flashyosship/10xa51226377ab2cbabship/flashyos/9de46f0f2a7f
2026-08-27 14:42flashyosship/10x9c6198b062ee257fship/flashyos/3f2444d324da
2026-08-27 14:51flashyosship/10xa685b0303e411e46ship/flashyos/dea4b69fee5f
2026-08-27 15:08flashyosship/10x20e819519b202a21ship/flashyos/0612773ccfad
2026-08-27 15:32flashyosship/10xb27020c24769da86ship/flashyos/ff60d3d96d00
2026-08-27 15:48flashyosship/10x33c195a3d8aa992fship/flashyos/8032a85450a2
2026-08-27 15:51flashyosship/10xf87c91001fa44a81ship/flashyos/9ea8c6804274
2026-08-27 15:54flashyosship/10xb2fd7a9d1d3180deship/flashyos/4d61b629f2a8
2026-08-27 15:56flashyosship/10x040e16a54ec583cfship/flashyos/e2c6f55778c5
2026-08-27 17:39flashyosship/10xae45c07671342557ship/flashyos/cd281a97a5aa
2026-08-27 17:41flashyosship/10x6106062ace488343ship/flashyos/036d4d7aea46
2026-08-27 17:47flashyosship/10x2290cad0074377e8ship/flashyos/ea001fa464cb
2026-08-27 18:01flashyosship/10x6f84eca79873254eship/flashyos/294c86a3d430
2026-08-27 20:00flashyosship/10x8de7df341dc26782ship/flashyos/e1325b1eaaaa
2026-08-27 20:01flashyosship/10x08233e31b592d810ship/flashyos/1229e8d4541d
2026-08-27 21:45flashyosship/10x491953c48cc7197fship/flashyos/9280f45d7a12
2026-08-27 21:56flashyosship/10x3c5a20467219e05fship/flashyos/a039bffd5c24
2026-08-27 22:16flashyosship/10xd9185f5cd409148aship/flashyos/c0d50f3123ce
2026-08-27 22:21flashyosship/10x9d596f46ae140c12ship/flashyos/006f20cb1d6b
2026-08-27 22:26flashyosship/10xcaab8a965de3c975ship/flashyos/97fb1c3b3ff2
2026-08-27 22:29flashyosship/10xf69383899ff8b642ship/flashyos/53288e3acaea
2026-08-27 23:02flashyosship/10xf49e54e4a48df113ship/flashyos/f6161d7bf021

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.