Closed-loop economy
The currency only has value inside the system. It can't be moved to another platform, so the operator controls every place it enters and leaves.
An interactive model of a centralized, asset-backed, closed-loop currency: an administrator provisions accounts, mints points against deposited physical goods, watches balances move through play, then burns points on redemption. Watch where the peg holds and where it breaks.
01 · Technical architecture
The back office holds write access to the supply. The client app can only spend what it was given. Both read from the same balance store, and that shared store is the system's single point of truth and of trust.
Superuser control panel, elevated permissions
User-facing interface, restricted permissions
| Dimension | Technical architecture (software) | Operational workflow (human) |
|---|---|---|
| Issuance | A privileged write to a balance field | Operator checks a physical deposit before writing |
| Redemption | Balance set to zero and an event logged | Operator hands goods back from the reserve |
| Integrity | Append-only log; supply = mint − burn ± play | Physical count must match the ledger's liabilities |
| Failure mode | Bugs, unauthorized writes, credential leaks | Miscount, theft, insolvency, operator discretion |
02 · Operational workflow
Every name and number here is made up, and everything resets when you reload. Make deposits, run play sessions at different return rates, then try redemptions. Watch the collateral ratio: it shows whether the reserve can still cover every point in circulation.
Back office: create a subordinate account.
Cards go into custody and points are issued at the peg.
Client app: balance changes at random around an expected return.
Points convert back to cards at the peg and those points are destroyed.
03 · Audit trail
Every change in supply is a recorded event. Reconciliation checks that the running supply equals mint − burn + net play, and compares it with the physical reserve.
| # | Time | Event | Seat | Δ Points | Δ Cards | Supply after |
|---|
04 · Vocabulary for the paper
Use these terms to keep the software design separate from the human process that keeps it honest.
The currency only has value inside the system. It can't be moved to another platform, so the operator controls every place it enters and leaves.
Each point is a claim on a physical good held in reserve. The issuer acts like a small reserve bank, and the token is only worth as much as the trust in that reserve.
Points are created when goods are deposited and destroyed when they are redeemed. Burning on redemption stops the same claim from being cashed twice (double spending).
Reserve ÷ (points outstanding ÷ peg). Below 100%, the custodian can't honor every claim at once. Play with an expected return above 100% pushes the system there.
No payment processor sits in the middle. The operator settles offline, so the peg holds only as long as the operator counts correctly and acts honestly.
Users can't check the reserve themselves. The administrator is issuer, custodian and auditor all at once, a concentration of roles that real financial regulation deliberately keeps separate.
05 · Notes for your paper
A strong analysis covers the economics and also the regulatory status of the model.
Most US jurisdictions define gambling by three elements together:
When users pay something of value in (cards), play games of chance, and can redeem winnings for value (cards back), all three elements are present. Swapping cash for collectibles generally doesn't change that. This is why platforms like Juwa, Milky Way and Game Vault, run through independent "distributors", face enforcement and state attorney-general actions. Legitimate social casinos avoid this by making their coins non-redeemable, or by running a legally structured sweepstakes with a free way to enter.