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 week332-73.7% vs last week
This month4643+246.8% 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.

5476–5500 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-09-02 14:08flashyosship/10x5d8254138021e34fship/flashyos/9609714f3185
2026-09-02 14:17flashyosship/10x686a176c5dd65483ship/flashyos/034ac2bc718f
2026-09-02 14:18flashyosship/10x5ffefa8b22637031ship/flashyos/1e0488083b91
2026-09-02 15:13flashyosship/10x3a01af172bc2f39dship/flashyos/cc604cd3b4c3
2026-09-02 16:09flashyosship/10x0cbb7740120bb33cship/flashyos/3e4ccfce522d
2026-09-02 16:20flashyosship/10x052fc0d584b5ddb3ship/flashyos/fd23f437d405
2026-09-02 16:30flashyosship/10x8ad44954fc5ce05aship/flashyos/9f07bec762ae
2026-09-02 16:48flashyosship/10xaf5d0fedee3d20bbship/flashyos/4e38d4693c28
2026-09-02 16:49flashyosship/10xedb0875273debc6aship/flashyos/d3194380b545
2026-09-02 17:07flashyosship/10x8bc149cb3f4d50f3ship/flashyos/7a27dbc95c09
2026-09-02 17:28flashyosship/10x24a2e5802bed42e8ship/flashyos/c8d59f4aa583
2026-09-02 17:33flashyosship/10x08c4269507cc6de1ship/flashyos/fe86ad9aaa5d
2026-09-02 17:43flashyosship/10x5dc1dda48ec9f299ship/flashyos/c89fd750824a
2026-09-02 17:47flashyosship/10xb6d0c6dec40c8d45ship/flashyos/32d6f2c1c81d
2026-09-02 17:54flashyosship/10xbd3d103ee249342bship/flashyos/b1e448dd4a3d
2026-09-02 17:57flashyosship/10x33b5159fa629be42ship/flashyos/9a28efba4993
2026-09-02 20:09flashyosship/10x58de8b4d5013821bship/flashyos/4ed0a105944b
2026-09-02 20:26flashyosship/10x10db26ad9b30a7abship/flashyos/2d476d9f2c5e
2026-09-02 20:28flashyosship/10x94a4fefebede07f4ship/flashyos/bd6cfa05d98c
2026-09-02 20:35flashyosship/10x9c3279865b371cd8ship/flashyos/cac4e4ceaca6
2026-09-02 20:59flashyosship/10xace0742b5dbf6885ship/flashyos/33755330cf1f
2026-09-02 21:17flashyosship/10xd80e86a89ba5174fship/flashyos/74d9f2c4706f
2026-09-02 21:21flashyosship/10x92a149b3b6faff43ship/flashyos/8ea5d14eaa19
2026-09-02 21:23flashyosship/10xe846c667b05de001ship/flashyos/37058b70dc72
2026-09-02 21:49flashyosship/10xb512ae62cdee645eship/flashyos/17c81eb85d31

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.