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 7357 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 | 7357 |
|---|---|
| Head root | 0xc7634c7a09b345a2e0a107179889c19480c12109c40368b3056fabfba2890efb |
| Most recent leaf | 2026-09-21T12:57:45.274Z |
| Stream regenerated | 2026-09-21T12:57:45.569Z |
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 | 700 | -33.5% vs last week |
|---|---|---|
| This month | 5032 | +243% 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 | 4468 | 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-09-01 21:15 | flashyos | ship/1 | 0x1cfe96a957de0469… | ship/flashyos/1d6f72564949 |
| 2026-09-02 01:57 | flashyos | ship/1 | 0xd572ea8a24a3f91e… | ship/flashyos/4a76b65a3bf8 |
| 2026-09-02 02:31 | flashyos | ship/1 | 0xa10e8a1124a72fb0… | ship/flashyos/30b7f6b4e0a9 |
| 2026-09-02 02:40 | flashyos | ship/1 | 0x87b41d33e55f2ea3… | ship/flashyos/ac2fb6d404a0 |
| 2026-09-02 03:06 | flashyos | ship/1 | 0xe6acc8c09215a7a1… | ship/flashyos/5c67c39efc73 |
| 2026-09-02 03:07 | flashyos | ship/1 | 0xd19d99d4fccf5383… | ship/flashyos/c2c04a6bdb07 |
| 2026-09-02 03:21 | flashyos | ship/1 | 0x096fbc980d785837… | ship/flashyos/1dc1b45d3c7d |
| 2026-09-02 03:27 | flashyos | ship/1 | 0x65ca1e47a71bc86d… | ship/flashyos/6de3c7ca30a0 |
| 2026-09-02 04:33 | flashyos | ship/1 | 0x9895e4551a9903b6… | ship/flashyos/15b0633fe12a |
| 2026-09-02 11:40 | flashyos | ship/1 | 0x0fe46fe2c657a602… | ship/flashyos/fa4957f33a57 |
| 2026-09-02 11:19 | flashyos | ship/1 | 0x581b7712fa15a50e… | ship/flashyos/ee5e1c8b32a4 |
| 2026-09-02 15:20 | flashyos | ship/1 | 0x732f9824450af6ca… | ship/flashyos/26bafd7bab1d |
| 2026-09-02 12:04 | flashyos | ship/1 | 0x0140f006f032685d… | ship/flashyos/9c3d2f498062 |
| 2026-09-02 16:05 | flashyos | ship/1 | 0xc64bb112a2c4973b… | ship/flashyos/c5a0a5f10fa9 |
| 2026-09-02 12:16 | flashyos | ship/1 | 0x288c9434c8fd1c8f… | ship/flashyos/dc58b6a4b3a7 |
| 2026-09-02 12:21 | flashyos | ship/1 | 0x7403f66ee0e52242… | ship/flashyos/d522ed74abb1 |
| 2026-09-02 16:54 | flashyos | ship/1 | 0xa8a8903297ff5328… | ship/flashyos/25a986e191cd |
| 2026-09-02 13:21 | flashyos | ship/1 | 0x4843dabbcf9d8544… | ship/flashyos/63ee09f9b3a3 |
| 2026-09-02 13:56 | flashyos | ship/1 | 0x4e05ae6f07153117… | ship/flashyos/42df04b7980f |
| 2026-09-02 14:08 | flashyos | ship/1 | 0x5d8254138021e34f… | ship/flashyos/9609714f3185 |
| 2026-09-02 14:17 | flashyos | ship/1 | 0x686a176c5dd65483… | ship/flashyos/034ac2bc718f |
| 2026-09-02 14:18 | flashyos | ship/1 | 0x5ffefa8b22637031… | ship/flashyos/1e0488083b91 |
| 2026-09-02 15:13 | flashyos | ship/1 | 0x3a01af172bc2f39d… | ship/flashyos/cc604cd3b4c3 |
| 2026-09-02 16:09 | flashyos | ship/1 | 0x0cbb7740120bb33c… | ship/flashyos/3e4ccfce522d |
| 2026-09-02 16:20 | flashyos | ship/1 | 0x052fc0d584b5ddb3… | ship/flashyos/fd23f437d405 |
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.