Cheat Sheet — Caps & Limits
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.
Limits
Section titled “Limits”| Item | What the source establishes |
|---|---|
| CHOA chat payment | At most one CHOA token per successful call, and only with sufficient CHOA balance |
| CHEON payment | At most one CHEON token per qualifying Su call, with sufficient CHEON balance |
| QING cover allowance | Must be strictly greater than the cover for a paid expired Join |
| QING guest entry | One day when set; early Join does not extend it |
| CROWS bouncer check | At least 25 tokens at the QING decimals when CROWS is enabled |
| UserVote.Submissions | uint8 representation, not a proven 255-submission game limit |
| H2O/VITUS overflow | Mint-time recipient threshold at Meridians(13); WORLD branch uses its pre-transfer balance against Meridians(20) |
| ENCRYPT | Index-array limit in Crypt; no automatic deletion or confidentiality guarantee |
Interpretation
Section titled “Interpretation”A cap is not a promised payment or an external price. Solidity checked arithmetic can revert. WORLD’s _cauda is not populated and WAR’s _taan is not updated in the pinned source, so neither should be described as an operational rising leaderboard or payout queue without deployed evidence.
Sources
Section titled “Sources”CHOA, CHEON, QING, UserVote, WORLD, WAR, ENCRYPT.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
QING.CoverCharge()Read
Open this function to load its call form.
VITUS.balanceOf(address account)Read
A callable deployment has not been resolved for this reference.
VITUS.Withdraw(uint256 Amount)Simulate / call
A callable deployment has not been resolved for this reference.