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 | 642 | -39.9% vs last week |
|---|---|---|
| This month | 5180 | +219.6% 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 22:02 | flashyos | ship/1 | 0xfeea854390ef7421… | ship/flashyos/79d052f812cc |
| 2026-08-30 22:02 | flashyos | ship/1 | 0x27f7aec47b138f21… | ship/flashyos/0a0061efcb19 |
| 2026-08-30 22:03 | flashyos | ship/1 | 0x4630bb7ef84d22c1… | ship/flashyos/72d2153c9005 |
| 2026-08-30 22:10 | flashyos | ship/1 | 0x98a670b215801dd2… | ship/flashyos/8b7da3cce208 |
| 2026-08-30 22:30 | flashyos | ship/1 | 0x2b321af2c82be432… | ship/flashyos/78d2b922b59a |
| 2026-08-30 22:34 | flashyos | ship/1 | 0x33d690d510f8a3c9… | ship/flashyos/fac594e834c8 |
| 2026-08-30 22:37 | flashyos | ship/1 | 0x872da4bda2c89efc… | ship/flashyos/11b7bad42052 |
| 2026-08-31 00:22 | flashyos | ship/1 | 0x670bf1f36bf852f1… | ship/flashyos/05fcbd92b31e |
| 2026-08-31 00:23 | flashyos | ship/1 | 0x902b56b5d427c900… | ship/flashyos/ec999a25ed7e |
| 2026-08-31 00:24 | flashyos | ship/1 | 0x4bed477948e85899… | ship/flashyos/94a59269d7a2 |
| 2026-08-31 00:34 | flashyos | ship/1 | 0x551c1e302af124af… | ship/flashyos/b133d1d2e5e8 |
| 2026-08-31 00:39 | flashyos | ship/1 | 0x0e36365ccecb6087… | ship/flashyos/ff4b8cc8392b |
| 2026-08-31 00:40 | flashyos | ship/1 | 0xd3f67f1fc7bebde9… | ship/flashyos/ab058032dcaa |
| 2026-08-31 00:40 | flashyos | ship/1 | 0x070e50400a63e699… | ship/flashyos/16339799e71b |
| 2026-08-31 00:41 | flashyos | ship/1 | 0xf30cd40e54282af6… | ship/flashyos/6fc726450854 |
| 2026-08-31 00:49 | flashyos | ship/1 | 0x2cd6a7fd42c1e5f6… | ship/flashyos/c1edc3492d07 |
| 2026-08-31 00:51 | flashyos | ship/1 | 0x4ea2f3a0d80087e1… | ship/flashyos/d8055d75f11a |
| 2026-08-31 00:54 | flashyos | ship/1 | 0x6fcc6e03731bcd2d… | ship/flashyos/11e73c2e8c3e |
| 2026-08-31 00:54 | flashyos | ship/1 | 0x6dfc2d65fe418711… | ship/flashyos/82c1ad3d05eb |
| 2026-08-31 00:56 | flashyos | ship/1 | 0x85416c18395567fb… | ship/flashyos/29db58a64995 |
| 2026-08-31 00:56 | flashyos | ship/1 | 0x21c11dfb6d0da510… | ship/flashyos/7149d8a90d5a |
| 2026-08-31 00:58 | flashyos | ship/1 | 0x68a211f7b4001837… | ship/flashyos/882efdb7c8c0 |
| 2026-08-31 01:00 | flashyos | ship/1 | 0xc989935629f10823… | ship/flashyos/af6d060c93c4 |
| 2026-08-31 01:01 | flashyos | ship/1 | 0xc23ee90f9a1a49ac… | ship/flashyos/88b6153692b6 |
| 2026-08-31 01:03 | flashyos | ship/1 | 0x73803106e890aad6… | ship/flashyos/9aee810aef05 |
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.