What Is Provably Fair Gambling? Complete Guide for 2026

Provably fair is a commitment scheme borrowed from cryptography and applied to casino games. It lets you confirm, after the fact, that a result was fixed before you bet and was not changed afterwards. Here is exactly how it works, how to check it yourself, and what it does not prove.

The commitment

Before you place a bet, the server generates a secret random string — the server seed — and shows you its SHA-256 hash. A hash is one-way: you cannot derive the seed from it, but the server cannot later produce a different seed that hashes to the same value. That published hash is a binding promise about a secret you cannot yet see.

The three inputs

• Server seed — secret until you rotate, committed to via its hash.
• Client seed — chosen by you, or generated in your browser, and changeable at any time. This is what stops the server from picking a seed it knows produces bad outcomes for you.
• Nonce — a counter that increments with each bet, so the same seed pair never repeats a result.

Each result is HMAC_SHA256(server_seed, client_seed:nonce). The digest is then mapped to an outcome — a dice roll, a crash multiplier, a sequence of left and right bounces in Plinko — by a documented rule.

The reveal

When you rotate your seed, the server publishes the old server seed. Now you can do two checks. First, hash it and compare to the commitment you were shown at the start: echo -n "server_seed" | shasum -a 256. Second, recompute any bet you played: echo -n "clientseed:7" | openssl dgst -sha256 -hmac "server_seed", and apply the documented mapping. Both must match. If the first fails, the seed was swapped; if the second fails, the mapping is not what was published.

Why the client seed matters

Without your input, the server could generate many candidate seeds, compute the outcomes each would produce, and publish the hash of whichever one loses least. Because the result depends on a value you control and can change at will, that search is useless — the server would have to know your future client seed in advance.

What it does not prove

This is the part marketing pages skip. Provably fair says nothing about:

• The house edge. A verifiable game can still pay 1.90x on a true 50/50 bet. Verification confirms the roll, not the payout table.
• Solvency or withdrawals. Cryptography does not make an operator able or willing to pay you.
• Interface honesty. The odds displayed on screen could differ from the ones used in the calculation. Only checking the published mapping catches that.
• Whether you should play. A perfectly verifiable game with a 1% edge still returns 99% of everything you wager.

What a good implementation looks like

The seed hash visible before the first bet, one-click seed rotation, a searchable history of past seeds with nonces and results, and public documentation of the exact digest-to-outcome mapping including how it avoids modulo bias. If any of those four are missing, you have a claim rather than a proof. Step-by-step instructions are in our verification guide.