CoinBets🔍

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

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

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. 🧵