How a provably fair round is checked by hand, and what the check cannot tell you

A provably fair round is a promise made in advance and testable afterwards, and the whole of it fits in two strings. One is published before the bet: a hash, 64 hexadecimal characters standing for 256 bits. The other is published after: the value that hash was made from. If hashing the second produces the first, the result of that round was decided before anybody saw the stake.

What are the four values, and what does each one do?

The server seed is the casino's secret for a series of rounds. It is generated by the house, kept hidden while the series runs, and revealed when the series ends.

The hashed server seed is the commitment. It is shown before the first bet, and because a hash cannot be run backwards, it gives away nothing about the seed while binding the house to it. Change the seed later and the hash no longer matches.

The client seed is the player's contribution. It is either supplied by the player or generated in the browser and editable, and its only job is to stop the house from choosing a seed pair whose outcomes it has already worked out.

The nonce is the counter. It starts at zero or one and increases by one every round, so that a single pair of seeds produces a different result each time without either side changing anything.

Together they make the outcome reproducible: the same four values always give the same result, and none of them can be altered after the fact without breaking the commitment.

How is the check performed, step by step?

Four steps, and the first is the only one that has to happen before the money moves.

First, copy the hashed server seed exactly as it is shown, before placing a bet, and keep it somewhere the site cannot edit. This is the entire foundation of the check. A commitment read after the round, off the same screen that produced the round, proves nothing at all.

Second, record the client seed in force and the nonce of the round you care about. Most implementations display both beside the bet in a history panel.

Third, rotate the seed. Changing the client seed, or asking for a new server seed, ends the series and causes the old server seed to be revealed. Nothing is verifiable until this happens, which is why a check is always retrospective.

Fourth, hash the revealed server seed with SHA-256 and compare the 64 characters that come out with the 64 you copied at the start. Identical means the house held to its commitment for every round in that series. Different, by a single character, means it did not.

A fifth step exists for anyone who wants the outcome itself rather than the commitment: the operator publishes the formula that turns the seeds and the nonce into a number, usually a keyed hash of the client seed and nonce under the server seed, with the leading hexadecimal characters read off as a value in the game's range. That formula is the operator's to publish, it differs between casinos and between games, and it can only be repeated where it has been written down.

What does the check never tell you?

Four things, and each one is the subject of a different page on this site.

It says nothing about the house edge. A round can be perfectly verifiable and still be priced so that the house keeps its margin, because the margin lives in the paytable rather than in the randomness.

It says nothing about whether a payout is approved. Verification concerns the result of a bet, not the fate of a balance, and the clauses that decide the second are the identity right and the withdrawal ceiling rather than a hash. What those say on this brand is set apart in the four questions behind is it legit.

It says nothing about the games it does not cover. Studio titles from suppliers such as NetEnt, whose supply conditions are reprinted in clause 4 of this operator's general terms dated 2 May 2022, run on the studio's own generator and are audited by testing laboratories. A provably fair check does not reach them, which at a site claiming more than 7,000 titles leaves it covering only the in-house originals, a share this operator does not publish. The four claimed counts and the seven studios actually named are set out in what a count is worth without a list.

And it says nothing about the operator's identity or solvency. The mathematics is indifferent to who is on the other side of the contract.

What is on record for this operator, and what is missing?

The claim is on record. The operator's own homepage copy, stored on 27 January 2026 and read here on 2 September 2026, describes the brand as a provably fair casino holding the Curacao eGaming licence.

Two things are worth noticing about that sentence rather than one. It is marketing prose, unnumbered and outside any contract. And the licence it names is not the licence the operator's own later footer names: the footer text served on 30 August 2026 records a Curacao Gaming Authority number issued on 15 May 2026 to a different company from the one in the 2022 terms. A fairness claim travelling with a superseded licence line is a claim whose date matters as much as its content.

The document that would settle it is missing. The fairness and RNG route on the operator's domain exists and returns HTTP 200 in stored copies, but every one of those copies is an application shell whose text is fetched at runtime from a content interface that answered our capture machine with HTTP 403 and a Cloudflare challenge header on 2 September 2026. So no seed policy, no formula, no verification page could be read.

Empty is printed as empty here, and never as no.

How many of the ten operators here publish the mechanism at all?

Four of the ten rows are recorded as publishing a provably fair check: Metaspins, Rainbet, Bitsler and Wolf.bet, all from readings dated 26 August 2026. Those records describe what each operator publishes about the mechanism. Not one of them describes a round verified by this desk, because verifying a round takes an account, a stake and a seed rotation, and this desk holds no account with any operator named on this site.

Which is the boundary this page ends on, and it is a real one. The four-step check above is exactly the sort of thing a reader can do and a document-reading desk cannot. What can be done from documents is telling you which values to demand, in what order, and what the answer will and will not have proved once you have it.

How every field on this site is filled, dated, and left blank when a document would not open is set out in the method.