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 8822 leaves from 14 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 | 8822 |
|---|---|
| Head root | 0x14ae1d69854a5c84c7fbb645e695cbe8e750035d82e469b9a43170cf8e9a6e0c |
| Most recent leaf | 2026-10-04T18:16:17.511Z |
| Stream regenerated | 2026-10-04T18:16:17.931Z |
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 |
| gdagroup-ritual | ritual/1 | ✓ folding |
| flashyos-ritual | ritual/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 | 287 | -31.8% vs last week |
|---|---|---|
| This month | 3163 | -28.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 | 5219 | checkpoint/1, devlog/1, settlement/1 |
| flashyos | 1145 | checkpoint/1, devlog/1, ship/1 |
| claimyourgold | 1010 | checkpoint/1, devlog/1, receipt/1, ship/1 |
| gdagroup | 270 | checkpoint/1, devlog/1, intent/1, ship/1 |
| academy | 235 | certificate/1, checkpoint/1, devlog/1, ship/1 |
| flashygroup | 228 | checkpoint/1, devlog/1, ship/1 |
| goldholdings | 183 | checkpoint/1, devlog/1, intent/1, ship/1 |
| flashyid | 167 | checkpoint/1, devlog/1, ship/1 |
| flashygold | 115 | checkpoint/1, devlog/1, ship/1 |
| magician | 103 | checkpoint/1, ship/1 |
| mlgblockchain | 92 | checkpoint/1, ship/1 |
| intentmesh | 40 | checkpoint/1, devlog/1, intent/1, ship/1 |
| rites | 13 | checkpoint/1, ship/1 |
| gdagroup-ritual | 2 | ritual/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-10-04 18:16 | flashynetwork | checkpoint/1 | 0x493a8a741df25e03… | https://flashynetwork.com/.… |
| 2026-10-04 17:40 | flashynetwork | checkpoint/1 | 0xf32a374571df56c2… | https://flashynetwork.com/.… |
| 2026-09-29 04:54 | mlgblockchain | ship/1 | 0xc212465d9a344730… | ship/mlgblockchain/bdd30d52… |
| 2026-10-03 09:56 | mlgblockchain | checkpoint/1 | 0x8f8da0f3e3b25ac1… | https://www.mlgblockchain.c… |
| 2026-09-01 07:52 | magician | ship/1 | 0x8d198a9877705828… | ship/magician/73d274a1bfff |
| 2026-09-01 08:06 | magician | ship/1 | 0x4bf1383eb857f346… | ship/magician/adc6a18577aa |
| 2026-09-01 08:12 | magician | ship/1 | 0xfb1dda1dca6f8697… | ship/magician/686e81896c98 |
| 2026-09-01 08:13 | magician | ship/1 | 0x03716f1cd4be0c73… | ship/magician/a5951b228a49 |
| 2026-09-01 08:13 | magician | ship/1 | 0x0e35c42fa241045f… | ship/magician/cbfedd5178b2 |
| 2026-09-01 08:31 | magician | ship/1 | 0x00e9de147d31f90b… | ship/magician/bd5842c4af6c |
| 2026-09-01 08:31 | magician | ship/1 | 0xf903ea50a7433263… | ship/magician/c0ad6fc75c90 |
| 2026-09-01 08:36 | magician | ship/1 | 0xf2876e1ebe941b60… | ship/magician/99e0d2ac79d1 |
| 2026-09-01 14:45 | magician | ship/1 | 0x2621c96373c05c95… | ship/magician/c3f7b236ac12 |
| 2026-09-01 14:45 | magician | ship/1 | 0x43e000c934a411d0… | ship/magician/4b4cdcfce502 |
| 2026-09-01 14:57 | magician | ship/1 | 0x0533b8c6200c5636… | ship/magician/06082bf7c259 |
| 2026-09-01 14:57 | magician | ship/1 | 0x3cfe1271f341d9d1… | ship/magician/8fd75d130ba9 |
| 2026-09-01 15:12 | magician | ship/1 | 0xa43b137dea4b4d2e… | ship/magician/a8aed13ed779 |
| 2026-09-01 15:12 | magician | ship/1 | 0x0e1914e26310b29e… | ship/magician/99584a5f7e8a |
| 2026-09-01 15:16 | magician | ship/1 | 0xf8f3ea6b1d99be3f… | ship/magician/75e50e9c6d59 |
| 2026-09-01 15:23 | magician | ship/1 | 0xa3e6bc6e324213b2… | ship/magician/3c8396bcbfcb |
| 2026-09-01 15:23 | magician | ship/1 | 0x5e16d3880b125dd8… | ship/magician/29a961f1ad5e |
| 2026-09-01 15:47 | magician | ship/1 | 0x0d5ea4cd22c51cad… | ship/magician/ad39ae458da7 |
| 2026-09-01 15:47 | magician | ship/1 | 0xbb3cdfeecc891a28… | ship/magician/327f2e815272 |
| 2026-09-01 17:56 | magician | ship/1 | 0x2f08820c635293e5… | ship/magician/547a73a79bf8 |
| 2026-09-01 17:57 | magician | ship/1 | 0xaa484c2ccf6142d0… | ship/magician/13ede4d7cd45 |
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.