WAR — The Battle System
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.
What this is
Section titled “What this is”WAR.Faa reads WORLD.Tail(cause, position) and returns zero immediately when that value is zero. Otherwise it calls RING.Eta, computes Waat with modular exponentiation, and compares Waat with the private _taan[cause][position] value.
What you actually do with it
Section titled “What you actually do with it”Simulate Faa(cause, position) for a specific deployment. If its reward branch runs, it requests H2O minting to the YUE and adds Chao to CO2. Outside that branch it does not add CO2. Use actual token transfers and state changes to identify a payout.
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.
Source limitations
Section titled “Source limitations”The pinned WAR source never assigns _taan after reading it. It therefore does not implement the rising per-position leaderboard previously described here. Its pinned WORLD dependency also never populates the _cauda index read by Tail, which prevents this source’s ordinary Tail path from producing a reward opportunity on a fresh deployment.
These are source observations, not proof that every deployed WAR has identical bytecode or storage. Do not rely on new-high farming, guaranteed H2O, or a CO2 penalty for losing without verifying the actual implementation.
Where it connects
Section titled “Where it connects”WAR source, WORLD, RING and H2O.