The Dysnomia guide
The public-facing guide to Dysnomia — the fully on-chain social operating system that shares its cryptographic backbone with the Atropa treasury system. Written for a reader meeting the system for the first time; statements carry the knowledge base’s provenance tags (
[src]recovered source,[chain]onchain query,[irc]dev-channel record,[ext]external/unverified).
What lives where
- This guide (
/dysnomia/guide/…) — the distilled, definitive explanation: what the system is, how each layer works, how it connects to the treasury side. Start with the overview. - The hub (/dysnomia) — generated state: the seven deployment waves, every system contract with its entity page, and the census aggregates (accounts, channels, venues, activity).
- Entity pages (
/dysnomia/contracts/{address}) — generated data views per contract and structural token: identity, deployment, supply/cap, liveness, links into the guide and the dev reference. - The dev reference (
/dysnomia/dev/…) — the per-contract engineering documentation, shipped from the project’s research layer largely as-is: identity tables, mechanical function tables, integration notes. denser than the guide, and the place to check a selector or a gate condition.
Reading order
- overview — what Dysnomia is, in one page
- accounts & chat — users, Souls, channels, the chat substrate
- venues — the hub, the map, QING venues, bouncers and bans
- the economy — YUE account tokens, bounties, escrow, the internal exchange
- the ladder — the derived “physics” chain and the tile oracle
- the treasury bridge — how Dysnomia and the treasury system interlock
- glossary — the vocabulary, decoded
The random-number backbone shared by both systems has its own reference page: /knowledge/reference/randomness.
The engineering counterpart to this guide — one doc per contract with mechanical function tables — ships under /dysnomia/dev. Generated state (waves, censuses, entity pages) lives on the hub.