How to Verify a Provably Fair Game Result — Step by Step

How to verify a provably fair game result means recomputing the outcome from published inputs — not trusting a black-box RNG claim. On VFairGames, you copy fairness fields from a settled round (or after a seed reveal) and paste them into verify.vfair.games.

This is a hands-on guide: what to enter, which game-specific fields matter, and what a “match” does and does not prove. For the plain-language overview of commit–reveal, see What is provably fair?.

Where to get the inputs

In-game Provably Fair / bet history shows:

• Server seed (commitment) — the hash you see while the seed is still in use
• Server seed — the revealed secret (only after you rotate to a new seed pair, or when history shows it revealed)
• Client seed — your side of the entropy
• Nonce — how many bets have used this seed pair (starts at 0)

You cannot verify the raw outcome until the server seed is revealed. Changing the seed pair reveals the previous server seed and starts a new commitment with a new client seed (nonce resets to 0). Rotation is blocked while a round is still open (for example an active Mines round).

Step-by-step on verify.vfair.games

1. Open verify.vfair.games.
2. Select the game (Dice, Limbo, Mines, Plinko, or Keno).
3. Paste server seed (required — 64 hex characters).
4. Optionally paste server seed hash — the tool checks SHA-256(server seed) against it (match / mismatch / skipped if blank).
5. Paste client seed and nonce.
6. Add game-specific fields when shown:
   • Mines — mine count (1–24)
   • Plinko — rows (8–16)
7. Click Verify. Everything runs in the browser via HMAC-SHA256.

What each game shows back

Game	Result the tool recomputes
Dice	Roll value
Limbo	Crash-style multiplier
Mines	5×5 mine layout
Plinko	Left/right path + bucket index
Keno	Drawn numbers (sorted)

Limbo uses the game’s configured RTP from launch settings inside the mapping (default 0.98 when unset). Plinko risk and Keno risk / picks are not form fields — the tool verifies the raw draw/path, not the paytable lookup.

What verification proves (and what it does not)

Proves

• The revealed server seed matches the earlier hash (if you entered the hash).
• The published HMAC mapping produces the same raw outcome as the UI for those seeds and nonce (and Mines/Plinko extras).

Does not prove

• That the wallet paid the right amount
• That deposits or KYC are safe
• That a risk level, target, or pick set was “optimal”
• Auto-matching against bet history (you compare manually)

Same honesty bar as any good PF write-up: cryptography locks the result generation, not the operator’s business.

Operator notes

Partners can launch a themed verifier via the games API verification launch endpoint and pull per-round fairness fields once a round is settled. Players evaluating VFairGames can stay on the public tool with copied seeds.

Game-by-game mechanics: Dice, Limbo, Plinko, Keno, Mines max win.

Evaluating VFairGames for your casino or platform? Email info@vfair.games.

FAQ

Can I verify before the server seed is revealed?

You can see the hash commitment, but you cannot recompute the outcome until the server seed is revealed (usually by rotating to a new seed pair).

Do I need the hash field?

No. Leave it blank to skip the hash badge. Filling it is the strong check that the revealed seed is the one that was committed.

Why doesn’t Plinko risk appear in the verifier?

Risk only selects a paytable. The verifier recomputes the HMAC path and bucket; you map that bucket to the published table for the risk you used.

Is verification run on VFairGames servers?

The public tool runs the HMAC math in your browser. You are not sending seeds to a black-box “trust us” endpoint for the recompute itself.