Provably Fair Seed Verifier & Win Audit Lab

Verify cryptographic seed pairs (HMAC-SHA256), replay verifiable Crash and Dice multiplier rounds, and calculate the mathematical reality behind sponsored "streamer wins" versus true house edge.

Cryptographic Audit Result

Verified locally via WebCrypto
VERIFIED MATCH
The computed outcome mathematically matches the reported round claim.
DERIVED OUTCOME
14.82x
RAW INT (32-BIT)
288,419,081
FLOAT [0.0 - 1.0)
0.067153
THEORETICAL ODDS
6.68% (1 in 15)
ALGORITHM PURITY
Deterministic
HMAC-SHA256 Derivation Breakdown
// Input string payload (ClientSeed:Nonce:Round):
player_proof_seed_994:42

// Computed HMAC-SHA256 (ServerSeed as Key):
42f9b8c0a89d14ec7a54e9...

// First 8 hex bytes extracted: 42f9b8c0Integer: 1123662016
// Multiplier Formula: Math.floor((100 - house_edge) / (1 - float)) / 100
Crash Flight Trajectory to 14.82x Round Replay
Verification complete. Seed pair is mathematically valid.

Why Replay Verification Matters

Promotional tweets and Discord bots frequently boast about "real users winning 500x or 10,000x." The only way to prove a round was not manufactured by an administrator or streamer balance is provable fairness.

Before you place a bet, the casino commits to a cryptographic hash of their Server Seed. Because you provide the Client Seed, neither party can predict or manipulate the outcome after the bet is made without breaking SHA-256 collision resistance.

The "Streamer Slop" Mathematical Trick

Why do casino partners always look like they are winning? Streamer house balance and survivorship bias:

  • Streamers are given $50,000+ demo or replenished balances and spin hundreds of times on high-variance games.
  • Hitting a 500x multiplier has a ~0.2% probability. A normal player with a $500 bankroll busts 94% of the time before hitting it.
  • The 1 hit is clipped and posted to social media as "real wins real people hit," hiding the thousands of preceding wipeouts.
How is the Crash multiplier calculated from HMAC-SHA256?

The server seed and client seed + nonce are hashed using HMAC-SHA256. The first 52 bits (or first 8 hex characters / 4 bytes) are converted to an integer and divided by 2^32 or 2^52 to yield a uniform floating-point number X between 0 and 1. If X lands in the casino's house edge window (e.g. 1 in 101 for 1%), the round instant-busts at 1.00x. Otherwise, the multiplier is derived as floor((100 - house_edge) / (1 - X)) / 100.

What is the difference between a pre-commitment and a revealed seed?

Prior to gameplay, the server displays SHA256(ServerSeed). You can record this hash. After the game or when rotating seeds, the casino reveals the unhashed plaintext ServerSeed. If hashing that plaintext reproduces the exact pre-commitment, you have mathematical certainty the house did not alter the result mid-flight.

Enjoy this tool? Build your own with Super