A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗
FLASHY GOLD IS OPERATED WITHIN THE FLASHY GROUP ALLIANCE · GOVERNED ON FLASHYOS
FOR BRANDSDEVELOPERSCIVILIZATIONPRESSTRUST & CONTROLSENGAGEMACHINE SURFACESFLASHYOS LIVE NETWORK ↗
FLAHYGOLD
⌕SIGN IN ↗SUPPORTENCLAIM YOUR GOLD ↗
/CHANGELOG/4 RELEASES · LATEST 2026-09-07

What shipped

Dated, attributable, and quotable without asking us what it meant. The record starts where it can be checked rather than where the story would prefer — entries below this line are the ones with something behind them.

THE RECORD

Flashy Gold settles on the estate-wide rail — Flashy Finance is live

Flashy Gold now settles on Flashy Rails, the estate-wide settlement layer shared across the group. flashy.gold reads a person's balance and the auditable statement behind it from that shared rail rather than from a single property's database, so one identity holds one Flashy Gold balance everywhere it is recognised. The read path is live now; earning stays on the alliance surfaces and the redemption marketplace remains waitlist-stage.

flashy.gold/settlement/ →

flashy.gold answers the mesh handshake

flashy.gold now serves /.well-known/flashyos.json — the fixed path any agent can fetch to learn who this organisation is and what it does, before holding a token or knowing a single endpoint. The document is tested against the same mesh identity the site reports with, so the two cannot disagree.

flashy.gold/.well-known/flashyos.json →

Dependency alerts, secret scanning and code analysis, on every push

Dependabot, gitleaks secret scanning and CodeQL analysis now run against this repository on every push. A rewards platform that cannot say whether a credential leaked has no basis for asking anyone to trust its ledger.

The ledger rules go public, and flashy.gold pins the published version

Flashy Gold balances are kept in a double-entry ledger whose rules are now published as @flashylabs/ledger under Apache-2.0: append-only, integer minor units, hash-chained tamper evidence, idempotent writes. Anyone may fork the rules, run their own books against them, and check ours. flashy.gold pins the published version rather than a local copy.

www.npmjs.com/package/@flashylabs/ledger →
WHY IT IS A RECORD AND NOT A BLOG

Every entry above is written to be a directory record as well as a paragraph: a named thing, a date it shipped, and the organisation accountable for it. That is the format the rest of the estate merges, so a release stated here once does not have to be restated anywhere else to be found — and nothing on this page links to another Flashy property just for the sake of the link.

The format is open. It is specified in @flashyos/directory, published under Apache-2.0, and you can emit it from your own repository without asking anyone.

Announcement headlines live on the newsroom page. This is the shipped record.