
CoinBets🔍
@coinbetscom • 2,962 subscribers
The Crypto Casino Watchdog - no affiliate links, no casino money. 100% independent.
Shorts
Videos

$300M + of VC and investor money has flooded into offshore crypto casinos in the last 18 months all trying to build the next STAKE Dicey.com - $157M MonkeyTilt.com - $51M MyPrize.com - $38M Bluff.com - $21M BetHog.com - $16M Winna.com - $15M backed by Paradigm, Sequoia, Pantera, Polychain + more hundreds of millions flowing into offshore gambling platforms we broke down the deals, the economics, and what it actually means for the space does massive VC money change the player experience for better or worse?
CoinBets🔍131,144 次观看 • 2 个月前

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
CoinBets🔍23,135 次观看 • 4 个月前

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 次观看 • 4 个月前
没有更多内容可加载