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 week343-72.9% vs last week
This month4670+253.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.

5426–5450 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-09-01 10:27flashyosship/10x39a9a45f27015485ship/flashyos/296688a48d79
2026-09-01 14:46flashyosship/10x39d327899d3de0ffship/flashyos/813cc6befc6b
2026-09-01 14:59flashyosship/10xe2086c41efeb5413ship/flashyos/3be8d40cd40d
2026-09-01 15:13flashyosship/10x64fd50a50f4cbea3ship/flashyos/03f2c03abc0b
2026-09-01 15:16flashyosship/10xe29bff17a0284aafship/flashyos/9bde84293aa6
2026-09-01 15:24flashyosship/10xd217de61a9951b2bship/flashyos/3312536a3069
2026-09-01 11:40flashyosship/10x88b5297140c348fbship/flashyos/193d9e4c31c2
2026-09-01 15:40flashyosship/10xaf56e90a08d9c937ship/flashyos/3fee6eb19d80
2026-09-01 15:56flashyosship/10x0a53e90f8e17acafship/flashyos/52bcf7f76673
2026-09-01 12:32flashyosship/10x858a74dd8f1f501eship/flashyos/1fd61f3123c4
2026-09-01 13:27flashyosship/10x085425bba2e61e9cship/flashyos/91194e670dce
2026-09-01 13:37flashyosship/10x869d2fb1e942dcdeship/flashyos/43ca093b0a8a
2026-09-01 14:31flashyosship/10x9b693305b5bfc65bship/flashyos/841f42398b0a
2026-09-01 14:37flashyosship/10xf319c93df902a6d6ship/flashyos/6b94af57a10c
2026-09-01 14:53flashyosship/10x1b1966b937a8ae76ship/flashyos/7b92c06a10fc
2026-09-01 14:59flashyosship/10x732b942b8863e587ship/flashyos/b02fc7b84e0c
2026-09-01 15:12flashyosship/10xae868397e8ef8960ship/flashyos/d12c956d68d2
2026-09-01 15:18flashyosship/10x7b75de44c9739a85ship/flashyos/f8974a7fdbd7
2026-09-01 15:27flashyosship/10xdfe9688bde7b11b9ship/flashyos/9e8929797364
2026-09-01 15:45flashyosship/10xb2ea824985ca2770ship/flashyos/1dcdfcaaac1b
2026-09-01 17:41flashyosship/10x3342fb96ecfa64d3ship/flashyos/c424f24856b5
2026-09-01 17:55flashyosship/10x1d079ac249aa967eship/flashyos/65517f06229d
2026-09-01 18:31flashyosship/10x9c0049ae10560242ship/flashyos/95724e1f303a
2026-09-01 19:01flashyosship/10xc739a4903fde2d00ship/flashyos/1611d88b1789
2026-09-01 19:05flashyosship/10xa6455f58861a8bbfship/flashyos/e32710ea2036

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.