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 | 2926 | -51.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 |
|---|---|---|
| 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-10-05 12:22 | intentmesh | ship/1 | 0x01a34634ecac09f4… | ship/intentmesh/0c583dc2fbff |
| 2026-10-05 13:10 | intentmesh | ship/1 | 0xf0f57284468a448c… | ship/intentmesh/6541021d15e4 |
| 2026-10-06 12:05 | intentmesh | ship/1 | 0xa1528724ed0640cc… | ship/intentmesh/9d166774fe54 |
| 2026-10-05 13:10 | intentmesh | devlog/1 | 0x167dd691fe4c40cf… | https://github.com/FlashyLa… |
| 2026-10-07 11:18 | intentmesh | checkpoint/1 | 0xba79f8ddf12bfd24… | https://www.intentmesh.org/… |
| 2026-09-22 15:10 | intentmesh | ship/1 | 0x1b607a390b603cf8… | ship/intentmesh/a091fd9be31e |
| 2026-09-23 10:05 | intentmesh | ship/1 | 0xc804fb6e97a02be2… | ship/intentmesh/e9b11ea0c7dd |
| 2026-10-01 11:41 | intentmesh | ship/1 | 0x933610623457db5c… | ship/intentmesh/0516d5a95f5f |
| 2026-10-02 11:10 | intentmesh | ship/1 | 0xea4e2a40a3e715ee… | ship/intentmesh/48c9093bd89d |
| 2026-10-03 10:28 | intentmesh | ship/1 | 0x81c7d1483934b38e… | ship/intentmesh/1c383cb32afc |
| 2026-10-04 11:10 | intentmesh | ship/1 | 0x222d8b489e9c6e7b… | ship/intentmesh/506898d40275 |
| 2026-10-05 11:47 | intentmesh | checkpoint/1 | 0x676002495f187f3a… | https://www.intentmesh.org/… |
| 2026-09-05 16:56 | intentmesh | devlog/1 | 0x67bbff9bc818364f… | https://github.com/FlashyLa… |
| 2026-09-05 18:12 | intentmesh | devlog/1 | 0x7557360bdb0ff18f… | https://github.com/FlashyLa… |
| 2026-09-15 14:36 | intentmesh | devlog/1 | 0xda66e0df2eebfe7a… | https://github.com/FlashyLa… |
| 2026-09-19 11:33 | intentmesh | ship/1 | 0xe7cfeee5e2ed7a70… | ship/intentmesh/0a43466632d5 |
| 2026-09-22 13:20 | intentmesh | ship/1 | 0x0cef908764e9ae77… | ship/intentmesh/d36ee33a857a |
| 2026-09-22 13:20 | intentmesh | ship/1 | 0xb9280f5799a5efc4… | ship/intentmesh/10cb3fe8383b |
| 2026-09-22 13:50 | intentmesh | ship/1 | 0xe6aa3f456462cdb5… | ship/intentmesh/7b5f470981a3 |
| 2026-09-22 13:50 | intentmesh | checkpoint/1 | 0xef494147f8581129… | https://www.intentmesh.org/… |
| 2026-09-19 00:00 | intentmesh | intent/1 | 0xc2c0ec3089bbf096… | imx/c2c0ec3089bb |
| 2026-09-19 00:00 | intentmesh | intent/1 | 0xc6ecbd3ca35de7ec… | imx/c6ecbd3ca35d |
| 2026-09-19 00:00 | intentmesh | intent/1 | 0x936afbb4ab995652… | imx/936afbb4ab99 |
| 2026-09-19 00:00 | intentmesh | intent/1 | 0xd1eb685f33792e32… | imx/d1eb685f3379 |
| 2026-09-19 00:00 | intentmesh | intent/1 | 0x9c45342fa33424f6… | imx/9c45342fa334 |
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.