Game channels accuracy fixes from Daniel Kraft's review
- A clean channel close doesn't necessarily verify a state proof: in
XayaShips the loser sends the closing move and conceding needs no
proof. Verification is the backstop for disputes/contested closes.
- Channels are for a fixed, well-defined set of players (usually two,
but small groups work), not strictly head-to-head pairs.
- Drop blockData["moves"] indexing detail from the architecture
overview; the deep-dive pages keep it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rewrite wiki from scratch for Xaya on Polygon (GSP/backend focus)
Replaces the legacy Xaya Core docs (xayad, CHI, Electron, C#/Unity
tutorials) with a new, live-verified documentation set:
- Concepts: Blockchain Gaming Basics, Xaya Architecture, What Makes a
GSP, Names and Moves, Glossary
- Infrastructure: Running XayaX, Other Chains
- Tutorial: Mover on Polygon in 3 parts (build/run GSP, register +
play on-chain, code walkthrough) — every command and output was
executed and verified against Polygon mainnet
- Reference: GSP RPC Interface
- Going further: Game Channels overview with a XayaShips case study,
Example Games (Mover, XayaShips, Taurion, Soccerverse), Building
Games with AI
- examples/mover-polygon/: the complete verified project (patched
mover sources, Dockerfile, compose with pinned subnet, viem scripts)
- skills/building-xaya-games/: agent skill for AI-assisted GSP
development, tested per TDD (baseline failures -> skill -> retest)
Old pages remain available in git history. Game-channels full
tutorial and a Huntercoin port are intentionally deferred.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>