Power — Entropy Discipline
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.
CHO.GetUser and GetUserBySoul react and update User entropy. The power functions can invoke them multiple times in one transaction. Entropy is not a monotonic experience counter, and a sequence of separately simulated reads is not necessarily the state seen by one nested transaction.
The play
Section titled “The play”Read the exact LAU and venue token balances and simulate the complete intended call with its origin. Integer division truncates; zero divisors can revert. Modular exponentiation is not monotonic in its inputs, so a larger balance does not guarantee a larger final Charge.
YUE.React adds Omega to Hypobar and Omicron to Epibar. These are power accumulators; the source has no counter-clearing branch in Hong, Hung or Withdraw. Do not infer a reward rate, decay schedule, or deposit/withdrawal total from them.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
CHO.Entropy()Read
Open this function to load its call form.
QING.Entropy()Read
Open this function to load its call form.
XIE.Power(uint256 QingWaat)Simulate / call
Open this function to load its call form.
CHEON.Su(address Qing)Simulate / call
Open this function to load its call form.