BEAT commits to a secret server seed before betting. Save its full fingerprint outside BEAT, then compare it with the revealed seed and the result in your bet record.

This guide covers BEAT Originals: Dice, Limbo, Keno, Mines, Plinko, Coin Flip, Roulette, HiLo, Blackjack, Baccarat, Crash and Slide. Supplier games, slots and live casino are outside this verifier. Use it for a bet with Provably Fair in its details.

Open the shield button (Provably Fair), then My Seeds. Copy Active Server Seed (Hashed) and New Server Seed (Hashed) into your own note outside BEAT. A screenshot may cut off the fingerprint. Save the values for the game you will play: games sharing a seed pair can display different commitments.

Open Verification in another tab. Choose Dice and keep these example values. They are public tutorial values, not a real wager.

8cea8352bc2fd1e579138401142a5a669aa19bdc19c611216736a0c066c3dbf4

beatgg-guide

1

Press Verify locally. Raw verifier output shows outcome 34.22. With Dice Under 49.50, this result is below the target. Calculation complete means that the browser calculated an outcome; it does not prove a saved bet is fair.

Change the last e in beatgg-guide to a: outcome becomes 11.08. Restore the client seed and change Nonce to 2: outcome becomes 3.55. The server seed hash stays the same.

Restore Nonce to 1 and change the last server seed character from 4 to 5. Outcome becomes 92.33 and the hash starts 7c23846c. Restore 4 to get the full hash below. Compare every character, not just its beginning.

68eb03bdfe0fe86f3181fa3356691821b038528d04cc9f9841fe5ba618a2a1952ef70be420cefd7d5a2fd236133c0a86a48be91c223cd180d71602965f1c26ea

Before betting you save the commitment. The game uses the secret seed, client seed, nonce and game settings. After disclosure, compare the revealed seed hash with your saved commitment, then compare the recalculated outcome with the stored outcome.

1. Save the game commitment outside BEAT before placing the bet.

2. Place your bet as usual.

3. For seed-pair games, open Provably Fair → History → Rotate To Verify. Disclosure waits until all related rounds finish. If rotation is blocked, finish the active rounds and retry. Crash and Slide reveal the event seed after the event finishes.

4. Open the bet in My Bets, then Provably Fair → Verify this bet. For Crash and Slide, choose Verify this round. The verifier receives the historical seeds, nonce, game settings, stored result and formula version in memory.

5. Read Result match and Receipt hash match. Paste your own saved commitment into Saved pre-bet commitment to read Saved pre-bet hash match. Without your saved value, BEAT records are being compared with other BEAT records; this does not establish what you saw before betting.

Waiting means the seed, historical settings, formula version or required action proof is unavailable. It is not a successful verification. Open the original receipt again after disclosure. A handoff expires after five minutes or a session change.

Check the game, full saved hash, exact nonce, seed characters and historical settings. Spaces can matter. If a mismatch remains, keep the Bet ID and your saved commitment and contact Live support.

Outcome matching verifies the recorded number, cards or positions. It does not prove wallet settlement, payout rounding, maximum payout enforcement or exchange rates.

Blackjack public verification calculates a card stream, not your actions or payout. HiLo seed-only calculation has the same limit; a stored HiLo proof can replay the recorded choices and settlement calculation. Currency conversion, caps and actual wallet credit still need separate evidence.

A hash from a BEAT record is not an independently saved pre-bet commitment. The verifier and verdicts are also BEAT software. Independent laboratory certification is a separate claim.

The operator knows the secret seed and can calculate outcomes. You can choose your own client seed after saving the next commitment. A hash comparison detects a changed secret seed; it does not prove how an operator selected it.

Shared seeds and rejected requests can consume nonces. Your bet history alone cannot explain every skipped number. History lists are limited; use a retained bet receipt to address a particular old round.

Historical receipts use their stored formula version. Missing or unsupported versions remain Waiting rather than being calculated with current rules.