Venues — Chat Mining
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.
CHOA.Chat first calls QING.Chat, then reacts the YUE and calculates MAI. The payment is CHOA’s own token transferred to the YUE, conditional on CHOA having enough balance. Direct QING.Chat only emits the venue message.
MAI.React uses QING.balanceOf(activeLAU) / User.Entropy, with integer truncation. It does not use the wallet’s underlying-asset balance. CHOA clamps this amount to one token at CHOA’s decimals; the result can be zero, below the cap, or unpaid if inventory is insufficient.
The play
Section titled “The play”Inspect the active LAU’s QING balance, YUE-token holdings at the origin, admission, and the exact CHOA simulation. Reactions can change the entropy used by later calls. Count verified CHOA transfers, gas and cover costs before drawing any economic conclusion. More messages do not imply a fixed or profitable return.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
VenueAsset.allowance(address owner, address spender)Read
Open this function to load its call form.
VenueAsset.approve(address spender, uint256 value)Simulate / call
Open this function to load its call form.
QING.Asset()Read
Open this function to load its call form.
QING.Admitted(address UserToken)Read
Open this function to load its call form.
QING.Join(address UserToken)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.
Sources
Section titled “Sources”CHOA.Chat, MAI.React, QING.Chat, and paid admission.