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 week476-60.1% vs last week
This month4713+268.5% 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.

5276–5300 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-31 03:12flashyosship/10x8201b9cda7cdb918ship/flashyos/fe82c87fcb89
2026-08-31 14:07flashyosship/10xc2391e387142b081ship/flashyos/fdd09df3bedb
2026-08-31 10:57flashyosship/10x6544a13a79479b96ship/flashyos/116b956fbb5e
2026-08-31 12:13flashyosship/10xed7f3ac5d92024faship/flashyos/9b5b45030af5
2026-08-31 12:13flashyosship/10xa7a09272539b04d9ship/flashyos/9aa47b6a7651
2026-08-31 12:30flashyosship/10x76718911c1b4ffd1ship/flashyos/b2b00f6510a6
2026-08-31 12:30flashyosship/10xc97cebdd620c1173ship/flashyos/20a03b1c05e1
2026-08-31 12:43flashyosship/10xb3ddec58ef375bfaship/flashyos/2817791078a1
2026-08-31 12:43flashyosship/10xc1e1337eead6f47eship/flashyos/2f4f4d75f930
2026-08-31 12:46flashyosship/10x2d0b10899207c2d0ship/flashyos/465240d93c6b
2026-08-31 12:51flashyosship/10xd29e1f877f3d81bfship/flashyos/35ccc573b0c7
2026-08-31 12:53flashyosship/10x65790ecbd872f365ship/flashyos/1aa6fe01fabd
2026-08-31 12:54flashyosship/10x7bb555c7bae72979ship/flashyos/3dd8e562c4f9
2026-08-31 12:55flashyosship/10xd998f441c15b1adeship/flashyos/e436d9cdef89
2026-08-31 12:56flashyosship/10x4d8b288c786c7c18ship/flashyos/873efe9db7ac
2026-08-31 12:57flashyosship/10x495e9d7d76b1b020ship/flashyos/358b673f56d7
2026-08-31 12:58flashyosship/10xc6e9c8f6e04f8520ship/flashyos/99a599b9869c
2026-08-31 13:02flashyosship/10x36e3eb23246b105eship/flashyos/f42dff5d8952
2026-08-31 13:02flashyosship/10xf03dd37718e701b9ship/flashyos/7caebe4ed0eb
2026-08-31 13:05flashyosship/10xee8b0fa42a1dea9fship/flashyos/6c9f4483247a
2026-08-31 13:05flashyosship/10xfe182ebec670993aship/flashyos/de893d97e06e
2026-08-31 13:33flashyosship/10x0a5675a54dfaeb22ship/flashyos/ab3c051f632c
2026-08-31 13:33flashyosship/10x70e81c3927da26dbship/flashyos/f7797a29a8b4
2026-08-31 13:52flashyosship/10xbb0aab312dfb1103ship/flashyos/8463721816ab
2026-08-31 13:59flashyosship/10x5db964fcc76be928ship/flashyos/dc6faa36ad16

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.