Dysnomia — Alpha & Strategy Notes

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.

Reading these guides

These pages explain source mechanics, not promised returns. Amounts, caller permissions, registry state and deployed bytecode all matter. A compiled interface or matching source-file hash does not prove that the deployed contract implements the same code.

Mechanics worth checking

• Chat payments transfer CHOA to the YUE conditionally; MAI is a calculated value based on QING tokens at the LAU.
• Paid admission does not extend on an early Join.
• Yuan composition uses the currency explicitly supplied by the caller.
• WORLD and WAR have missing index/score writes in the pinned source; a working deployed version must be independently established.
• Word-game types do not establish current gameplay entry points or limits.
• ENCRYPT exposes transaction arguments and does not offer automatic erasure of chain history.

Verifying an outcome

An eth_call is a preview. A submitted transaction is not execution success: require an explicit successful receipt, canonical block membership and the expected events or resulting state. Distinguish protocol rules from stricter wallet or MCP policies. Check the selected deployed instance before acting on these guides.