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 week476-60.3% vs last week
This month4716+269.3% 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.

5251–5275 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-31 00:54flashyosship/10x6dfc2d65fe418711ship/flashyos/82c1ad3d05eb
2026-08-31 00:56flashyosship/10x85416c18395567fbship/flashyos/29db58a64995
2026-08-31 00:56flashyosship/10x21c11dfb6d0da510ship/flashyos/7149d8a90d5a
2026-08-31 00:58flashyosship/10x68a211f7b4001837ship/flashyos/882efdb7c8c0
2026-08-31 01:00flashyosship/10xc989935629f10823ship/flashyos/af6d060c93c4
2026-08-31 01:01flashyosship/10xc23ee90f9a1a49acship/flashyos/88b6153692b6
2026-08-31 01:03flashyosship/10x73803106e890aad6ship/flashyos/9aee810aef05
2026-08-31 01:11flashyosship/10xe728e037c93dbf05ship/flashyos/e23a013f0afd
2026-08-31 01:12flashyosship/10xbf24c98e4a767847ship/flashyos/4a147a8c830f
2026-08-31 01:19flashyosship/10x94c0eb3a34d16b22ship/flashyos/458fdee3254f
2026-08-31 01:21flashyosship/10xbfb0d3d6cdd766ecship/flashyos/e602f5824053
2026-08-31 01:28flashyosship/10x5bb54e104cdb2589ship/flashyos/a3d419185136
2026-08-31 01:31flashyosship/10x17d465cd24b9712aship/flashyos/3131de5290cf
2026-08-31 01:31flashyosship/10xbc764f039b1bd6e7ship/flashyos/a20f4e316070
2026-08-31 01:43flashyosship/10x8bab0df8f38207c3ship/flashyos/7e4e824be440
2026-08-31 01:49flashyosship/10xcc27c9de9529015aship/flashyos/38bdc53eed0b
2026-08-31 01:49flashyosship/10x697071b207200838ship/flashyos/0be9afd4979c
2026-08-31 02:16flashyosship/10x88fb24e16d76b397ship/flashyos/cab85dfcb74e
2026-08-31 02:16flashyosship/10x14855dfbfad10453ship/flashyos/e956aca00541
2026-08-31 02:17flashyosship/10x4d1b08d93e7a5ca5ship/flashyos/38b8d9b1e893
2026-08-31 02:18flashyosship/10x5ce6655b99a1b7d3ship/flashyos/6338cb249f83
2026-08-31 02:31flashyosship/10xd83bc7087119b396ship/flashyos/ecf78696570c
2026-08-31 02:32flashyosship/10x55e9af47cde0087eship/flashyos/a67772d0e6ba
2026-08-31 02:56flashyosship/10xba8bf242a9cc2f53ship/flashyos/3e6e7422d850
2026-08-31 03:12flashyosship/10xe6867d2e15fad347ship/flashyos/f9712ad3b6af

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.