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 2375 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 | 2375 |
|---|---|
| Head root | 0xce03e5f55078f80c8ba8456b3089f534bc59fdc1ab988e599864a41bc6e5f9d0 |
| Most recent leaf | 2026-09-05T17:03:02.503Z |
| Stream regenerated | 2026-09-05T17:03:53.774Z |
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 | 962 | +284.8% vs last week |
|---|---|---|
| This month | 1606 | +448.1% 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 |
|---|---|---|
| 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 | 122 | 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 | 10 | checkpoint/1, ship/1 |
| flashynetwork | 5 | checkpoint/1 |
| rites | 2 | 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-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/… |
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.