Nobody stacks the deck. Not even us.
You don't have to take our word for it. Your own browser checks every hand, while you play, without you doing a thing.
In plain English
1. Every player helps shuffle
Before each hand the server shuffles a deck and locks every card, face down. Then each player's device adds a random number of its own, sealed so nobody can see it. Those numbers, together, decide which locked card is dealt where. The server can't pick the cards, because it doesn't know the players' numbers. A player can't either, because the deck was locked first. Bots add no number: they run on the server.
2. The deck's fingerprint is locked before the first card
Before anyone adds a number, the server sends every player's browser a fingerprint of the locked deck, and the browser keeps it. Change one card afterwards and the fingerprint no longer matches. When the hand is over, the server opens the locks on every card that was shown, and your browser checks them against that fingerprint.
3. Your browser checks every hand
Your browser keeps its own copy of the table and plays every hand along by the rules: every bet, every pot, every stack. It never takes the server's word for who won. Every move a player makes is signed by that player's device, so the server can pass a move on but can't invent or change one. When all of it adds up, the hand shows ✓ fair. The table's results it counts itself too, hand by hand, and holds the server's count to its own while you sit at the table.
4. What the red warning means
A ⚠ warning means your browser saw something that only a server breaking the rules could cause: cards that don't match the locked deck, a move nobody signed, chips that don't add up. The checks are built so that a bad connection, a locked phone, or a slow tap gets a quiet note at most, never a warning. A warning never goes away once shown, and the results list marks the chips won or lost in that hand, so nobody can pass off a spoiled hand as a clean win.
Cards that were never shown (folded hands, mucked hands, the rest of the deck) stay locked for good. Nobody at the table gets to see what you folded.
For experts
The dealing method, version 3, as the code runs it. Hashes are SHA-256, signatures Ed25519, both from the browser's Web Crypto. All shuffle randomness comes from crypto.getRandomValues.
- Commit. The server shuffles 52 cards (Fisher-Yates, no modulo bias) and seals each position on its own: a hash of the position, the card, and a 16-byte random salt. It announces one commitment over the hand id, the deal order, the human players dealt in (seat and public key), and all 52 sealed cards.
- Seal. Each human player's browser checks the announcement against its own copy of the table, saves it, picks a fresh random seed, and sends a seal (a hash of the commitment, its seat, and the seed) signed with its table key.
- Reveal. Once every seal is in, the server sends everyone the full list, exactly once per hand. Each browser checks every signature and that every human has exactly one seal, saves the list, and only then reveals its seed. A second list fails the hand.
- Mix. The seeds and the commitment are hashed into a public order: the card dealt to slot s is the server's card at position mix[s]. Hole cards go out in two rounds starting left of the button, then five board cards. No burn cards.
- Late devices. A player whose seal doesn't arrive in time is folded and the round starts over under a fresh hand id, before anything was revealed. A player whose revealed seed doesn't arrive is folded and the hand is dealt without it. A hand never starts over after a reveal. A hand id is never used twice.
- Prove. After the hand the server publishes all 52 sealed cards, every signed seal and seed, and the salts of the cards that were shown. Each player already holds the salts of its own hole cards. Every browser rechecks the commitment, the list of humans, every signature, every seed against its seal, the mixing order, and every card it saw.
- Shadow table. Each browser runs the same rules engine as the server and matches every event, in order, against what the rules produce. Blinds, the button, pots, side pots, and final stacks are computed, never accepted. Taken on trust only: the table as it stands when the browser sits down, the button of the first hand after that, and the end of a hand already under way.
- Signed actions. Every fold, check, call, bet, raise, and seat change is signed by the player's table key and pinned to the table, the hand, the seat, and its place in the hand (a seat change: the table, the seat, and that seat's change number). Moves the server makes itself (a timeout, a bot's move, a dropped connection) are marked as such.
- Keys. Each browser makes a table key per table. The player's identity (a Nostr key, made on the device at first visit) vouches for it with a signed note. The note goes only to this server, which passes it to the other browsers at the table so they can check it; it is never posted to a Nostr relay.
The shuffle, measured
We dealt 1,000,000 hands with the game's own shuffle and mixing code and its real random source (2026-10-01), and tested the server's shuffle, the players' mix, and the two together. Every test passed.
- Card positions. Every card lands in every deck position about equally. Scores 2,531, 2,791, and 2,567; a fair shuffle scores about 2,601, and the limit is 2,970.
- Starting hands by seat. Across 8,000,000 starting hands, each of 8 seats got premium hands (the top 10%) 10.0% of the time.
- Consecutive cards. No card makes another more likely to follow it. Scores 2,728, 2,612, and 2,736; fair is about 2,651, the limit 3,023.
- Prediction. Four pattern-finders made 51,000,000 guesses each per step. None did better than blind guessing (3,538,044 right, give or take 8,362).
Each limit is set so a fair shuffle goes over it about once in a million runs. This measures the shuffle, not the host: the checks in your browser are what catch a host that changes the cards.
The Daily Deal
One deal a day: 20 hands against five bots, and everyone plays the very same hands that day: the same cards, the same suits, the same seats, and the same bots, as in duplicate bridge. There are no other players at the table to help shuffle, so its cards are fixed another way.
1. The day's cards are locked in a day ahead
The morning before, the server makes a secret for the day and publishes a lock on it, together with the number of a block of a public blockchain that has not been made yet (about six hours away). When that block arrives, its fingerprint, which nobody could know in advance, is mixed with the secret, and every card of the day comes from the two. So the server could not have picked the day's cards: it was bound to its secret before the block existed.
Your browser checks that block itself, asking only this site. It checks that it is a real block: each one carries proof of the enormous work it took to make, which nobody could fake. That it is the very block the lock named: the site sends the chain of blocks from the one that was newest when the lock was made, each block naming the one before it, so the block's place is pinned to the lock, not taken on anyone's word. And that it was made after the lock: one from before it is refused. The fairness list shows it under "today's cards", with the block's number and ✓ checked. A check that fails is a red warning. If the site is slow to answer, the line says "not checked yet", never red. A lock your browser has seen is kept as it was: one shown later for the same day that differs is a red warning too.
2. Your browser checks every hand
Before each hand, your browser is sent a fingerprint of that hand's 52 locked cards and keeps it. After the hand it checks every card you saw against it, and plays the hand along by the rules as at any table: every bet, the pot, your chips. Every hand starts everyone at 10,000 chips, and a hand ends the moment you fold. Your moves are signed by your device. The fairness list counts the hands your browser checked under "your hands" ("20 of 20 ✓ fair"), and "show each hand" lists them one by one.
3. The day after, your browser checks they were the day's own
Once the day is over, at 5:20 am Central the next morning (five minutes after its last hand was played out), the server publishes the day's secret. The next time you open the Daily Deal, your browser holds the secret to the lock it kept from the day before, then deals each of your hands again from the secret and the day's block (the one it checked on the day: a server that now said the day had none, or named another, is a red warning), and checks that each is the very deck sealed before the hand, at your own table. So your cards were the day's own: the same cards as everyone's, fixed before the block existed. The fairness list says so under the day's name: "yesterday's cards", "your 20 hands", ✓ the day's own. A hand that doesn't match is a red warning, kept. The server never publishes a day's secret sooner: until the day is over it would give its cards away. Your browser keeps each hand's lock for a week, so a phone that comes back up to a week later checks the days it played. A run played on another device is checked there, and the list says "played on another device"; a run played before this check came says "played before this check came". If the site is slow to answer, the line says "not checked yet", never red.
4. Par, and where you stand
Par is set before the hand is played. A hand's par is what one of the bots, the Shark, expects to score with your two cards, from your seat, after the moves the other bots made before your turn: averaged over all the cards nobody has seen yet (the other players' cards and the board still to come). So par does not know what is coming, any more than you do. Folding can never get ahead of par: a hand's par is never lower than what a fold costs, and a fold matches par only where the Shark would fold too.
All-in luck is taken out of your score. When all the chips go in before the last card and nobody can bet any more, your hand is scored by your fair share of the pot: your chances of winning it, counted over every card that could still come. The table and the log still show who won the pot.
Your result is your score over the 20 hands, each set against its own par. Where you stand is your place among the runs finished that day so far, by your number for the day (the same number shares a place), so it can move until the day ends at 5 am Central.
Each hand gets a number: your chips in it over or under its par, divided by the big blind and rounded to a whole number. A half rounds away from 0, the same for plus and minus (+0.5 is +1, -0.5 is -1), so within half a big blind of par a hand is 0. Your number for the day is the sum of your 20 hands' numbers, and nothing else. Plus means you beat par, minus that you missed it, 0 that you matched it. As soon as your run is over, your results show each hand's number, and they add up to your number; wherever a hand's number or your number shows, it is that same number. Days played before this way of counting began keep the numbers they showed (the day's chips over or under par rounded once, with a hand or two in your results rounded the other way so that the 20 added up to it).
Your edge is the average of your last 20 days (with fewer, of the ones you have; none before your fifth), and higher is better. It counts how well you decided, not the cards that came. Each decision you made is set against what the Shark expects from that very spot, with your two cards and what you had seen, and the cards that came after are left out; 0 is the Shark. A day counts once it is over, at 5:15 am Central the next morning, and the server has worked it out, from every seat's cards and the day's secret, so anyone with the secret and this game's code can work it out again (the server publishes the secret once the day is over: see 3 above). Your results then say what that day gave your edge, as in "+3 BB for your edge". Until then, and on days before one deal for everyone, a day counts as your chips over or under par that day, in whole big blinds.
The ♛. At the reset that opens each Monday (5 am Central), the saved player with the best edge over the last 30 days wears a ♛ beside their name at every table, friends tables and the Daily Deal, until the next Monday's. Saved means a spot kept with a passkey or linked to your own Nostr id: your page tells the server so with each Daily Deal run, and the server takes its word (it can't tell whose saved spot is whose). The 30 days run through Saturday's deal (Sunday's runs are still being finished and worked out as Monday opens, so they count the next week), and only days whose decisions the server has worked out count, at least 10 of them; never a day counted against par. The number is the average of those days, the latest 20 at most, so for someone who plays most days it is about the edge in their results (the edge rounds each day first). A tie shares it, and with nobody who qualifies, nobody wears it. Once posted it stays up all week, whatever happens. A table is told who wears it only for the players seated at it.
A match with a friend. You and a friend can play each day's hands as a match: one of you asks with a link, the other says yes, and either of you can stop it at any time. From 5:15 am Central the next morning, once that day is over for everyone (by the server's clock, whatever a phone's says), each of you sees your 20 hands beside the other's: each hand's number against its par in big blinds, and how the other played it. The higher number wins the hand and the same number ties it, and the match is told as hands won: "you won, 12 to 6", with "2 tied" under it. Each hand's number is the one in your results, rounded on its own, so the same play always reads the same, and each side adds up to that player's number for the day. Only days you both played, from the day of the yes on, and never anyone's edge, streak, or ♛; nothing ranks. Your browser checks the cards of your own hands as ever; your friend's numbers and moves are the server's word, as your place is.
The Daily Deal is always played 100 big blinds deep: 10,000 chips at blinds of 50 and 100, a fresh stack every hand. Par has been set this way since October 15, 2026, and your edge counts the runs from then on. If the depth ever changed, par would be set anew, and a new edge would start.
Its limits, said plainly. The server deals these cards, so it knows them, as at a friends table. Your browser checks each hand's cards against that hand's fingerprint, the day's block itself, and, the day after, that the cards were the day's own, the same as everyone's as long as the server shows everyone the same lock (a server that showed one player a lock of their own could deal that player other cards, and no single browser could tell); it does not check that every bot played by its script (that needs the bots' code, not published yet). A server that never published a day's secret would leave that day "not checked yet", never red: an answer without it looks the same as one from an older version of the game. Your browser holds the day's block to the time the lock says it was made: a server that kept its lock back until after the block, and gave it an earlier time, would go unseen by a browser that first saw the lock after the block (a browser that saw it the day before keeps it, and would see a lock changed). On a day the server says no block came in time, the cards come from the secret alone, and your browser cannot check that the block did not come. Par is worked out by our server, from many sample hands: it is good to a few tenths of a big blind a day (about three on the days before one deal for everyone), and the same for everyone. Your edge's numbers are worked out by our server from sample hands too, so each day's is itself a little rough, by about ten big blinds, which evens out over your days; your browser does not check them either (that needs the bots' code too). Because par is never lower than a fold, even the Shark lands a little under it over time. If a day's par were ever not ready when the day opens, that day would be scored the older way (the Shark's result on the deal's own cards, with no all-in adjustment) and would not count toward your edge. One run a day is per device: a second device or browser gets a second run, on the same cards. So someone could play a second device first and learn the day's cards, the way someone could look up the answer to a daily word puzzle: possible, and pointless, with nothing to win. From that run's results they could learn each hand's par too. Neither helps with the ♛: your edge counts each decision by what it is worth over the cards you have not seen, never the cards that came, so knowing them changes nothing there. In a test, a run that knew every card won about 15 big blinds a hand more chips than the Shark on the same hands, and its edge came out no better than the Shark's 0. Who wears the ♛ is the server's count: your browser checks neither the edges nor the count (it would need every player's runs).
Saving your spot
Your game key lives in one browser, and your Daily Deal history (each day's number, your edge, your streak) goes with it. On the same phone and browser you stay you, with nothing to do. To keep it through a new phone or a wiped browser, save your spot with a passkey: at the end of a Daily Deal run, one tap on "Keep this scorecard: Face ID" (or your device's own lock; at a friends table, "Keep tonight's results" once you leave), then Face ID (or your passkey app's own unlock). On a new phone, tap the box where you type your name: your passkey is offered above the keyboard, as a saved password is; pick it, and your spot is back. Where your browser can't offer it there, "New phone? Get them back" under the box does the same. Any passkey app works: Apple Passwords, Google Password Manager, 1Password, Dashlane, Bitwarden, Windows Hello. It keeps the passkey, synced by its account (Windows Hello may keep it on that computer alone), so a new phone on the same account has it; another kind of device uses your system's own scan-a-code step with your phone.
When you save, your browser makes a secret and puts it inside the passkey, as the passkey's own id. Your passkey app hands it back, for this site only, after Face ID or its own unlock. From it your browser makes two things: the address of a box, and the key that locks it. The box holds your game key and your name. The server keeps the locked box at its address, and nothing else: it never sees the secret, can't open the box, and can't tell whose it is. Only your passkey can. Saving and asking for boxes is limited to a few times an hour from one address. No email, no password, no account with us.
Bringing it back on a browser that already has a spot of its own asks you first, and says plainly what switching means. The one catch: the secret lives inside your passkey, so anyone who can open your password manager can open your saved spot, the same as your passwords; and lose that account and the saved spot is lost with it. There is no "forgot password", because we hold nothing that could open the box.
A second door, for players with their own Nostr id: tap "your nostr id" under the name box. Your Nostr app (a browser extension, or an app on your phone such as Primal) signs one fresh question from the server, once, to prove the Nostr id is yours. Your browser then locks your spot (your game key and your name) so that only that Nostr id can open it, and the server keeps the locked spot, with the public half of its lock, under your Nostr id's public part (its npub), and nothing else. The line then shows your own Nostr id. On a new phone, the same tap with the same Nostr app brings your spot back: your app is asked once more, to open it. The game never asks for, sees, or keeps your Nostr app's secret. One Nostr id links to one spot; a browser with a spot of its own asks you first, as above. Tap the line again to unlink it: nothing is asked of your app.
Known limits
What this does not prove, said plainly.
- The server knows the cards during a hand. It can't change them unnoticed, but this version trusts it not to look. The next version of the deck is planned so that no one knows the cards, the server included.
- The checks run in the page this site serves. A dishonest host could serve a page that lies about its own checks. An independent checker is built and not yet published.
- Hidden cards are never opened, so they are never checked. Only cards that were shown, and your own, are. So nothing proves that the cards nobody saw made up a proper deck: a card locked in twice is caught only when one player gets to see both copies.
- Timing is not checked. Your browser can't tell why a server was slow.
- A dishonest server can still spoil a hand. It can't change a locked card or move chips against the rules without a red warning. But things a bad connection can also cause (a missed turn, a fold before the deal because a device's number never arrived) get only a quiet note, so a server could hide behind those. The fold before the deal matters most: a server sees every number before it deals, so it could act as if one arrived too late, fold that player, and deal without it. That gives it a pick between two deals. When a number goes missing, every browser sees whose.
- Who sits at the table comes from the server, and so does how a bot plays. Each player's key is vouched for by the identity shown beside the name. A made-up player still can't choose the cards: the most it can do is hold back its own number, which is the limit above.
- The table's results before you came are the server's count, and so are the results shown right after you leave the table, which your card is made from. From when your browser first sees the table it counts every hand itself, but it holds the server's count to its own only while you sit at the table; and if the server sends a hand's news it cannot follow, it stops counting until it is shown the table again, and then takes the server's count.
- Away for 15 minutes or more? If the table forgot you in that time, your browser can't check the hand you left. The other players' browsers still check it.
- An update can cancel a hand. Before the server restarts for an update, the hand being played finishes, or, still going after 2 minutes, is cancelled: every chip goes back where it was when it started, and its cards are still checked. Your browser checks that an update was announced during that hand, that players still had moves to make, and that the cancel came no sooner than the 2 minutes an honest update waits, less 30 seconds for a slow connection (unless your connection dropped meanwhile). A dishonest host could still stall a hand for 90 seconds and then cancel it, in plain sight: it shows on every screen as a cancelled hand.
- A server crash in the middle of a hand shows that hand's players the red warning, though nobody cheated.
- Your keys live in your browser, not locked away. Anyone using your unlocked browser can play as you. A saved spot is as safe as your passkeys: anyone who can open your password manager (your unlocked phone, or its account) can bring your spot back. A linked one is as safe as your Nostr app: anyone who can use it, or anyone it signs for without asking you (some apps do, by default, for apps you connected), can bring your spot back, or leave a spot of theirs under your Nostr id for a new phone to bring back.
- Players can team up, as at any table. No software stops two friends on the phone.