ZHENG — The Installation Registry

One-line pitch: ZHENG permanently registers (“installs”) tokens and operations into the system. Once installed, the slot is reserved forever. Plumbing — you don’t call it directly.

What this is

ZHENG maintains a Sigma mapping: each numbered slot gets filled with a Bao (operation receipt) when a token or operation is installed. Slots can’t collide — trying to install over an existing slot reverts with SigmaAlreadyInstalled.

Installation also triggers market-rate setup, so when a new token appears in the system, ZHENG makes sure it has an exchange rate from day one.

If you’ve played a web3 game before

• Closest analogy: a permanent NFT slot registry — once slot #N is claimed, it’s claimed forever.
• Or: ENS — human-readable permanent registrations.
• Or: an append-only ledger of “this token is now part of the system.”

Dysnomia term	What it maps to
ZHENG	Installation registry
Install	Bind a token to a permanent slot + set its initial market rate
Sigma mapping	slot-number → Bao receipt
Eta	ZHENG’s link to its parent YI

What you actually do with it

• Nothing directly. ZHENG is called during deployment/onboarding.

Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.

ZHENG0x24E62C39e34d7fE2B7dF1162e1344eB6eb3b3e15

ZHENG.Eta()Read

Open this function to load its call form.

Rewards / costs

• Cost: none directly.
• Reward: none — infrastructure.

Requirements & gating

• None for players.

Where it connects

Depends on YI. Feeds into ZHOU. Every token the system cares about passes through ZHENG at install time.

Quick FAQ

Q: Can a slot be re-installed? A: No — SigmaAlreadyInstalled reverts. Installations are permanent.

Q: What happens if install fails? A: The tx reverts. The slot remains free for a later, valid install.

---

Want the Solidity? The contract reference lives at technical/core/05_ZHENG.