The game · the hash, the seed, the check
Provably fair, checked rather than believed
«Provably fair» is not a promise, it is an offer: the operator commits to a number before the round and shows you the number afterwards, and you check that the two match. Here is what the check proves, what it does not, and how to run it.
This is an independent guide. It is not BC.Game, it is not operated by or affiliated with BC.Game, and it does not take deposits or run accounts.
Most casino games ask for trust. A provably fair crash game replaces part of that trust with arithmetic you can run yourself — and it is worth knowing exactly which part.
The three ingredients
The server seed. A secret string the operator generates. It is the source of the results.
The hash of the server seed. A one-way fingerprint of that secret, published before you play. Publishing it commits the operator: change the seed later and the fingerprint no longer matches.
Your client seed and the nonce. A string you control and a counter that increases by one each round. They are mixed with the server seed so that the operator cannot know in advance which result lands on which of your bets.
The check, step by step
- Find the current hash in the game's fairness panel, before you play.
Copy it somewhere outside the site.
- Set your own client seed. Any string. The point is that it is yours.
- Play some rounds. The nonce climbs with each one.
- Rotate the seed. When you change the client seed or ask for a new server
seed, the old server seed is revealed.
- Hash the revealed seed with SHA-256 and compare it to the fingerprint
you copied in step 1. They must be identical.
- Reproduce the results. Feed the revealed server seed, your client seed
and each nonce into the published formula and check that it returns the multipliers you actually saw.
Step 5 is the commitment check and step 6 is the result check. Doing only one of them is half a verification — and step 5 is the half that people skip, because it has to be done before you play, not after you lose.
What it proves and what it does not
| It proves | It does not prove |
|---|---|
| This round came from the pre-committed seed | That the odds are good |
| Your client seed was in the mix | That the operator will pay you |
| The result was not edited after the fact | That the published house edge is what is used |
| The sequence is reproducible | Anything about withdrawal limits or bonus terms |
The right-hand column is the reason this site has other pages. A perfectly verifiable round can sit behind a bonus balance that blocks a withdrawal, see bonus and wagering, or a payout limit that turns a big multiplier into instalments, see deposits and withdrawals.
The hash chain
Some crash implementations do not draw each round independently at play time. They generate the whole chain of results in advance, then walk it backwards: each round's seed hashes to the previous one, so the entire history can be checked from a single published anchor. It is a stronger commitment, because the operator cannot pick a seed after seeing your bets — the chain was fixed before anyone played.
Which construction a given game uses is stated in its own fairness documentation, and that is where to read it. This site has not been able to open the operator's documentation from where it works, so the specifics of their implementation — including the house-edge figure used elsewhere on this site — are theirs, quoted, and not verified by us.
The honest limit
Verification is retrospective. It tells you that the rounds you already played were clean. It cannot tell you that the next thousand will be, that the operator is solvent, or that a withdrawal will clear. Those are questions about a company, not about a hash.
That is also why the useful version of «is it rigged?» is a narrow one: the round is resolved before the curve moves, and it is checkable, as described on how the round works. What is not checkable — and never was — is the marketing built on top of it, which is the subject of predictors and signals.
Where a figure on this site is the operator's own rather than something we could confirm, it is attributed — the practice, and the funding behind it, is set out on about this site.
The rest of the picture is on bc game crash game.