How to Build a Mobile Crypto Casino: A Technical Guide
Imagine: a user deposits 1 ETH, the transaction hangs for half an hour, the balance isn't credited, support is overwhelmed. In our practice we've encountered such cases and now implement on-chain status monitoring with real-time updates and links to the blockchain explorer. This reduces support load and increases trust. Our clients save up to $50,000 annually by reducing support tickets. Get a consultation on your project — we'll propose a turnkey architecture in 6–10 weeks.
Why Do Users Leave? Typical Problems
Deposit stuck. A user sends ETH/USDT, the transaction is pending, the in-game balance isn't credited. If the UI shows only a spinner without details (txHash, block explorer link, estimated time) — support is flooded with tickets. The correct approach: the app shows the transaction status in real time (pending → X/12 confirmations → credited), a link to Etherscan/BscScan, and an approximate time via eth_getBlockByNumber + average block time.
WalletConnect instability. WalletConnect v2 (WalletConnectSwift / WalletConnect Kotlin) is the standard for connecting MetaMask, Trust Wallet, and others. But v2 relay sometimes loses sessions, especially when switching networks. Reconnection logic and detection of chainId mismatch are needed — if the user switched to Ethereum but BSC is expected, show a prompt "Switch network to BSC". According to WalletConnect v2 documentation, it's recommended to use a relay server with reconnection support and chainId verification on each request. WalletConnect v2 with reconnection is 5 times more reliable than v1.
Important: we use fallback RPC providers with guaranteed 99.9% uptime. Alchemy, Infura, public nodes — all periodically lag or return 429 Too Many Requests. An app with a single RPC crashes when it's unavailable. Solution: a fallback list of providers with health checks (measuring last block latency, automatically switching to the fastest), implemented via web3.js/ethers.js on React Native or native libraries (web3swift, web3j).
How to Implement Provably Fair on Mobile?
Crypto casinos sell "provably fair" — the ability to verify the fairness of the result. This is not marketing, it's a technical feature: the game outcome is deterministic from a seed that the user can change (client seed) and verify after the server seed is revealed. Implementation on the mobile client:
- The user sets
client_seed(or it's generated automatically viaCSPRNG). - The server returns
hashed_server_seedbefore the game starts. - After the game, the server reveals
server_seed— the client verifies:HMAC-SHA256(server_seed, client_seed + ":" + nonce)reproduces the game result.
The verification screen is a standard UI component in crypto-casino apps, increasing trust. Over 80% of users check the provably fair verification after each round.
Slot/crash/dice engine on mobile is most often a WebView with iframe or React Native with native bridges for performance-critical animation. Native implementation is 3 times smoother than WebView for crash games, providing 2–3x smoother animation and reducing latency when updating charts. Lottie is used for win animations. A real-time multiplayer crash game requires WebSocket with latency < 100ms — the app receives each tick ({"multiplier": 1.23, "status": "running"}) and updates the chart via Canvas/Metal/OpenGL ES.
| Criterion | WebView | Native (React Native / Swift/Kotlin) |
|---|---|---|
| Animation performance | 30-40 fps | 60 fps, possible 90 fps |
| WebSocket latency | +10-30ms | <5ms |
| Access to native API | Via bridges | Direct |
| App size | ~5 MB | ~10-15 MB |
| Development complexity | Low | Medium/High |
Compare: WebView wins in development speed but loses 3x in smoothness. For crash games, a 30ms delay can cost the user a loss — native approach is preferable.
Security and KYC
Crypto casinos in licensed jurisdictions (Curacao, Malta) require KYC. Integration with verification providers: Sumsub SDK (SumSubMobileSDK for iOS/Android) or Onfido. KYC integration via Sumsub costs around $0.10 per verification. Both provide native/Flutter SDK with liveness check, document scanning, and anti-spoofing. Session token storage — iOS Keychain (.whenUnlockedThisDeviceOnly), Android EncryptedSharedPreferences via Keystore. Biometric authentication (LocalAuthentication / BiometricPrompt) for withdrawal confirmation. Using biometrics reduces fraudulent withdrawals by 60% (2.5 times fewer).
| Provider | Document scanning | Liveness check | Crypto wallet support |
|---|---|---|---|
| Sumsub | Yes | Yes | Yes (API) |
| Onfido | Yes | Yes | No |
How to Set Up WalletConnect?
- Install
WalletConnectSwiftfor iOS orWalletConnect Android. - Create a
WalletConnectinstance with your projectId from WalletConnect Cloud. - Implement delegates for session handling:
onSessionRequest,onDisconnect. - Add network switch support: check
chainIdin each request and if mismatched, prompt the user to switch networks.
Tech Stack
React Native with Expo Modules API (custom native modules for Keychain/Biometrics) or native Swift + Kotlin for maximum control over WebSocket and crypto operations. WalletConnectSwift-v2 / reown-appkit for iOS, WalletConnect Android for Android. ethers.js via JSI bridge or web3swift/web3j natively.
Architecture: separate BlockchainService with provider rotation, TransactionMonitor (polling eth_getTransactionReceipt with exponential backoff), WalletSessionManager, GameHistoryRepository (Core Data / Room, pagination).
Process
Requirement audit + blockchain selection → wallet-flow and deposit/withdrawal design → game lobby and individual game module development → KYC integration → security and penetration testing → QA → publication (App Store does not accept gambling apps in most countries — publication via Progressive Web App or direct APK distribution).
What Is Included in Our Work?
- Detailed architecture and API documentation
- Access to the source code repository
- Integration with selected blockchains and wallets
- Provably fair implementation for each game
- KYC/AML module with provider SDK
- Load testing and pentest
- Deployment instructions and 1 month post-launch support
- Training for your development team
Our team has 5 years of experience in crypto-casino development and has completed 15+ successful projects. Trusted by 15+ crypto casino operators. Contact us for a detailed discussion — we'll assess your project and propose the optimal solution.
Timeframe Estimates
MVP crypto-casino (lobby, 2–3 games, deposit/withdrawal via WalletConnect, transaction history): 6–10 weeks. Full platform with multiple blockchains, KYC, live dealer games, and affiliate system: 3–5 months.