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 10409 leaves from 15 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 | 10409 |
|---|---|
| Head root | 0xc3622336df72608fb0cafe2f708102a82cb227a0ea383b0bbbf81d32c4e59f82 |
| Most recent leaf | 2026-10-15T09:17:00.056Z |
| Stream regenerated | 2026-10-15T09:17:00.384Z |
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, mail/1, initiative/1 | ✓ folding |
| 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 | ✓ folding |
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 | 793 | +0.6% vs last week |
|---|---|---|
| This month | 2944 | -50.7% 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 | 6139 | checkpoint/1, devlog/1, settlement/1 |
| flashyos | 1401 | checkpoint/1, devlog/1, initiative/1, ship/1 |
| claimyourgold | 1107 | anchor/1, checkpoint/1, devlog/1, receipt/1, ship/1 |
| gdagroup | 301 | checkpoint/1, devlog/1, intent/1, ship/1 |
| academy | 252 | certificate/1, checkpoint/1, devlog/1, ship/1 |
| flashygroup | 252 | checkpoint/1, devlog/1, ship/1 |
| magician | 216 | checkpoint/1, ship/1 |
| goldholdings | 207 | checkpoint/1, devlog/1, intent/1, ship/1 |
| flashyid | 199 | checkpoint/1, devlog/1, ship/1 |
| flashygold | 136 | checkpoint/1, devlog/1, ship/1 |
| mlgblockchain | 101 | checkpoint/1, ship/1 |
| intentmesh | 52 | checkpoint/1, devlog/1, intent/1, ship/1 |
| flashyos-ritual | 29 | ritual/1 |
| rites | 15 | 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-14 11:28 | flashyid | ship/1 | 0x0745b5e76a4432e1… | ship/flashyid/2d767511c172 |
| 2026-10-14 11:28 | flashyid | devlog/1 | 0xd97dbe80ef337b25… | https://github.com/FlashyLa… |
| 2026-10-14 03:25 | flashyid | ship/1 | 0x0b57614312a02db7… | ship/flashyid/529367a1f897 |
| 2026-10-14 03:25 | flashyid | devlog/1 | 0xb0f8024c1dffb0dc… | https://github.com/FlashyLa… |
| 2026-10-14 09:34 | flashyid | checkpoint/1 | 0x7bb210e492f251d6… | https://www.flashyid.com/.w… |
| 2026-10-13 15:46 | flashyid | ship/1 | 0x488eaf184e79badb… | ship/flashyid/d70bf8c061c7 |
| 2026-10-14 02:11 | flashyid | ship/1 | 0xf59c15a237fbe32f… | ship/flashyid/ef7d5a06ec7b |
| 2026-10-14 03:23 | flashyid | ship/1 | 0x4dbd9b026586de3e… | ship/flashyid/7b1a5afaa92b |
| 2026-10-13 15:46 | flashyid | checkpoint/1 | 0x55af238250c9c14f… | https://www.flashyid.com/.w… |
| 2026-10-10 06:49 | flashyid | ship/1 | 0xe45cd71d097096b7… | ship/flashyid/11ceb13e87bf |
| 2026-10-13 11:53 | flashyid | checkpoint/1 | 0x63458be16fe9ed54… | https://www.flashyid.com/.w… |
| 2026-09-24 15:06 | flashyid | ship/1 | 0x402154ce34bfbb0f… | ship/flashyid/e4f5b19061e8 |
| 2026-09-24 17:30 | flashyid | ship/1 | 0x3638bae4f86b09a7… | ship/flashyid/43f78e4c8235 |
| 2026-09-25 20:58 | flashyid | ship/1 | 0xae00ce34a72b8ae2… | ship/flashyid/536b5c669b19 |
| 2026-09-28 22:27 | flashyid | ship/1 | 0xfcece7f287fe2829… | ship/flashyid/a2706c0bc890 |
| 2026-09-29 05:59 | flashyid | ship/1 | 0x88330a687e68d152… | ship/flashyid/fbba4e9eeea4 |
| 2026-10-10 05:17 | flashyid | ship/1 | 0x15202a59b0faa0c8… | ship/flashyid/b316bac9a39b |
| 2026-10-10 06:36 | flashyid | ship/1 | 0xc6d1c03233ecfc74… | ship/flashyid/4850c1348c2b |
| 2026-10-10 05:21 | flashyid | checkpoint/1 | 0xc4ab856808fefac3… | https://www.flashyid.com/.w… |
| 2026-10-04 18:24 | flashyid | ship/1 | 0xf5e8e17f1354ffde… | ship/flashyid/04e61f877cbf |
| 2026-10-09 23:56 | flashyid | ship/1 | 0x57c0e64a65e38c2b… | ship/flashyid/7177e08c8719 |
| 2026-10-04 18:24 | flashyid | devlog/1 | 0xa82fd99cf90ddfaa… | https://github.com/FlashyLa… |
| 2026-10-09 23:56 | flashyid | devlog/1 | 0xcdc3245ea6d38d82… | https://github.com/FlashyLa… |
| 2026-10-09 23:56 | flashyid | checkpoint/1 | 0xca248573f528777a… | https://www.flashyid.com/.w… |
| 2026-10-04 08:25 | flashyid | ship/1 | 0x4cb7cd81f3a4f0f5… | ship/flashyid/4c1470bfe7c4 |
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.