trackersino
stale
18+Data only · No predictions · Play responsiblyHow this site works
BetaPublic beta · expect occasional gaps while we stabilise feeds.
BC.Game logo
BC.Game · provably-fair verifier

Crash

Rotate seed ↗

Verify any BC.Game Crash round. The session walks a SHA-256 chain of game hashes; each round XORs through a Bitcoin block hash (v2 salt) into a 52-bit slice, then `(100 - houseEdge) / (1 - X)` gives the crash point. Default salt = the publicly committed Bitcoin block hash; default he = 1%.

Round identifiers
Clear

Frequently asked

Is BC.Game Crash really provably fair?

Yes. BC.Game publishes a cryptographic commitment (the hash of the server seed) for each round BEFORE you bet. Afterwards the server seed is revealed and anyone can recompute the outcome — which is exactly what the verifier above does. If the computed result matches the shown one, the round wasn't manipulated.

How do I verify a BC.Game Crash round?

Paste the revealed server seed into the form above. The verifier re-runs the official math and shows you the exact result, step by step. Everything runs in your browser — your seeds never leave the device.

Where do I find my BC.Game seeds?

On your BC.Game account's fairness / seed page. There you can rotate the server seed: rotating reveals the old one (so you can verify all your previous bets) and commits a fresh hash for the next ones.

Can BC.Game cheat on BC.Game Crash?

Not without getting caught. The server-seed hash is published before the bet, so BC.Game can't change the seed after the fact — any change would produce a different hash than the committed one. That's what makes the game verifiable.