Table rules

The game

The rules are the standard Yahtzee rules: 2–6 players per table, 13 rounds. Every seat plays every round at its own pace — there is no shared turn order, so you are never waiting on someone else's dice. Each round you get up to three rolls: after each roll you click the dice you want to keep (nothing marked means reroll everything) and either roll again or score — you may score with the category of your choice after any roll, not only the third, which is also the one lever you have over how many transactions your turn costs. Upper-section bonus: +35 when your six upper categories total 63+. Extra fives of a kind: +100 each while your Five of a Kind box holds 50, with the standard joker placement rules: a further five of a kind must go in its matching upper box if that is open; if it is filled, any open lower box scores its full value (Full House 25, Small Straight 30, Large Straight 40); if only upper boxes remain, one of those at face value. Under those rules a five of a kind cannot be burned for 0, and the +100 bonus is paid only while the box holds 50, not 0.

Stakes and payout

• Four table tiers: 100 / 1,000 / 10,000 / 100,000 NIGHT per seat. Your stake goes into the table pot when you take a seat.
• The winner takes 99% of the pot. 1% (rounded down; the rounding remainder stays with the winner) goes to the table operator's rake address, which is fixed at table creation and publicly visible on-chain.
• Ties never split the pot. Highest total wins; if tied, a finished card beats an unfinished one; if still tied, the lower seat number — the earlier to join — wins. In a full game every finisher completes in the same round, so between two finished cards the seat number decides. Deterministic, and enforced by the contract: the table page says which rule decided a tied game.

Playing the bot. A game against the practice bot costs a fee: the stake its button in the lobby names. The fee pays for the DUST the house spends on your game — the bot's moves and the operator's — and it is never returned: not when you win, not when you lose, not if you leave before the start, and not if the game never starts or stalls. The refunds and the pot described above are an ordinary table's. At a practice table the contract gives the bot back exactly its own stake however the game ends, sends your fee to the house, and pays no winner. A win there is still recorded as a win; it pays nothing.

Fees, and two warnings your wallet will thank you for

Every move you make is a transaction paid in DUST. DUST regenerates from NIGHT you hold and have designated — NIGHT locked in a pot generates nothing.

Timeouts — a table can never trap your stake

• Every round has a deadline. Miss it while you still owe the round and anyone can eliminate your seat — permissionlessly, for no reward to them. The penalty is a fraction of your stake, r/13 for round r (round 1 costs a thirteenth; round 13 costs everything): the more of the game you have played, the more your leaving costs the players who stayed. The forfeited share stays in the pot for the winner; the rest is yours, redeemable once the table finishes.
• If the table itself stalls (the operator stops resolving rolls), anyone can trigger an abort after the table deadline: every seated player gets their full stake back (minus any penalty already applied to an eliminated seat), and the rake gets nothing.
• If every seat is eliminated before the game ends, the table becomes abandoned — a pending, not payable, state. One more permissionless call (abortTable) then waives every penalty, so everyone still redeems their full stake; only the 1% rake is still paid, since the operator did its work regardless of how the players fared.

Fairness — verify any game yourself

Dice come from a commit–reveal scheme: the operator commits to a secret seed before the table opens; your per-round entropy is forced from a key you commit to when you join; every roll mixes in the digest of the round as it stood when the round opened. Neither you, other players, nor the operator can steer a single die — the operator's only power is to stop resolving (which ends in the refund above, never in a changed outcome). When a game ends, the seed becomes public: the Verify this game panel re-derives every roll of the game in your browser, and you can do the same offline from the chain log alone.

The operator does not play at tables it operates — with interactive holds, a seed-knowing player could otherwise compute every hold outcome before choosing.

Playing the bot. The bot is run by the people who run this site, as a separate program with its own wallet, and it never sees the operator's dice seed. It gets its dice exactly as you do, so it cannot choose or change a roll. One thing is our promise rather than something the chain proves: on this ledger the operator can work out a roll before you see it, and the chain cannot show that the bot never learns a roll early. That is why the bot plays only practice games, where the result moves no money: the contract gives the bot back exactly its own stake, whoever wins.

How long does a table take, and what does a turn cost?

A fast table has been measured with a person at it: a two-seat game against the bot ran 20 minutes from the first click to the payout — about 85 seconds a round, playing without pause. About 20 seconds of each round is the chain (one settlement per player and one close by the operator, each counting the moment its block is in; only the payout waits for finality); the rest is you rolling, choosing what to hold and where to score, and your wallet proving every move. Two people at the table run a little longer than one person and the bot. A slow machine proving on device makes a round longer for everyone, because the round ends when its slowest player has played. Seats play in parallel, so a fuller table adds a little, not a multiple.

An on-chain table puts every roll on the chain as its own transaction: about 30 seconds for each one you send from your wallet, about 8 for each of the operator's. A full three-roll turn is 4 transactions you sign and 3 the operator submits to resolve your rolls, one after the other; scoring right after your first roll is 2 + 1. Stopping early is the biggest lever you have over how long such a table takes. Nobody has played one for real yet, so that column is an estimate and says so.

Audit it yourself

The contracts are public and Apache-2.0 licensed: github.com/chrispalaskas/dust-dice-contract at tag v0.5.0 — the Compact source of the table and lobby circuits, their TypeScript mirrors, and the independent verifier this site's Verify page runs.

A link to source proves nothing on its own, so here is the part that does. Every table is pinned to one compilation: the chain checks each call against that build's verifier keys, and a hash of those keys is the build fingerprint. The operator is running reading…, asked of it live. Compilation is reproducible — clone the tag, run npm run compact -w contract, and hash the verifier keys the same way (service/src/build-id.ts). If your fingerprint matches, the circuits deciding your dice and holding your stake are the ones you just read.

If it does NOT match, something is running that this source does not describe — which is worth knowing, and is the reason the number is published at all.

What this site is not

Dice and scorecards are public — this is an open-information game and we make no privacy claims about play. This deployment is a technology demo on a test network; the NIGHT staked here is test value. See the legal note in the project README.