Case studies
- Flashy Group
Books anyone can audit, rules anyone can fork
Building the settlement layer beneath the AAO Stack: append-only, hash-chained ledger rules published as open source, with every cross-organization settlement sealed to a sha256 anyone can recompute — and an npm package that does exactly that.
Bridges & settlement · Agent coordination runtime - ClaimYour.Gold
One identity, three surfaces, no fork
Building the account system beneath a consumer programme that had to work identically on the web, inside a messenger, and from other services — without three separate account tables drifting apart.
Identity & accounts - ClaimYour.Gold
The mechanics that make a programme habitual
Streaks, quests, crews, duels and referral, built as more than a hundred distinct services rather than one “gamification” module — because at real scale, each mechanic has its own abuse pattern.
Engagement & social systems - ClaimYour.Gold
A programme inside the messenger, not beside it
Shipping a full mini-app and bot surface inside Telegram, sharing one identity with the web product rather than forking the account — for an audience that will not install a second app.
Telegram & messaging apps - Flashy Gold
A rewards ledger that reconciles, by construction
A points-and-rewards ledger built so that a repeated request cannot double-credit a balance — with the idempotency key derived from the event that caused it, never from a timestamp.
Loyalty, points & rewards · Wallet — service, mobile & extension - Flashy Finance
Redemption without a liquidity promise the catalogue could not keep
Building the redemption side of a rewards programme — catalogue, fulfilment, partner settlement — deliberately before building swap routing, because a redemption promise a reserve cannot honour is the failure that ends these programmes.
Swaps & redemption gateway - Flashy Academy
A learning platform where the certificate means something
Assessment and certification infrastructure built so a completion record can be verified by an employer without a phone call — a hundred-plus services deep on the content and delivery side alone.
Learning & certification platform - Flashy Wallet
Finding the edges of a wallet SDK before an agent does
Integrating Tether’s WDK toolkit behind Flashy Wallet’s engine, auditing every module it ships, and open-sourcing the two primitives it does not: a per-agent spending-policy layer and a reference staking design.
Wallet — service, mobile & extension · Agent coordination runtime - FlashyOS
Reconciling a branch that drifted 179 commits from main
The wallet authorization plane — governed spending limits for AI agents, built on Tether WDK — lived on its own branch long enough that main moved 179 commits without it. Merging it back meant re-verifying against everything that had shipped in the meantime, not just resolving a diff.
Agent coordination runtime · Wallet — service, mobile & extension - Flashy Network
Counting an intention once, however many ways it is observed
A transparency log needed to ingest a future-tense “intentions” format as leaves, but three properties already self-published the same underlying fact under a different source name. Folding the new format in naively would have counted each of their items twice.
Agent coordination runtime · Bridges & settlement - Flashy Finance
A rail under inherited code, not a rewrite over it
Three acquired projects — a username platform, a staking product and a bridge — arrived as years-old front-end and contract archives. Rather than rewrite them, each got a small new module that lets a holder use the feature against a rail the platform already trusts, with the original archives kept, byte-scanned, and left alone.
Identity & accounts · Wallet — service, mobile & extension · Bridges & settlement
Why this is separate from the catalogue
A platform page is a pitch for what MLG’s engineering can build for you. A case study is evidence that it already works, at real scale, inside the group — which is a different claim and deserves its own page, its own affiliate name, and its own disclosure rather than a footnote on the product it evidences.