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 week493-58.7% vs last week
This month4724+272% 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.

5226–5250 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-30 21:24flashyosship/10x9ecee97274753effship/flashyos/e8160f34f326
2026-08-31 01:28flashyosship/10x1d05ea0ac1460f8bship/flashyos/d8da55b94623
2026-08-30 21:42flashyosship/10x20da8faf85a84a0bship/flashyos/618f59769cd2
2026-08-31 01:42flashyosship/10x6bee8cc27b74be8fship/flashyos/8f32b8440bee
2026-08-30 21:47flashyosship/10x0001ea3257b887d2ship/flashyos/0fcf252321c2
2026-08-30 21:56flashyosship/10x0777d7210fc91cb5ship/flashyos/35694d1e5800
2026-08-30 21:59flashyosship/10x0226f6cd9d53780cship/flashyos/6ace1379604e
2026-08-30 22:02flashyosship/10xfeea854390ef7421ship/flashyos/79d052f812cc
2026-08-30 22:02flashyosship/10x27f7aec47b138f21ship/flashyos/0a0061efcb19
2026-08-30 22:03flashyosship/10x4630bb7ef84d22c1ship/flashyos/72d2153c9005
2026-08-30 22:10flashyosship/10x98a670b215801dd2ship/flashyos/8b7da3cce208
2026-08-30 22:30flashyosship/10x2b321af2c82be432ship/flashyos/78d2b922b59a
2026-08-30 22:34flashyosship/10x33d690d510f8a3c9ship/flashyos/fac594e834c8
2026-08-30 22:37flashyosship/10x872da4bda2c89efcship/flashyos/11b7bad42052
2026-08-31 00:22flashyosship/10x670bf1f36bf852f1ship/flashyos/05fcbd92b31e
2026-08-31 00:23flashyosship/10x902b56b5d427c900ship/flashyos/ec999a25ed7e
2026-08-31 00:24flashyosship/10x4bed477948e85899ship/flashyos/94a59269d7a2
2026-08-31 00:34flashyosship/10x551c1e302af124afship/flashyos/b133d1d2e5e8
2026-08-31 00:39flashyosship/10x0e36365ccecb6087ship/flashyos/ff4b8cc8392b
2026-08-31 00:40flashyosship/10xd3f67f1fc7bebde9ship/flashyos/ab058032dcaa
2026-08-31 00:40flashyosship/10x070e50400a63e699ship/flashyos/16339799e71b
2026-08-31 00:41flashyosship/10xf30cd40e54282af6ship/flashyos/6fc726450854
2026-08-31 00:49flashyosship/10x2cd6a7fd42c1e5f6ship/flashyos/c1edc3492d07
2026-08-31 00:51flashyosship/10x4ea2f3a0d80087e1ship/flashyos/d8055d75f11a
2026-08-31 00:54flashyosship/10x6fcc6e03731bcd2dship/flashyos/11e73c2e8c3e

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.