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 | 640 | -40.1% vs last week |
|---|---|---|
| This month | 5177 | +218.8% 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-31 01:11 | flashyos | ship/1 | 0xe728e037c93dbf05… | ship/flashyos/e23a013f0afd |
| 2026-08-31 01:12 | flashyos | ship/1 | 0xbf24c98e4a767847… | ship/flashyos/4a147a8c830f |
| 2026-08-31 01:19 | flashyos | ship/1 | 0x94c0eb3a34d16b22… | ship/flashyos/458fdee3254f |
| 2026-08-31 01:21 | flashyos | ship/1 | 0xbfb0d3d6cdd766ec… | ship/flashyos/e602f5824053 |
| 2026-08-31 01:28 | flashyos | ship/1 | 0x5bb54e104cdb2589… | ship/flashyos/a3d419185136 |
| 2026-08-31 01:31 | flashyos | ship/1 | 0x17d465cd24b9712a… | ship/flashyos/3131de5290cf |
| 2026-08-31 01:31 | flashyos | ship/1 | 0xbc764f039b1bd6e7… | ship/flashyos/a20f4e316070 |
| 2026-08-31 01:43 | flashyos | ship/1 | 0x8bab0df8f38207c3… | ship/flashyos/7e4e824be440 |
| 2026-08-31 01:49 | flashyos | ship/1 | 0xcc27c9de9529015a… | ship/flashyos/38bdc53eed0b |
| 2026-08-31 01:49 | flashyos | ship/1 | 0x697071b207200838… | ship/flashyos/0be9afd4979c |
| 2026-08-31 02:16 | flashyos | ship/1 | 0x88fb24e16d76b397… | ship/flashyos/cab85dfcb74e |
| 2026-08-31 02:16 | flashyos | ship/1 | 0x14855dfbfad10453… | ship/flashyos/e956aca00541 |
| 2026-08-31 02:17 | flashyos | ship/1 | 0x4d1b08d93e7a5ca5… | ship/flashyos/38b8d9b1e893 |
| 2026-08-31 02:18 | flashyos | ship/1 | 0x5ce6655b99a1b7d3… | ship/flashyos/6338cb249f83 |
| 2026-08-31 02:31 | flashyos | ship/1 | 0xd83bc7087119b396… | ship/flashyos/ecf78696570c |
| 2026-08-31 02:32 | flashyos | ship/1 | 0x55e9af47cde0087e… | ship/flashyos/a67772d0e6ba |
| 2026-08-31 02:56 | flashyos | ship/1 | 0xba8bf242a9cc2f53… | ship/flashyos/3e6e7422d850 |
| 2026-08-31 03:12 | flashyos | ship/1 | 0xe6867d2e15fad347… | ship/flashyos/f9712ad3b6af |
| 2026-08-31 03:12 | flashyos | ship/1 | 0x8201b9cda7cdb918… | ship/flashyos/fe82c87fcb89 |
| 2026-08-31 14:07 | flashyos | ship/1 | 0xc2391e387142b081… | ship/flashyos/fdd09df3bedb |
| 2026-08-31 10:57 | flashyos | ship/1 | 0x6544a13a79479b96… | ship/flashyos/116b956fbb5e |
| 2026-08-31 12:13 | flashyos | ship/1 | 0xed7f3ac5d92024fa… | ship/flashyos/9b5b45030af5 |
| 2026-08-31 12:13 | flashyos | ship/1 | 0xa7a09272539b04d9… | ship/flashyos/9aa47b6a7651 |
| 2026-08-31 12:30 | flashyos | ship/1 | 0x76718911c1b4ffd1… | ship/flashyos/b2b00f6510a6 |
| 2026-08-31 12:30 | flashyos | ship/1 | 0xc97cebdd620c1173… | ship/flashyos/20a03b1c05e1 |
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.