What hashing algorithm do most crash games use?

SHA-256 is the industry standard, the same algorithm used in Bitcoin's own proof-of-work. It's a one-way function: easy to compute forward, computationally infeasible to reverse.

Can a casino cheat even with Provably Fair enabled?

Not on the specific round's crash-point calculation, if implemented correctly — that's exactly what the pre-committed hash prevents. A casino could still cheat elsewhere (e.g. never actually crediting winnings), which is why licensing and reputation checks still matter alongside Provably Fair.

What's a client seed and why does it matter?

It's an input you control (some platforms let you set it manually, others generate one for you) that gets combined with the server seed. Its purpose is ensuring you have some influence over the outcome's inputs, so the casino's server seed alone can't fully predetermine every round in a way that only benefits the house.

Is a game without Provably Fair automatically untrustworthy?

Not automatically — some licensed, audited RNG games use certified random-number generators verified by independent testing labs (like eCOGRA or iTech Labs) instead of Provably Fair hashing, which is a different but also legitimate verification model. The concern is a game with neither Provably Fair nor third-party RNG certification.

How do I find a round's server seed after it ends?

Most crash-game platforms show this in a 'round history' or 'fairness' panel accessible from your bet history or the game interface itself — the exact location varies by casino, but reputable ones make it easy to find, not buried.

Rehberler

Provably Fair, Explained

The cryptographic method that lets you verify a crash-game round wasn't altered after the fact — not just trust that it wasn't.

Yazan Elena Rhodes · 2026-08-14

Before Provably Fair systems existed, playing an online crash game meant trusting the operator's word that the crash point for each round was generated fairly and not adjusted based on who was betting or how much. Provably Fair replaces that trust requirement with math you can check yourself.

The problem Provably Fair solves

The core risk in any random-outcome game is that whoever generates the randomness could bias it — deliberately crashing a round early once a large bet is placed, for instance. A casino simply saying "we don't do that" isn't verifiable. Provably Fair fixes this by making the operator commit to the round's outcome before betting closes, in a way that can be checked after the round without letting them change it in between.

How the hashing actually works

The standard implementation uses two inputs: a server seed, generated by the casino and kept hidden until after the round, and a client seed, which you can see and sometimes influence. Before the round starts, the casino publishes the SHA-256 hash of the server seed — not the seed itself, just its cryptographic fingerprint. A hash is one-way: you can't reverse it to find the original seed, but if you're later given the seed, you can hash it yourself and confirm it matches exactly.

After the round completes, the casino reveals the actual server seed. You combine it with the client seed and the round number (often called a nonce), run it through the agreed algorithm, and the result determines the crash point using a public formula. If your calculation matches both the pre-committed hash and the round's actual crash point, the round was not tampered with — the casino couldn't have changed the seed after seeing your bet, because they'd already published its hash beforehand.

Verifying a round yourself

Practically, verification means: (1) note the round's server seed hash shown before betting closes, (2) after the round, get the revealed server seed, client seed, and nonce from the casino's round history, (3) compute SHA-256(server seed) yourself and confirm it matches the pre-round hash exactly, (4) run the revealed values through the game's published crash-point formula and confirm it matches what actually happened on screen. Our Provably Fair verifier tool automates steps 3 and 4 so you can paste in the values and check instantly.

What Provably Fair doesn't guarantee

Provably Fair verifies that a specific round's outcome wasn't altered after commitment — it does not verify that the casino's overall software, payout processing, or account handling is trustworthy. A platform could theoretically implement Provably Fair correctly for game rounds while still having unrelated problems elsewhere (slow withdrawals, unclear terms, an unlicensed operation). Treat Provably Fair as one strong signal among several, not a complete trust guarantee on its own — pair it with checking licensing, covered in our security guide.