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 5025 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 | 5025 |
|---|---|
| Head root | 0x30fa65c235043c54423da803bfcaf26b886bf296029ca9c8d72a48fb8373e9a9 |
| Most recent leaf | 2026-09-05T20:56:11.659Z |
| Stream regenerated | 2026-09-05T21:12:18.222Z |
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 | 1585 | +41.5% vs last week |
|---|---|---|
| This month | 3972 | +638.3% 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 | 2638 | checkpoint/1, settlement/1 |
| claimyourgold | 884 | checkpoint/1, receipt/1, ship/1 |
| flashyos | 619 | checkpoint/1, ship/1 |
| gdagroup | 202 | checkpoint/1, ship/1 |
| flashygroup | 159 | checkpoint/1, ship/1 |
| academy | 133 | certificate/1, checkpoint/1, ship/1 |
| flashyid | 112 | checkpoint/1, ship/1 |
| goldholdings | 104 | checkpoint/1, ship/1 |
| flashygold | 81 | checkpoint/1, ship/1 |
| mlgblockchain | 75 | checkpoint/1, ship/1 |
| intentmesh | 12 | 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-09-02 16:22 | flashygold | ship/1 | 0xd5deaa027e04caf5… | ship/flashy-gold/ebd1709a68… |
| 2026-09-02 17:34 | flashygold | ship/1 | 0x262cba2fcfbb3313… | ship/flashy-gold/fd528443fd… |
| 2026-09-02 17:46 | flashygold | ship/1 | 0x9b981881fed89481… | ship/flashy-gold/5e05826774… |
| 2026-09-03 02:42 | flashygold | ship/1 | 0x3aebfaa852ded720… | ship/flashy-gold/e0c6dc6e3f… |
| 2026-09-04 17:24 | flashygold | ship/1 | 0x07debcbab090aef6… | ship/flashy-gold/0e7680627b… |
| 2026-09-04 08:54 | flashygold | checkpoint/1 | 0x7fc7862a3a570514… | https://www.flashy.gold/.we… |
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.