Build a game for the Xaya Arcade.
A game here is two artifacts: a deterministic rules.wasm judge and a UI on the shared SDK, and no server of your own. These pages take you from the template to a running, registered game.
This arcade takes no uploads during the curated phase: you test a game on the public playground and open a submission on GitHub, and the registration and hosting steps are operator actions. See What you need.
New to XAYA itself: what a GSP is, how game channels settle a match off-chain, and the paper that invented them? That background lives on Learn
Quickstart
The shortest honest path from nothing to a game on the Arcade: starting with whether your idea fits at all.
Driving an AI agent
The literal opening prompt to paste at the start of the conversation, one per architecture.
Overview
What the Xaya Arcade is, how the pieces fit together, and the rules of the road for a game.
What you need
The repositories, access, and local tooling required to build an Arcade game.
Getting started
Fork the template, run it locally against the committed SDK, and tour the project.
Make it yours
Turn the template into your own game: the full rename surface, one field at a time.
The rules blob
The wasm judge contract: the arcade_* ABI, the pinned limits, and a reproducible build.
The SDK
Build your UI on @xayaarcade/sdk: the adapter, configureApp, debug logging, and vendoring.
Testing
The determinism ladder, the off-chain channel scenarios, and the blob checks.
Hosting & registration
The operator runbook: hosted bundles, the games-host, on-chain registration, and wagering.
Submitting your game
Submit a GitHub issue with the tested commit, WASM hash, game details and test results.
Operating the platform
The platform's components and their configuration.