YI — The Token Foundry¶
One-line pitch: YI is the foundry that spawns new identity tokens, coordinates reactions, and tracks "Bao" (operation tickets) for each player. Plumbing — you don't call it directly.
What this is¶
YI is the orchestrator for player cryptographic state. It owns a SHIO, knows about SHAFactory and SHIOFactory, and maintains a mapping of per-address Bao (operation-ticket structs) that record the cryptographic state around each account's last significant action.
It's also the contract that wires new tokens into the ecosystem — when someone creates a QING, a LAU, or any new ERC-20 the system needs, YI orchestrates its creation.
If you've played a web3 game before¶
- Closest analogy: a token factory + registry hybrid — the Uniswap V2 Factory + a per-user storage buffer.
- Or: a character creation DAO — mints your on-chain cryptographic identity when you onboard.
- Or: an ERC-20 deployer with per-user state stuck onto it.
| Dysnomia term | What it maps to |
|---|---|
| YI | The token-foundry + per-player Bao registry |
| Bao | Your latest operation-receipt struct |
| Psi | The SHIO this YI references internally |
| Ring / Xi | Internal counters for ordering reactions |
What you actually do with it¶
- Nothing directly. YI is called by LAUFactory, ZHENG, and the wider bootstrap path.
- Indirectly: every time you act in the game, a Bao lands in YI's mapping.
Rewards / costs¶
- Cost: none to you directly.
- Reward: none — infrastructure only.
Requirements & gating¶
- None for players.
Where it connects¶
Owns a SHIO. Uses SHAFactory and SHIOFactory. Feeds into ZHENG, then ZHOU, then YAU → YANG → SIU — the whole spine of the crypto plumbing.
Quick FAQ¶
Q: What's a Bao? A: Think of it as a timestamped cryptographic receipt of your most recent meaningful action. It records the state of your keys at that moment.
Q: Why is YI called "CHATLOG Yi" in its token name? A: The CHATLOG prefix groups all the plumbing contracts that underpin chat — Yi, Zheng, Zhou, Yau, Yang, Siu. They're the chat infrastructure stack.
Want the Solidity? The contract reference lives at
technical/docs/core/04_YI.md.