18+ only. Gambling can be addictive. Play responsibly.

Get help
Velvet Odds Español

HomeProvably fair checker

Ad Affiliate disclosure: we earn a commission if you sign up through our links, at no cost to you. It never changes our scores. How we make money.

Provably fair checker

By The editorial team · Updated 31 October 2026 · Free, no sign-up, nothing sent anywhere

Paste the seeds from a finished round. This page checks that the revealed server seed matches the hash the casino showed you before you bet, then recomputes the result with the casino's own published formula. It runs in your browser and the page's security policy stops it from sending what you paste anywhere.

Offers hidden here. Casino offers and links are shown only to visitors in the places where the casinos we list accept players. They are not shown here. Our reviews and guides stay readable.

Nothing you paste leaves your browser.

How provably fair works

  1. Before you bet, the casino picks a secret server seed and shows you only its SHA-256 hash. A hash is a fingerprint: it fixes the seed without revealing it.
  2. You add a client seed (set your own, do not keep the default) and every bet gets a nonce, a counter that goes up by one.
  3. The result comes from HMAC-SHA256 of the server seed with your client seed and nonce, turned into a game result by a published formula.
  4. When you rotate the seed pair, the casino reveals the old server seed. Hash it yourself: if it matches the hash you saved, the casino could not have swapped the seed after seeing your bets, and you can recompute every round from it.

Crash games work a little differently: every round shares one public game hash taken from a chain of hashes the casino fixed in advance, mixed with a salt such as a Bitcoin block hash nobody knew when the chain was published. The checker covers both.

What this checker proves, and what it cannot

A match proves one thing: that round was not changed after you bet. It does not prove any of these:

Two habits make the check worth something: save the hashed server seed before you play, and set your own client seed. A seed hash you only see after the round proves nothing.

Which casinos and games it supports

Only formulas a casino publishes itself, copied from its own page and tested against its own published examples where it has any. Updated 31 October 2026.

Casino and gamesFormulaSourceTested against
Stake
Dice, Limbo, Roulette, raw floats
bytes = HMAC_SHA256(server seed, client seed:nonce:0); float = 4 bytes / 256^1..4; dice = float x 10001 / 100; limbo = max(1, floor(0.99 / float x 100) / 100); roulette = floor(float x 37) stake.com/provably-fair/implementation (Wayback snapshot 26 Sep 2026)
stake.com/provably-fair/conversions (Wayback snapshot 14 Oct 2025)
stake.com/provably-fair/game-events (Wayback snapshot 19 Jul 2025)
Stake publishes no example seeds. Its seed to float code is the same as Shuffle's, and that step matches Shuffle's published example. The dice, limbo and roulette steps are one line each, copied from Stake's page. stake.com is blocked from our network, so we read it through the Wayback Machine.
Stake
Crash and Slide
h = HMAC_SHA256(key = round hash, message = salt); n = first 8 hex characters; crash = max(1, 2^32 / (n + 1) x 0.99), Slide x 0.98. Salt: Bitcoin block 584,500 (Crash), 631,111 (Slide). Chain: SHA-256 of the previous hash as hex text Stake Crash seeding thread, BitcoinTalk, 8 Jul 2019 (read 31 Oct 2026)
Stake Slide seeding thread, BitcoinTalk, 20 May 2020 (read 31 Oct 2026)
Not tested against a round: Stake publishes the last hash of each chain but no round with its result. Stake's code does not round; we show 2 decimals cut, plus the exact value.
Shuffle
Dice, Limbo, raw floats
same bytes and floats as Stake; dice = floor(float x 10001) / 100; limbo = 0.99 x 2^24 / (2^24 x float + 1), cut to 2 decimals help.shuffle.com, Provably Fair: Implementation (article 9286058) (read 31 Oct 2026)
help.shuffle.com, Provably Fair: Game Events (article 9286069) (read 31 Oct 2026)
Shuffle's own example (server seed def, client seed abc, nonce 1): the floats, dice 43.05, limbo 2.29 and the blackjack cards all match. Shuffle's printed raw limbo value (2.298905) does not follow from its own formula (2.2994); the shown 2.29 does.
BC.Game
Limbo
h = HMAC_SHA256(server seed, client seed:nonce); r = first 13 hex characters; X = r / 2^52; limbo = max(1, floor(99 / (1 - X)) / 100) BC.Game verifier, GitHub bcgame-project/verify, limbo.html (read 31 Oct 2026) Not tested against a round: BC.Game publishes no example seeds with a result.
BC.Game
Crash, seed chain from 6 Sep 2026 (game 9,614,372 on)
h = HMAC_SHA256(key = salt as text, message = round hash as bytes); r = first 13 hex characters; X = r / 2^52, to 9 digits; crash = max(1, floor(99 / (1 - X)) / 100). Salt: Bitcoin block 967,100. Chain: SHA-256 of the previous hash as hex text BC.Game verifier, GitHub bcgame-project/verify, crash.html (read 31 Oct 2026)
BC.Game Crash fairness notice, BitcoinTalk, Sep 2026 (read 31 Oct 2026)
Not tested against a round: BC.Game publishes round 1's hash but no round with its result. Older rounds use a salt BC.Game's verifier names but we found no BC.Game post announcing, so we do not offer it.
bustabit
Crash, 2025 seed chain (4th seeding event)
h = HMAC_SHA256(key = salt as text, message = round hash as bytes); r = first 13 hex characters; X = r / 2^52; crash = max(1, floor(99 / (1 - X)) / 100). Salt: Bitcoin block 917,000. Chain: SHA-256 of the previous hash as bytes bustabit 4th seeding event, BitcoinTalk, 27 Sep 2025 (read 31 Oct 2026)
bustabit verifier, GitHub bustabit/verifier (read 31 Oct 2026)
Not tested against a round: bustabit publishes no round hash with its result.

Not covered, and why

Found a casino whose published method we should add, or a result that does not match? Write to editor@velvetodds.com with the casino's fairness page and one round's seeds.

Read more

The long version, with the step-by-step maths and the red flags on a fairness page: Provably fair explained. How the house edge works: House edge and RTP explained.