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 | 567 | -46.7% vs last week |
|---|---|---|
| This month | 5012 | +182.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.
| 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:23 | flashyid | ship/1 | 0x338d3b1689b367ae… | ship/flashyid/e9de27f952d9 |
| 2026-08-30 17:38 | flashyid | ship/1 | 0x07a8633abba8f0b8… | ship/flashyid/26362253d17b |
| 2026-08-30 21:48 | flashyid | ship/1 | 0x92932809528a9025… | ship/flashyid/9878db1df5a6 |
| 2026-08-30 21:57 | flashyid | ship/1 | 0x47e63d2d119dd6e5… | ship/flashyid/5218ec7de7f1 |
| 2026-08-30 17:59 | flashyid | ship/1 | 0x82d04c7f4f2142fa… | ship/flashyid/bac24513b16b |
| 2026-08-30 18:01 | flashyid | ship/1 | 0xcbdad8b46f5baf2d… | ship/flashyid/0a5721db680e |
| 2026-08-30 18:37 | flashyid | ship/1 | 0xfbd81982ee67030a… | ship/flashyid/00c1b6854ae8 |
| 2026-08-30 19:25 | flashyid | ship/1 | 0x6d35b7ab2f37f994… | ship/flashyid/ba1973808eae |
| 2026-08-30 19:45 | flashyid | ship/1 | 0x0597db0adbda9615… | ship/flashyid/58ffb8d6323c |
| 2026-08-30 21:38 | flashyid | ship/1 | 0xa5ea3c0e50957611… | ship/flashyid/a985949045e7 |
| 2026-08-30 21:40 | flashyid | ship/1 | 0x5189d9011a2f53d9… | ship/flashyid/420302ed7d13 |
| 2026-08-30 21:44 | flashyid | ship/1 | 0xc0fbd1984ccdfc89… | ship/flashyid/b780e2f9e18f |
| 2026-08-30 21:44 | flashyid | ship/1 | 0x0dbee2d5c5121b4d… | ship/flashyid/5021b43ba2e4 |
| 2026-08-30 21:55 | flashyid | ship/1 | 0xcf4031d31e6eb763… | ship/flashyid/e6d3145202dc |
| 2026-08-30 21:57 | flashyid | ship/1 | 0x418f1e42e58f6967… | ship/flashyid/71e551c7c295 |
| 2026-08-30 22:06 | flashyid | ship/1 | 0xc11e7a1551357d0e… | ship/flashyid/e53cf38d9339 |
| 2026-08-31 00:31 | flashyid | ship/1 | 0x5fdebce64b1b42d9… | ship/flashyid/72bf2591f827 |
| 2026-08-31 00:42 | flashyid | ship/1 | 0xdc06f38156df3daa… | ship/flashyid/dfbaa1386d93 |
| 2026-08-31 00:43 | flashyid | ship/1 | 0x0f0e76499166fb99… | ship/flashyid/e02d038da563 |
| 2026-08-31 00:50 | flashyid | ship/1 | 0xbfcdbedc1b400935… | ship/flashyid/cd795a3261bf |
| 2026-08-31 01:00 | flashyid | ship/1 | 0x46dda237527c1da0… | ship/flashyid/27d4096d4b34 |
| 2026-08-31 01:00 | flashyid | ship/1 | 0x34a6a9950eb31859… | ship/flashyid/14d87f825142 |
| 2026-08-31 01:01 | flashyid | ship/1 | 0x94a46572961a8b1d… | ship/flashyid/9ce26ba3c7e1 |
| 2026-08-31 01:45 | flashyid | ship/1 | 0x4bf8eac50531036c… | ship/flashyid/e79c4ee87b23 |
| 2026-08-31 02:19 | flashyid | ship/1 | 0x3fa5d96fb7f9e6b5… | ship/flashyid/ad3e5305bc26 |
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.