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 week469-60.9% vs last week
This month4710+267.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.

5301–5325 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-31 13:59flashyosship/10x6dc41ad398135611ship/flashyos/9af76db5eef8
2026-08-31 13:59flashyosship/10x754e57d041a652a2ship/flashyos/1302c808e385
2026-08-31 14:01flashyosship/10x5350e67c32b3660aship/flashyos/cde9d4f13395
2026-08-31 14:02flashyosship/10xe296451d63c074c5ship/flashyos/3e016e56ca2a
2026-08-31 14:04flashyosship/10xcdf9077bbca16233ship/flashyos/508e1fe69f9f
2026-08-31 14:08flashyosship/10x7732f486b419d4fcship/flashyos/d6a90d817b57
2026-08-31 14:35flashyosship/10x7936606b639a5755ship/flashyos/a251aa57ab0c
2026-08-31 14:36flashyosship/10xae58794135df887aship/flashyos/cbfad4985275
2026-08-31 15:02flashyosship/10x498344e84fb10e9bship/flashyos/5650127f0ee1
2026-08-31 15:05flashyosship/10x9700d5c4b9c39458ship/flashyos/1a5f06806062
2026-08-31 15:05flashyosship/10x28f67e4a5e2e4a3cship/flashyos/997aac33e96d
2026-08-31 19:42flashyosship/10xdc1bff62a5107d96ship/flashyos/863bd2b2bfc1
2026-08-31 16:05flashyosship/10xfbca6758249f93f7ship/flashyos/62c40752e7c4
2026-08-31 16:06flashyosship/10xf6f0eb5fa34f11eaship/flashyos/68e15ffd24cb
2026-08-31 16:07flashyosship/10x09bd2fd264102d87ship/flashyos/a218143db40b
2026-08-31 16:07flashyosship/10x95572f689fc384e0ship/flashyos/90b4cf781e06
2026-08-31 16:08flashyosship/10x747f66bb1900188dship/flashyos/02e0c2d568d6
2026-08-31 16:09flashyosship/10x7915f7a154eb65fdship/flashyos/d653a21743ae
2026-08-31 16:12flashyosship/10x1b38c4ac620e2354ship/flashyos/e6477f26f040
2026-08-31 16:12flashyosship/10x8ad0e16c67b0a46fship/flashyos/5887da0fe9f1
2026-08-31 16:15flashyosship/10x381ddd66bea7b59eship/flashyos/c5ca7b62e276
2026-08-31 16:17flashyosship/10xbd45bfafad174aa3ship/flashyos/fd7850851e67
2026-08-31 16:18flashyosship/10xa0a63594cb2b678eship/flashyos/ae3761a5f57e
2026-08-31 16:18flashyosship/10x1a362420a32f992aship/flashyos/efdb7b9e2bc6
2026-08-31 16:21flashyosship/10x75a3deec3028eba3ship/flashyos/aa5cc24f7c0f

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.