Provably fair casinos, checked rather than described
Provably fair is the one claim in this industry that can be checked with arithmetic rather than trust. This section checks it: a verifier that runs in your browser, and a record of which operators’ claims actually reproduce.
How many of the 14 casinos publish a provably fair system?
11 of the 14 operators read publish a fairness system on their own domain, and 5 document it well enough for an outsider to reproduce a result. None of the 11 publishers covers every game it offers. 9 provide a verifier, 2 of which run in the browser. 1 could not be retrieved, so 13 documents were read.
Documents last checked Reviewed by CryptoGuardz Register Desk, editorial desk
14 operators13 documents retrieved11 publish a system5 reproducible by a third partycollected 2026-09-22
Every page that ranks in this search is written by an operator about its own system. That is not a conspiracy, it is an absence: nobody outside the industry has sat down with all fourteen fairness documents on one day and written down what each one actually lets a player do. This is that record. It was collected on 2026-09-22, each answer comes from the operator’s own documentation on its own domain, and every claim below can be checked by opening the URL we cite.
The five figures
What each figure means
11 of 14 publish a fairness system
Stake, Shuffle, Sportsbet.io, BC.GAME, Thunderpick, Gamdom, Flush, Wild.io, Cloudbet, BetFury and Roobet. Two publish nothing that anyone can check: Winz.io and Rakebit. Winz’s provably fair URL is a lobby listing game titles, and its own support answer confirms the lobby is the whole answer. Rakebit’s home page says Fairness is verifiable, not promised
, and no fairness page exists behind it. A sentence asserting the property is marketing copy. It is not a system.
One operator, Jackbit, could not be reached at all, so it is excluded from every denominator on this page rather than counted as publishing nothing. We did not establish that it publishes nothing. We established that we could not retrieve anything.
5 of 14 document it well enough for a third party
Reproducible means someone with no account could recompute a published result from the documentation alone. Stake, Shuffle, Sportsbet.io, BC.GAME and Thunderpick clear that bar. Three more publish a system whose specification stops short of the point where anyone could use it: Wild.io, Cloudbet and BetFury. BetFury names the primitive and nothing else, The provably fair principle is based on SHA256 technology the same as Bitcoin
, and never says what goes into the hash. Cloudbet names SHA3-256 and SHAKE256 and stops before the message construction. Wild.io names no hash function anywhere. Each of those pages is written to be reassuring rather than to be used.
0 of the 11 cover all their games
Not one. Every operator that publishes a system covers its own in-house originals and excludes third-party publisher slots and live dealer tables, which is where most of the money is wagered. Cloudbet’s calculator covers exactly one game, Mines, and the page says so. Thunderpick’s single equation covers Roulette and not even its own Originals suite. Gamdom carries verifiers for fifteen games while its front page advertises over three thousand. A player who verifies a dice roll and concludes the casino is verifiable has verified the smallest room in the building.
2 of the 9 verifiers demonstrably run on your machine
This is the figure the industry does not report, and it is the one that decides whether verification means anything. A verifier that takes your seeds, sends them to the operator and returns a verdict has not verified anything. It has asked the party under suspicion whether it cheated, and printed the answer. The arithmetic must happen somewhere you control, or the result is the operator’s word in a different typeface.
Only Sportsbet.io and Gamdom demonstrably pass that test. Sportsbet.io publishes standalone source and says The verifier below is standalone, it depends only on the Node.js crypto module and reproduces the random draws exactly
. Gamdom’s per-game verifiers are CodeSandbox embeds, which execute in the viewer’s browser but are not hosted by Gamdom. For the other seven, including the two best-documented operators on the register, the documentation never says where the computation happens, so we have recorded nothing rather than a guess. That is a gap in what they publish, and it would cost them one sentence to close.
Wild.io shows the failure mode in its own words: Go to Fairness, then Verify and input: Client Seed, Original Server Seed, Round ID. The tool instantly confirms the outcome.
An instant confirmation from the party being checked is the exact shape of verification that proves nothing. Our verifier runs in your browser instead, and says so because you should be asking.
What a reproduced result proves
It proves the operator applied the algorithm it documents to a seed it committed to before your bet, and that the seed was not swapped afterwards. That is a real guarantee and it is worth having.
It does not prove the house edge is what the operator claims, that the paytable is right, that the games outside the scheme are fair, or that the operator will pay a withdrawal. An operator can run flawlessly verifiable dice and still freeze an account. 11 of these 14 publish a fairness system. Not one publishes a system that covers the games most of their customers play.
What this register does not tell you
Every field here is read from an operator’s own documentation. We have not audited a running game, captured live seed pairs from an account, or tested whether an operator’s production servers do what its help centre says. A documented scheme that is well specified and honestly implemented and a documented scheme that is well specified and quietly ignored look identical from outside.
2 entries are partial because the page would not render: Gamdom and Roobet. Those fields are recorded as not established, never as absent.
Where the record is incomplete
- Jackbit: nothing retrieved. Eight candidate paths and the sitemap returned empty, duplicate or dead responses. Excluded from every denominator.
- Roobet: the fairness page renders and names fourteen games, but the algorithm, the commitment, the rotation and the verifier all sit behind per-game JavaScript tabs that would not open. A rendered attempt returned
You’ve Encountered An Unexpected Error
. Six fields are null as a result. - Gamdom: the prose could not be extracted; a rendering browser returned the page’s configuration payload instead. The verifier fields come from that payload. The commitment fields are not recorded.
- Flush: the page claims to publish its code. We could not render the code block, so reproducibility is recorded as not established rather than credited to a thing we have not seen.
Each of these is a gap in retrieval on one date, not a finding about the operator, and each should be closed by hand before this section is used to rank anybody.
How an operator gets onto this register
The set is the fourteen operators already on the casino register, so nobody is added for having a good fairness page and nobody is dropped for having a bad one. For each, we look for fairness documentation on the operator’s own estate: its domain, its help centre or its docs subdomain. Nothing is taken from an affiliate page, a review site or another operator. Where a page is rendered by JavaScript and will not render for us, the retrieval date is still recorded and the dependent fields are left empty with a note saying which, because an empty field that says why is a record and a guessed field is not.
Commercial relationships on this page
The rest of this section
- Implementations. The register: every operator, what it documents, which games it covers and which it leaves out.
- Verifier. Recompute a bet from its seeds, in your browser, with every intermediate value shown.
- Game sheets. RTP as the studio publishes it, and whether the operator can change it, for the games people search for and every crash game. No demo, no rating.
- Studios. Every studio with 20 or more catalogue games: RTP low, median and high, largest max win.
- The casino register. The same fourteen operators, read against the register of the authority that licensed them.
- Clause watch. What their contracts say they can do with your balance, which a verifiable dice roll does not touch.
- Method. How every value on this site is collected and dated.