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 week323-73.8% vs last week
This month4614+240% 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.

5576–5600 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-30 05:46flashyidship/10x021575db9ad86ce0ship/flashyid/2f0242bfea02
2026-08-30 05:48flashyidship/10x8a8451bb5b2faa34ship/flashyid/50c7e08261b7
2026-08-30 13:21flashyidship/10x43f28d6822d12a3cship/flashyid/22eeb79e0fd1
2026-08-30 15:46flashyidship/10x8cd423ab1f94d433ship/flashyid/466299ed5d64
2026-08-30 16:18flashyidship/10xf3b8a5c7da1504a7ship/flashyid/6c9d2df305be
2026-08-30 17:18flashyidship/10xf5de84954f38fb83ship/flashyid/06b4f7412515
2026-08-30 17:23flashyidship/10x680e4cc79a575193ship/flashyid/b0f03a270ba2
2026-08-30 17:23flashyidship/10x338d3b1689b367aeship/flashyid/e9de27f952d9
2026-08-30 17:38flashyidship/10x07a8633abba8f0b8ship/flashyid/26362253d17b
2026-08-30 21:48flashyidship/10x92932809528a9025ship/flashyid/9878db1df5a6
2026-08-30 21:57flashyidship/10x47e63d2d119dd6e5ship/flashyid/5218ec7de7f1
2026-08-30 17:59flashyidship/10x82d04c7f4f2142faship/flashyid/bac24513b16b
2026-08-30 18:01flashyidship/10xcbdad8b46f5baf2dship/flashyid/0a5721db680e
2026-08-30 18:37flashyidship/10xfbd81982ee67030aship/flashyid/00c1b6854ae8
2026-08-30 19:25flashyidship/10x6d35b7ab2f37f994ship/flashyid/ba1973808eae
2026-08-30 19:45flashyidship/10x0597db0adbda9615ship/flashyid/58ffb8d6323c
2026-08-30 21:38flashyidship/10xa5ea3c0e50957611ship/flashyid/a985949045e7
2026-08-30 21:40flashyidship/10x5189d9011a2f53d9ship/flashyid/420302ed7d13
2026-08-30 21:44flashyidship/10xc0fbd1984ccdfc89ship/flashyid/b780e2f9e18f
2026-08-30 21:44flashyidship/10x0dbee2d5c5121b4dship/flashyid/5021b43ba2e4
2026-08-30 21:55flashyidship/10xcf4031d31e6eb763ship/flashyid/e6d3145202dc
2026-08-30 21:57flashyidship/10x418f1e42e58f6967ship/flashyid/71e551c7c295
2026-08-30 22:06flashyidship/10xc11e7a1551357d0eship/flashyid/e53cf38d9339
2026-08-31 00:31flashyidship/10x5fdebce64b1b42d9ship/flashyid/72bf2591f827
2026-08-31 00:42flashyidship/10xdc06f38156df3daaship/flashyid/dfbaa1386d93

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.