Provably fair gambling, explained

'Provably fair' is a specific cryptographic protocol, not a marketing slogan. What it commits to is this: the casino cannot change the outcome of a round after you see the inputs, and you can prove this was the case for any given round, after the fact.

That is a narrower claim than 'the casino is honest'. Provably fair does not prove that the casino's odds are advertised correctly. It does not prove the RNG is unbiased. It proves exactly one thing: the result was determined before your bet was placed, and the operator did not pick the result to make you lose.

It's useful. It's not a panacea.

Before you place a bet, the casino generates a secret value called the server seed. They immediately publish a cryptographic hash of that secret — typically SHA-256. You see the hash; you don't see the secret itself yet. This is the commitment.

You provide a client seed. Most interfaces let you set this explicitly — your username, a random number, anything you choose. The point is that the casino can't predict it because you chose it independently.

Each round uses a nonce — just a counter. Round one has nonce zero. Round two, nonce one. And so on.

The result of any given round is a deterministic function of these three inputs: HMAC-SHA256(server_seed, client_seed:nonce). The casino can't know the result until all three values exist, and the server seed is the only part they control.

Here's the critical point. The casino commits to their server seed before you know what it is. Once committed, they cannot change it without changing the hash — which is cryptographically impossible for SHA-256 within any reasonable computational budget.

After your session ends — or whenever you rotate your seed — the casino reveals the server seed. You can then compute SHA-256 of the revealed seed and compare to the hash they committed before. If it matches, they didn't swap seeds mid-session.

With the revealed server seed plus your client seed and the nonce sequence, you can recompute every single bet result. If what you computed matches what actually happened in the game, the round was honest.

Stake Originals Dice, as a concrete example. Before your session: casino publishes hash H = SHA-256(server_seed). You set client_seed = 'mysession123'. You place bet on nonce = 0, betting under 50.

The result is determined by computing HMAC-SHA256(server_seed, 'mysession123:0'), taking the first 4 bytes of output, mod 10001, dividing by 100. That gives you a number between 0.00 and 100.00 — the 'dice roll'.

If your dice roll comes up 37.45, you win (under 50). After you rotate your seed, Stake reveals server_seed. You compute SHA-256(server_seed) and verify it matches the committed H. You compute HMAC-SHA256(server_seed, 'mysession123:0') and check the roll calculation produces 37.45. All three checks pass — the round was honest.

Tools exist to do this verification automatically — Stake's own dashboard has a verifier built in. You can also verify externally with a standard cryptographic library if you want complete independence.

The odds. If a dice game claims a 1% house edge but actually runs 3%, provably fair verification doesn't catch that. The math distribution of outcomes is correct, but the payout on those outcomes is a separate operator-controlled parameter.

The RNG quality. A malicious operator could use a weak server seed source. Provably fair proves they committed to the seed, not that the seed was cryptographically strong.

Third-party slots. Almost no third-party slots (Pragmatic Play, Hacksaw, Nolimit City) use provably fair seeds. They use provider-level RNG certification audited by third parties. Different trust mechanism, same goal, not interoperable.

The platform's overall honesty. An operator could run every game provably fair, freeze your withdrawal, and the provably fair mechanic would tell you nothing about the withdrawal freeze. Separate concerns.

Stake's implementation is the industry reference. Seed commitment before the session, reveal after rotation, automatic verifier in the dashboard, documented algorithm for every original. Every Stake Original uses it.

BC.Game's implementation is similar but less well-surfaced. The mechanism exists; finding the verifier takes more clicks.

Rollbit and Duelbits publish seed-reveal on their originals but the UX is less polished.

Some smaller operators claim 'provably fair' but don't publish hash commitments or seed-reveal tools. Claim without mechanism. Don't trust these.