White-Label Crypto Exchange: Matching Engine, Security, and Licensing

Building a Secure and Efficient White-Label Crypto Exchange

Many companies choose a ready-made platform for a crypto exchange but face problems: low matching engine performance, vulnerabilities in the custodial system, non-compliance with regulatory requirements. A white-label solution from an experienced vendor is a compromise, but only if the architecture is well-designed. We share our experience: which components are critical, how a Rust-based matching engine works, why fund security is not an option but a necessity, and which jurisdictions are suitable for licensing. A quality turnkey exchange reduces capital expenditure by 2–3 times compared to building from scratch, while providing production-ready code. A typical mistake is choosing a vendor that offers only a frontend and basic API, outsourcing complex components like the matching engine and custodial system. With over 9 years of proven experience and certified security audits, we guarantee a reliable platform.

Key components of a white-label crypto exchange

A turnkey exchange is not just a clone with a repainted logo. It is a full-fledged product: matching engine, custodial system, KYC/AML, liquidity, and compliance. Let's break down the architecture, real-world challenges, and how to distinguish a quality solution from a cheap knockoff.

How does the matching engine work?

The matching engine is the critical component that determines performance. The order book is stored in memory, not in the database. A typical implementation in Rust:

use std::collections::BTreeMap;

struct OrderBook {
    bids: BTreeMap<Price, PriceLevel>,
    asks: BTreeMap<Price, PriceLevel>,
    orders: HashMap<OrderId, Order>,
}

struct PriceLevel {
    price: Price,
    total_quantity: Quantity,
    orders: VecDeque<OrderId>,
}

FIFO matching (price-time priority) is standard for spot. Pro-rata is used for derivatives.

Production requirements: 10,000–100,000 orders/sec, latency <1ms matching, <10ms end-to-end. For volumes up to $10M/day, Go or Java is sufficient; Rust/C++ is needed for >$100M/day. A C++ matching engine handles up to 500,000 orders/sec, 10x faster than Python implementations.

How is fund storage organized?

Classic scheme: over 90% in a cold wallet (multi-sig, HSM), 5–8% in a warm wallet (automatic replenishment from cold), 2–5% in a hot wallet (small withdrawals). Transition logic: if hot < 1% → transfer from warm; if hot > 10% → surplus to cold.

Addressing: each user receives a unique deposit address via BIP-44 derivation. HD wallet seed phrase is stored only in HSM or AWS CloudHSM.

Deposit detection

class DepositDetector:
    async def monitor_evm_deposits(self, network: str):
        async with websockets.connect(self.rpc_ws_url) as ws:
            await ws.send(json.dumps({
                "id": 1,
                "method": "eth_subscribe",
                "params": ["newHeads"]
            }))
            async for message in ws:
                block_data = json.loads(message)
                if "params" in block_data:
                    block_hash = block_data["params"]["result"]["hash"]
                    await self.process_block(block_hash, network)

Confirmations: Bitcoin 2–3, Ethereum 12–20, Polygon/Arbitrum 20–64.

How is the liquidity problem solved?

A new exchange without liquidity is an empty order book. Options:

1. External liquidity aggregation: a market-making bot connects to Binance/OKX, places orders in your book, and hedges positions externally. Spread becomes your income.
2. B-Book model: the exchange acts as counterparty (high risk, full control).
3. Institutional liquidity: providers like B2Broker, Cumberland, Wintermute charge a fee or spread sharing.

A white-label solution costs 2-3 times less than building from scratch ($50,000–$100,000 license fee) while providing the same level of functionality.

Liquidity and compliance: what to consider

KYC levels: from email-only (no deposit) to institutional (no limit). The FATF Travel Rule requires transmitting sender/receiver data for transfers >$1000 between VASPs. Integration with Notabene, Sygna, or OpenVASP is mandatory for EU (MiCA), US (FinCEN), UK jurisdictions. According to a recent report, 70% of crypto exchanges face vulnerabilities in custodial systems — code audits are critical.

Which jurisdictions are suitable for licensing?

Popular options: Estonia (VASP), Lithuania (VASP), BVI (VASP), Seychelles, Dubai VARA, EU MiCA. The choice depends on the target market and budget. Learn more about Virtual Asset Service Provider — what it is and how it is regulated.

What's included in our white-label package

• Complete source code with documentation
• API and integration support (REST, WebSocket, FIX)
• Training for your team (up to 5 sessions)
• 6 months of post-launch support and updates
• Regular security audits and penetration testing
• Deployment on your infrastructure or cloud (bare metal + Kubernetes)

Development process and timeline

Stages: analytics → architecture design → implementation of matching engine, custodial system, frontend → integration of KYC/AML, liquidity → testing (unit, integration, pen test) → deployment on bare metal for matching engine, Kubernetes for market data, API Gateway, databases.

Recommended infrastructure: PostgreSQL + TimescaleDB, Redis Cluster, Kafka, Prometheus + Grafana. Choosing the jurisdiction is a critical decision.

From 9 to 18 months for a team of 8–15 engineers, depending on scope. Licensing a white-label vendor (Openware, B2Broker, Merkeleon) is an alternative for a quick start. The cost is calculated individually. Request a consultation to evaluate the cost and timeline for your case.

How to choose a white-label provider

1. Request a technical portfolio: which blockchains are integrated, how many orders per second the matching engine can handle.
2. Check if the source code is provided and auditable.
3. Clarify compliance modules: which jurisdictions are supported, is Travel Rule implemented.
4. Evaluate customization: can you change the interface, add pairs, configure limits.
5. Request documentation for APIs and integration with external liquidity providers.

We have been developing turnkey exchanges for over 9 years: 20+ projects launched, load up to $200M/day. Contact us to discuss your project — we will select the architecture and timeline. Request a consultation to evaluate the cost and timeline for your case.

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.