Territory — CO2 Dynamics
Evidence scope: The behavior below is from the pinned Solidity source. A source-file hash does not establish deployed bytecode equivalence. Check the selected deployment and caller before sending a transaction.
WAR.Faa returns zero when WORLD.Tail returns zero. Otherwise it obtains RING outputs, computes Waat, and only inside Waat > _taan[cause][position] requests H2O minting and adds Chao to CO2. A losing or early-return path does not add CO2.
The play
Section titled “The play”Inspect the actual deployment and simulate the complete call. The pinned source never writes _taan; it does not establish an increasing high-score barrier. Its WORLD source never populates the _cauda index used by Tail. Those omissions invalidate advice to farm fresh positions against an evolving leaderboard in this snapshot.
CO2 is a checked uint256 addition in the reward branch. An emitted transaction hash does not prove that branch ran; use the receipt, token logs and state reads. No fixed H2O-to-CO2 price or fee is established by the source.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
WAR.CO2()Read
A callable deployment has not been resolved for this reference.
WAR.Faa(address Caude, uint256 Position)Simulate / call
A callable deployment has not been resolved for this reference.