YANG — The State Tracker¶
One-line pitch: YANG is the system's game-save. It stores the three "Pole" values that identity generation and reactions depend on. Plumbing — you don't call it directly.
What this is¶
YANG maintains a Pole[3] — three uint64 values that represent the current cryptographic state of the system. These Pole values flow into SIU when new player identities are minted, and they evolve over time through reactions.
The internal Augment() function steps YANG forward in response to upstream activity.
If you've played a web3 game before¶
- Closest analogy: a three-slot hash chain that gets extended by every reaction.
- Or: a game-save file — single source of truth for "where are we?"
- Or: a Merkle root that updates as state changes.
| Dysnomia term | What it maps to |
|---|---|
| YANG | System state tracker |
| Pole[3] | The three canonical state values |
| Augment() | Internal state-advance function |
| Mu | YANG's link to parent YAU |
What you actually do with it¶
- Nothing directly. YANG is stepped by upstream contracts.
Rewards / costs¶
- Cost: none directly.
- Reward: none — infrastructure.
Requirements & gating¶
- None for players.
Where it connects¶
Depends on YAU. Feeds into SIU and identity generation for new LAUs.
Quick FAQ¶
Q: Why three Pole values? A: The identity-generation math mixes all three into the resulting Soul/Aura. Three slots give the system enough entropy to avoid collisions without ballooning storage.
Q: Can Pole ever be zero? A: Only at the initial genesis state. Once the system has seen any activity, Pole values drift.
Want the Solidity? The contract reference lives at
technical/docs/core/08_YANG.md.