By Zavian Thornell — iGaming researcher, founder of FairGameLab.com
Key Findings
- Provably fair isn’t marketing — it’s a cryptographic protocol where the casino commits to an outcome before you bet, and you can verify after that they didn’t cheat.
- I built FairGameLab.com with 16 free verification calculators covering Crash, Dice, Mines, Plinko, Limbo, Keno, Wheel, HiLo, Baccarat, and more — no signup, no data collection.
- The math is public. Most crypto casinos use HMAC-SHA256 with three seeds (server seed, client seed, nonce) — and the algorithm for every game is published.
- Not all “provably fair” claims are equal. Some casinos hide the algorithm, refuse to rotate server seeds, or gate verification behind support tickets. I tested them.
- You can verify a bet in under 30 seconds once you know the flow. The barrier isn’t math — it’s that casinos rarely explain it.
- Responsible gambling still applies. Provably fair means the outcome is honest, not that you’ll win. The house edge doesn’t disappear because the math is transparent.
Can You Actually Trust an Online Casino?
That’s the question that pulled me down this rabbit hole in the first place.
I’ve been researching iGaming for years, and the honest answer used to be: “You trust the license, the auditor, and the reputation.” You trust that eCOGRA or iTech Labs actually tested the RNG. You trust that the Curaçao regulator followed up. You trust that the review site you’re reading isn’t just chasing affiliate commissions.
That’s a lot of trust to hand out to people you’ll never meet.
Then I ran into provably fair gaming — a system where you don’t have to trust anyone. Not the casino. Not the auditor. Not me. You just verify the math yourself. And once I understood how it worked, I couldn’t unsee it: this is what online gambling should have been from day one.
The problem? Almost no player actually verifies anything. Not because they don’t care — because nobody has ever shown them how. Casinos publish a “Provably Fair” page full of hashes and seeds and cryptographic jargon, and 99% of players nod and click “Play.”
So I built FairGameLab.com. Sixteen free calculators. One for each major provably fair game. No account required. No email. Just paste your seeds and nonce, hit verify, and see the math work in your browser.
This article is the story of what I built, what I learned along the way, and what it means for anyone who’s ever wondered whether the casino is really giving them a fair shake.
What “Provably Fair” Actually Means
Let me start with an analogy I keep coming back to.
Imagine you’re playing a game of cards with a stranger. Before the deal, they write down the exact order of the deck on a piece of paper, seal it in an envelope, and hand it to you. You don’t get to read it — but you’re holding it. Then they deal. When the round ends, you open the envelope and check: did the cards come out in the exact order they claimed before the deal?
If yes — they couldn’t have cheated. They committed to the outcome before knowing what you’d bet on.
That’s provably fair gaming. Every round works like this:
- The casino generates a “server seed” — a long random string — and shows you its cryptographic hash (SHA-256) before you bet. That hash is the sealed envelope.
- You provide a “client seed” — either the default your browser generates, or one you type in yourself. This ensures the casino can’t have pre-computed outcomes based on knowing everything in advance.
- A “nonce” increments with each bet you make (1, 2, 3, and so on) so the same seed pair produces a different outcome every round.
- The game runs. You win or lose.
- The server seed is revealed at the end of a session (or when you rotate seeds manually). Now you can verify: does hashing the revealed server seed produce the exact hash they showed you before? If yes, they didn’t tamper.
- You re-run the algorithm yourself using the revealed seeds and the nonce. If the game outcome matches, the round was honest.
The whole system rests on one mathematical property of SHA-256: given a hash, you cannot reverse-engineer the input. And given an input, you always get the same hash. So the casino can’t change the server seed after seeing your bet — the hash they published would no longer match.
That’s it. That’s the entire trust model. No regulator, no auditor, no affiliate site required.
Why I Actually Built the Lab
Here’s what pushed me over the edge.
I was researching a well-known crypto casino for a review. Their Provably Fair page was thorough — they published the HMAC-SHA256 algorithm, the seed rotation flow, even sample code. I copied a losing Crash round I’d played and tried to verify it manually.
It took me forty minutes. I’m technical. I’d read the docs three times. I still had to open a Node.js console, install a crypto library, hand-type the seeds, and debug an encoding mismatch (the client seed had a hidden trailing space — thanks, clipboard).
At the end I got the multiplier: 1.42x. Which matched what the game had shown me. So the round was honest. But if a fluent developer needs forty minutes, what’s the realistic verification rate among actual players? Somewhere between zero and rounding-error-zero.
Provably fair had solved the trust problem in theory and abandoned it in practice.
So I built the tool I wished I’d had that day. Sixteen calculators. Each one implements the exact algorithm the major crypto casinos use — Stake, BC.Game, Roobet, Rollbit, and their smaller competitors — for a specific game. You paste in three fields, click verify, and you see the outcome plus the intermediate math. Thirty seconds. No installs. No console.
The site is at fairgamelab.com. Every calculator runs client-side in your browser — I don’t see your seeds, don’t log your bets, don’t have an account system. If you want to verify a $10,000 whale bet you’re welcome to it, and I’ll never know.
How the Verification Actually Works — With a Real Example
Let me walk you through a Dice verification, which is the simplest game and a good starting point.
The setup: You bet on Dice with these parameters:
- Server seed (revealed after session): a3f9c2e8b1d4f7… (64 hex characters)
- Client seed: my-cool-seed-2026
- Nonce: 47 (this was your 47th bet in the session)
Step 1: HMAC-SHA256
The casino computes HMAC-SHA256(server_seed, client_seed:nonce). This produces a 64-character hex string. Something like:
7c4d8b3e2a1f9c… (full 64 hex chars)
That’s your raw entropy for this bet. Pure cryptographic output. No human input past this point.
Step 2: Slice the entropy
For Dice, the algorithm takes the first 8 characters of the HMAC output and converts them from hex to a decimal number. 7c4d8b3e becomes 2085655358.
Step 3: Convert to a game result
Divide that number by 4294967296 (2^32) and multiply by 10001. Round down. Divide by 100. Now you have a number between 0.00 and 100.00.
For our example: (2085655358 / 4294967296) × 10001 / 100 = 48.57
That’s your roll. If you bet “under 50,” you win. If you bet “over 50,” you lose.
Every casino I’ve tested uses this exact algorithm for Dice, sometimes with a tiny variation in the multiplier constant. The Dice calculator on FairGameLab runs this in one click and shows you every intermediate value so you can spot-check the math.
Not Every Game Works the Same Way
The interesting thing about building sixteen calculators is discovering how differently each game maps cryptographic entropy to outcomes.
Crash takes the first 8 hex characters of HMAC output, converts to an integer, and runs it through a specific formula that produces a distribution favoring low multipliers. There’s a “house edge slot” — typically 1-in-33 rounds where the multiplier is forced to 1.00x — that’s how the casino makes money. The rest is provably random.
Mines is more elegant. The algorithm shuffles the 25 tiles using a Fisher-Yates shuffle seeded by the HMAC output, then places your chosen number of mines on the first N shuffled positions. You can verify not just that you hit a mine, but that the specific mine positions were determined before you clicked.
Plinko takes each ball drop as a separate roll — one HMAC iteration per row of pegs, each producing a left-or-right decision. A 16-row Plinko board requires 16 hex slices per drop. This is why the Plinko calculator on the lab takes a bit longer to render.
Limbo is basically inverted Crash — same core algorithm, different presentation. You pick a target multiplier, and the game rolls; if the rolled multiplier is ≥ your target, you win.
Keno shuffles a bag of numbers and draws N of them. Same shuffle logic as Mines.
Wheel, HiLo, Baccarat each have their own quirks, but all share the same three-input foundation: server seed, client seed, nonce.
What surprised me most was how deterministic everything is once you know the seeds. It really is a mathematical function. Same inputs, same output, every time. The illusion of randomness comes entirely from the fact that you don’t know the server seed until after you’ve bet.
What I Found When I Tested Real Casinos
Building the calculators forced me to read a lot of provably fair documentation across a lot of platforms. Here’s what I actually found — the good, the mediocre, and the concerning.
The good. The largest crypto casinos — the ones most players have heard of — implement provably fair correctly. Their algorithms are documented, their seeds rotate on demand, and their published hashes match the seeds when revealed. I verified dozens of real historical bets and every single one checked out. The math works.
The mediocre. A tier of mid-size casinos publishes the algorithm but makes rotation clunky. You have to email support to reveal a server seed. You have to know the right terminology to even find the verification page. In practice, most players will never verify anything, and the casinos know it.
The concerning. A handful of casinos advertise “provably fair” without publishing their algorithm at all. They give you a hash and a seed and say “trust us, the math works.” That’s not provably fair — that’s provably-fair-flavored branding. If the algorithm isn’t public, you cannot verify anything. Full stop.
The tell is simple: can you, sitting at your keyboard right now, reproduce a game outcome from published seeds using public code? If yes, it’s real. If no, it’s marketing.
FairGameLab covers the algorithms used by the top platforms. If a casino uses a non-standard algorithm and won’t share it, no external calculator can help you — and that itself is a signal about how much they actually value transparency.
Which Games Are Actually Verifiable
Here’s my working taxonomy after months of this:
Fully verifiable in real time: Dice, Crash, Limbo, Mines, Plinko, Wheel, HiLo, Keno, and their close cousins. These are pure algorithmic games — one bet, one outcome, one function call. My lab handles all of them.
Verifiable but harder to check bet-by-bet: Blackjack, Baccarat, poker, video poker. These involve card orderings, and while the shuffle is provably fair, following which card went where across a multi-decision hand takes more work. Still doable — the lab has Baccarat — but the mental overhead is higher.
Provably fair claim, but limited scope: Live dealer games. These aren’t actually provably fair in the cryptographic sense because there’s a physical dealer involved. Some platforms overlay a provably fair layer on top of the shoe order, but the trust model is fundamentally different.
Not provably fair at all: Traditional slots from big studios (NetEnt, Pragmatic, Play’n GO, etc.). These use certified RNGs audited by regulators — a different trust model entirely. You trust the regulator, not the math. Neither model is wrong, but only one lets you personally verify.
If verifying every bet matters to you, stick with the first category. If you’re okay trusting audits, the second and fourth are fine. Provably fair is a tool, not a moral requirement.
The One Thing Provably Fair Does Not Do
I need to be direct here because this misconception costs people money.
Provably fair does not change the house edge.
If a Crash game has a 1% house edge, provably fair guarantees the outcome of each round was honestly generated. It does not guarantee you’ll win, or break even, or lose less than 1% of your wagered volume over the long run. The math that governs the outcomes is the same math that guarantees the casino profits.
Verifying that a losing round was honestly lost doesn’t make you less broke. What it does is guarantee that the reason you lost was randomness, not manipulation. Those are very different things, and only one of them is under your control.
I built FairGameLab because I think transparency is intrinsically valuable — because knowing the game wasn’t rigged is worth knowing. But I’d be lying if I said the lab exists to help you win. It exists to help you know. Please don’t confuse the two.
Responsible Gambling — A Non-Optional Section
If you’re using provably fair casinos, or thinking about it, treat gambling as a form of paid entertainment with an expected cost, not as an income source. The house edge is real, verifiable math confirms it every round, and provably fair changes exactly nothing about it.
- Set a session budget before you play. Stick to it.
- Never chase losses. The math has no memory of what you lost yesterday.
- If gambling is causing stress, financial pressure, or lying to people you love, please reach out — BeGambleAware (UK), 1-800-GAMBLER (US), Gambling Therapy (international).
- Provably fair gambling is still gambling.
Nothing on FairGameLab, nothing in this article, and nothing on any of my sites should be read as encouragement to gamble more or bigger. The calculators exist to serve people who are already gambling and want the ability to verify their outcomes. If that’s not you, that’s fine — please close this tab and go do something else.
Try It Yourself
The whole point of this project is to lower the barrier from “in theory you could verify this” to “you can literally verify this in thirty seconds without installing anything.”
Head to fairgamelab.com, pick the calculator for whichever game you play, and paste your next bet’s server seed (revealed after rotation), client seed, and nonce. You’ll see the outcome computed step by step. If it matches what the casino showed you, that round was honest. If it doesn’t, you have a real problem — and a lot of ammunition to escalate it.
Everything runs in your browser. I don’t see your seeds. I don’t log your bets. I don’t run ads that track you. It’s genuinely a free public utility, built because I got tired of provably fair being a promise nobody could keep in practice.
If you find a game the lab doesn’t cover, or a casino using a non-standard algorithm, let me know via the contact form and I’ll look into adding it. And if the lab saves you thirty minutes and a headache, that’s the entire point.
Verify everything. Trust nothing you can’t check yourself. That’s the whole ethos.
About the author: Zavian Thornell is an iGaming researcher focused on transparency, cryptographic verification, and consumer protection in online gambling. Founder of FairGameLab.com. More writing at zavian-thornell.com. Knowledge Graph: /g/11yhjzfsgm.
Not sponsored: FairGameLab has no casino partnerships, takes no affiliate commissions from operators tested, and shows no ads. The lab is funded by the author.
