Provably Fair CheckerSHA-256 (no HMAC for dice family)

BC.Game Provably Fair Verifier

BC.Game is unusual: its dice-style games hash with plain SHA-256 and no HMAC at all, while games like Mines, Keno, Wheel and Dragon Tower switch to HMAC-SHA256. Mixing those up gives wrong results, so this verifier applies BC.Game's correct construction per game.

10 games at BC.Game

Seed pair

Client seed

Server seed (unhashed)

Nonce

Runs entirely in your browser - your seeds never leave this device.

Roll Result

00.00

0255075100

Provably fair verification lets anyone independently recompute a game's result from its server seed, client seed and nonce - confirming the casino could not have altered the outcome after the bet. Browse all casinos & games

How BC.Game provably fair works

For Dice, Limbo and similar games, BC.Game takes a plain SHA-256 hash of the message serverSeed:clientSeed:nonce - there is no HMAC keying step. The hash is converted to a Stake-style float, and Dice in particular maps it with floor(float * 10001) / 100 to land in the 0.00-100.00 range.

For Mines, Keno, Wheel and Dragon Tower, BC.Game uses HMAC-SHA256 keyed by the server seed over clientSeed:nonce, then runs a two-round number-generation shuffle to place bombs or draw tiles. So the same account uses two different cryptographic constructions depending on the game.

Across both families the server seed is committed before the bet, so results can't be altered after the fact. Rotate your seed pair to reveal the server seed and confirm any past round here.

BC.Game's provably-fair games

BC.Game's seed-pair games - Dice, Limbo, Plinko, Mines, Keno, Wheel and Dragon Tower - are reproducible above with the right per-game hashing. Roulette runs on a shared rotating seed, and a couple of games use a hashed-client-seed variant, so the verifier focuses on the rounds it can reproduce exactly.

How to verify a BC.Game result

1Open the Fairness or Provably Fair section of your BC.Game account.
2Rotate your server seed to reveal the previous seed in unhashed form.
3Copy the server seed, your client seed and the nonce.
4Paste them above and pick the BC.Game game - the tool selects plain SHA-256 or HMAC automatically.

BC.Game provably fair FAQ

What makes BC.Game's algorithm different?⌄

Its dice family uses plain SHA-256 of serverSeed:clientSeed:nonce with no HMAC, while Mines, Keno, Wheel and Dragon Tower use HMAC-SHA256. Verifiers that assume one construction for everything get BC.Game wrong - this tool applies the correct one per game.

Is BC.Game provably fair?⌄

Yes. Every result is bound to a server seed committed before the bet, and this verifier reproduces the seed-pair games from the revealed seed so you can confirm fairness independently.

How is BC.Game Dice calculated?⌄

BC.Game hashes serverSeed:clientSeed:nonce with plain SHA-256, converts it to a float, and applies floor(float * 10001) / 100 to produce the 0.00-100.00 roll. The verifier reproduces that exact value.

Which BC.Game games can I verify here?⌄

Dice, Limbo, Plinko, Mines, Keno, Wheel and Dragon Tower reproduce from your seed pair and nonce. Roulette and a few hashed-client-seed games use a different model and sit outside the per-bet verifier.