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 6811 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 | 6811 |
|---|---|
| Head root | 0x9026f7eb76108b06d14caa8d362249c14427bb735d7e0ab10b29381c50a07480 |
| Most recent leaf | 2026-09-15T20:36:04.231Z |
| Stream regenerated | 2026-09-15T21:29:47.629Z |
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 | ◇ awaiting first event |
| 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 | 883 | -24.8% vs last week |
|---|---|---|
| This month | 5182 | +515.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 | 3942 | checkpoint/1, settlement/1 |
| claimyourgold | 921 | checkpoint/1, receipt/1, ship/1 |
| flashyos | 872 | checkpoint/1, ship/1 |
| gdagroup | 233 | checkpoint/1, intent/1, ship/1 |
| academy | 187 | certificate/1, checkpoint/1, ship/1 |
| flashygroup | 170 | checkpoint/1, ship/1 |
| goldholdings | 151 | checkpoint/1, intent/1, ship/1 |
| flashyid | 132 | checkpoint/1, ship/1 |
| flashygold | 94 | checkpoint/1, ship/1 |
| mlgblockchain | 79 | checkpoint/1, ship/1 |
| intentmesh | 24 | checkpoint/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-22 02:57 | academy | certificate/1 | 0xc367e0ddd7e88158… | https://flashy.academy/acad… |
| 2026-08-20 03:12 | academy | certificate/1 | 0x9b0ae161884235ab… | https://flashy.academy/acad… |
| 2026-08-20 02:27 | academy | certificate/1 | 0x593b721952609773… | https://flashy.academy/acad… |
| 2026-08-20 01:46 | academy | certificate/1 | 0x9752d5d7a021c5c9… | https://flashy.academy/acad… |
| 2026-08-20 01:44 | academy | certificate/1 | 0x3174bad0b9298d4f… | https://flashy.academy/acad… |
| 2026-08-20 01:24 | academy | certificate/1 | 0x319a1e8b0c67d2db… | https://flashy.academy/acad… |
| 2026-09-04 17:24 | academy | ship/1 | 0x06982ff8c63a3570… | ship/flashy-academy/ba9f9b2… |
| 2026-09-05 15:32 | academy | ship/1 | 0x56e7190c712e617a… | ship/flashy-academy/19175dc… |
| 2026-09-05 17:04 | academy | ship/1 | 0x8d118759456fef11… | ship/flashy-academy/20023d3… |
| 2026-09-05 17:05 | academy | checkpoint/1 | 0x9d0815bc6e7a76ac… | https://flashy.academy/.wel… |
| 2026-09-06 08:43 | flashynetwork | checkpoint/1 | 0x46ca7e7c40a69c42… | https://flashynetwork.com/.… |
| 2026-09-04 16:47 | rites | ship/1 | 0xa96adb4ab30a858a… | ship/rites-network/55fec7f2… |
| 2026-09-05 16:37 | rites | checkpoint/1 | 0xd20d753b881496ef… | https://www.rites.network/.… |
| 2026-08-30 19:20 | intentmesh | ship/1 | 0x83ea6f3336ce6644… | ship/intentmesh/f948f0d2739f |
| 2026-09-01 15:25 | intentmesh | ship/1 | 0x7ef08344d1bb1db8… | ship/intentmesh/0e181d155891 |
| 2026-09-01 17:08 | intentmesh | ship/1 | 0x226bb093020fe295… | ship/intentmesh/f3354141d86f |
| 2026-09-01 17:12 | intentmesh | ship/1 | 0xd37168e1a3e6a107… | ship/intentmesh/2a124f768f84 |
| 2026-09-01 17:46 | intentmesh | ship/1 | 0x7e08fc5c9ecaf4e4… | ship/intentmesh/76a4771b8bc4 |
| 2026-09-01 17:57 | intentmesh | ship/1 | 0x237079d4e8907b2a… | ship/intentmesh/09ee86a3d891 |
| 2026-09-01 17:58 | intentmesh | ship/1 | 0x778ab27d37e73385… | ship/intentmesh/9c1df2413d92 |
| 2026-09-01 18:39 | intentmesh | ship/1 | 0x10addb6b43e29ce5… | ship/intentmesh/bbe53fca5663 |
| 2026-09-01 18:53 | intentmesh | ship/1 | 0xa19fa7185c4fe028… | ship/intentmesh/6095ced67ef9 |
| 2026-09-05 16:50 | intentmesh | checkpoint/1 | 0xade31b4c4355c079… | https://www.intentmesh.org/… |
| 2026-09-05 17:03 | flashynetwork | checkpoint/1 | 0x674a26b9b46f0e84… | https://flashynetwork.com/.… |
| 2026-09-04 20:22 | flashyos | ship/1 | 0xd826356a85e266f4… | ship/flashyos/d86209da0af4 |
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.