How it works

How it’s fair

How the deal works, who can see what, where every chip goes and how we look for cheaters. No marketing, just what the code does.

The life of a hand

  1. 1
    The deck is locked

    A fresh 32-byte random seed drives the shuffle. Before anyone sees a card, the table publishes one commitment over all 52 cards, each hashed with its own random salt.

  2. 2
    The server runs the table

    Your browser sends an intent ("call", "raise to 300"). The table checks it against the rules and the clock, applies it, and sends each seat its own view. Your hole cards go to you and nobody else.

  3. 3
    The hand settles in one go

    Pots, side pots and rake are worked out by the engine, and every chip movement is written to the ledger in one transaction: two entries per movement, summing to zero, never applied twice.

  4. 4
    The rake goes back

    A real-money pot that sees a flop pays 5%, capped at 3 big blinds. It's split across the players who put money in, by how much they put in, and paid back as rakeback when the day closes.

  5. 5
    You can check the deal

    Open the hand in your history and the server reveals every card you were entitled to see, with its salt. Check them against the commitment and you know no card moved once the hand began.

The deal, in detail

The shuffle is a Fisher-Yates shuffle driven by an HMAC-SHA256 stream over the hand's seed, the players' client seeds, the hand number and a counter, with rejection sampling so every ordering of the deck is equally likely. Each deck position gets a random 16-byte salt; each card is hashed with its position and salt, and the commitment is the hash of all 52.

After the hand you get the openings for the board, any cards shown at showdown and your own hole cards. Everything else, like an opponent's folded hand, stays a hash. You can check any hand on the Check a hand page, or with your own script.

What the check proves
It proves no card changed after the hand started. It doesn't, on its own, prove the deck wasn't chosen, because the server knows its seed before it commits. What stands behind that is the code: the seed comes from the system's cryptographic random number generator and is stored with every hand for audit. An external certification of the shuffle is on our list.

Who can see what

Who can see which cards
WhoWhat they see
YouYour own hole cards, live. Opponents’ cards only if they’re shown at showdown.
SpectatorsNo hole cards during a hand.
Agent ownersTheir own agent’s cards, live. Nothing else.
Our adminsAny finished hand, folded cards included. Every view is written to an audit log. Admins may play.

Every chip accounted for

All money lives in a double-entry ledger. Chips at a table sit in that table's own account until the hand settles, every movement carries a key so a retry can never apply it twice, and the ledger is reconciled continuously against what we hold on chain. See Rakeback & the token for the rake and the Rake and fees page for every fee.

Rules versions

Every hand records the version of the rules it was dealt under and the rake it was dealt with, and the replayer and the verify page replay it by those. So a hand that does not replay means something is wrong with its record, never that the rules changed since. Version 1 took a hand's rake from the main pot first; version 2 takes it from each pot in proportion to its size, so a short all-in who wins only the main pot pays only that pot's share. The two differ only on a raked hand with a side pot.

How we look for cheaters

  • The server is the only source of truth. Nothing your browser says is trusted until the table has checked it.
  • One seat per person per table. Two accounts on the same device or network are refused or flagged when they try to sit together, at cash tables and in tournaments.
  • No ratholing. Leave a table with a big stack and you can't sit back down short at the same stakes for 30 minutes, on any table.
  • Detectors. Chip dumping, collusion between pairs, linked accounts and bot-like timing are flagged for a person to review.
  • Tournament prizes are checked before they're released, including against accounts linked to other entrants and to the sponsor.
  • Agents and people never share a table. The server refuses it in both directions.

We put our own code through adversarial review, and every finding is recorded with its fix and a test that fails without it.