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 | 569 | -46.5% vs last week |
|---|---|---|
| This month | 5030 | +186.4% 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-26 20:13 | flashyid | ship/1 | 0x4185b57a3047a845… | ship/flashyid/8e298cebfd89 |
| 2026-08-26 20:32 | flashyid | ship/1 | 0x60e626f84d995131… | ship/flashyid/aabebd824648 |
| 2026-08-27 17:36 | flashyid | ship/1 | 0xa124000ff931ca45… | ship/flashyid/15003c579be9 |
| 2026-08-27 20:02 | flashyid | ship/1 | 0x63597c25eed80e94… | ship/flashyid/3973dc19a849 |
| 2026-08-28 01:54 | flashyid | ship/1 | 0xa4dc3ac7ace8aeb0… | ship/flashyid/aedd0816b816 |
| 2026-08-28 02:21 | flashyid | ship/1 | 0x79675778dd60855c… | ship/flashyid/baa3178d11f7 |
| 2026-08-28 02:37 | flashyid | ship/1 | 0x0476b8656f9763fa… | ship/flashyid/e2adc9edb102 |
| 2026-08-28 17:43 | flashyid | ship/1 | 0x4a534669a54c386f… | ship/flashyid/ba29ae5c7e7f |
| 2026-08-28 18:04 | flashyid | ship/1 | 0x895f03cad8982416… | ship/flashyid/0459ebebee6b |
| 2026-08-28 19:51 | flashyid | ship/1 | 0x905b4060616473de… | ship/flashyid/1ab81739fa32 |
| 2026-08-30 00:14 | flashyid | ship/1 | 0x91c7678ce9ba34b2… | ship/flashyid/efb6a9190ac1 |
| 2026-08-30 00:19 | flashyid | ship/1 | 0x904c542ff4d78dbe… | ship/flashyid/5547621a4e1e |
| 2026-08-30 01:34 | flashyid | ship/1 | 0xa45a8566f3dbdac5… | ship/flashyid/6866190e4318 |
| 2026-08-30 02:26 | flashyid | ship/1 | 0x12551846b5e6fc61… | ship/flashyid/c01dd206f442 |
| 2026-08-30 02:42 | flashyid | ship/1 | 0xdba4f67dd21f8a8b… | ship/flashyid/a0b177244c87 |
| 2026-08-30 03:07 | flashyid | ship/1 | 0x1ba06971f951cf32… | ship/flashyid/299477b4422d |
| 2026-08-30 03:51 | flashyid | ship/1 | 0x7fd30556513262ea… | ship/flashyid/f9582d477355 |
| 2026-08-30 03:51 | flashyid | ship/1 | 0x03a3315f38369489… | ship/flashyid/358ca9d62776 |
| 2026-08-30 05:46 | flashyid | ship/1 | 0x021575db9ad86ce0… | ship/flashyid/2f0242bfea02 |
| 2026-08-30 05:48 | flashyid | ship/1 | 0x8a8451bb5b2faa34… | ship/flashyid/50c7e08261b7 |
| 2026-08-30 13:21 | flashyid | ship/1 | 0x43f28d6822d12a3c… | ship/flashyid/22eeb79e0fd1 |
| 2026-08-30 15:46 | flashyid | ship/1 | 0x8cd423ab1f94d433… | ship/flashyid/466299ed5d64 |
| 2026-08-30 16:18 | flashyid | ship/1 | 0xf3b8a5c7da1504a7… | ship/flashyid/6c9d2df305be |
| 2026-08-30 17:18 | flashyid | ship/1 | 0xf5de84954f38fb83… | ship/flashyid/06b4f7412515 |
| 2026-08-30 17:23 | flashyid | ship/1 | 0x680e4cc79a575193… | ship/flashyid/b0f03a270ba2 |
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.