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 7681 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 size | 7681 |
|---|---|
| Head root | 0x65c796ed397bc9e35d84a5d6f8ebac3d5385428e8f999efa1b838949ab8ce9af |
| Most recent leaf | 2026-09-22T20:33:43.900Z |
| Stream regenerated | 2026-09-22T20:33:44.342Z |
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.
| Source | Event | Status |
|---|---|---|
| academy | certificate/1 | ✓ folding |
| claimyourgold | receipt/1 | ✓ folding |
| flashyid | verification/1 | ◇ awaiting first event |
| flashynetwork | settlement/1 | ✓ folding |
| flashyos | countersignature/1 | ◇ awaiting first event |
| gdagroup | intent/1 | ✓ folding |
| goldholdings | intent/1 | ✓ folding |
| intentmesh | intent/1 | ✓ folding |
| magician | introduction/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 week | 651 | -38.9% vs last week |
|---|---|---|
| This month | 5182 | +220.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.
| Source | Leaves | Kinds |
|---|---|---|
| flashynetwork | 4542 | checkpoint/1, devlog/1, settlement/1 |
| flashyos | 991 | checkpoint/1, ship/1 |
| claimyourgold | 932 | checkpoint/1, receipt/1, ship/1 |
| gdagroup | 250 | checkpoint/1, devlog/1, intent/1, ship/1 |
| academy | 225 | certificate/1, checkpoint/1, devlog/1, ship/1 |
| flashygroup | 179 | checkpoint/1, ship/1 |
| goldholdings | 162 | checkpoint/1, intent/1, ship/1 |
| flashyid | 157 | checkpoint/1, devlog/1, ship/1 |
| flashygold | 113 | checkpoint/1, devlog/1, ship/1 |
| mlgblockchain | 85 | checkpoint/1, ship/1 |
| intentmesh | 37 | checkpoint/1, intent/1, ship/1 |
| rites | 8 | checkpoint/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.
| Time (UTC) | Source | Kind | Hash | Ref |
|---|---|---|---|---|
| 2026-08-30 17:18 | flashyos | ship/1 | 0x19102c46f586f89b… | ship/flashyos/06e1174e5224 |
| 2026-08-30 17:29 | flashyos | ship/1 | 0x70e9184f1d869295… | ship/flashyos/9d5c4962eee6 |
| 2026-08-30 18:01 | flashyos | ship/1 | 0xa13936138640b641… | ship/flashyos/25eb7a513576 |
| 2026-08-30 18:05 | flashyos | ship/1 | 0xcb57447418e0306f… | ship/flashyos/4b91ecaacdce |
| 2026-08-30 22:26 | flashyos | ship/1 | 0x4dae2a169c38562e… | ship/flashyos/64720890f388 |
| 2026-08-30 18:26 | flashyos | ship/1 | 0x4ceb3698d1b81122… | ship/flashyos/58a7e4ff88e3 |
| 2026-08-30 22:30 | flashyos | ship/1 | 0xa6201ba7980b96de… | ship/flashyos/c8d761b1d418 |
| 2026-08-30 19:13 | flashyos | ship/1 | 0xbf8bb0226d14ce95… | ship/flashyos/e669cd92da24 |
| 2026-08-30 19:31 | flashyos | ship/1 | 0x9462175d423949e9… | ship/flashyos/fdf73217514b |
| 2026-08-30 19:35 | flashyos | ship/1 | 0x5160139c8db41fb3… | ship/flashyos/75e88b422fa4 |
| 2026-08-30 19:44 | flashyos | ship/1 | 0x70189e798438770f… | ship/flashyos/513943ee1556 |
| 2026-08-30 19:47 | flashyos | ship/1 | 0xf64c02d84ac10bde… | ship/flashyos/9c19569459bf |
| 2026-08-31 00:24 | flashyos | ship/1 | 0xa4055e6209f08455… | ship/flashyos/119f420d69d1 |
| 2026-08-31 00:40 | flashyos | ship/1 | 0x840a30d814540981… | ship/flashyos/8a8d3258c470 |
| 2026-08-30 20:41 | flashyos | ship/1 | 0xd3d98e8ecae30594… | ship/flashyos/aa0835181554 |
| 2026-08-30 20:43 | flashyos | ship/1 | 0xe66cb5b448e84ffa… | ship/flashyos/e23d3f2a36f9 |
| 2026-08-30 20:53 | flashyos | ship/1 | 0x21d6eb61e1118c78… | ship/flashyos/ebcf8a04b6ad |
| 2026-08-30 20:55 | flashyos | ship/1 | 0xf252ae24d5968b5a… | ship/flashyos/990091c9e3d5 |
| 2026-08-30 21:24 | flashyos | ship/1 | 0x9ecee97274753eff… | ship/flashyos/e8160f34f326 |
| 2026-08-31 01:28 | flashyos | ship/1 | 0x1d05ea0ac1460f8b… | ship/flashyos/d8da55b94623 |
| 2026-08-30 21:42 | flashyos | ship/1 | 0x20da8faf85a84a0b… | ship/flashyos/618f59769cd2 |
| 2026-08-31 01:42 | flashyos | ship/1 | 0x6bee8cc27b74be8f… | ship/flashyos/8f32b8440bee |
| 2026-08-30 21:47 | flashyos | ship/1 | 0x0001ea3257b887d2… | ship/flashyos/0fcf252321c2 |
| 2026-08-30 21:56 | flashyos | ship/1 | 0x0777d7210fc91cb5… | ship/flashyos/35694d1e5800 |
| 2026-08-30 21:59 | flashyos | ship/1 | 0x0226f6cd9d53780c… | ship/flashyos/6ace1379604e |
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.