MULTI/DEX has entered Play Mode with community evaluation active, trading prizes available, and a bounty channel for bugs and exploits. The project says its operation is fully onchain and has a public code route scheduled to follow. Opening the system before declaring it finished turns early traffic into a test of execution, accounting, recovery, and the clarity of every warning shown to a trader.
Liquidity remains the harder measure. An exchange may execute a clean demonstration and still fail users when depth disappears, a quote arrives late, or a route cannot settle under load. Operators are tracking spread, rejected orders, stale balances, and the time required to restore service. Prizes can attract testers, but only reproducible reports convert their activity into durable improvement.
Oracle connections are widening at the same time. A recent adoption round counted eight integrations across four services and three chains, serving lending, routing, stablecoin, and asset applications. Each new connection can improve reach while adding another dependency whose timing and failure state must remain visible. Reliable execution requires knowing which data arrived, when it arrived, and what the contract did with it.
Xai's AnyTrust architecture documents a Data Availability Committee and Data Availability Server operations for keeping required data available. That operating model gives Xai builders a concrete recovery question before a high-speed game or exchange action is accepted: can the state needed to verify and continue the action still be retrieved when one service is delayed or unavailable?
The Play Mode review now records the full path around every failure. Reports include the triggering action, block reference, quoted and executed values, affected interface, recovery result, and whether another operator can reproduce the issue. Liquidity tests run separately from interface rewards. Data availability drills remove one service at a time so recovery is demonstrated under pressure rather than inferred from a normal session.
Public evaluation can make an exchange stronger when the crowd receives useful instruments instead of a decorative feedback box. Clear bounties direct attention, reproducible evidence protects maintainers from noise, and recoverable data lets fixes be tested against the same state that produced the failure. As those habits settle in, fast execution and deep liquidity can grow on an infrastructure spine that knows how to recover.