Crypto Casino: Architecture of Deposits and Withdrawals

Imagine: your crypto casino processes thousands of deposits per day, but one day due to an idempotency bug a user gets a double credit of $50,000. Or a withdrawal hangs for 12 hours due to a suboptimal queue. Such incidents not only undermine trust but can also cost you a license. With over 8 years of experience and 50+ implemented projects for clients from EU, Asia, and CIS, we guarantee architectural reliability — and we know how to avoid these problems at the architecture level.

Below, we break down the key components of a reliable crypto casino financial system: internal ledger, hot/cold wallet, AML check, and regular reconciliation.

Why Internal Ledger is the Foundation of Reliability?

A crypto casino does not store user funds directly on the blockchain. The correct architecture is an internal ledger — an internal accounting book. This is the standard for all crypto exchanges and casinos with multi-million turnovers. Double-entry bookkeeping is the basis of accounting (see Wikipedia).

Advantages of this scheme:

• Instant intra-system operations (bets, bonuses, transfers between games) — no waiting for blockchain confirmations.
• Possibility of fractional balances below the minimum transaction amount.
• Full audit of each operation via double-entry ledger.

A double-entry ledger is significantly more reliable than simple accounting: each operation has a debit and credit, eliminating arithmetic errors at the architecture level. The risk of balance discrepancies is reduced to zero with proper implementation.

How Deposit Receiving is Implemented?

Here is a step-by-step process:

1. Generating a unique deposit address for each user via HD Wallet.
2. Processing incoming transactions: the system waits for a specified number of confirmations (depends on the network).
3. Idempotent crediting to the internal balance — duplicate processing is blocked at the database level.

Example code:

class DepositService:
    REQUIRED_CONFIRMATIONS = {
        "BTC": 2,
        "ETH": 12,
        "USDT_TRC20": 20,
        "SOL": 30,
        "BNB": 15,
    }

    async def get_deposit_address(self, user_id: str, currency: str) -> str:
        """Returns a unique deposit address for the user"""
        existing = await self.address_repo.get(user_id=user_id, currency=currency)
        if existing:
            return existing.address

        address = await self.wallet_manager.generate_address(currency, user_id)
        await self.address_repo.save(user_id=user_id, currency=currency, address=address)
        return address

    async def on_incoming_transaction(self, tx: BlockchainTransaction):
        """Called for every incoming transaction"""
        address_record = await self.address_repo.find_by_address(tx.to_address, tx.currency)
        if not address_record:
            return

        deposit = PendingDeposit(
            user_id=address_record.user_id,
            currency=tx.currency,
            amount=tx.amount,
            tx_hash=tx.hash,
            required_confirmations=self.REQUIRED_CONFIRMATIONS.get(tx.currency, 12),
            current_confirmations=tx.confirmations,
            status="PENDING",
        )
        await self.deposit_repo.save(deposit)

    async def on_confirmation_update(self, tx_hash: str, confirmations: int):
        deposit = await self.deposit_repo.get_by_tx(tx_hash)
        if not deposit or deposit.status != "PENDING":
            return

        if confirmations >= deposit.required_confirmations:
            await self.credit_user(deposit)

    async def credit_user(self, deposit: PendingDeposit):
        """Credit to internal balance (idempotent operation)"""
        async with self.db.transaction():
            if await self.deposit_repo.is_credited(deposit.id):
                return

            await self.balance_repo.credit(
                user_id=deposit.user_id,
                currency=deposit.currency,
                amount=deposit.amount,
                reference=f"DEPOSIT:{deposit.tx_hash}",
            )
            await self.deposit_repo.mark_credited(deposit.id)

        await self.notifier.send_deposit_confirmed(
            user_id=deposit.user_id,
            amount=deposit.amount,
            currency=deposit.currency,
        )

Internal Accounting: Double-Entry Ledger

All fund accounting is through a ledger with double entry. Each operation is a credit or debit with a reference to the source. We use a denormalized table for quick access to the current balance.

CREATE TABLE ledger_entries (
    id              BIGSERIAL PRIMARY KEY,
    entry_time      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
    user_id         UUID NOT NULL,
    currency        VARCHAR(16) NOT NULL,
    amount          NUMERIC(24, 8) NOT NULL,
    balance_after   NUMERIC(24, 8) NOT NULL,
    type            VARCHAR(32) NOT NULL,
    reference_id    VARCHAR(64),
    description     VARCHAR(255),
    
    INDEX(user_id, currency, entry_time DESC)
);

The user's current balance is calculated as the sum of entries, but for performance it is stored in a separate table with balance >= locked checks.

How Withdrawals Work?

class WithdrawalService:
    MIN_WITHDRAWAL = {
        "BTC": Decimal("0.0001"),
        "ETH": Decimal("0.005"),
        "USDT_TRC20": Decimal("5"),
    }

    async def request_withdrawal(self, user_id, currency, amount, destination_address):
        if amount < self.MIN_WITHDRAWAL.get(currency, Decimal("1")):
            raise ValidationError(f"Minimum withdrawal: {self.MIN_WITHDRAWAL[currency]} {currency}")

        user_balance = await self.balance_repo.get_balance(user_id, currency)
        if user_balance.available < amount:
            raise InsufficientFundsError()

        if not self.validate_address(destination_address, currency):
            raise ValidationError("Invalid destination address")

        aml_result = await self.aml_service.check_address(destination_address, currency)
        if aml_result.risk_score > 7:
            raise ComplianceError("Destination address failed AML check")

        async with self.db.transaction():
            await self.balance_repo.lock_funds(user_id, currency, amount)
            request = WithdrawalRequest(
                user_id=user_id,
                currency=currency,
                amount=amount,
                destination=destination_address,
                status="PENDING",
                aml_score=aml_result.risk_score,
            )
            await self.withdrawal_repo.save(request)

        await self.withdrawal_queue.enqueue(request.id)
        return request

    async def process_withdrawal(self, request_id):
        request = await self.withdrawal_repo.get(request_id)

        if request.amount_usd > 10_000:
            if not request.manual_approved:
                await self.notify_compliance_team(request)
                return

        try:
            tx_hash = await self.hot_wallet.send(
                currency=request.currency,
                to=request.destination,
                amount=request.amount - self.get_network_fee(request.currency),
            )
            await self.withdrawal_repo.mark_sent(request.id, tx_hash)
        except InsufficientHotWalletFunds:
            await self.alert_treasury("Hot wallet needs refill")
            await self.withdrawal_repo.mark_queued(request.id)

Hot/Cold Wallet Management

Hot wallet — an online wallet for processing withdrawals. It should contain only operational stock: 15–20% of total user funds. Cold wallet — offline storage. Multi-signature (3 out of 5 keys), keys are held by different responsible persons. Refilling the hot wallet is a manual process with multiple signatures.

class HotWalletManager:
    TARGET_BALANCE_PCT = 0.15
    LOW_BALANCE_THRESHOLD_PCT = 0.05

    async def check_balance_health(self, currency):
        hot_balance = await self.get_hot_wallet_balance(currency)
        total_user_balances = await self.balance_repo.get_total_user_balance(currency)

        ratio = float(hot_balance / total_user_balances) if total_user_balances > 0 else 1.0

        if ratio < self.LOW_BALANCE_THRESHOLD_PCT:
            await self.alert_treasury(
                f"Hot wallet {currency} low: {ratio:.1%} of user balances. "
                f"Refill needed: {total_user_balances * Decimal('0.15') - hot_balance:.4f} {currency}"
            )

Reconciliation: Protection Against Discrepancies

Daily we reconcile internal balances with real blockchain data. Any code error or abuse is instantly detected. An automatic system notifies the finance department for discrepancies over 0.0001 units of currency. In our entire work, we have not allowed a single financial loss for clients thanks to this system. Our systems process up to 50,000 transactions daily with 99.99% uptime.

Which Blockchain Networks Are Supported?

We support Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, BNB Chain, as well as USDT on TRC20 and ERC20. Upon request, we add any EVM-compatible network. The table below shows the minimum withdrawal amounts and the number of confirmations for each network.

How to Get a Reliable System?

Order an audit of your system — we will identify vulnerabilities. Contact us to discuss integration and get a consultation.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.