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 6811 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 size6811
Head root0x9026f7eb76108b06d14caa8d362249c14427bb735d7e0ab10b29381c50a07480
Most recent leaf2026-09-15T20:36:04.231Z
Stream regenerated2026-09-15T21:29:47.629Z

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 week729-40% vs last week
This month4973+374.1% 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
flashynetwork3942checkpoint/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.

4926–4950 of 6,811 · newest first
Time (UTC)SourceKindHashRef
2026-07-08 22:33flashyosship/10x59110bbe4b1352feship/flashyos/3d6404de3245
2026-07-09 00:21flashyosship/10xea2ecaeabb8c8c8bship/flashyos/a6398465e81e
2026-07-09 00:33flashyosship/10x2827c63c6fe4d2f6ship/flashyos/b3ff57d3a7d2
2026-07-09 00:45flashyosship/10x935525a6046cb280ship/flashyos/28ef1fce874d
2026-07-09 16:25flashyosship/10xdcca4814c9049968ship/flashyos/fcc689ea43e9
2026-07-09 16:31flashyosship/10xc7c55eff4669b904ship/flashyos/d3b11ead9963
2026-07-09 16:46flashyosship/10xdfe087f78cf083f2ship/flashyos/224d4c8364be
2026-07-09 17:14flashyosship/10x4916fd0c9ad28998ship/flashyos/c19c072fa57a
2026-07-09 18:53flashyosship/10x696c43c0493030e1ship/flashyos/d2fd1c8f59fd
2026-07-09 18:57flashyosship/10xcc052c62d433d350ship/flashyos/7c27eb59eebb
2026-07-09 19:02flashyosship/10x8a7b45d7716b14f3ship/flashyos/4c8b6b6adac8
2026-07-09 19:07flashyosship/10xceb9586df0d80a56ship/flashyos/9fd14ab5e651
2026-07-09 19:17flashyosship/10xadc394d10e5f266fship/flashyos/07ea048a0de3
2026-07-09 19:29flashyosship/10xf18f9b76537f2419ship/flashyos/3063f62f0e88
2026-07-09 19:39flashyosship/10x96992ccd150e2601ship/flashyos/899fd55a3fef
2026-07-09 19:44flashyosship/10x43653e8d1007b065ship/flashyos/db38a0ee4c67
2026-07-09 21:14flashyosship/10x16a2321671b12d93ship/flashyos/6fa238bafd13
2026-07-10 02:01flashyosship/10x928d2d59fdc1d262ship/flashyos/d0b05f833a73
2026-07-10 00:44flashyosship/10xaa19cdaba6793d12ship/flashyos/f8a98dc34c37
2026-07-10 11:11flashyosship/10xd3ce8b3a86f879c8ship/flashyos/03c9030b9bc2
2026-07-10 11:13flashyosship/10xc89f15d980a19376ship/flashyos/99423ed38727
2026-07-10 11:31flashyosship/10xebf1b4c32c25aa1fship/flashyos/6b29b9c772d3
2026-07-10 11:44flashyosship/10x0da482c56263958aship/flashyos/4e6e94eb8157
2026-07-10 11:51flashyosship/10x609c05f4ab6175dfship/flashyos/7f5779036c48
2026-07-10 19:54flashyosship/10xc7fb80b52bcecd4fship/flashyos/75fef6e8f423

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.