Skip to content

Territory — CO2 Dynamics

TL;DR: CO2 is a global monotonic uint256 in WAR, increased by Chao on every successful new WAR high-score. It never decreases. The game doesn't currently gate anything on it — but it's the only system-wide ledger of cumulative intensity, and it's asymmetric.

Why this matters

CO2 accumulates silently. Every time someone Faas a position and beats the previous high, CO2 += Chao. Neither your H2O nor your VITUS depends on CO2 directly — but CO2 is the only global counter that the contracts track across all players. If future mechanics (or forks) introduce CO2-gated effects, being on the right side of the CO2 curve matters.

For now this is a "know that it exists" page rather than a "here's the bet" page. But it's the ledger-level asymmetry that makes farming H2O an externality.

The numbers

From WAR:

Faa(Caude, Position):
    Buzz = World.Tail(Caude, Position)
    if Buzz == 0: return 0
    (Phoebe, Iota, Chao, Charge) = World.Meta().Ring().Eta()
    Waat = modExp(Phoebe, Charge, Meridians[89])
    if Waat > _taan[Caude][Position]:
        Water.Mint(Chi, Iota)    // H2O to your YUE
        CO2 += Chao              // global CO2 grows
    return Waat
State Where Behaviour
CO2 WAR contract, uint256 public Monotonic. No decrement path.
_taan[Caude][Position] WAR private mapping Monotonic per (Caude, Position).
Chao From Ring.Eta() Per-call output; depends on Yue.React(Phobos) / Omicron.

CO2 is public; you can read it at any time.

The play

  1. Read CO2 before you farm. CO2 is public on WAR. Knowing the slope — how fast it's rising — tells you how "hot" the global game is.
  2. (inferred) Low-Chao Faa calls still pay H2O. If your goal is H2O with minimal CO2 contribution, optimize for Iota without dragging Chao up. Iota comes from Push's pre-squared Iota; Chao comes from Yue.React(Phobos)/Omicron. These are largely independent.
  3. (inferred) Expect future CO2 gates. If a future patch gates something on CO2 > threshold, early farmers benefit from low-CO2 era. Stockpile H2O now, hedge if you suspect CO2 gates are coming.
  4. No revert on CO2. Neither Faa nor Code checks CO2 before running. It's pure bookkeeping today.
  5. _taan is per-(Caude, Position). The monotonic high-score lives under the (Caude, Position) key. If you Faa at Position=1 for Caude=A, then Position=2 for the same Caude, the high-score at Position=2 is fresh for you to beat. Territory-wide farming cycles through positions to avoid competing with your own prior highs.

Worked example

Say CO2 is currently 1e20 on WAR. You plan to run 10 Faa operations targeting positions where the high-score is 0 (i.e. easy to beat).

Each successful Faa adds some Chao to CO2. If typical Chao at your current RING state is 1e15, 10 Faas add 1e16. CO2 climbs to 1.01e20. No gate trips (there are none), but the global ledger rose by 10%.

If a friend runs the same 10 Faas in parallel, global CO2 rises 20%.

If 100 players in parallel, 1000%.

CO2 is the fingerprint of collective activity. Today, it's just a number. Tomorrow, it might be the denominator of some payout formula — or it might not. Decide how much you care.

Gotchas

  • You can't read _taan[Caude][Position] publicly. It's private. You only learn of your success via balance changes (H2O minted or not) and CO2 movement.
  • CO2 Contribution ≈ Chao. Chao depends on Phobos's state, not the Caude/Position you're hitting. So the CO2 cost of a Faa is more-or-less fixed by the global Phobos state at the moment — you can't tune your Faa to "be greener".
  • (inferred) Distribute does not affect CO2. Distribute is a WORLD call; it doesn't touch WAR. CO2 only moves on WAR.Faa new-highs.
  • Massively parallel WAR farming by many players drives CO2 up fast. If you see a huge jump on CO2, expect the game's economics to be under strain — some venues may get throttled or forbidden by governance.

Where it cross-connects