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 week510-57% vs last week
This month4746+280.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.

5176–5200 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-30 01:57flashyosship/10xc89a81399ad65ea5ship/flashyos/30f00812a3b0
2026-08-30 02:10flashyosship/10x2af3a0ae183f4a9cship/flashyos/f2925904208a
2026-08-30 02:17flashyosship/10x9580da3338ae4269ship/flashyos/46b3ad36ea87
2026-08-30 02:17flashyosship/10x7db41115ce4b561cship/flashyos/e42496cd9481
2026-08-30 02:26flashyosship/10xac786e45e7aaab05ship/flashyos/53df476a2a55
2026-08-30 02:55flashyosship/10x8174164b2f40d12bship/flashyos/6d36866db657
2026-08-30 02:55flashyosship/10xe464a89ab8f78078ship/flashyos/8233af3cdcab
2026-08-30 02:58flashyosship/10x2c067ba8473af31aship/flashyos/5db478c6454f
2026-08-30 03:44flashyosship/10x549099251cc67c1cship/flashyos/c21012c58481
2026-08-30 03:51flashyosship/10x3acbf06b7e045899ship/flashyos/5e2fd2173f7f
2026-08-30 03:51flashyosship/10xc56caf9f2f6b80fcship/flashyos/422d73de00ac
2026-08-30 04:00flashyosship/10x09fb8e5375f0c2c1ship/flashyos/403207e7f8b7
2026-08-30 04:05flashyosship/10xdec1a365974b444fship/flashyos/47a5ed604dc1
2026-08-30 04:09flashyosship/10x0bba7e530a885455ship/flashyos/620764b59794
2026-08-30 05:06flashyosship/10x59a173d9f1b1989aship/flashyos/94afb841db78
2026-08-30 05:06flashyosship/10xb7d69e0bbf1118f3ship/flashyos/12546cf759e0
2026-08-30 05:12flashyosship/10xb1aa7f20cfa30170ship/flashyos/44e08d399cc8
2026-08-30 05:13flashyosship/10x9105c5b11bb16d61ship/flashyos/b0d3bd64ee22
2026-08-30 06:44flashyosship/10xa964420e110ac9c9ship/flashyos/518ced9b2c45
2026-08-30 06:44flashyosship/10x5422ab32cbda10ecship/flashyos/129620e5aade
2026-08-30 12:57flashyosship/10x772ee0840fac191eship/flashyos/e2afb7aa4fd6
2026-08-30 13:03flashyosship/10x2afc734a8295e0a2ship/flashyos/08b1d457a25d
2026-08-30 14:07flashyosship/10xa189e3e6e65a0707ship/flashyos/4c0482a3ad42
2026-08-30 14:07flashyosship/10xcfd7a58a77010f63ship/flashyos/c68a82161e08
2026-08-30 14:14flashyosship/10x1d19986ef3bc2399ship/flashyos/ed5798fbd66e

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.