CoinBets🔍's banner
CoinBets🔍's profile picture

CoinBets🔍

@coinbetscom2,962 subscribers

The Crypto Casino Watchdog - no affiliate links, no casino money. 100% independent.

Shorts

Another terrible “provably fair” implementation: Betpanda​.io their setup lets them cherry pick outcomes and cheat players they rotate the server seed EVERY bet client seed stays fixed nonce = always 0 what this means: -after your first bet the server knows your input -it can simulate outcomes before serving one -cherry-pick a seed that makes you lose on larger bets -keep small bets normal so stats look fine your verification still passes because the math is correct for the seed they chose what you can’t prove is how many winning seeds were discarded first this isn’t provably fair the house can pick the outcome before you see it no legit pf system works like this standard is one committed seed + incrementing nonce Have you played at betpanda? what do you think?

Another terrible “provably fair” implementation: Betpanda​.io their setup lets them cherry pick outcomes and cheat players they rotate the server seed EVERY bet client seed stays fixed nonce = always 0 what this means: -after your first bet the server knows your input -it can simulate outcomes before serving one -cherry-pick a seed that makes you lose on larger bets -keep small bets normal so stats look fine your verification still passes because the math is correct for the seed they chose what you can’t prove is how many winning seeds were discarded first this isn’t provably fair the house can pick the outcome before you see it no legit pf system works like this standard is one committed seed + incrementing nonce Have you played at betpanda? what do you think?

16,950 views

Videos

coinbetscom's profile picture

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

CoinBets🔍

20,973 views • 4 months ago

No more content to load