Is a provably fair game actually fair? How would a player know? "Provably fair" has become a badge casinos award themselves. Almost every casino claims it. Almost none can prove it. Today we're launching ProvablyFair​.org Certification An independent open-source audit standard for casino built games. Here's why it exists: The casino builds the game. The casino builds the verifier. Then they tell you to use that verifier as proof the game is fair. Of course it matches. That only proves the casino is consistent with itself. It doesn't prove the game is fair. And the gap is real. Every one of these surfaced in the last 6 months. All marketed provably fair, all passing the casino's own verification: -Pay table quietly swapped to lower RTP, the verifier updated to match - A client seed accepted but never used. Decoration - Server seed rotated every bet, nonce stuck at zero, discarding unfavorable seeds - A committed hash swapped after the player locked their seed. Defeats commit-reveal entirely - A verifier running different code from the live game None of these were caught by the casinos own protocols, because a self-verification system can't catch a problem its own author built into both sides. And none of them are things a normal player can realistically detect. So here's how we built it. The method rests on one decision: we rebuild each game from its published rules, not the casino's code. Re-running a casino's own code only proves it's consistent with itself. Rebuilding it independently tests whether the live game does what the casino publicly claims. From that rebuild, for every game we: - Capture and recompute thousands of real bets independently - Run the entire provably fair chain, every cryptographic rule in order - Derive the true RTP from first principles, never trusting the casino's own number - Confirm it across millions of simulated rounds Break even one core rule and the game can be rigged. Pass them all, with the RTP holding up, and it's provably fair. It's binary. It's math, not opinion. That's the standard we think provably fair gaming should be held to. Not a black box audit. Not a trust-us bro PDF. Every audit is public, every verifier is public, every repository is open source. Anyone can clone the code and reproduce the findings themselves. Self-verification proves a casino is consistent with itself. Independent verification proves it's consistent with what it publicly claims. Only the second tells you whether the games are actually fair.

Update: BetFury responded to our investigation and confirmed our core finding. If you played Limbo on BetFury between May 29 and July 24, you may be owed money. Contact support and ask for your session records and what compensation applies to your account. Their response came privately, by email (attached) In their words: "the game's actual parameters did not match the RTP and win probability displayed to users." They attribute it to a configuration error, "not intentional," running May 29 to July 24, and say affected accounts are being adjusted. We can't confirm those dates. Our captures only cover July 15 and 16. The rest of that window comes from BetFury alone. Still not addressed: the "Provably Fair" system that doesn't let players verify how results are generated. It is why a wrong RTP could run for months undetected and why the only evidence for that timeline comes from BetFury. A real provably fair implementation would let players verify both. We said we would publicly update if BetFury responded. This is that update. If you contact them, let us know how it goes.

Provably fair dispute: @xxxmourn's investigation for player Heyri - who asked us to review his case with @Winna @paulwinnacom We've only heard one side, so this is an invitation to Winna. 2 issues need answers. Issue 1: The disputed bets can't be verified, at all. The public bet pages load with no result, no seeds, no fairness details. That page is the whole point of provably fair. Issue 2: The VIP Slide had no lock on the outcome. Winna's own seed data shows it ran the Limbo formula with the safeguards stripped: - a fresh operator seed every bet - no published chain (the seeds connect to nothing) - nonce stuck at 0 - a client seed fixed to a 2023 Bitcoin block the player couldn't change The operator's seed alone decided each result, nothing locked it in beforehand. That's the information we have been given at this stage. To complete the record, we're asking @Winna to provide all 62 rounds, one row per bet: bet ID, time, stake, player's target, result, server seed, the hash shown before the bet. Along with any other relevant information they have so we have both sides of the story. Winna's fairness page confirms every one of these values should exist. Only a pre bet commitment can prove fairness, but this lets us start a fair assessment of the situation - and we'll publish the outcome independently either way.

If you've played @betfury_gaming Limbo and felt like you hit way too many 1.00× instant busts - you weren't imagining it. We measured almost 2× the expected number of 1.00× busts. You can feel it. You can't prove it. Proving it took 240,000 recorded bets. That's why 3rd party testing matters. Full data + scripts in the quoted thread.