okbet is non-custodial and runs on Base mainnet. Every bet is its own escrow contract, the code is source-verified on Basescan, and there is no path that sends your funds to an arbitrary address. Here's the detail.
okbet's v1 contracts went through multiple rounds of internal peer review and security hardening — reentrancy protection (checks-effects-interactions ordering plus ReentrancyGuard), pull-based payouts, initialization validation, and fee-path fund-safety. Internal peer review is complete and an external security-firm audit is in progress. All deployed contracts are source-verified on Basescan. For the latest review status, email security@okehbet.com.
BASE MAINNET · CHAIN 8453 · DEPLOY BLOCK 46965116
Every genuine bet is a clone deployed by the factory above. The factory exposes isBet(address), which returns truefor any real okbet bet — an authoritative way to verify a bet's provenance on-chain.
okbet deploys a brand-new escrow contract for every bet (EIP-1167 minimal-proxy “clones”) so each bet's funds stay isolated. A seconds-old address has no transaction history, so some wallet scanners flag the first approve as “untrusted” or “deceptive.”
It's a false positive driven by the clone-per-bet design, not malicious behavior. You can verify any bet on-chain with the factory's isBet check, and we're working with wallet-security providers to allowlist the factory and its clones.
Found something? Email security@okehbet.com. Please don't disclose publicly until we've had a chance to respond. See also the protocol overview.