The Verification Lab
Editorial policy
How The Verification Lab researches, computes, checks and corrects every guide on this site.
The lab rules
| Rule | What it means in practice |
|---|---|
| Answer first | The first two sentences of a guide answer the question in the title. |
| Real computations | Every hash, HMAC and derived number on the site is produced by running the code, then pasted — never typed by hand. |
| Re-run before publishing | A script recomputes every example and the browser verifier is checked against Python output. |
| Label examples | Seeds and example games are made up for explanation and labelled as such. |
| Say what a proof doesn't show | Each guide is clear about the limits of a fairness proof, not just its strengths. |
| No rankings | We don't rate, rank or recommend operators. |
| No profit claims | We never present gambling as a way to make money. |
Methods differ
Provably fair schemes are not one standard. Where we show a method, we say it's one common convention and tell you to compare it with the documentation of the game you're checking.
Corrections
If you find an error, email support@provablyfairsites.com. We fix confirmed errors promptly and add an "Updated" date to the guide.
Commercial influence
Commercial relationships, if any, are described on our disclosure page and have no say over what a guide concludes.