Played through Discord
A new dungeon every day, the same for everyone. The Discord bot is dev-hosted and runs intermittently; local play needs no server at all: nobody watches your moves or referees you.
verified operating system + economy
Public proof record 04 / build
Working examples from the repository
Markets, votes, games, code forges, and confined agents. Their security rules live in the system, not in each app.
All examples below are tested code. The system is still hardening for heavy load and true adversaries.
01
Principal exhibit
A daily text dungeon played with friends. Nobody can cheat, not because a server watches, but because invalid moves cannot enter the world.
A new dungeon every day, the same for everyone. The Discord bot is dev-hosted and runs intermittently; local play needs no server at all: nobody watches your moves or referees you.
Land an impossible hit, take treasure without its key, or spend gold you do not have: the move does not count.
The day’s dungeon comes from a public coin flip nobody controls. Everyone gets the same dungeon and can verify it was not rigged.
A reward is an owned, transferable item. It cannot be duplicated; its rarity can be proven.
Characters keep levels and scars from day to day. In hardcore, dead is dead. Death itself advances the character a little.
Finish a run and anyone can reach the same result. The run stays private until you choose to anchor the win.
Still open: the wide public launch, and proving a win without revealing the moves. Open the code →
02
Catalogue A
Two strangers trade through escrow. If the seller disappears, the buyer reclaims. Value cannot leak or appear.
Secret bids, simultaneous reveal, fair award. A bid cannot be changed after it is committed.
An AI trades a fixed budget. Evidence travels with each price, over-budget trades are refused, and a false track record fails the audit. Paper trading only.
An Ethereum contract verifies dregg’s compressed proof on a live test network. Verifiers for Solana and Cosmos are generated from the same specification.
03
Catalogue B
Double votes bounce, stuffed counts are refused, a dropped ballot is detected, and anyone can re-check the tally.
An AI arbiter refuses the proven manipulation case, answers to a supermajority, and gives a forged ruling no weight.
Shared settings change only when a vote passes: all at once, or not at all.
Prove what a wallet holds on Solana, Ethereum, or Cosmos and vote with that weight. The tokens do not move into a vault.
04
Catalogue C
A strategy game where seeing the enemy side requires a key only they hold. You cannot choose to peek or leak it.
An AI storyteller cannot be talked into handing out an item that was not earned. Every scene is certified.
Votes choose each plot branch. The whole playthrough can be re-checked afterward, beat by beat.
Edit together or offline. A collision becomes a side-by-side choice, never a silent overwrite.
05
Catalogue D
Review, merge, and ship code where commits are receipts and a merge is a proven combination of both edits. There is no git underneath.
Comments and approvals are signed by the named reviewer. A merge waits for its required checks and keys.
A real Matrix homeserver runs inside a lockbox with exactly one folder and one port, metered like a rented room.
06
Catalogue E
Give an agent a tool that expires Friday, works ten times, and touches one folder. The system enforces the limit.
Rent an agent with one granted door to the world, or none. Every action is metered and receipted; the run can be checked offline.
Publish, rent, review, and fork. A fork keeps its family history; a child cannot hold more power than its parent.