What Should a Provably Fair Poker Verifier Check?
A provably fair poker verifier is a tool that checks whether a finished hand matches the evidence published for that hand. It should not ask the player to trust a green badge. It should take the transcript, recompute the important parts, and show whether the commitments, shuffle path, visible cards, and result agree.
This matters because "verified" can mean very different things. A weak page may only say that a hand passed an internal check. A stronger verifier gives enough detail for a player, reviewer, or independent developer to repeat the same check outside the game client. For the hands-on idea, start with verify a shuffle yourself.
Inputs the verifier needs
A verifier needs the exact evidence for one hand. That usually includes a hand identifier, seat order, deck format, rules, commitments, reveal values, shuffle steps, visible board cards, shown private cards, action log, and final settlement. If any of those pieces are missing, the tool should say so clearly instead of pretending the proof is complete.
The input should also identify the algorithm and version used. A transcript that says "hash" or "random" is too vague. The verifier must know what data was hashed, in what order, with which encoding, and which comparison rule should pass. This is why a good poker shuffle transcript is more useful than a screenshot.
Checks that should pass
The first check is commitment integrity. Values promised before the hand should match the values revealed later. If a commitment was supposed to lock a seed, encrypted deck, or transcript step, the verifier should recompute the fingerprint and compare it with the earlier record.
The second check is deck reconstruction. Given the revealed data, the tool should rebuild the card order or the relevant encrypted-deck path and confirm that the visible cards came from that path. It should also notice impossible states: duplicate cards, missing cards, out-of-order reveals, or a board card that does not match the committed process.
The third check is result consistency. The final pot, winner, shown hands, folds, and showdown result should agree with the hand history. A fair shuffle proof is incomplete if the settlement record points to a different hand than the card evidence.
A useful verifier is not a decoration. It is a repeatable calculation that should reach the same answer even when the platform is not the one running it.
What the result should explain
Good verifier output should be plain. It can show "passed" or "failed," but it should also say which check was performed. If a transcript fails, the tool should point to the first mismatch: commitment mismatch, missing reveal data, invalid card sequence, broken action order, or settlement disagreement.
This is important for honest disputes. A player who sees an unlikely river card may feel cheated, but variance is not proof. A verifier helps separate "the result hurt" from "the evidence does not match." For common misunderstandings, see provably fair verification mistakes.
Limits of a verifier
A poker verifier is strongest at checking the deal and the hand record. It cannot prove that two players did not talk outside the table. It cannot detect every bot. It cannot prove that a player's device was clean or that an account was controlled by only one person. Those problems need anti-cheat review, reports, account security, and moderation.
It also depends on honest, complete export data. If the platform refuses to provide the transcript, publishes only a vague summary, or makes the checker run only inside a closed client, the player is still mostly trusting the platform.
What players should look for
Look for a verifier that can run independently, uses exportable evidence, explains failures, and documents the exact steps. It should avoid asking for personal secrets. A hand transcript should contain verification material, not passwords, recovery codes, private messages, or unnecessary device data.
Fair Poker's verification approach is built around this narrow promise: a hand should leave evidence that can be checked after play. The public guide at fairpoker.app/verify-guide.html is the practical place to start.
Final thought
A provably fair poker verifier turns a fairness claim into a test. The best version is boring in the right way: clear inputs, repeatable calculations, useful failure messages, and honest limits. That is what lets players move from "trust the site" toward "check the hand."