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 | 573 | -46.6% vs last week |
|---|---|---|
| This month | 5042 | +188.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 | 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-09-03 11:28 | flashyos | ship/1 | 0x23b6207f26d3905a… | ship/flashyos/0faa34d6d849 |
| 2026-09-03 11:29 | flashyos | ship/1 | 0x9635842c52b277a1… | ship/flashyos/793dc19dcb46 |
| 2026-09-03 12:04 | flashyos | ship/1 | 0x0a6c8d9b2e5416d6… | ship/flashyos/10d7fbbf33bf |
| 2026-09-03 16:26 | flashyos | ship/1 | 0xd94e953643a5a721… | ship/flashyos/8e7d4c0dd85a |
| 2026-09-03 16:31 | flashyos | ship/1 | 0xb8ef231db413ad16… | ship/flashyos/4cd54e454744 |
| 2026-09-04 02:46 | flashyos | ship/1 | 0xcf978b23bd686d29… | ship/flashyos/7a1a0cc35133 |
| 2026-09-04 02:51 | flashyos | ship/1 | 0xc26e200eadfde1e1… | ship/flashyos/13c6c0591489 |
| 2026-09-04 04:32 | flashyos | ship/1 | 0x357c4d417cbe696f… | ship/flashyos/4fa8e0bc7174 |
| 2026-09-04 10:00 | flashyos | ship/1 | 0x9e15cd47219ac1aa… | ship/flashyos/73d7a801cdd1 |
| 2026-09-04 12:06 | flashyos | ship/1 | 0xd9937c9f5ac6f284… | ship/flashyos/bb7fb0a08059 |
| 2026-09-04 18:23 | flashyos | ship/1 | 0x3571ebc3e91b57cb… | ship/flashyos/5e9ede1d99d8 |
| 2026-09-04 17:17 | flashyos | ship/1 | 0x9c55c34e53b223ca… | ship/flashyos/d9ab311b47cf |
| 2026-09-04 17:25 | flashyos | ship/1 | 0xfed4cbacdfce4128… | ship/flashyos/47fc2933bbb8 |
| 2026-09-04 17:31 | flashyos | ship/1 | 0x79d2cad6bffe6116… | ship/flashyos/972b4eb8eb7b |
| 2026-09-04 17:37 | flashyos | ship/1 | 0xcd3ca72f09fdefa7… | ship/flashyos/59825ed631ec |
| 2026-09-04 17:45 | flashyos | ship/1 | 0xc1060523b2a5d127… | ship/flashyos/3c4395c2476a |
| 2026-09-04 18:25 | flashyos | ship/1 | 0x4faf01847f96499c… | ship/flashyos/8c30b5ee032f |
| 2026-09-04 18:39 | flashyos | ship/1 | 0x17977bbe3e72b569… | ship/flashyos/e20465ac6dc4 |
| 2026-09-04 18:58 | flashyos | ship/1 | 0x172be11c91cf7154… | ship/flashyos/c931922d0da3 |
| 2026-09-04 19:21 | flashyos | ship/1 | 0x13c617b9a13d5b12… | ship/flashyos/e306f5a1750d |
| 2026-09-04 19:58 | flashyos | ship/1 | 0x12604bb80d554d2f… | ship/flashyos/a7d7f4b07d3a |
| 2026-09-04 20:09 | flashyos | ship/1 | 0xa911849386edecac… | ship/flashyos/93ff4bc942c7 |
| 2026-09-04 20:19 | flashyos | ship/1 | 0x34005a2f17782e63… | ship/flashyos/849b77e11433 |
| 2026-08-18 21:27 | flashyid | ship/1 | 0x9fd27f07e2830426… | ship/flashyid/95d9f01d1418 |
| 2026-08-19 18:23 | flashyid | ship/1 | 0x54509618b01ddd4d… | ship/flashyid/3e569704c269 |
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.