Skip to content

Power — Soeng Chain Optimization

TL;DR: QI → MAI → XIE → ZI → PANG feeds multiple tokens (SHIO, QING, Fomalhaute, Fornax, Tethys) into six nested modExp ops. Holding all five at moderate levels beats holding one at huge levels, because each token only affects one stage.

Why this matters

The Soeng chain is six mostly-independent stages. Each stage reads a specific balance and divides by an Entropy. A naive player maxes one token and expects "more = better"; the contracts don't reward that. They reward having an input at every stage.

Understanding which token plugs into which stage lets you build a much more efficient stat profile for the same total capital.

The numbers

From the Power Formulas cheat sheet, condensed to the "which token does what" view:

Stage Reads Acts as Source
QI SHIO.balanceOf(x) / Entropy Raw energy QI
MAI QING.balanceOf(x) / User.Entropy Per-venue power; also chat reward (capped 1) MAI
XIE Fomalhaute.balanceOf (modulus), Fornax.balanceOf (Omicron / Omega) Charge + reaction outputs XIE
ZI Yuan(QING) (modulus), Tethys.balanceOf (Omega / Eta) Spin; overwrites XIE's Omicron/Omega ZI
PANG Yuan(QING) (modulus), QING.Entropy() (exponent) Push; feeds RING/META/WAR PANG

Key observation: the modulus at each stage is a different quantity. Fomalhaute at XIE, Yuan at ZI and PANG, Meridians[89] at WAR. Each defines a codomain, not a numerator — holding Fomalhaute does not make you "more XIE".

The play

  1. Have some of every stage-token. SHIO (QI), the target QING's asset (MAI), Fornax (XIE), Tethys (ZI). You can't participate in a stage if your balance is zero — you get a zero out of that stage's balanceOf / Entropy.
  2. Treat Fomalhaute as infrastructure, not stat-stick. It's only a modulus. Pump Fomalhaute when you want a wider XIE output range, not when you want a bigger Charge.
  3. Yuan is a modulus in ZI and PANG. Increasing Yuan (via YUE stacking, see Power: Yuan Composition) changes ZI/PANG outputs nonlinearly; it doesn't directly "raise" them.
  4. The 1-token chat MAI cap doesn't limit your MAI stage. MAI as a stat (QING.balanceOf / Entropy) is uncapped — it's only the reward mint at CHOA.Chat that's clamped. Don't conflate the two. Holding way more of a QING's asset still matters for XIE/ZI even though it won't earn more per chat message.
  5. Entropy divides at QI, MAI, XIE-Omicron/Omega, ZI-Omega/Eta. Four stages divide by User.Entropy (and two by QING.Entropy()). Keeping your User.Entropy low matters four times over. See Power: Entropy Discipline.
  6. (inferred) Diminishing returns beyond "enough of each". modExp is sensitive to exponent size, not base size, in an irregular way. Going from 0 → 1 of a stage token is enormous; going from 100 → 200 is tiny. The sweet spot is "nonzero everywhere".

Worked example

You have a budget of X atomic units of token-mass to distribute. Compare two builds:

Build A — lopsided: 100% of mass into SHIO.

  • QI: maxed.
  • MAI: zero (no QING asset).
  • XIE: Charge = modExp(QI_QING, 0, Fomalhaute) = 1. Your MAI exponent of 0 collapses the whole stage.
  • ZI, PANG: feed from 1. Irrelevant.
  • Result: you have giant QI and nothing else.

Build B — balanced: 30% SHIO, 20% target QING asset, 20% Fornax, 20% Tethys, 10% Fomalhaute.

  • QI: moderate.
  • MAI: moderate.
  • XIE: Charge = modExp(moderate, moderate, moderate-modulus) — nonzero, interesting output.
  • ZI: reads Tethys for Omega/Eta. Nonzero.
  • PANG: computes nonzero Iota, Omicron.
  • Result: full chain participates; downstream (RING → META.Beat → Dione/Yeo, WAR.Faa → Iota → H2O) all have real values.

Build B strictly dominates Build A for any purpose that reads past the MAI stage (territory, WAR, META).

Gotchas

  • MAI in Soeng ≠ MAI as chat reward. Same name, two roles. Chat is capped at 1; the Soeng input isn't.
  • Modulus vs. base confusion. If someone says "stack Fomalhaute", ask them what they're optimizing. If the answer is "XIE charge", they're wrong — Fomalhaute is the modulus.
  • ZI overwrites XIE's Omicron and Omega. If your strategy leaned on XIE's Omicron being big, ZI discards that halfway through. What matters downstream is ZI's Omicron/Omega, not XIE's.
  • (inferred) Zero any one stage and downstream collapses. The chain multiplies and exponentiates; one zero propagates.
  • QING.Entropy() changes. It's not a constant. A QING that's seeing heavy traffic has a moving QING.Entropy(), which shows up in PANG as an exponent — your PANG output there is volatile.

Where it cross-connects