A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗

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 12230 leaves from 21 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 size12230
Head root0x7d43d673300b9a0f0787b2fdb28997101ee7f9597a25f07d4f52e6cf448989aa
Most recent leaf2026-10-30T06:28:19.978Z
Stream regenerated2026-10-30T06:35:26.276Z

Engineering roadmap, by organisation

The same leaf stream, read as what each organisation is building rather than as one flat list. Every estate record format is a tense: planned is intent/1 (the backlog), in progress is initiative/1 and ritual/1 (joint work and recurring practice), and shipped is ship/1 and devlog/1 (what shipped and the changelog). Across the log that is 4529 shipped, 189 in progress and 30 planned, from 21 of 21 organisations. Every figure is a count of leaves already folded — none is typed here.

OrganisationPlannedIn progressShippedLatest
flashyos1514214272026-10-29
claimyourgold0010162026-10-29
gdagroup102922026-10-26
magician002732026-10-26
flashygroup002562026-10-26
academy002442026-10-26
goldholdings402172026-10-26
flashyid002042026-10-26
flashygold001372026-10-26
mlgblockchain001162026-10-26
fourventures001072026-10-26
flashytools00932026-10-30
intentmesh100512026-10-19
flashyos-ritual04402026-10-29
flashynetwork00412026-10-30
metaversegroup00262026-10-19
rites00202026-10-29
botzgroup0072026-10-19
gdagroup-ritual0202026-09-22
michaelgord0022026-10-16
rites-ritual0102026-09-28

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.

SourceEventStatus
academycertificate/1✓ folding
claimyourgoldreceipt/1✓ folding
flashyidverification/1◇ awaiting first event
flashynetworksettlement/1✓ folding
flashyoscountersignature/1, mail/1, initiative/1✓ folding
flashyos-countersign-claimscountersign/1◇ awaiting first event
gdagroupintent/1✓ folding
goldholdingsintent/1✓ folding
intentmeshintent/1✓ folding
magicianintroduction/1◇ awaiting first event
gdagroup-ritualritual/1✓ folding
flashyos-ritualritual/1✓ folding
rites-ritualritual/1✓ folding
chroniclechronicle/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 week268-54% vs last week
This month3090-20.9% 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.

SourceLeavesKinds
flashynetwork7133checkpoint/1, devlog/1, settlement/1
flashyos1629checkpoint/1, devlog/1, initiative/1, intent/1, ship/1
claimyourgold1193anchor/1, checkpoint/1, devlog/1, receipt/1, ship/1
gdagroup319checkpoint/1, devlog/1, intent/1, ship/1
academy276certificate/1, checkpoint/1, devlog/1, ship/1
flashygroup274checkpoint/1, devlog/1, ship/1
magician274checkpoint/1, ship/1
goldholdings239checkpoint/1, devlog/1, intent/1, ship/1
flashyid226checkpoint/1, devlog/1, ship/1
flashygold152checkpoint/1, devlog/1, ship/1
mlgblockchain130checkpoint/1, devlog/1, ship/1
fourventures107devlog/1, ship/1
flashytools93devlog/1, ship/1
intentmesh76checkpoint/1, devlog/1, intent/1, ship/1
flashyos-ritual44ritual/1
rites27checkpoint/1, devlog/1, ship/1
metaversegroup26devlog/1
botzgroup7devlog/1
gdagroup-ritual2ritual/1
michaelgord2devlog/1
rites-ritual1ritual/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.

4551–4575 of 12,230 · newest first
Time (UTC)SourceKindHashRef
2026-09-05 18:12ritesship/10x034fa55c17265966…ship/rites-network/0e6a8c3d…
2026-09-22 09:25ritescheckpoint/10xc1706cca37079596…https://www.rites.network/.…
2026-09-21 19:21mlgblockchainship/10x78419581f576a214…ship/mlgblockchain/1e17c306…
2026-09-22 09:22mlgblockchaincheckpoint/10x8bfa6d5e6092d9ee…https://www.mlgblockchain.c…
2026-09-19 11:33intentmeshship/10xe7cfeee5e2ed7a70…ship/intentmesh/0a43466632d5
2026-09-22 13:20intentmeshship/10x0cef908764e9ae77…ship/intentmesh/d36ee33a857a
2026-09-22 13:20intentmeshship/10xb9280f5799a5efc4…ship/intentmesh/10cb3fe8383b
2026-09-22 13:50intentmeshship/10xe6aa3f456462cdb5…ship/intentmesh/7b5f470981a3
2026-09-22 13:50intentmeshcheckpoint/10xef494147f8581129…https://www.intentmesh.org/…
2026-09-21 19:21goldholdingsship/10xd3be0966b5103909…ship/gold-holdings/62582e27…
2026-09-21 19:46goldholdingsship/10x47284972559a5870…ship/gold-holdings/0fdff935…
2026-09-22 12:12goldholdingsship/10x628f39f5ce5bf596…ship/gold-holdings/ad249541…
2026-09-22 13:23goldholdingsship/10x018fb29a4ec0c41f…ship/gold-holdings/63dcc296…
2026-09-22 13:46goldholdingsship/10x39180e15980bde56…ship/gold-holdings/5c3ec5dd…
2026-09-22 09:22goldholdingscheckpoint/10xf3bedf417bc60447…https://www.gord.holdings/.…
2026-09-22 13:30gdagroupship/10x8cea9282b0a84179…ship/gda-group/64119affb8c3
2026-09-22 15:08gdagroupship/10x474a467ab9a7988e…ship/gda-group/c6100d0db7f8
2026-07-22 16:34gdagroupdevlog/10xfa0a7688f913c701…https://github.com/FlashyLa…
2026-07-22 16:53gdagroupdevlog/10x28aa33e33b5584b1…https://github.com/FlashyLa…
2026-07-23 14:04gdagroupdevlog/10xee6d3d26225b4fa2…https://github.com/FlashyLa…
2026-08-18 03:17gdagroupdevlog/10x830f622096f49a9b…https://github.com/FlashyLa…
2026-08-18 03:18gdagroupdevlog/10xa98cf3dbcddf8d02…https://github.com/FlashyLa…
2026-08-21 14:00gdagroupdevlog/10x469243a5de70871c…https://github.com/FlashyLa…
2026-08-22 13:13gdagroupdevlog/10x261388ebaa189e2f…https://github.com/FlashyLa…
2026-08-28 23:15gdagroupdevlog/10xbcf72fb4b1197f73…https://github.com/FlashyLa…

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.