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 | 661 | -37.5% vs last week |
|---|---|---|
| This month | 5188 | +221.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-08-30 02:58 | flashyos | ship/1 | 0x2c067ba8473af31a… | ship/flashyos/5db478c6454f |
| 2026-08-30 03:44 | flashyos | ship/1 | 0x549099251cc67c1c… | ship/flashyos/c21012c58481 |
| 2026-08-30 03:51 | flashyos | ship/1 | 0x3acbf06b7e045899… | ship/flashyos/5e2fd2173f7f |
| 2026-08-30 03:51 | flashyos | ship/1 | 0xc56caf9f2f6b80fc… | ship/flashyos/422d73de00ac |
| 2026-08-30 04:00 | flashyos | ship/1 | 0x09fb8e5375f0c2c1… | ship/flashyos/403207e7f8b7 |
| 2026-08-30 04:05 | flashyos | ship/1 | 0xdec1a365974b444f… | ship/flashyos/47a5ed604dc1 |
| 2026-08-30 04:09 | flashyos | ship/1 | 0x0bba7e530a885455… | ship/flashyos/620764b59794 |
| 2026-08-30 05:06 | flashyos | ship/1 | 0x59a173d9f1b1989a… | ship/flashyos/94afb841db78 |
| 2026-08-30 05:06 | flashyos | ship/1 | 0xb7d69e0bbf1118f3… | ship/flashyos/12546cf759e0 |
| 2026-08-30 05:12 | flashyos | ship/1 | 0xb1aa7f20cfa30170… | ship/flashyos/44e08d399cc8 |
| 2026-08-30 05:13 | flashyos | ship/1 | 0x9105c5b11bb16d61… | ship/flashyos/b0d3bd64ee22 |
| 2026-08-30 06:44 | flashyos | ship/1 | 0xa964420e110ac9c9… | ship/flashyos/518ced9b2c45 |
| 2026-08-30 06:44 | flashyos | ship/1 | 0x5422ab32cbda10ec… | ship/flashyos/129620e5aade |
| 2026-08-30 12:57 | flashyos | ship/1 | 0x772ee0840fac191e… | ship/flashyos/e2afb7aa4fd6 |
| 2026-08-30 13:03 | flashyos | ship/1 | 0x2afc734a8295e0a2… | ship/flashyos/08b1d457a25d |
| 2026-08-30 14:07 | flashyos | ship/1 | 0xa189e3e6e65a0707… | ship/flashyos/4c0482a3ad42 |
| 2026-08-30 14:07 | flashyos | ship/1 | 0xcfd7a58a77010f63… | ship/flashyos/c68a82161e08 |
| 2026-08-30 14:14 | flashyos | ship/1 | 0x1d19986ef3bc2399… | ship/flashyos/ed5798fbd66e |
| 2026-08-30 15:48 | flashyos | ship/1 | 0x40546ea0d770383a… | ship/flashyos/417a1e955310 |
| 2026-08-30 15:53 | flashyos | ship/1 | 0xe07c95c6821ac210… | ship/flashyos/6dc3e870704c |
| 2026-08-30 16:02 | flashyos | ship/1 | 0x51f5cd27bd7dca1e… | ship/flashyos/a046e1c7baf7 |
| 2026-08-30 16:44 | flashyos | ship/1 | 0x9d67be592c3b6cdd… | ship/flashyos/808c98614948 |
| 2026-08-30 16:46 | flashyos | ship/1 | 0x3723c7d394158f03… | ship/flashyos/6bd78d82a5ad |
| 2026-08-30 16:56 | flashyos | ship/1 | 0xfcfdbccfda3f7b75… | ship/flashyos/42fd8b7a556f |
| 2026-08-30 17:02 | flashyos | ship/1 | 0x618a19f07e4f5086… | ship/flashyos/269d451aaba6 |
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.