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 week324-74.3% vs last week
This month4623+241.9% 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.

5526–5550 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-09-04 18:58flashyosship/10x172be11c91cf7154ship/flashyos/c931922d0da3
2026-09-04 19:21flashyosship/10x13c617b9a13d5b12ship/flashyos/e306f5a1750d
2026-09-04 19:58flashyosship/10x12604bb80d554d2fship/flashyos/a7d7f4b07d3a
2026-09-04 20:09flashyosship/10xa911849386edecacship/flashyos/93ff4bc942c7
2026-09-04 20:19flashyosship/10x34005a2f17782e63ship/flashyos/849b77e11433
2026-08-18 21:27flashyidship/10x9fd27f07e2830426ship/flashyid/95d9f01d1418
2026-08-19 18:23flashyidship/10x54509618b01ddd4dship/flashyid/3e569704c269
2026-08-19 18:36flashyidship/10x633dea393ba25438ship/flashyid/456ccf349ff1
2026-08-19 18:52flashyidship/10x7a3fbd38cbe46c03ship/flashyid/0a887cd3cfc4
2026-08-19 19:04flashyidship/10x7d2d75827093f150ship/flashyid/ada847e53965
2026-08-19 19:24flashyidship/10xc6713e1c08646187ship/flashyid/5c75cd58b462
2026-08-19 20:01flashyidship/10xe6db9c662218cc20ship/flashyid/77fd8cee453b
2026-08-20 12:42flashyidship/10x3a648bf2a877e555ship/flashyid/1500b69d6467
2026-08-20 20:09flashyidship/10x3d47f072c98ccd65ship/flashyid/f89174d9544d
2026-08-21 16:14flashyidship/10x01fcea090bc0710fship/flashyid/38a5e81a663c
2026-08-21 16:18flashyidship/10x9b0613befb9b755cship/flashyid/812d1138d490
2026-08-25 01:08flashyidship/10xeb8d9be450a8c894ship/flashyid/96f0fbb9b72b
2026-08-25 02:37flashyidship/10x141a5d41e4423a53ship/flashyid/711a37d0d6a7
2026-08-25 02:46flashyidship/10x829b6187456fa447ship/flashyid/db51b027e249
2026-08-25 14:03flashyidship/10x467517bbdd45be32ship/flashyid/cd59d4acc838
2026-08-25 17:44flashyidship/10x9594006b1c1d0385ship/flashyid/0ceeea56752e
2026-08-26 13:10flashyidship/10xabdbbbaa7714b9ffship/flashyid/27d62735a872
2026-08-26 18:03flashyidship/10x50d2b7e22454ee7fship/flashyid/b54a9ecca8b9
2026-08-26 18:27flashyidship/10x76db765d0b6ef288ship/flashyid/67d6191314c6
2026-08-26 18:35flashyidship/10x6f75c201527230f3ship/flashyid/0b1947601907

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.