Payouts and refunds: follow the on-chain state

Miteos Team · Reviewed 2026-10-24 · revision 4

Current product format — 24 October 2026: fictional marketplaces are free Practice, with no new funded entries. Historical testnet matches retain their original settlement and refund rights. Live Arena is a separate, owner-controlled, no-money website-repair prototype using Qwen and Meta models hosted by Cloudflare Workers AI. It is not qualified for paid competition. Mainnet and card payments remain disabled.

Live Arena prototype coaching, tool actions and generated code are published only after explicit consent. Do not include personal data or secrets. Private Practice strategies are not imported or exposed. The prototype has separate task/evaluator versions; marketplace qualifications do not apply. Availability, actual completed demonstrations and limitations are shown in Task Arena.

Crypto Arena is a separate, unranked, no-money BTC/USDT forecast experience, not trading or investment management. Signed-in players can save private model/competitor configurations, prepare comparisons against a clearly labeled reference AI, and create or accept player invitations. Saving and inviting do not trigger inference. Live execution remains disabled pending established data-use permission and current included-resource activation. A ready round requires an explicit start request; it may queue before its forecast timer begins. Invitations expire after 24 hours and can be cancelled before execution.

Crypto coaching stays private and is sent only to the selected Cloudflare-hosted model. Immutable strategy versions and private configurations are stored with your account; ask support about access or deletion requests. Opponent coaching is never available through invitations, evidence, or images. After both forecasts lock, their targets reveal together. Player handles, competitor names, model identities, outcomes and result evidence are public and may appear in personalized share cards. A reference-AI comparison is not human competition and earns no rating. No exchange account, trading key, order or withdrawal access is requested. Recorded source observations and absolute forecast errors—not a model judge—determine a result. Model/data failures can void a round. The operator's source capture remains a trust boundary. Marketplace explanations below concern free Practice and historical obligations, not new paid admission.

An application result, a signed receipt, registered settlement and a completed claim are different steps. Check the match's network, contract, transaction receipts and exact deadlines. Support can investigate but cannot move your funds for you.

Decisive result or draw After a valid result is registered in time, the winner can claim the prize and the treasury can claim only the earned fee. A registered draw or void gives each depositor their entry back with no fee. Anyone may submit a valid signed result, but cannot redirect its recipient. Claims are pull-based; a repeated claim has nothing further to pay.

Unfilled challenge When only the first player has funded, that player can cancel before the second joins. Anyone can expire an unfilled match at or after its funding deadline; only the original depositor can receive the refund. A competing join/cancel transaction is resolved by actual on-chain ordering, not the website's clock.

No result registered After both deposits, the contract fixes a result-registration deadline, normally24 hours after the second deposit. A valid result can be registered at the deadline second. If none is registered, expiry/refund becomes valid strictly AFTER that deadline. The original match's displayed timestamp is authoritative; a local test's simulated clock is not public-chain evidence.

Signed is not settled An off-chain signed result alone does not defeat a refund deadline. Once a result is registered in time, a later timeout cannot override it. If the backend stops, contract timeout rights still exist, subject to the chain and token operating. Pausing new entries must not trap existing claims.

Missing or failed transactions Verify the correct network, native token, recipient and transaction status. A rejected wallet request or failed transaction is not a successful deposit. Do not repeatedly approve or send tokens to an address manually. A plain USDC transfer to escrow is not a valid match entry. Preserve the hash and open a Refunds request if reconciliation is unclear.

Open a claims/refund request · Fees