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.

The strengths of $SHFL: - considerable real value being delivered to the token (more than most cryptocurrencies can claim) - strong, crypto-native team The weaknesses of $SHFL: - one centralised source of value - total supply too high, too much locked in treasury - generally low confidence in gamblefi from the market This year is about converting these weaknesses to strengths; I have a feeling that solving the first two leads to the third following suit. More to come.

does a public founder actually make you trust a casino more? crypto casino founders used to be anonymous no interviews no socials just offshore companies and mystery operators now they’re building personal brands, doing podcasts, flexing online it’s not random in an industry with weak licenses, identical games and low trust a visible founder suddenly matters

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

A player recently pointed out that while our provably fair system showed your hashed server seed, you couldn't easily verify the unhashed seed after rotating. To be clear, the cryptography behind every bet has always been sound. Your outcomes were determined by pre-committed, hashed server seeds before any wager was placed. That never changed. For anyone wanting extra peace of mind, our team can also verify any bets placed prior to this update, just reach out. But provably fair means you should be able to prove it, not just take our word for it. Here's what we've shipped: - Full seed history is now visible - Unhashed server seeds from past rotations are verifiable - You can hash any previous server seed (SHA-256) and match it against the hash you were shown, proving nothing was altered This is exactly how it should work. Community asks, we respond.

We conducted an independent technical audit of Winna​.com's Plinko game following their March 10 incident report. Our analysis shows that for nearly 3 months, players were playing Plinko on worse odds than the site publicly stated. If you played Winna Plinko between Dec 17 and March 10, your bets were placed under those probabilities. Here’s what the code shows. 🧵

After year of trying to force different narratives, Bloomberg settled on smugly claiming that our stake games are rigged in favor of drake and adin based on a sample size of.... 0.1 hours for adin and 1.3 hours for drake