Provably Fair explained — and how to verify it yourself

What Provably Fair means

Provably Fair is a method that lets the result of a single game round be checked afterwards — not by a testing body, not by a seal, but by a calculation any player can run with the data from their own account.

It is the one genuine technical difference between a crypto casino and a classic online casino. Everything else — game selection, bonus structure, payout speed — is a matter of the business model. Provably Fair is a matter of cryptography. And it is striking how few players ever use the method, even though it is the reason they supposedly trust the operator.

The problem it solves

In a classic online casino the random number generator runs on the operator's server. The player sees the result, not how it came about. Whether the generator works correctly, they must trust — or trust a testing organisation that checked it at some point.

That check is a sample taken in the past. It says nothing about whether the round you just lost ran correctly. Provably Fair closes exactly that gap: it moves the proof from an instance you must trust to a calculation you can follow yourself.

Server seed, client seed and nonce

The method works with three components.

The server seed is a random string the operator generates. It substantially determines the result — and must therefore not be known to the player before play, or they could calculate the outcome and only bet when they would win.

The client seed is a string assigned to the player. In any soundly implemented system it can be changed freely. That is the most important point of the whole method: because the player sets this value themselves, the operator cannot construct the result in advance towards a particular outcome.

The nonce is a counter that rises by one with each round. It ensures that the same combination of server seed and client seed does not always produce the same result.

Before play, the operator publishes not the server seed itself but its hash value — a checksum from which the original value cannot be back-calculated, but which can later be matched unambiguously. That is the commitment: the operator binds itself to a value without revealing it.

Re-calculating a result step by step

The check has two parts, and both are doable without expert knowledge.

Step one: confirm the server seed. After a seed period ends — usually when the client seed changes — the operator reveals the server seed in plain text. You form the hash of that plain text and compare it with the hash shown before play. If the two match, the server seed was fixed before the round and was not altered afterwards. If they diverge, that is not room for interpretation but proof of manipulation.

Step two: reproduce the result. From server seed, client seed and nonce the system computes, via a cryptographic hash function — usually HMAC with SHA-256 or SHA-512 — a value that is then translated into the game result. In a crash game that is the multiplier; in a dice game the number rolled. Run the same calculation with the same inputs and the same result must come out.

In practice you need no program of your own. Sound operators provide a verifier, and independent checking sites exist where you enter the three values. Anyone wanting more can run the calculation themselves in a few lines of code — the hash functions used are included in every common programming language.

What to watch in the implementation

The term Provably Fair is not protected. It appears on sites that implement the method cleanly, and on sites where only the heading remains of it. These four points tell them apart.

Can the client seed be changed? If not, the method lacks its load-bearing pillar. A fixed client seed means both inputs come from the operator.

Is the server-seed hash shown before the round? If it appears only afterwards, it is worthless — then nothing was committed.

Is there a way to reveal the old server seed? Without revelation, step one cannot be carried out and the check stays theory.

Is the method documented? An operator serious about being checkable describes which hash function is used and how the hash value is translated into a game result. Without that description, step two cannot be followed.

What Provably Fair does not do

Here it matters, because this is where the term is routinely overstretched in marketing.

It does not make the game profitable. Provably Fair proves that a round ran correctly according to the stated rules. Those rules contain the house edge. A demonstrably fair game with a five-percent edge is, over time, exactly as loss-making as an unproven one with five percent — only demonstrably so.

It says nothing about the payout. The proof concerns the game round, not whether the operator then transfers the winnings. The most common complaints about crypto casinos concern not manipulated results but delayed or refused withdrawals. Against that the method does not help.

It does not replace a licence. A mathematical proof for a game round is a different thing from a supervisor you can turn to in a dispute. Both answer different questions. Provably Fair answers "was the round correct"; a licence answers "who do I turn to when something goes wrong".

It almost never applies to slots from external providers. The method works for in-house games — Crash, Dice, Plinko, Mines. Slots from large game studios run on their servers with their random generators and are not part of the Provably Fair system, even when they sit in the same casino.

And in Germany?

Operators with a German licence do not use Provably Fair. They are instead subject to a technical check of their random generators within the licensing procedure and to ongoing supervision by the GGL.

These are two different answers to the same question. Provably Fair moves the check to the player and makes it possible for the single round. German regulation moves it to an authority and, in exchange, makes the operator reachable. Anyone wanting to re-calculate the single round themselves does not get that in the German system — anyone wanting a responsible supervisor and enforceable player-protection rules does not get that in the crypto system. Why no licensed German operator accepts crypto is set out under legality.