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 week327-74% vs last week
This month4626+242.7% 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.

5501–5525 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-09-02 21:50flashyosship/10x2ac63b7f4e40774aship/flashyos/735b0b6c484c
2026-09-03 00:04flashyosship/10xbf02991473f7edbeship/flashyos/d24492a731d3
2026-09-03 02:55flashyosship/10x139f837fb0f12bddship/flashyos/ed82f33b44b5
2026-09-03 02:57flashyosship/10xcaa88e15b38b4b78ship/flashyos/f517e787ce96
2026-09-03 03:08flashyosship/10x024413c506bc7709ship/flashyos/47875bf7732f
2026-09-03 10:04flashyosship/10xe542c9b770b70e2eship/flashyos/51fe661f1e3f
2026-09-03 11:15flashyosship/10x1a828d93e105ba6bship/flashyos/2cef62849b7b
2026-09-03 11:28flashyosship/10x23b6207f26d3905aship/flashyos/0faa34d6d849
2026-09-03 11:29flashyosship/10x9635842c52b277a1ship/flashyos/793dc19dcb46
2026-09-03 12:04flashyosship/10x0a6c8d9b2e5416d6ship/flashyos/10d7fbbf33bf
2026-09-03 16:26flashyosship/10xd94e953643a5a721ship/flashyos/8e7d4c0dd85a
2026-09-03 16:31flashyosship/10xb8ef231db413ad16ship/flashyos/4cd54e454744
2026-09-04 02:46flashyosship/10xcf978b23bd686d29ship/flashyos/7a1a0cc35133
2026-09-04 02:51flashyosship/10xc26e200eadfde1e1ship/flashyos/13c6c0591489
2026-09-04 04:32flashyosship/10x357c4d417cbe696fship/flashyos/4fa8e0bc7174
2026-09-04 10:00flashyosship/10x9e15cd47219ac1aaship/flashyos/73d7a801cdd1
2026-09-04 12:06flashyosship/10xd9937c9f5ac6f284ship/flashyos/bb7fb0a08059
2026-09-04 18:23flashyosship/10x3571ebc3e91b57cbship/flashyos/5e9ede1d99d8
2026-09-04 17:17flashyosship/10x9c55c34e53b223caship/flashyos/d9ab311b47cf
2026-09-04 17:25flashyosship/10xfed4cbacdfce4128ship/flashyos/47fc2933bbb8
2026-09-04 17:31flashyosship/10x79d2cad6bffe6116ship/flashyos/972b4eb8eb7b
2026-09-04 17:37flashyosship/10xcd3ca72f09fdefa7ship/flashyos/59825ed631ec
2026-09-04 17:45flashyosship/10xc1060523b2a5d127ship/flashyos/3c4395c2476a
2026-09-04 18:25flashyosship/10x4faf01847f96499cship/flashyos/8c30b5ee032f
2026-09-04 18:39flashyosship/10x17977bbe3e72b569ship/flashyos/e20465ac6dc4

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.