MAI — Venue Power (Step 2 of 6)
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”MAI.React(Soul, QingWaat) obtains a User record and QING, then returns QING.balanceOf(Alpha.On.Phi) / Alpha.Entropy. CHO.Enter sets Alpha.On.Phi to the LAU address. The numerator is therefore the LAU’s QING-token balance, not the wallet’s underlying-asset balance.
What you actually do with it
Section titled “What you actually do with it”Simulate React for the intended Soul and Waat. It is non-view: a transaction can update reaction state and call _mintToCap. Solidity integer division truncates, and zero entropy can revert. A reading is specific to the state and call path being simulated.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
MAI.React(uint64 Soul, uint256 QingWaat)Simulate / call
Open this function to load its call form.
CHOA.Chat(address Qing, string MSG)Simulate / call
Open this function to load its call form.
Rewards / costs
Section titled “Rewards / costs”MAI is the calculation used by XIA and by the reward amounts in CHOA/CHEON. CHOA transfers its own CHOA token to the YUE; CHEON transfers its own CHEON token. Their one-token ceilings do not cap the MAI value used elsewhere, and MAI.React itself does not pay those chat rewards.
Where it connects
Section titled “Where it connects”MAI source, XIA, CHOA and CHEON. Fomalhaute supplies XIA’s modulus; it is not an input to MAI’s division.