Blotto Cup
Reviewing this for a hackathon or an audit? Start at REVIEWERS.md.
A paid-entry tournament on Solana, built on the Colonel Blotto game: the result is decided by the players' decisions, with no chance in the scoring.
Up to 64 players enter a pool. Each one places points across seven sealed battles of five
stats — Strength, Speed, Heart, Wit, Durability — on a board, against one three-minute clock. When
the pool closes, every allocation is revealed and each player's seven battles are scored against the
matching battle of every other player (441 comparisons per player, 14,112 in a full pool). No
pairings, no bracket, no chance in the mechanism: everyone faces the identical field. The player
ranked first is paid the pool's whole fixed prize pool (players tied for first share it equally).
Each entrant also receives a non-transferable character pass whose class is drawn with verifiable
on-chain randomness. The class is cosmetic — nothing in scoring, payout or ranking reads it.
Status: devnet only. The program has never been deployed to mainnet and no real money has
entered it. Mainnet is gated on independent legal review and the checklist in
docs/ROADMAP.md. Under decision R5, an internal program review stands in for a
formal audit before launch, and an independent audit follows after ten settled mainnet pools.
Program ID (devnet): 5aawXayPYgEqrnHi6pGiYRpuHNuwauj8GqftRjkeXH17.
Two modes
| Easy | Hard |
|---|
| What you place | 100 points in each of the seven battles | 700 points anywhere across all 35 cells |
| How a battle is won | the larger number wins a stat; three stats of five win the battle; otherwise a draw | identical |
| Clock | one three-minute clock for the whole board, starting at the first point placed | identical |
Each mode runs its own pools with its own entry and prize pool. The rules live in
backend/scoring/src/allocation.ts and
backend/scoring/src/engine.ts; the one scoring module is run
unchanged by the settlement service and by the browser, so any player can recompute the result.
How the money moves
- The prize is funded before anyone can enter. Opening a pool moves that tier's fixed pot from
the platform treasury into the pool's own vault. The pot is a constant per tier, not a share of
entries, so it is the same whether 40 players enter or 64.
- Entries go to the treasury. An entry never touches the prize vault.
- The pool either plays or refunds. Entries close 12 hours after opening. With 40 or more seats
filled (or all 64) the pool seals and plays. Below 40, every entry is refunded in full from the
treasury and the untouched pot returns to the treasury. The floor is written onto each pool when
it opens, so a later change cannot move it under players who already entered.
- Once a pool plays, its prize is only ever paid to players. The prize leaves the vault through
pay_prizes, release_escrow or pay_next_place. A share held back by an upheld review is not
returned to the operator — it passes to the next eligible place. There is no withdraw
instruction on a vault and no admin escape hatch;
scripts/check-standing-rules.sh asserts the exact exit set on
every change.
Seven entry tiers exist, from 0.1 SOL to 7.5 SOL, on the same ladder for both modes; the prices, pots and which tiers are open live in
programs/blotto_cup/src/constants.rs and on-chain in
Config. docs/compliance/PRODUCT-FACTS.md lists every value
with its source.
Documentation
The full map is docs/README.md.
Quick start
The app on fixture data — no credentials, database or Docker needed:
git config core.hooksPath .githooks # enables the keypair pre-commit hook
npm run setup # installs every package (required — see Getting started)
cd app && npm run dev # http://localhost:3000
The backend stack, the program build and every CI check are in
Getting started.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
