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 week527-57.1% vs last week
This month4797+297.4% 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.

5051–5075 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-25 02:46flashyosship/10xcb906ec2f457b4abship/flashyos/8b0ad386a623
2026-08-25 12:51flashyosship/10x8f779943f6adf0baship/flashyos/9636f9b5f5c3
2026-08-25 13:19flashyosship/10x59b7007f88ae5860ship/flashyos/499787432eea
2026-08-25 13:30flashyosship/10xc0193c49043e7972ship/flashyos/eb783b21fb35
2026-08-25 13:44flashyosship/10xf7d0cd15fcfa160fship/flashyos/96a1842e25b8
2026-08-25 14:00flashyosship/10xda2b75aa1615396eship/flashyos/9f3a35aa3ab1
2026-08-25 14:20flashyosship/10xd88dae6ea65224f7ship/flashyos/4dde4c707649
2026-08-25 14:21flashyosship/10xf0d839f747efdb35ship/flashyos/4ef533821c35
2026-08-25 14:29flashyosship/10x5c6eb8fb3fd3f36bship/flashyos/35ff731e172b
2026-08-25 16:09flashyosship/10xa77ed4a1ed1185fbship/flashyos/cf4cdc881859
2026-08-25 16:43flashyosship/10x578294c67d14edffship/flashyos/5ee3dc01be1e
2026-08-25 17:05flashyosship/10x4e65842222334a42ship/flashyos/e538af7d295a
2026-08-25 17:14flashyosship/10xdf7597ec21298dafship/flashyos/ac0d9188cebe
2026-08-25 17:27flashyosship/10xc7abffea2bfc3836ship/flashyos/be10534dc4b5
2026-08-25 17:55flashyosship/10xedaf6f06443ed839ship/flashyos/b5228ac8ff62
2026-08-25 19:58flashyosship/10xf3dd6635c4616685ship/flashyos/5640d7d0395b
2026-08-25 20:09flashyosship/10xa828d77c94a5abe8ship/flashyos/579014867d8b
2026-08-25 20:42flashyosship/10xc3ffd4add40da9deship/flashyos/1aa9b2d19e3b
2026-08-25 20:46flashyosship/10x2ac36ce3db09d243ship/flashyos/28c44c2e2b8f
2026-08-25 23:21flashyosship/10x51d0579a509058aeship/flashyos/61bc3c6cf391
2026-08-26 00:59flashyosship/10xb5cef29c5eb7f0a4ship/flashyos/fe579ec870ce
2026-08-26 02:44flashyosship/10x5c90aebe19e8faeaship/flashyos/94358ef649e4
2026-08-26 02:56flashyosship/10x78d4d731d9b32d41ship/flashyos/8dfb0b57e9e1
2026-08-26 02:56flashyosship/10x36b32a1b51511d0cship/flashyos/5cbd4cde3b8e
2026-08-26 03:08flashyosship/10x71e10be0f493fff9ship/flashyos/f2d64d60777c

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.