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 7357 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 size7357
Head root0xc7634c7a09b345a2e0a107179889c19480c12109c40368b3056fabfba2890efb
Most recent leaf2026-09-21T12:57:45.274Z
Stream regenerated2026-09-21T12:57:45.569Z

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✓ folding
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 week704-33% vs last week
This month5054+249.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
flashynetwork4468checkpoint/1, devlog/1, settlement/1
claimyourgold924checkpoint/1, receipt/1, ship/1
flashyos872checkpoint/1, ship/1
gdagroup235checkpoint/1, intent/1, ship/1
academy188certificate/1, checkpoint/1, ship/1
flashygroup172checkpoint/1, ship/1
goldholdings151checkpoint/1, intent/1, ship/1
flashyid132checkpoint/1, ship/1
flashygold96checkpoint/1, ship/1
mlgblockchain81checkpoint/1, ship/1
intentmesh32checkpoint/1, intent/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.

5976–6000 of 7,357 · newest first
Time (UTC)SourceKindHashRef
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
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

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.