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 | 666 | -37.2% vs last week |
|---|---|---|
| This month | 5197 | +224% 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-28 20:57 | flashyos | ship/1 | 0xf15309a467b216b4… | ship/flashyos/7d2f780ac238 |
| 2026-08-29 11:35 | flashyos | ship/1 | 0x1444d3ca46adebea… | ship/flashyos/f9e69e6c647c |
| 2026-08-29 17:04 | flashyos | ship/1 | 0xf398f866cfce4f82… | ship/flashyos/c1c67b82f839 |
| 2026-08-29 19:32 | flashyos | ship/1 | 0x173015d05d3eecb2… | ship/flashyos/12d6f964c8d4 |
| 2026-08-29 19:52 | flashyos | ship/1 | 0x51aab2c21139fa47… | ship/flashyos/88f9a2bd2c4f |
| 2026-08-29 19:55 | flashyos | ship/1 | 0x979f664444e04a8d… | ship/flashyos/8dd115687790 |
| 2026-08-29 20:06 | flashyos | ship/1 | 0x99f0916db8b9d534… | ship/flashyos/c8b0d7c2d9c4 |
| 2026-08-29 23:32 | flashyos | ship/1 | 0x5a717b64dffccb96… | ship/flashyos/30e7f998b278 |
| 2026-08-29 23:56 | flashyos | ship/1 | 0xa26dd87d6ce738e5… | ship/flashyos/64f3433228aa |
| 2026-08-30 00:34 | flashyos | ship/1 | 0xf040c172c4bf7190… | ship/flashyos/69dc12df60bd |
| 2026-08-30 01:07 | flashyos | ship/1 | 0xe00e2f9941aeef67… | ship/flashyos/5bb268ebb703 |
| 2026-08-30 01:10 | flashyos | ship/1 | 0x3b30513a1a1f8e7c… | ship/flashyos/573b68979fd4 |
| 2026-08-30 01:26 | flashyos | ship/1 | 0x52e3a8a159101564… | ship/flashyos/520bdee204ab |
| 2026-08-30 01:33 | flashyos | ship/1 | 0x812321ad1b161eb5… | ship/flashyos/740027a90584 |
| 2026-08-30 01:42 | flashyos | ship/1 | 0x4c98531cd6a1ff39… | ship/flashyos/aa44e40cbabc |
| 2026-08-30 01:51 | flashyos | ship/1 | 0x3aadea58755c08b7… | ship/flashyos/1c6cf7c1aac4 |
| 2026-08-30 01:51 | flashyos | ship/1 | 0x42fdd7f4fbe83067… | ship/flashyos/f540834858f6 |
| 2026-08-30 01:57 | flashyos | ship/1 | 0xfe2c5314e3a87928… | ship/flashyos/a4dce18321eb |
| 2026-08-30 01:57 | flashyos | ship/1 | 0xc89a81399ad65ea5… | ship/flashyos/30f00812a3b0 |
| 2026-08-30 02:10 | flashyos | ship/1 | 0x2af3a0ae183f4a9c… | ship/flashyos/f2925904208a |
| 2026-08-30 02:17 | flashyos | ship/1 | 0x9580da3338ae4269… | ship/flashyos/46b3ad36ea87 |
| 2026-08-30 02:17 | flashyos | ship/1 | 0x7db41115ce4b561c… | ship/flashyos/e42496cd9481 |
| 2026-08-30 02:26 | flashyos | ship/1 | 0xac786e45e7aaab05… | ship/flashyos/53df476a2a55 |
| 2026-08-30 02:55 | flashyos | ship/1 | 0x8174164b2f40d12b… | ship/flashyos/6d36866db657 |
| 2026-08-30 02:55 | flashyos | ship/1 | 0xe464a89ab8f78078… | ship/flashyos/8233af3cdcab |
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.