PROVABLY FAIR

Do not take our word for it. Verify the round yourself.

ZamZam Games publishes a cryptographic commitment before a result and reveals the secret after the result. This page explains what that means and gives you a verifier that runs entirely in your browser.

Hash before result Secret after result Independent verification

The simple version

Imagine putting the round result inside a locked transparent box. Before bets are resolved, everyone can see the box’s unique fingerprint — the hash — but cannot see what is inside. After the round, the box is opened by publishing the secret and the exact result value.

If anyone changed the secret or result after publishing the fingerprint, the newly calculated hash would be different. A match proves that the revealed data is the same data committed before the outcome was shown.

SECRET+-+ROUND VALUESHA-256HASH

Provably fair proves that committed round data was not changed afterward. It does not guarantee a win, remove variance or eliminate the mathematical house edge.

How to verify one of your rounds

Open the round details

In a game, expand Round verification data. Copy the Round hash before or during the round if you want to observe the commitment live.

Wait for the result

The secret is intentionally hidden while the outcome is unresolved. After settlement, copy the revealed secret and exact result or sequence from the completed round details. For deck and path games, the full committed sequence is required.

Keep formatting exact

Capitalization, slashes, zeroes and decimal places matter. For example, Crash and Dice values use two decimal places: 8.90 is not the same text as 8.9.

Use the verifier

Paste the three values below and press Verify. The tool calculates SHA-256 of secret-value locally and compares it with the published hash.

IN-BROWSER TOOL

Round hash verifier

Your values are processed by your browser and are not submitted to our server.

What should I use as the “round value”?

Different games commit different data. Use the complete value exactly as recorded; do not add spaces or thousands separators. If a completed round does not expose the full committed sequence, keep its hash and secret and request the complete verification value through Support — a visible subset is not sufficient proof.

Roulette

The final roll number, for example 1.

Crash

The final crash multiplier with two decimals, for example 8.96.

Dice & Limbo

The generated roll with two decimals, for example 85.88.

Mines, Tower & Chicken

The full generated route encoded in order as one value. Copy it rather than typing it manually.

Hi-Lo & Coinflip

The complete committed card or flip sequence joined with /.

Blackjack, Baccarat & Dragon Tiger

The full committed deck order joined with /, not only the cards visible in the final hand.

Sic Bo

The three committed dice joined with /, for example 3/5/1.

Keno

The complete drawn-number sequence joined with /.

European Roulette

The pocket the ball landed in, 0 to 36, for example 17.

Plinko

The full left/right path value used to produce the final bucket.

Case Opening

The winning ticket in the case's 100 000-ticket table, for example 41233. Walk the published drop table to that ticket to find the skin.

Wheel

The drawn segment index (0-9), for example 4.

Rock Paper Scissors

The house's committed move, for example rock.

Aviamasters

The complete item sequence followed by the landing roll: b1/x2/bomb-4821. Its hash is published before the wager; the secret and exact value are revealed after settlement.

Slots

Every raw reel roll, zero-padded to four digits and concatenated in resolution order. Bonus-spin rolls are appended when a bonus occurs.

Sugar Bonanza

The round seed. Every grid, tumble and multiplier bomb — including a full free-spin round — is derived from it by hash chaining, so the whole round replays deterministically from this one value.

Sun of Zam

The round seed. The base grid, every coin face, and every respin of the hold & win feature are derived from it by hash chaining — nothing about the round is stored, because all of it replays from this one value.

Gem Megaways

The round seed. The six reel heights, every symbol, every cascade refill and every free spin are derived from it by hash chaining, in a fixed and published order.

Book of Zam

The round seed. Every grid and — crucially — the expanding symbol drawn for the free spins are derived from it by hash chaining, so which symbol you were given is verifiable after the fact and could not have been chosen once the round was underway.

Understanding the answer

Hash matches

The revealed secret and round value reproduce the commitment published for that round. The committed data was not changed after the original hash was created.

Hash does not match

First check copied spaces, decimal zeroes, letter case and sequence separators. Try copying every field again. A formatting difference is the most common cause.

What if it still does not match?

Do not place another bet in the affected game until you understand the discrepancy.
Take a screenshot of the hash, secret, value, game name and approximate round time.
Open one Support ticket and include the calculated hash displayed by this verifier.
Do not post secrets, account data or transaction details in public chat.

Technical reference for advanced users

The platform calculates:

SHA256(secret + "-" + exactRoundValue)

You can reproduce it independently in a terminal:

printf %s 'YOUR_SECRET-YOUR_VALUE' | shasum -a 256

Or in PHP:

<?php echo hash('sha256', $secret . '-' . $value); ?>

Never add a newline to the payload. The browser verifier above uses UTF-8 and compares lowercase hexadecimal SHA-256 strings.