1xBet
Cryptographic verification

Provably fair, fully transparent

Every game outcome on 1xBet is pre-determined cryptographically before each round starts. Neither 1xBet nor the player can alter the result after bets are placed.

Interactive SHA-256 Outcome Verifier

Input any round’s server seed, your client seed, and the round nonce to verify the mathematical outcome independently.

CALCULATION PROVEN ACCURATE
Verified Multiplier Outcome: 4.85x

HMAC_SHA256(server_seed, client_seed + ":" + nonce) verified against blockchain hash.

1

1. Server Seed Generation

The server generates a secret cryptographic seed and provides the SHA-256 hash to you before any bets are placed.

2

2. Player Client Seed

Your browser contributes an independent client seed that you can customize anytime to influence the outcome.

3

3. Immutable Result

The combination is hashed deterministically. After the round, the raw server seed is revealed for instant proof.

Do it yourself

Verifying a round by hand

“We use SHA-256” is a claim, not evidence. These four steps are how you check it without trusting anything on this page.

Takes about five minutes the first time. Once you have done it on one round, the same method works on every game we run.

  1. 01

    Copy the hash before you bet

    Open Game → Fairness in any 1xOriginals title. The panel shows the hashed server seed for the round that is about to start. Copy it somewhere outside the site — a notes app is fine. The point is to hold a copy we cannot edit later.

  2. 02

    Set your own client seed

    The same panel lets you replace the client seed with any string you like. Type something only you would pick. Because the result is derived from both seeds combined, we cannot know the outcome in advance without knowing your half — and you chose it after we committed to ours.

  3. 03

    Play the round, then reveal the seed

    When the round settles, the unhashed server seed appears in the history. Take it and run it through any SHA-256 tool. In a terminal that is one line:

    echo -n "<revealed-server-seed>" | shasum -a 256

    If the output matches the hash you copied in step one, the seed existed before you bet and was never swapped. If it does not match, something is wrong and we would want to hear about it immediately.

  4. 04

    Reproduce the result yourself

    The round outcome is HMAC_SHA256(server_seed, client_seed:nonce), where the nonce is the round number. Take the first 13 hex characters of that digest, read them as an integer, and divide by 252 to get a number between 0 and 1. Feed it through the crash formula and you have the multiplier we paid out.

    None of this requires our verifier. That is the entire idea — the maths belongs to you, not to us.

What this does not prove. Provably fair confirms a specific round was not tampered with. It says nothing about the house edge, which is disclosed separately in each game’s RTP and is working against you whether or not the maths checks out. Both things are true at once.