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 week515-56.9% vs last week
This month4758+284.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.

5126–5150 of 6,813 · newest first
Time (UTC)SourceKindHashRef
2026-08-27 23:12flashyosship/10xabc6641b18366648ship/flashyos/2bc01f13e1cb
2026-08-27 23:17flashyosship/10x7c06c3c3accc2d3aship/flashyos/c2cc38993f7e
2026-08-27 23:39flashyosship/10x65113af7abda52adship/flashyos/638e97bf4081
2026-08-27 23:44flashyosship/10x22426803b677dcf0ship/flashyos/bc8b11a4844a
2026-08-27 23:47flashyosship/10x8964cd4d09b83924ship/flashyos/a1d4f7a074a0
2026-08-27 23:48flashyosship/10xeddf436019c274feship/flashyos/93787228fc69
2026-08-27 23:49flashyosship/10xaca553c94b8bc848ship/flashyos/5aedaa92a640
2026-08-27 23:59flashyosship/10x92b9569708277819ship/flashyos/38d35beee86a
2026-08-28 00:05flashyosship/10x869693db8a4b9dd2ship/flashyos/c6dd58c5eec3
2026-08-28 00:06flashyosship/10x3ed4e4e44c3a5d93ship/flashyos/e055d678d895
2026-08-28 00:43flashyosship/10x024de682cc0e00bdship/flashyos/5bab29fe10de
2026-08-28 01:27flashyosship/10x052bf97d1854aa54ship/flashyos/0d3735cdaf32
2026-08-28 01:32flashyosship/10xf213cf7a042caf0eship/flashyos/9e8ffd9aa605
2026-08-28 01:54flashyosship/10x7ee3b8c28b355feeship/flashyos/721f74086caf
2026-08-28 02:08flashyosship/10x8c288ce6bf818c5eship/flashyos/055ff9423fcb
2026-08-28 02:11flashyosship/10x1e5829de61fc01f7ship/flashyos/15fc939da927
2026-08-28 02:20flashyosship/10xacbb46059a37e892ship/flashyos/e81805a92ed7
2026-08-28 02:46flashyosship/10x7f88bd191d122fddship/flashyos/9d7781ea904c
2026-08-28 02:50flashyosship/10x520fc4ef7adff088ship/flashyos/5e3efe21a0e8
2026-08-28 02:54flashyosship/10x0cf0459925446b02ship/flashyos/30dff957f178
2026-08-28 02:57flashyosship/10xf6d511887668f3cfship/flashyos/c471df988eb4
2026-08-28 03:00flashyosship/10xb03100679960481fship/flashyos/6f5364e289d5
2026-08-28 03:27flashyosship/10x4e61d3f2a578f867ship/flashyos/8fcce931a404
2026-08-28 16:55flashyosship/10xcba2480b5ffee43aship/flashyos/729a6046c2e8
2026-08-28 17:22flashyosship/10x94edd636b56600e9ship/flashyos/a3661380ad39

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.