How we verify platforms

The rule

A platform appears in the verifier only after two things are true. First, the platform publishes its provably fair algorithm: the hash function, the exact way seeds and nonce are combined, and how the hash becomes a result. Second, our implementation of that published algorithm reproduces at least one real, documented result exactly. If either is missing, the platform is not selectable, no matter how popular it is. A wrong verifier is worse than no verifier.

What the labels mean

• Verified.Our implementation reproduced a real result: either a worked example from the operator's own fairness page, or a cross-check against the operator's own verifier with live seeds.
• Implemented, awaiting confirmation. The operator publishes a formula and we implemented it exactly as written, but no real result has confirmed it yet. Not selectable in the tool.
• Blocked. The operator claims provably fair but does not publish enough to reproduce a result. We name what is missing.
• Cannot be independently verified. The site publishes no verifiable algorithm at all. We say so plainly.

Right now 9 of the 17 platforms we cover have at least one verified game. Every platform page shows its exact per-game status.

Why calculations run on your device

The whole point of independent verification is that no operator, and no middleman including us, can influence the result. So the verifier runs entirely in your browser using its built-in Web Crypto API. When you click verify, zero network requests fire. You can confirm this yourself: open DevTools, switch to the Network tab, and click the button.

What verification cannot prove

A passing check proves one thing: the outcome came from the seeds and nonce that were fixed before you played. It does not prove that a withdrawal will go through, or that the wider site is trustworthy as a business. We repeat this everywhere on purpose. Treating a passing hash check as an endorsement is exactly the mistake this site exists to prevent.

Sources and corrections

Every parameter we implement is taken from the operator's own published fairness page, linked from the platform's page here. When an operator's documentation contradicts its own code, we follow the code and note the discrepancy. If you find an error, we want it: send the seeds, the expected result, and the platform, and we will re-test and correct publicly.