Gaming guide

Provably Fair Casino: What It Proves for a License

Provably fair proves a result was not changed after commitment. It does not prove the odds, payouts or licence. How it works and what regulators still need.

By Iryna H., Gaming Licensing. Compliance review by Dariia Y.

Published 10 Nov 2026 Updated 10 Nov 2026 9-min read

ContentsHide contents

Provably fair is a commit-and-reveal scheme: the casino publishes a hash of its secret seed before you bet, then reveals the seed afterwards so you can recompute every result. It proves a result was not changed after the commitment, and nothing more. It does not prove the odds, the payout table, that withdrawals are honoured or that the operator is licensed. For a licence application that means one thing: a provably fair game is still a game, and the regulator will still ask for the lab certificate, the return-to-player maths and the controls around it.

Key takeaways
  • Provably fair = a hashed server seed committed before play, plus your client seed and a nonce, then a reveal and a check.
  • It proves a result was not altered after commitment. It cannot prove the house edge, the payout table or solvency.
  • In the UK, Malta and Anjouan material we reviewed, RNG-driven games sit under independent testing rules, and none treats provably fair as a substitute.
  • For an application, bring both: a published verification spec players can run, and a lab certificate the regulator can read.

How provably fair works, step by step

The scheme is a cryptographic commitment. Three inputs go into every result.

The server seed. A secret string the casino generates. Before you bet, the casino shows you its hash, the commitment. A hash is a fixed-length fingerprint: SHA-256, specified in NIST’s Secure Hash Standard (FIPS 180-4), always produces a 256-bit digest, shown as 64 hexadecimal characters. Once the seed is revealed, anyone can hash it and compare.

The client seed. A string you choose, or the browser generates. It exists so the casino cannot pick a server seed that suits one known set of rolls. The casino committed to its seed before it knew yours.

The nonce. A counter that goes up by one with every bet, so each bet under the same seed pair gets a different result.

The casino then runs a keyed hash. Formats differ by operator, and there is no regulator or standards-body specification for the scheme that we could find. A common pattern is HMAC-SHA256 with the server seed as the key and the client seed plus the nonce as the message. HMAC is defined in RFC 2104 and in NIST’s FIPS 198-1: hash the key combined with one fixed pad and the message, then hash the key combined with a second pad and that result. The output bytes are then converted into a game result such as a dice roll or a card.

When you rotate seeds, the casino reveals the old server seed. You check two things: that it hashes to the commitment you saw earlier, and that it reproduces your recorded results. If both hold, the casino did not swap the seed or the outcomes after seeing your bets.

A worked verification example

The numbers below are an illustration, using a published test vector in place of a real casino seed so you can check it yourself. RFC 4231 gives the HMAC-SHA-256 of the key “Jefe” and the message “what do ya want for nothing?” as 5bdcc146bf60754e6a042426089575c75a003f089d2739839dec58b964ec3843. Treat that as the output of one bet.

Step 1: take the first four bytes. 5b dc c1 46 in hexadecimal is 1,541,194,054 in decimal (91 × 16,777,216 + 220 × 65,536 + 193 × 256 + 70).

Step 2: scale to a fraction. Four bytes can hold 2³² = 4,294,967,296 values. 1,541,194,054 ÷ 4,294,967,296 ≈ 0.3588.

Step 3: map to a roll. Multiply by 10,000 and round down: 3,588, which is a dice roll of 35.88 on a 0.00 to 99.99 scale. The next four bytes, bf 60 75 4e, give 74.75 for a game that needs a second number.

Anyone with the revealed inputs gets the same 35.88. That is the whole proof. The weak points sit outside it, and two show up in this example.

The scaling step. 2³² is not a multiple of 10,000. It equals 10,000 × 429,496 plus a remainder of 7,296. So 7,296 of the 10,000 possible rolls are reached by 429,497 input values and 2,704 by 429,496, a gap of about 0.0002%. Negligible in practice, but it shows where a laboratory looks: GLI-19 requires scaling and mapping algorithms to be unbiased, checked by source code review.

The payout table. Say the game pays 2.00x if the roll is below 49.50. The win chance is 49.50%, so the expected return is 0.495 × 2.00 = 0.99 and the house edge is 1%. A second casino running the same verifiable rolls pays only 1.90x: 0.495 × 1.90 = 0.9405, a 5.95% edge. Over 10,000 bets of 10 units, the first casino expects to keep 1,000 in gross gaming revenue (see what GGR means) and the second 5,950. Every single roll verifies in both. Provably fair checks the roll, not the price.

What provably fair proves, and what it does not

Question Does provably fair answer it?
Was this result changed after I bet? Yes, if the commitment was shown first and you verify independently
Was the server seed hard to guess? No. RFC 2104 says HMAC keys should be random or come from a strong generator, and short keys are discouraged
Is the payout table what is advertised? No. The roll verifies whatever the table is
Is the house edge fair or disclosed? No
Will the casino honour withdrawals? No
Is the operator licensed and audited? No

The seed-quality row matters because the scheme is only as strong as the random source behind the server seed. A seed from a predictable source can be guessed by a determined player before it is revealed. NIST’s SP 800-90A Rev. 1 specifies deterministic random bit generators, the kind of generator a seed should come from.

The verifier page is not the proof. If the only tool that checks results is hosted by the casino, you are trusting the casino to run the check. A real verification publishes the exact formula, the byte-to-number mapping and test vectors, so a third party can build an independent checker.

Provably fair versus a lab-certified RNG

They answer different questions and are not substitutes.

Provably fair Lab-certified RNG
Who checks The player, per bet An independent laboratory, before release
What is checked Result matches the committed seed Randomness, scaling, mapping, payout maths
Source code reviewed No Yes
Covers the odds No Yes, against the published rules
Output a regulator reads None A certificate and test report

GLI-19, a published technical standard that regulators may adopt in whole or in part, shows what the laboratory side looks like. The lab reviews the source code of every algorithm that plays a critical role in the final outcome, including scaling and shuffling. It runs statistical tests on the final outcomes after scaling, evaluated at a 99% confidence level, for distribution and independence between draws. It also requires the RNG to be cryptographically strong and not seeded from a time value alone. It also expects the operator to keep documents such as PAR sheets recording the theoretical return to player. A player cannot verify any of that with a seed and a calculator.

What regulators say

None of the technical standards we reviewed mentions provably fair or treats it as a way around testing. Here is what each says about RNG-driven games.

UK Gambling Commission. RTS 7 requires random number generation and game results to be “acceptably random”, meaning it can be shown to a high degree of confidence, for example through statistical analysis with generally accepted tests. Games must also implement the rules shown to the customer, with outcomes mapped according to the stated probabilities and pay tables. Under the Commission’s testing strategy, licensees must have new products tested by an approved test house and supply the report. External assurance applies mainly to the fairness of RNG-driven products.

Malta Gaming Authority. Components hosting random number generators are listed among a licensee’s essential technical components. When a licensee adds new games whose RNG is not already approved, it must submit a valid relevant RNG certificate with the key technical setup documentation, the updated system specifications and the gaming engine specifications. Compliance audits are only recognised if carried out by auditors the Authority has approved.

Anjouan Gaming. The Authority’s regulatory standards state that random number generators used in gaming products must be certified by an approved independent testing facility, and that licensed operators must ensure all games offered are fair and operate as represented.

We found no provision in these materials that accepts a player-verifiable commitment in place of independent certification. If your target regulator has said otherwise, ask for the clause in writing.

What this means for your licence application

Treat provably fair as a feature of a game that still takes the normal route. Prepare these before you file.

  1. A game inventory. Every game, its provider, and the certificate that covers it. Third-party content brings the supplier’s certificate. Games you built yourself need your own.
  2. A laboratory certificate for in-house games. It should cover the RNG, the scaling and mapping, and the payout maths, with the source code available for review. The lab must be one your regulator recognises.
  3. A verification specification. The exact formula, the seed and nonce handling, the byte-to-result mapping, the scaling method and two or three test vectors. Publish it, and keep it consistent with what the lab tested.
  4. A seed management procedure. How server seeds are generated (from a cryptographically strong source), stored, rotated and revealed, who can access them, and what happens if one is lost or exposed.
  5. Return-to-player documentation and change control. The theoretical RTP per game, the PAR-style documentation behind it, and a rule that payout tables do not change while a game is live except as the rules provide.
  6. The surrounding controls. The AML and source-of-funds programme for crypto deposits is where most crypto files get slowed; our crypto casino licence guide and iGaming AML and KYC primer cover it.

If you supply games rather than run a casino, a separate credential may apply: see the B2B gaming supplier licence. Our iGaming certification service covers the lab route, and what is RNG in iGaming goes deeper on how labs test. To see where the technical file sits in an application, compare the Anjouan requirements and the Malta requirements.

The practical rule

Offer provably fair as a trust feature for players, and certify the game for the regulator. The first answers “was this roll changed?” The second answers “are the odds what you say they are?”, and that is the question a licensing authority, a bank and a payment provider will ask.

A provably fair result does not replace a certified generator: what an RNG is and how it is tested explains what the regulator asks for.

If you are deciding which licence fits a provably fair crypto product and want the technical file mapped to a specific regulator, that is a scoping call on our crypto casino licence service, and it is free.

Frequently asked questions

Select a question to open the answer.

What does provably fair mean?

Provably fair is a commit-and-reveal scheme. The casino publishes a hash of its secret server seed before you bet, you add your own client seed, and after play the casino reveals the server seed so you can recompute every result. It proves a result was not altered after the commitment. It does not prove the odds or payouts are what the casino advertises.

How does provably fair work?

Three inputs produce each result: the casino's server seed (hidden, but committed by its hash), your client seed and a nonce that counts bets. A common design feeds them to HMAC-SHA256 and converts the output bytes into a number. After you rotate the seed the casino reveals the old one, and you check that it hashes to the earlier commitment and reproduces your results.

Is a provably fair casino legit?

Provably fair only shows that individual results were not changed after the fact. A casino can run fair-looking rolls with a poor payout table, refuse withdrawals or operate unlicensed, and the scheme would still verify. Check the licence on the regulator's own register, the published house edge and the independent test certificate as well.

Is provably fair the same as a certified RNG?

No. A certified RNG has been tested by an independent laboratory: source code review, statistical tests on the final outcomes, and checks that the maths matches the published rules. Provably fair is a verification method the player can run. A provably fair game still needs a good random seed and correct payout maths underneath it.

Does a provably fair casino need a license?

Yes. Provably fair is a feature of the game, not a legal status. In the regimes we reviewed (the UK, Malta and Anjouan) a game that produces outcomes still falls under the licensing and testing rules, and none of the published rules we found treats provably fair as a substitute for them.

Can you cheat a provably fair casino?

You cannot change a committed result, but the casino can still cheat elsewhere: a worse payout table than advertised, a server seed that was predictable, or a verifier page that does not match the real calculation. Verify with an independent tool, not the casino's own page, and compare the payout table with the stated return.

Sources

Sources (11)Hide the sources

Related service Crypto casino licence →

This article is for general informational purposes only and is not legal, tax or financial advice. Consult a qualified professional before acting.

Stay ahead of the rules.

Licence fees, rules and deadlines change through the year. Subscribe and we'll email you Vantegris licensing updates.

We use your email to send these updates and note where you signed up. Unsubscribe any time from any email. Privacy policy.

Licence, done right.

300+ operators licensed across 40+ jurisdictions. Book a free consultation.

  • Iryna H.Gaming Licensing
  • Dariia Y.Junior Associate, Crypto Licensing
  • Aleksandra A.Paralegal, Gaming Licensing
  • Maksym D.Paralegal, Banking & Payments
  • Diana K.Paralegal, Compliance & Legal
  • Myroslava V.Business Development Assistant