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 7357 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 | 7357 |
|---|---|
| Head root | 0xc7634c7a09b345a2e0a107179889c19480c12109c40368b3056fabfba2890efb |
| Most recent leaf | 2026-09-21T12:57:45.274Z |
| Stream regenerated | 2026-09-21T12:57:45.569Z |
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 | 707 | -33.4% vs last week |
|---|---|---|
| This month | 5059 | +251.3% 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 | 4468 | checkpoint/1, devlog/1, settlement/1 |
| claimyourgold | 924 | checkpoint/1, receipt/1, ship/1 |
| flashyos | 872 | checkpoint/1, ship/1 |
| gdagroup | 235 | checkpoint/1, intent/1, ship/1 |
| academy | 188 | certificate/1, checkpoint/1, ship/1 |
| flashygroup | 172 | checkpoint/1, ship/1 |
| goldholdings | 151 | checkpoint/1, intent/1, ship/1 |
| flashyid | 132 | checkpoint/1, ship/1 |
| flashygold | 96 | checkpoint/1, ship/1 |
| mlgblockchain | 81 | checkpoint/1, ship/1 |
| intentmesh | 32 | checkpoint/1, intent/1, ship/1 |
| rites | 6 | 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 20:31 | flashyos | ship/1 | 0x21494aeeff2b9379… | ship/flashyos/5f4968be0d9f |
| 2026-08-31 20:35 | flashyos | ship/1 | 0x9a1287a5026aba52… | ship/flashyos/c1bb699217d5 |
| 2026-08-31 20:42 | flashyos | ship/1 | 0x6fd28b2a925c05a2… | ship/flashyos/ca51c819aee2 |
| 2026-08-31 20:45 | flashyos | ship/1 | 0xa0fd7401260b997d… | ship/flashyos/802d820c48ee |
| 2026-08-31 20:47 | flashyos | ship/1 | 0x1a662a44bb439f09… | ship/flashyos/22d3c3a64178 |
| 2026-08-31 20:49 | flashyos | ship/1 | 0xd03747a5da463776… | ship/flashyos/99d09bb9679e |
| 2026-08-31 21:02 | flashyos | ship/1 | 0x83ec5e42fae5e0d1… | ship/flashyos/99aa5bbf4961 |
| 2026-08-31 21:05 | flashyos | ship/1 | 0x9ec72cd95e347dc0… | ship/flashyos/bef64ae0318a |
| 2026-08-31 21:07 | flashyos | ship/1 | 0x993843b3d3c768c5… | ship/flashyos/9853bd9aa159 |
| 2026-08-31 21:10 | flashyos | ship/1 | 0xeec7c486b7b6245f… | ship/flashyos/52fc794214b8 |
| 2026-08-31 21:23 | flashyos | ship/1 | 0x8a194460bcd189c6… | ship/flashyos/77a092aa113e |
| 2026-08-31 21:39 | flashyos | ship/1 | 0x4ea8f77711d2ed17… | ship/flashyos/ef77a9118c8d |
| 2026-08-31 21:57 | flashyos | ship/1 | 0x1d83700dbbed2732… | ship/flashyos/3a6690363975 |
| 2026-08-31 22:24 | flashyos | ship/1 | 0xb14913fb3b94de95… | ship/flashyos/c64198c4bee8 |
| 2026-09-01 08:18 | flashyos | ship/1 | 0x38dac22998a4cc12… | ship/flashyos/f6412c3d0d76 |
| 2026-09-01 08:19 | flashyos | ship/1 | 0x3ad6f8c2d0c6b029… | ship/flashyos/afbb72a28ea5 |
| 2026-09-01 08:32 | flashyos | ship/1 | 0x9a57e516bb71207f… | ship/flashyos/9f85e5c2f088 |
| 2026-09-01 08:36 | flashyos | ship/1 | 0xaef5018d60137ec4… | ship/flashyos/b4dcdf3a27b8 |
| 2026-09-01 10:24 | flashyos | ship/1 | 0x1fa7575e1c58ccd0… | ship/flashyos/8e5627dd07a6 |
| 2026-09-01 10:27 | flashyos | ship/1 | 0x39a9a45f27015485… | ship/flashyos/296688a48d79 |
| 2026-09-01 14:46 | flashyos | ship/1 | 0x39d327899d3de0ff… | ship/flashyos/813cc6befc6b |
| 2026-09-01 14:59 | flashyos | ship/1 | 0xe2086c41efeb5413… | ship/flashyos/3be8d40cd40d |
| 2026-09-01 15:13 | flashyos | ship/1 | 0x64fd50a50f4cbea3… | ship/flashyos/03f2c03abc0b |
| 2026-09-01 15:16 | flashyos | ship/1 | 0xe29bff17a0284aaf… | ship/flashyos/9bde84293aa6 |
| 2026-09-01 15:24 | flashyos | ship/1 | 0xd217de61a9951b2b… | ship/flashyos/3312536a3069 |
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.