Bao — Your Action Receipt¶
One-line pitch: Bao is the struct bundled up and stamped every time you perform a significant on-chain action — it's the cryptographic receipt of that moment.
What this is¶
Every meaningful operation you perform emits a Bao — a struct containing:
- Phi — your address (who did it).
- Mu — a reference to your Rod SHA.
- Xi — an index/generation number.
- Pi — reserved auxiliary field.
- Shio — reference to your SHIO pair.
- Ring — result of SHIO magnetization.
- Omicron / Omega — two reaction outputs.
Bao lives in mappings across YI, ZHENG, and other plumbing contracts — keyed by your address or by installation slot. If you ever see a "per-user operation buffer" in the technical docs, it's Bao.
If you've played a web3 game before¶
- Closest analogy: a transaction receipt — but with the cryptographic state bundled alongside.
- Or: a bearer-token bundle — what you need to prove you did the thing.
- Or: a session struct in a login framework — carries identity + state.
| Dysnomia term | What it maps to |
|---|---|
| Bao | Action-receipt struct |
| Phi | Associated address |
| Mu / Shio | Pointers to your cryptographic tokens |
| Omicron / Omega | Reaction outputs (consumed by XIE) |
| Ring | Magnetization result (consumed by RING) |
What you actually do with it¶
- Nothing. Bao is populated by the system during your actions.
- Observe that contracts reading your Bao can reconstruct your full identity + state.
Rewards / costs¶
- Cost: gas (indirectly — Bao writes cost storage).
- Reward: none direct — Bao is a data artifact, not a payout.
Requirements & gating¶
- None — Bao is generated automatically from the actions you take.
Where it connects¶
Populated in YI. Consumed by ZHENG, XIE, RING, and anywhere a contract needs "what was this user's crypto state at their last action?"
Quick FAQ¶
Q: How often is a new Bao created for me? A: Whenever an action needs a fresh reaction-receipt — practically every time you chat, battle, or claim territory.
Q: Does Bao cost me gas? A: Yes — but it's bundled into the gas cost of whatever action you already paid for. There's no separate "Bao fee."
Q: Can two users share a Bao? A: No. Bao is per-address (per Phi).
Want the Solidity? The contract reference lives at
technical/docs/include/BAO.md.