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 10409 leaves from 15 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 | 10409 |
|---|---|
| Head root | 0xc3622336df72608fb0cafe2f708102a82cb227a0ea383b0bbbf81d32c4e59f82 |
| Most recent leaf | 2026-10-15T09:17:00.056Z |
| Stream regenerated | 2026-10-15T09:17:00.384Z |
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, mail/1, initiative/1 | ✓ folding |
| gdagroup | intent/1 | ✓ folding |
| goldholdings | intent/1 | ✓ folding |
| intentmesh | intent/1 | ✓ folding |
| magician | introduction/1 | ◇ awaiting first event |
| gdagroup-ritual | ritual/1 | ✓ folding |
| flashyos-ritual | ritual/1 | ✓ folding |
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 | 793 | +0.6% vs last week |
|---|---|---|
| This month | 2932 | -51% 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 | 6139 | checkpoint/1, devlog/1, settlement/1 |
| flashyos | 1401 | checkpoint/1, devlog/1, initiative/1, ship/1 |
| claimyourgold | 1107 | anchor/1, checkpoint/1, devlog/1, receipt/1, ship/1 |
| gdagroup | 301 | checkpoint/1, devlog/1, intent/1, ship/1 |
| academy | 252 | certificate/1, checkpoint/1, devlog/1, ship/1 |
| flashygroup | 252 | checkpoint/1, devlog/1, ship/1 |
| magician | 216 | checkpoint/1, ship/1 |
| goldholdings | 207 | checkpoint/1, devlog/1, intent/1, ship/1 |
| flashyid | 199 | checkpoint/1, devlog/1, ship/1 |
| flashygold | 136 | checkpoint/1, devlog/1, ship/1 |
| mlgblockchain | 101 | checkpoint/1, ship/1 |
| intentmesh | 52 | checkpoint/1, devlog/1, intent/1, ship/1 |
| flashyos-ritual | 29 | ritual/1 |
| rites | 15 | checkpoint/1, ship/1 |
| gdagroup-ritual | 2 | ritual/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-23 14:33 | rites | ship/1 | 0x54156d61851024c3… | ship/rites-network/d1ca56aa… |
| 2026-10-09 11:27 | rites | checkpoint/1 | 0xa8cc1184247e04a7… | https://www.rites.network/.… |
| 2026-09-22 13:45 | rites | ship/1 | 0x11131fd1cfde5dcf… | ship/rites-network/5c9916c2… |
| 2026-09-23 14:05 | rites | ship/1 | 0x8d2947bb46218ea5… | ship/rites-network/a5628724… |
| 2026-09-23 14:18 | rites | ship/1 | 0x5acbda334faa5952… | ship/rites-network/9eb06293… |
| 2026-09-23 14:29 | rites | ship/1 | 0xafb7f1e065a1b989… | ship/rites-network/979491bf… |
| 2026-09-23 14:30 | rites | checkpoint/1 | 0x245c928f5792f7e0… | https://www.rites.network/.… |
| 2026-09-05 18:12 | rites | ship/1 | 0x034fa55c17265966… | ship/rites-network/0e6a8c3d… |
| 2026-09-22 09:25 | rites | checkpoint/1 | 0xc1706cca37079596… | https://www.rites.network/.… |
| 2026-09-02 15:56 | rites | ship/1 | 0x7ea4603e9e06eb35… | ship/rites-network/e636134b… |
| 2026-09-02 16:35 | rites | ship/1 | 0xfe5748dc3d78cee4… | ship/rites-network/9008f789… |
| 2026-09-05 16:56 | rites | ship/1 | 0xe93fb06410d08326… | ship/rites-network/27e7ba89… |
| 2026-09-05 16:56 | rites | checkpoint/1 | 0xb453766b22fc64ad… | https://www.rites.network/.… |
| 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/.… |
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.