Provably Fair Explained
What a cryptographic check can establish—and what it cannot.
A check, not a guarantee
Some games publish a seed commitment and an algorithm so players can check a completed result. A valid check needs the exact documented scheme and evidence that the commitment was published before betting closed. It does not establish a licence, safe operation, correct payouts or a profitable game.
How It Works
Schemes differ. Some use a committed server seed, a client seed and a round counter. Others include a future blockchain value. You must use the inputs and encoding documented for that game.
- Server Seed: The casino generates a string of data (the server seed) and hashes it. This hashed version is shown to the players before the round begins. Because it is hashed, you cannot know the crash point, but the casino has committed to it. They cannot change it without changing the hash you already see.
- Client Seed: The players (or their browsers) generate their own random string of data (the client seed).
- The Combination: Depending on the game, once betting closes, the pre-committed hash chain is combined with client seeds or future blockchain entropy (such as a future Tron block hash) to generate the final multiplier.
Verifying a Round
First, compare the revealed seed with the earlier commitment using the specified encoding and hash function. Then use the published outcome algorithm, all required inputs and its exact rounding rules. A generic SHA-256 calculation alone cannot verify a multiplier.
Our SHA-256 commitment checker checks only a single hash commitment. It is not an outcome verifier. A match does not prove when the commitment was published or whether a payment was made.
Why This Matters
A crash at 1.00x is not, by itself, evidence of manipulation. A past sequence also cannot predict an independent future result. Where a scheme uses future blockchain data, the final result is not fully known before bets are placed.