BC.Game Crash Verifier
Verify a BC.Game Crash round from its game hash and salt, or a Fast Crash bet from your seeds
Understanding BC.Game Crash
Game Statistics
How It Works
floor(99 / (1 - X)) / 100, never below 1.00x
clientSeed:nonce keyed with your server seed, then floor(98 / (1 - X)) / 100 at the 2% house edge, without the rounding
100% Private
All verification happens entirely in your browser. Your seeds and bet data never leave your device - we don't collect, store, or transmit any information.
How to Verify BC.Game Crash Results
Step 1: Get your round data from BC.Game
Crash and Fast Crash are verified from different data:
- Crash (multiplayer): Open the round from Crash's history and copy its game hash. Every player in that round shares the same crash point, so no personal seeds are involved.
- Salt: The form fills in BC.Game's current salt, the hash of Bitcoin block 967,100 (announced in BC.Game's September 15, 2026 notice), which applies from round #9,614,372. An older round needs the salt of its era (below).
- Fast Crash: Go to Fairness settings on BC.Game and click "Unhash" to reveal the server seed. Copy it with your client seed, and take the nonce from the bet's details.
Salts for older Crash rounds, from BC.Game's reseed announcements and its verification page:
- Up to round #2,561,902: no salt. Clear the Salt field.
- After round #2,561,902: the hash of Bitcoin block 635,380,
0000000000000000(BC.Game's June 2020 announcement).000e3a66df611d69 35b30632f352e493 4c21059696117f28 - After round #5,282,960: the hash of block 758,160,
0000000000000000(BC.Game's October 2022 announcement).00030587dd9ded1f cc5d603652da58de b670319bd2e09445 - Later rounds up to #9,614,371: the hash of block 790,100 (mined in May 2023),
0000000000000000. BC.Game's verification page uses this salt for every round before #9,614,372, but BC.Game has not published the round where it replaced block 758,160's salt, so if an older round does not match, try that one.000301e2801a9a95 98bfb114e574a91a 887f2132f33047e6
Note: For Fast Crash, you can only verify bets made before you unhash the server seed.
Step 2: Enter your data in the form above
Choose the game, then paste your data into the verification form:
- Crash: paste the Game Hash and keep the salt that matches the round
- Fast Crash: enter your Client Seed, the Server Seed (Unhashed) and the Nonce for the bet, and keep the House Edge at 2 unless your bet was settled at another edge
The verifier calculates the crash multiplier using BC.Game's exact HMAC-SHA256 algorithm.
Step 3: Compare the result with your bet
After clicking Verify, you'll see the calculated crash multiplier:
- The result will be the crash multiplier (e.g., 1.98x, 5.42x, etc.)
- Compare this with the crash point shown in your BC.Game bet history
- If they match exactly, the bet was provably fair
If results don't match, check that you picked the right game, then the salt (Crash) or the unhashed server seed and nonce (Fast Crash).
Frequently Asked Questions
What is BC.Game Crash and how does it work?
BC.Game Crash is a multiplayer game where a line rises from 1.00x until it crashes, and everyone in the round shares the same crash point. You cash out before the crash to win your bet times the current multiplier. Each round's crash point comes from its game hash and a published salt, and the formula uses a 1% house edge (99 in the numerator). Fast Crash is a separate single-player game whose crash point comes from your own server seed, client seed and nonce, settled at a 2% house edge (98% RTP).
How does BC.Game calculate the crash multiplier?
For Crash, BC.Game's verification script computes HMAC-SHA256 with the round's game hash (as bytes) as the message and the salt as the key. The first 13 hex characters (52 bits) divided by 2^52 and rounded to 9 significant digits give X, and the crash point is floor(99 / (1 - X)) / 100, never below 1.00x. Fast Crash takes the same 52 bits from HMAC-SHA256 of clientSeed:nonce keyed with your server seed, without the 9-digit rounding, and uses (100 - house edge) in place of 99: floor(98 / (1 - X)) / 100 at BC.Game's 2% edge. Within a seed chain, the previous round's game hash is the SHA-256 of the current one. BC.Game started a new chain at round #9,614,372, so that round does not link back to #9,614,371 this way.
Why doesn't my verification result match?
Common reasons for mismatched results:
- Using hashed server seed: You need the unhashed (revealed) server seed, not the hashed version.
- Wrong nonce: Each bet has a unique nonce - verify you're using the exact nonce for that specific bet.
- Seed pair mismatch: The seeds must be the exact pair that was active when the bet was placed.
- Wrong game or salt: A Crash round needs its game hash and the salt of its era; a Fast Crash bet needs the Fast Crash mode.
Is my bet data safe when using this tool?
Absolutely. All verification happens 100% client-side in your browser using JavaScript. Your seeds, nonces, and bet data never leave your device - we don't collect, store, or transmit any information to our servers. You can even use this tool offline.