Setting Up Multi-Crypto Betting for Casino Platforms
We designed and deployed a multi-currency deposit system for a casino with $10M+ monthly turnover. Our expertise: 5+ years in blockchain development, 30+ successful integrations for gambling projects. Accepting bets in BTC, ETH, USDT, BNB, SOL, and 20 other tokens is technically nontrivial. Each network has its own address model, finality, fees, and speed. If not architected correctly, you risk frozen funds (deposit not credited due to incorrect confirmation) or accounting holes (USDT on Ethereum vs USDT on TRON—different tokens, different networks, but one row in the database).
We offer a turnkey solution: from HD wallet generation to transaction monitoring and accounting integration. You get a unified interface for accepting bets in any token, conversion to USD for GGR calculation, and secure storage with automatic cold wallet sweeps. Free project assessment available.
How to Build the Multi-Currency Betting Architecture
HD Wallets and Unique Addresses
Each user needs a unique address per network—otherwise you cannot automatically match incoming payments to accounts. Standard approach: HD wallet (BIP-32/BIP-44) with address derivation.
Master seed → derivation via path m/44'/coin_type'/account'/0/index:
import { HDKey } from '@scure/bip32' import { mnemonicToSeedSync } from '@scure/bip39' const masterSeed = mnemonicToSeedSync(process.env.MASTER_MNEMONIC!) const masterKey = HDKey.fromMasterSeed(masterSeed) function deriveAddress(coinType: number, userId: number): string { // BIP-44: m/44'/coinType'/0'/0/userId const child = masterKey.derive(`m/44'/${coinType}'/0'/0/${userId}`) // For EVM networks coinType=60, Bitcoin=0, Solana=501 return toChecksumAddress(child.publicKey) } For EVM-compatible networks (Ethereum, BNB Chain, Polygon, Arbitrum)—the same address works across all networks, but these are DIFFERENT balances. Do not mix: a user may send ETH to their BSC address—coins will be on another network and never credited.
Monitoring Incoming Transactions
Two approaches:
- Webhook-based via payment provider (NOWPayments, CoinsPaid, Binance Pay API). The provider monitors addresses and sends webhooks on deposit. Fast to integrate, but:
- Provider has access to your funds
- Higher fees
- Less control
- Self-hosted monitoring—your own service listens to nodes and indexes incoming transactions. Full control, lower costs at volume, but infrastructure responsibility is yours.
// Monitoring EVM addresses via eth_getLogs + transfer topic const TRANSFER_TOPIC = '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef' async function monitorIncomingTransfers( addresses: string[], fromBlock: number ) { const logs = await client.getLogs({ fromBlock: BigInt(fromBlock), toBlock: 'latest', topics: [ TRANSFER_TOPIC, null, // from: any addresses.map(padAddress), // to: our addresses ], }) for (const log of logs) { const token = log.address // ERC-20 contract const to = unpadAddress(log.topics[2]) const amount = BigInt(log.data) await processDeposit({ token, to, amount, txHash: log.transactionHash, blockNumber: log.blockNumber }) } } Why Network Finality Matters
The most common mistake: crediting a bet after 1 confirmation in all networks. Reorgs happen, and the bet gets credited without real funds.
| Network | Recommended Confirmations | Approx. Time |
|---|---|---|
| Bitcoin | 3-6 | 30-60 min |
| Ethereum | 12-15 (PoS safe) | 3-4 min |
| BNB Chain | 15-20 | 60-90 sec |
| Polygon | 256 (checkpoint on ETH) | ~10 min |
| Solana | 32 (finalized) | ~15 sec |
| TRON | 19 (SR solid) | ~60 sec |
| Arbitrum | 1 (L2 finality) | sec (soft), 7 days (challenge period) |
For betting, a reasonable compromise: Ethereum—12 confirmations, fast L1s (BSC, Tron)—20 confirmations, Solana—finalized status.
How to Properly Account for Multi-Currency Balances
The database must distinguish not just 'token', but 'token + network':
CREATE TABLE user_balances ( user_id BIGINT NOT NULL, network VARCHAR(50) NOT NULL, -- 'ethereum', 'bsc', 'tron' token_address VARCHAR(100), -- NULL for native token token_symbol VARCHAR(20) NOT NULL, raw_amount NUMERIC(78, 0) NOT NULL, -- wei/lamports, without decimals decimals SMALLINT NOT NULL, PRIMARY KEY (user_id, network, COALESCE(token_address, 'native')) ); -- USDT on different networks — DIFFERENT rows -- user_id=1, network='ethereum', token='0xdAC17F...', symbol='USDT' -- user_id=1, network='tron', token='TR7NHqjeKQ...', symbol='USDT' Never sum raw_amount tokens with different decimals without normalization. USDT = 6 decimals, most ERC-20 = 18 decimals.
How to Convert Cryptocurrencies to a Single Accounting Currency
Casinos need to calculate GGR in a single currency (usually USD or EUR). Use a price feed:
// Record USD value at bet time async function recordBet(userId: number, currency: string, network: string, rawAmount: bigint, decimals: number) { const humanAmount = Number(rawAmount) / Math.pow(10, decimals) const usdPrice = await priceOracle.getPrice(currency) // Chainlink, CoinGecko, Binance const usdValue = humanAmount * usdPrice await db.query(` INSERT INTO bets (user_id, currency, network, raw_amount, decimals, usd_value_at_time, placed_at) VALUES ($1, $2, $3, $4, $5, $6, NOW()) `, [userId, currency, network, rawAmount.toString(), decimals, usdValue]) } Fix the USD value at the moment of the bet—otherwise PnL reports depend on the current exchange rate, making financial reporting unpredictable.
How to Ensure Fund Security: Hot and Cold Wallets
Don't keep all user funds on a hot wallet. Standard scheme:
- Hot wallet—5-10% of daily turnover. Instant payouts.
- Cold/warm wallet (multisig)—the rest. Scheduled sweeps.
Automatic sweep: as soon as the deposit address balance exceeds a threshold, automatically transfer to a hot wallet aggregation address. Otherwise funds are scattered across thousands of addresses and impossible to manage.
Payment Provider or Self-Hosted: Which to Choose?
| Parameter | Provider (NOWPayments, CoinsPaid) | Self-Hosted |
|---|---|---|
| Integration time | 1-3 days | 2-4 weeks |
| Fee | 0.5-1% of turnover | Only gas |
| Private key control | With provider | With you |
| Multi-network | 30-200+ coins out of the box | As many as you implement |
| Confirmation customization | Limited | Full |
For small casinos (< $100k turnover/day), a provider is justified. As volumes grow, provider fees become a significant expense. A self-hosted solution pays for itself in 3-6 months at $500k/month turnover, saving over $5,000 per month on provider fees—making it 20x more cost-effective at scale.
Why Network Finality Matters (Detailed)
Reorg depth varies by network. For example, Ethereum often sees 1–2 block reorgs, while Solana rarely has finalized reorgs. Our recommended confirmations balance speed and safety for betting.
Deliverables
- Requirements analysis and architecture selection (provider or self-hosted, network list).
- Master seed generation and HD wallets, address derivation for all users.
- Transaction monitoring setup (webhook or self-hosted service).
- Integration with your platform (API for deposits, withdrawals, balance checks).
- USD conversion for financial reporting.
- Hot/cold wallet and automatic sweep configuration.
- Testing on testnet and mainnet, including edge cases (reorgs, fee spikes).
- API and administration documentation.
- Team training.
- Code warranty and 3-month support after launch.
Why Choose Us
We are a team of blockchain engineers with 5+ years of experience in smart contracts and DeFi. Certified Solidity and Rust developers. We have launched 30+ projects with a combined turnover exceeding $50M. We guarantee security: use Slither, Mythril, and formal verification. Our nodes maintain 100% uptime. Contact us for a free project assessment. Get a consultation from our technical lead.