Contracts & deployments

Rooms deployment#

Independent human deployments use rules 14 or 18 on Monad Testnet 10143, as identified by their manifests. Both retain Classic and all 24 Chaos events with bounded physics work and reusable storage inside each independently delegated arena. Rules 18 increase paddle speed to 300 units per second and preserve the predecessor's ordered rating history and original seeds. Shared lobby, rating, profile, private-data and financial contracts remain on Monad. New games are enabled only by the release admission gate; deployed addresses alone do not establish availability.

Read GET /api/independent/config for the exact approved arenas, epoch health and admission state. The 5 October v3 migration preserves 16 public rating rows and six repeat counters, reuses the same family, profiles and private-data contracts, and keeps the 25 previous published results accessible. Existing grants retain their scope; historical balances are not transferred. The wallet selector exposes earlier human betting credit for owner-authorized withdrawal.

The human lobby is 0x527ccb705048820694a4ac209f83528db68fff3f, using Interlude hub 0x98922c6e5e4bea62761c71d2401c7ec2c26ec43e. The agent pool is 0x1f7d8a7b470a724df48d1b72723d7782d8e6014a on that same hub, with independently reserved capacity. See the human v3 manifest for every current and previous human address. Old room URLs open their original history and never silently create a new game.

The independent source and evidence documents the new generation. The historical rooms manifest and financial manifest keep their original meanings. The tables below list preserved V1 to V4 contracts.

Preserved V4 arcade#

V4 remains available separately. V4 deploys new immutable GameV3, ArcadeSessions and Vault instances with MarketV4 and TournamentsV4. The implementation name GameV3 is not the same as the application's deployment generation.

The following tables are generated from the repository's public active manifest and its legacy chain. They expose only version, chain, start block and contract addresses. Follow each address to the testnet explorer.

Bindings and upgrades#

Game, market, vault and tournament links are sealed before use. These contracts have no upgradeable proxy. A new deployment may inherit ratings, but existing balances and financial rights remain attached to the old contracts.

The treasury is immutable where specified by the contract constructor. Replacing it requires a compatible new deployment, not an undocumented administrative edit to an existing match.

Match references#

A rooms reference includes base chain, application address, delegation epoch and full match identifier. A bare number or previous rooms URL must never silently resolve to another deployment.

v4:12 means match 12 in V4. It is different from v3:12. Envio and private replay notes use deployment-qualified references. Active numeric API routes are scoped by /api/config; legacy reads require the chosen deployment parameter.

Code must preserve the deployment when storing a receipt, replay, position or payout origin. Never assume a number alone identifies a match across upgrades.

Financial compatibility#

V4 transfers due winnings and refunds to the fixed wallet recipient. V1–V3 claims credit their original vaults and need a signed withdrawal. A UI rollback must retain support for every deployment already accepted by the relayer journal.

The source manifest includes deployment evidence. The permission model and operations guide explain the boundaries around these contracts.