Every outcome on this site comes from a server seed committed before you bet, your own client seed, and a nonce. Here is the exact scheme, and how to check it yourself.
Before you place a bet, the site shows you the SHA-256 hash of the server seed it will use. It does not show you the seed itself - that would let you compute every outcome in advance - but publishing the hash commits it. A hash cannot be reversed, and no second seed produces the same hash, so the server cannot change its mind later and claim it was always going to use a different one.
You also set a client seed, which you choose and can change whenever you like. Your input is part of every outcome, so even a dishonest server could not pick a server seed that produces a favourable result, because it would have to know your client seed before committing.
Each bet combines the server seed, your client seed and an incrementing nonce, hashes them, and turns the result into whatever the game needs - a number from 0 to 99.99 for Dice, a crash point for Crash, a shuffled six-deck shoe for Blackjack, a bomb layout for Mines.
The nonce is why your thousandth bet on a seed pair is different from your first without anything needing to be re-committed. The whole sequence is deterministic: the same three inputs always produce the same outcome.
When you rotate your seed pair, the old server seed is revealed. At that point you can do two things. First, hash it and check it matches the hash you were shown before you ever bet on it. Second, re-run every bet you made on that pair - same server seed, same client seed, same nonces - and confirm each one produces the outcome you were actually given.
The fairness panel inside each game lists your retired seed pairs and every round each one produced, so the data you need for that check is already there rather than something you have to have logged yourself.
Every game on the site draws its result from a committed seed. Most can be rebuilt on the verifier at /verify, or straight from a bet in the live feed with Verify this bet. The rest are rebuilt where they are played: a slot's Fairness tab, a table's shoe, or the result screen of a live duel.
Slots are checked in their own Fairness tab rather than the verifier because a spin depends on what came before it, like free spins left, sticky wilds or a bought feature. When you rotate your seed there, the server rebuilds every spin you played on the old one and tells you, spin by spin, whether it matches.
| Game | What the seed decides | Where you check it |
|---|---|---|
| Dice | The roll, 0.00 to 99.99 | Verifier |
| Limbo | The multiplier the round reaches | Verifier |
| Crash | The crash point of each shared round | Verifier |
| 990x | The multiplier the round lands on | Verifier |
| Mines | Where every mine sits on the board | Verifier |
| Plinko | Left or right at every peg | Verifier |
| Keno | The numbers drawn | Verifier |
| Roulette | The pocket the ball lands in | Verifier |
| Coinflip | Heads or tails | Verifier |
| Hi-Lo | Every card in the run | Verifier |
| Card Packs | The cards in the pack | Verifier |
| Chicken Cross | Which lanes are safe | Verifier |
| Tower | The safe tiles on every floor | Verifier |
| Moles | Which holes hide a mole | Verifier |
| Goal | Where the keeper stands on every row | Verifier |
| Rock Paper Scissors | The house's throw | Verifier |
| Video Poker | The deal and the draw | Verifier |
| Banker's Deal | What is in every case | Verifier |
| Party Run | The lanes in every round | The game's Fairness panel |
| Blackjack | The shuffled shoe | The table's Fairness panel |
| Baccarat | The shuffled shoe | The table's Fairness panel |
| Live Blackjack, Live War, Live Hi-Lo | The shared shoe or deck | The table's Fairness panel |
| Hold'em | The deck for every hand | The table's Fairness panel |
| Cases | The item you open | The case page's Fairness panel |
| Case Battles | Every item in the battle | The battle page |
| Duel Arena | Every hit, roll and special in the fight | The arena's Fairness panel |
| Staking Grounds duels, dice and Flower Poker | The fight, the roll or the flowers | The result screen in the live room |
| Gielinor Bonanza, Gates of Saradomin | Every symbol and every tumble | The slot's Fairness tab |
| Yak King, Fire Portals, Fruit Party | Every symbol, wild and multiplier | The slot's Fairness tab |
| Wanted: Dead or a Wildy, Le Rogue, Gnome Unit | Every symbol and every feature | The slot's Fairness tab |
| Golden Casket, Yama's Lock, Wildy Run | Every symbol on the reels | The slot's Fairness tab |
| Zaros Rising, Wise Old Fortune, Gielinor Big Catch, Book of Amascut | Every symbol and every feature | The slot's Fairness tab |
| Sports | Nothing: settled on the real match result | No seed to check |
Provably fair proves that outcomes were not tampered with after you committed to them. It says nothing about the house edge, which is a property of the paytable rather than the random number - a game can be perfectly provably fair and still take 30% of every wager.
So use the seeds to check that every result was honest, and read a game's rules and paytable, shown on the game itself, before you decide whether to play it.
Open the verifier at /verify. Rotate your seed pair there to reveal the old server seed, and it checks the hash and rebuilds every round that ran on it. To check one bet, click it in the live feed and press Verify this bet - the seeds and nonce are filled in for you.
No. The server seed is committed as a hash before you bet, and your own client seed is an input to every outcome, so neither side can steer a result after the fact.
No. It proves the result was honest, not that the game is even money. Every game has a published house edge and loses money over a long run - that is what a house edge is.
No. Every outcome and every wallet movement is produced server-side inside the database, so nothing about a result depends on code running on your machine.
FireBet is not affiliated with Jagex Ltd.