🔐 Provably Fair Verifier

Enter the server seed and hash revealed at the end of a tournament to independently verify that every crash point was predetermined and not manipulated.

Enter Tournament Data

Server Seed (revealed after tournament ends) SHA-256 Hash (shown before tournament started) Number of Rounds (any number up to 500 — see note below)

💡 About the round count: Every crash point is locked in the moment the seed is created — the number of rounds you enter here only controls how many are shown in the table below. It does not affect the hash check or the crash points themselves. You can enter more rounds than the tournament actually played to see what would have come up if it had continued.

🔎 What is Provably Fair?

Provably Fair is a system that lets you independently verify that every crash point in a tournament was determined before the game started — and that results were never changed or manipulated after the fact.

Every tournament gets its own unique seed. Each tournament's results are completely independent of all others, and there is no way for us to know what crash points will occur when the seed is created.

📖 How It Works — Step by Step

Step 1 — Before the tournament starts
The server secretly generates a random string called a Server Seed — a long unique string of characters generated fresh for that tournament. Nobody sees this yet. The server then runs it through a one-way cryptographic function called SHA-256 to produce a Hash — think of it like a fingerprint of the seed. That hash is published publicly before a single round is played.

Since SHA-256 is a one-way function, it is mathematically impossible to reverse-engineer the seed from the hash — so knowing the hash in advance tells you nothing about the actual crash points that will happen.

Step 2 — During the tournament
Each round's crash point is calculated using HMAC-SHA256(serverSeed, roundNumber) — a cryptographic function combining the Server Seed with the round number. Round 1 uses seed + "1", Round 2 uses seed + "2", and so on. This means all crash points were locked in the moment the seed was created, before anyone registered or placed a bet.

Step 3 — After the tournament ends
The Server Seed is revealed. You can now verify two things:

1. Run SHA-256(serverSeed) and confirm it matches the hash published before the tournament started — proving the seed was never changed.

2. Recalculate every round's crash point using HMAC-SHA256(serverSeed, roundNumber) and confirm they match exactly what happened in the game.

There is no way for us to change the crash points after the hash has been published. The math is open, standardised, and verifiable by anyone using the tool above or any SHA-256 / HMAC-SHA256 calculator on the internet.