Playground: disposable chain, test WCHI, wiped without warning
For builders

Ship a game nobody can shut down.

Everything on this shelf was built with open-source tools you can use today, and you can publish a provably fair game straight into this arcade now, behind a moderation gate.

Available now

Build a XAYA game today

The full stack is open source: a battle-tested C++ framework that handles the blockchain for you, and the same tools the official games are built with. The step-by-step path is the builder docs, and the quickstart takes you from nothing to a game running. We build games AI-first, and the skills we use are the ones we publish: two agent skills covering game channels and the Arcade, and fully on-chain persistent worlds: download them as a zip and unzip into .claude/skills/. If you are driving an AI agent, the opening prompt is the literal text to paste first.

Publishing

Publish into the Arcade (curated phase)

Shipping a provably fair game into the Arcade means four uploaded files (your rules blob and UI bundle, each with its sha256 sidecar) plus the registry facts you type into the form, and not a single server. Play a full match on the public playground first, then submit the same bytes here. New to the concepts? Start with the builder docs

rules.wasm + .sha256

Your game's judge

The deterministic rules of your game, compiled to WebAssembly: it decides what moves are legal and who won. With its detached sha256 sidecar.

bundle.tar.gz + .sha256

Your game's face

The browser frontend players see: a static web bundle built on the Arcade SDK (React/Next today), mounted inside the Arcade shell. With its detached sha256 sidecar.

registry facts

Your game's card

Name, art, slug, seat range and the repo link: typed into the submission, not a file. This is what the Arcade lists and serves you by.

The platform runs everything else

Referee, wallets, wagering, matchmaking, chat and hosting are the Arcade's job: you never run a server. Open publishing with ratings comes with Arcade v2.