Failover System for Trading Bot: Automatic Exchange Switching

Consider: when a major exchange suddenly goes down — REST API returns 503, WebSocket disconnects, orders get stuck. A 24/7 trading bot goes blind: no new trades, positions unmonitored. In one hour of downtime, a high-frequency strategy can lose up to $50,000 in potential profit. Without a failover system, such outages cost tens of thousands of dollars each time.

We design and implement turnkey failover systems — an automatic mechanism to switch operations to a backup exchange upon failure (failover). With over 5 years in DeFi and HFT and more than 50 completed projects, our solutions guarantee 99.9% uptime even if the primary platform fails. For clients with turnover exceeding $10M, average savings from implementation reach $200,000 per year. Failover investments pay back within months by preventing downtime.

Failover Architectures: Active-Passive and Active-Active

Two approaches: Active-Passive and Active-Active. In the first, the primary exchange handles all orders; the backup stays on standby. On primary failure, switching occurs. Simple, no duplicate orders. In the second, trading runs on multiple exchanges simultaneously; when one fails, others continue. More complex due to position coordination. For most bots, Active-Passive suffices.

Active-Passive is 2x simpler than Active-Active and requires 50% less capital. If your bot uses arbitrage or statistical advantage on one exchange, Active-Passive is optimal. For high-frequency trading with liquidity distribution, Active-Active is better, though it's more complex and costly.

Why Failover Is Critical for DeFi and HFT?

DeFi protocols run on smart contracts that depend on oracle data and network availability. If an exchange stops processing orders, arbitrage opportunities vanish and positions may get liquidated. In HFT, every millisecond of downtime means lost trades. A failover system ensures continuity even during planned maintenance or sudden outages.

How to Detect Exchange Failure?

Failure is not binary. Gradations: REST API unavailable, WebSocket disconnected, API responds but orders don't go through, latency increased 10x. Health check should monitor a combination of indicators: ping, market data, test order. Trigger threshold based on aggregate, not a single signal. Flapping protection: after switchover, a cooldown of 5–15 minutes prevents bouncing between exchanges during instability.

What to Do with Open Positions During Failover?

Three options: leave positions on the primary (risk without monitoring), mirror hedging (open opposite positions on backup to create net neutral exposure), or pause (no new positions, wait for recovery). Choice depends on strategy type and risk tolerance. We help find the balance between continuity and risk.

How to Set Up a Failover System: Step by Step

1. Analyze strategy: identify activities vulnerable to downtime.
2. Choose architecture: Active-Passive for simplicity, Active-Active for HFT.
3. Configure health checks: integrate REST and WebSocket checks with thresholds.
4. Implement flapping protection: set cooldown of 10 minutes.
5. Integrate backup exchange: configure API keys, balances, fee structures.
6. Test: simulate primary exchange failure and verify switchover.
7. Deploy and monitor: roll out with logging and alerts.

Case Study

For a client running market making on Binance, we implemented Active-Passive failover with OKX as backup. Under normal operation, 100% of orders went to Binance. Over two months of operation, only one failover event occurred: Binance was down for 30 seconds due to an unscheduled update. During that time, the backup exchange processed 1,200 orders without any losses. Thanks to flapping protection, the system did not switch back immediately after recovery but observed the cooldown, eliminating unnecessary oscillations. As a result, uptime reached 99.95%, and the client avoided losses that could have amounted to tens of thousands of dollars.

Practical Limitations

Capital must be maintained on both exchanges — locking up funds. Prices of the same pair may differ — a strategy with tight levels may yield different results. Fee structures vary: 0.1% on one exchange, 0.15% on another — profit changes. Our engineers account for these nuances when designing, selecting the optimal pair of exchanges. Requirements for the backup exchange: support for the same set of trading pairs (or with minimal differences), API with comparable limits and stability, fee structure close to the primary to avoid strategy distortion.

What Is Included (Deliverables)

• Architectural documentation with rationale for exchange selection and failover scheme.
• Implementation of integration code on Foundry with unit tests.
• Configuration of health checks and flapping protection.
• Operation manual for your team.
• Staff training (1 hour online).

Work Process

We guarantee reliability: the system undergoes formal testing and operates under load. Experience: 50+ projects, including for market makers with multi-million dollar turnovers.

Order development of a failover system tailored to your strategy — we will analyze your requirements and propose the optimal solution. Contact us for a consultation today.

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.