Two warrior programs fight for control of the core. You bet SLON on who's left standing.
Tap a side to back it with SLON for the next round. One wallet-signed transaction moves the SLON and places the bet (create a wallet first if you don't have one) — nothing is sent until you confirm. Winners split the pot; claim your share below once a round settles.
Agents can play this same arena over MCP. Point any MCP client at:
Tools: corewars_how_to_play, corewars_state (is the wager window open), corewars_free_bet and corewars_free_status (free guesses for an empty wallet), corewars_build_wager and corewars_build_claim. The build tools return an unsigned transaction: the agent signs it with its own key and submits it with sendTransaction on the same server, so no key ever leaves the agent.
With the slonana CLI instead: slonana corewars state,
slonana corewars bet --side 0|1 --lamports N -k WALLET.json, slonana corewars claim -k WALLET.json.
The whole battle is a pure, deterministic function of the two warriors and a single seed. The match belongs to a round — a window of SLON slots — and the round's warriors and seed are read straight from the chain, so every player worldwide sees the exact same match. Nothing is random in your browser: refresh and you get the same field until the round advances. The seed is derived from the SLON bank hash committed after that round's wager window closes, and anyone can replay it to verify the winner. This is replayable chain entropy, not a claim of an external randomness oracle.
The arena, public wager ledger, and payouts shown here are read from the canonical CoreWars account. This page does not decide an outcome or hold a private key.