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 7356 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 | 7356 |
|---|---|
| Head root | 0xc5b5528a0c1d2baa36fa7e235d59a9260b90e2426c9db02327e329af7805d211 |
| Most recent leaf | 2026-09-21T12:25:07.864Z |
| Stream regenerated | 2026-09-21T12:57:07.989Z |
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 | 755 | -30.5% vs last week |
|---|---|---|
| This month | 5069 | +254.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 | 4467 | 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 14:36 | flashyos | ship/1 | 0xae58794135df887a… | ship/flashyos/cbfad4985275 |
| 2026-08-31 15:02 | flashyos | ship/1 | 0x498344e84fb10e9b… | ship/flashyos/5650127f0ee1 |
| 2026-08-31 15:05 | flashyos | ship/1 | 0x9700d5c4b9c39458… | ship/flashyos/1a5f06806062 |
| 2026-08-31 15:05 | flashyos | ship/1 | 0x28f67e4a5e2e4a3c… | ship/flashyos/997aac33e96d |
| 2026-08-31 19:42 | flashyos | ship/1 | 0xdc1bff62a5107d96… | ship/flashyos/863bd2b2bfc1 |
| 2026-08-31 16:05 | flashyos | ship/1 | 0xfbca6758249f93f7… | ship/flashyos/62c40752e7c4 |
| 2026-08-31 16:06 | flashyos | ship/1 | 0xf6f0eb5fa34f11ea… | ship/flashyos/68e15ffd24cb |
| 2026-08-31 16:07 | flashyos | ship/1 | 0x09bd2fd264102d87… | ship/flashyos/a218143db40b |
| 2026-08-31 16:07 | flashyos | ship/1 | 0x95572f689fc384e0… | ship/flashyos/90b4cf781e06 |
| 2026-08-31 16:08 | flashyos | ship/1 | 0x747f66bb1900188d… | ship/flashyos/02e0c2d568d6 |
| 2026-08-31 16:09 | flashyos | ship/1 | 0x7915f7a154eb65fd… | ship/flashyos/d653a21743ae |
| 2026-08-31 16:12 | flashyos | ship/1 | 0x1b38c4ac620e2354… | ship/flashyos/e6477f26f040 |
| 2026-08-31 16:12 | flashyos | ship/1 | 0x8ad0e16c67b0a46f… | ship/flashyos/5887da0fe9f1 |
| 2026-08-31 16:15 | flashyos | ship/1 | 0x381ddd66bea7b59e… | ship/flashyos/c5ca7b62e276 |
| 2026-08-31 16:17 | flashyos | ship/1 | 0xbd45bfafad174aa3… | ship/flashyos/fd7850851e67 |
| 2026-08-31 16:18 | flashyos | ship/1 | 0xa0a63594cb2b678e… | ship/flashyos/ae3761a5f57e |
| 2026-08-31 16:18 | flashyos | ship/1 | 0x1a362420a32f992a… | ship/flashyos/efdb7b9e2bc6 |
| 2026-08-31 16:21 | flashyos | ship/1 | 0x75a3deec3028eba3… | ship/flashyos/aa5cc24f7c0f |
| 2026-08-31 16:21 | flashyos | ship/1 | 0xa75b528b3317947d… | ship/flashyos/89690161c4ec |
| 2026-08-31 16:25 | flashyos | ship/1 | 0xbce63eb85b3ad959… | ship/flashyos/21bb9fec27f9 |
| 2026-08-31 16:26 | flashyos | ship/1 | 0x22678b18913543f5… | ship/flashyos/4e2d1503b6d7 |
| 2026-08-31 16:28 | flashyos | ship/1 | 0xcf56dd3deb5e884e… | ship/flashyos/95eab7aec53a |
| 2026-08-31 16:30 | flashyos | ship/1 | 0x15bd5c63fc0d98b5… | ship/flashyos/fd884415931a |
| 2026-08-31 16:30 | flashyos | ship/1 | 0x43681d397b800c86… | ship/flashyos/85ba6614ee0d |
| 2026-08-31 16:31 | flashyos | ship/1 | 0xa17bf94f802f6243… | ship/flashyos/a003c032bc37 |
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.