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 week339-73.2% vs last week
This month4666+253.2% 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.

5451–5475 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-09-01 19:05flashyosship/10x46f9cc72a70c014cship/flashyos/d5ca492684b0
2026-09-01 19:06flashyosship/10x9a2dcc44a643fdc5ship/flashyos/16b39b884dd3
2026-09-01 19:07flashyosship/10xe7012b47aaea9421ship/flashyos/b05388f4cafb
2026-09-01 19:13flashyosship/10x8ca01d6490e5d30cship/flashyos/98b537b62315
2026-09-01 19:14flashyosship/10xf4d9d2f056171d87ship/flashyos/3720dc8a1c8b
2026-09-01 21:08flashyosship/10x56d0b5b21a0c73eaship/flashyos/7807312fdd51
2026-09-01 21:15flashyosship/10x1cfe96a957de0469ship/flashyos/1d6f72564949
2026-09-02 01:57flashyosship/10xd572ea8a24a3f91eship/flashyos/4a76b65a3bf8
2026-09-02 02:31flashyosship/10xa10e8a1124a72fb0ship/flashyos/30b7f6b4e0a9
2026-09-02 02:40flashyosship/10x87b41d33e55f2ea3ship/flashyos/ac2fb6d404a0
2026-09-02 03:06flashyosship/10xe6acc8c09215a7a1ship/flashyos/5c67c39efc73
2026-09-02 03:07flashyosship/10xd19d99d4fccf5383ship/flashyos/c2c04a6bdb07
2026-09-02 03:21flashyosship/10x096fbc980d785837ship/flashyos/1dc1b45d3c7d
2026-09-02 03:27flashyosship/10x65ca1e47a71bc86dship/flashyos/6de3c7ca30a0
2026-09-02 04:33flashyosship/10x9895e4551a9903b6ship/flashyos/15b0633fe12a
2026-09-02 11:40flashyosship/10x0fe46fe2c657a602ship/flashyos/fa4957f33a57
2026-09-02 11:19flashyosship/10x581b7712fa15a50eship/flashyos/ee5e1c8b32a4
2026-09-02 15:20flashyosship/10x732f9824450af6caship/flashyos/26bafd7bab1d
2026-09-02 12:04flashyosship/10x0140f006f032685dship/flashyos/9c3d2f498062
2026-09-02 16:05flashyosship/10xc64bb112a2c4973bship/flashyos/c5a0a5f10fa9
2026-09-02 12:16flashyosship/10x288c9434c8fd1c8fship/flashyos/dc58b6a4b3a7
2026-09-02 12:21flashyosship/10x7403f66ee0e52242ship/flashyos/d522ed74abb1
2026-09-02 16:54flashyosship/10xa8a8903297ff5328ship/flashyos/25a986e191cd
2026-09-02 13:21flashyosship/10x4843dabbcf9d8544ship/flashyos/63ee09f9b3a3
2026-09-02 13:56flashyosship/10x4e05ae6f07153117ship/flashyos/42df04b7980f

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.