What You're Verifying
When you verify a provably fair bet, you're confirming two things. First: the server seed used for your bet matches the hash that was committed before you placed the bet (proving the casino didn't change the seed after seeing your wager). Second: the game result that was shown to you matches what the algorithm produces when you feed it the server seed, your client seed, and the nonce. If both checks pass, the outcome was fair. If either fails, something went wrong. This is a complete, independent audit of a single bet — no trust required.
Step 1: Know Your Seeds Before Betting
Before you start a betting session, visit the Fairness section of your casino (on Rookie, it's the Fairness page). You'll see three pieces of information: the server seed hash (a long string of hexadecimal characters — this is the SHA-256 hash of the server seed that will determine your outcomes), your client seed (a string you can set yourself or let the system generate), and your current nonce (a counter that increments with each bet). Copy and save the server seed hash somewhere. This is your proof that the server committed to a specific seed before your bets. Your client seed can be changed at any time — some players set it to something personal or random for extra confidence.
Step 2: Place Your Bet and Note the Result
Play normally. After each bet, the result is displayed as usual — your Crash multiplier, your Plinko bin, your slot reel positions, your blackjack cards. Note the specific result you want to verify. Also note the nonce for that particular bet (it increments by 1 for each bet since your last seed rotation). Most provably fair casinos show the nonce in the bet history or fairness section. On Rookie, your bet history includes all the information needed for verification.
Step 3: Reveal the Server Seed
To verify past bets, you need the actual server seed (not just the hash). You can reveal it by rotating to a new server seed — this reveals the old seed while generating and committing a new one for future bets. On Rookie, you do this on the Fairness page by clicking "Rotate Seed." Once revealed, the unhashed server seed is visible in your seed history. Important: rotating reveals the old seed, meaning all bets made under that seed are now fully verifiable. Your new seed takes effect immediately for future bets.
Step 4: Verify the Hash Commitment
Take the revealed server seed and compute its SHA-256 hash. You can do this with any SHA-256 tool — there are free ones online, or you can use a terminal command (echo -n "your_server_seed" | shasum -a 256). Compare the hash you compute to the server seed hash you saved in Step 1. They must match exactly. If they match, the server didn't change the seed between when it was committed and when you were betting. If they don't match, the server changed the seed, which is a serious integrity violation.
Step 5: Reproduce the Game Result
Now take the server seed, your client seed, and the nonce for the specific bet you want to check. Compute HMAC-SHA256(server_seed, client_seed:nonce) — again, available through online tools, scripts, or terminal commands. This produces a hex string. The game-specific algorithm converts this hex string into a result: a Crash multiplier, Plinko bounce sequence, card values, slot reel positions, etc. On Rookie, the Fairness page has a built-in verification tool where you can enter these values and see the computed result. It should match exactly what you experienced during gameplay. If it matches, the bet was provably fair.
Using Third-Party Verification
For maximum confidence, you don't have to use the casino's own verification tool. Because the algorithm is documented (HMAC-SHA256 with published game-specific derivation), anyone can build a verification tool. You can write a simple script in Python, JavaScript, or any language with HMAC-SHA256 support. The algorithm documentation on Rookie's Fairness page provides everything needed to reproduce any result independently. Third-party verification is the strongest form of audit: you're not trusting the casino's tool to tell you the casino was fair — you're computing it yourself from the raw cryptographic primitives.
What If Verification Fails?
If at any point the verification doesn't match — the hash doesn't equal what was committed, or the computed result doesn't match what was displayed — that's a red flag. On a legitimate provably fair platform, this should never happen. If it does, document everything (screenshot your seeds, hashes, and the mismatching results) and contact the platform's support with the evidence. On Rookie, the entire provably fair system is deterministic: the same inputs always produce the same output. If you follow the verification steps correctly and get a mismatch, something is genuinely wrong and needs investigation.