Arbitrage exploits price differences between markets to earn near-risk-free profit. In crypto, opportunities arise from fragmented exchanges, mismatched fees, mispriced trading pairs, or funding rate dislocations. This guide explains common arbitrage types, walks through worked examples with numbers, analyzes the full risk stack, and provides operational checklists and best practices.
1. Common forms of crypto arbitrage
- Spatial / cross-exchange: buy on Exchange A and sell on Exchange B.
- Triangular (within exchange): exploit inconsistencies across three pairs (e.g., BTC/USDT ↔ ETH/USDT ↔ ETH/BTC).
- Funding / perpetual basis arbitrage: long spot + short perpetual (or vice versa) to capture positive funding.
- Statistical / latency arbitrage: use models and speed to capture transient micro inefficiencies.
2. Worked examples
Example A — Spatial arbitrage (1 BTC)
Assumptions:
- BTC price on Exchange A = $60,000
- BTC price on Exchange B = $60,300
- Buy fee = 0.1%, sell fee = 0.1%
- Withdrawal fee from Exchange A = 0.0005 BTC (≈ $30 at $60k)
Calculations:
- Cost to buy: $60,000 × (1 + 0.001) = $60,060
- Proceeds from sell: $60,300 × (1 − 0.001) = $60,239.70
- Withdrawal cost: ≈ $30
- Gross profit ≈ $60,239.70 − ($60,060 + $30) = $149.70
Key risk: price moves on Exchange B during the transfer. A 0.25% adverse move (~$150) wipes the profit. Include slippage and network fees when evaluating opportunities.
Example B — Triangular arbitrage
Market quotes:
- BTC/USDT = $60,000
- ETH/USDT = $4,000
- ETH/BTC market = 0.0675
Implied ETH/BTC from spot = 4,000 / 60,000 = 0.0666667, but market shows 0.0675. Strategy:
- Start with $60,000 → buy 15 ETH at $4,000.
- Sell 15 ETH at 0.0675 ETH/BTC → receive 1.0125 BTC.
- Sell 1.0125 BTC at $60,000 → $60,750.
Gross profit ≈ $750 before fees. Because triangular arbitrage executes entirely on one exchange, transfer risk is minimal but execution must be near-instant and fees low. After three taker fees (0.1% each), profit diminishes; execution speed and low fees are decisive.
3. Full risk analysis
Slippage / market impact
Large orders on thin order books cause slippage. Always check cumulative depth inside the target price band (for example ±0.25%). Define worst-case slippage in your profit model.
Fees and withdrawal costs
Include maker/taker fees, withdrawal fees, and blockchain gas in your break-even calculation. For spatial arbitrage, on-chain transfer fees can be material.
Latency and price movement during transfer
Cross-exchange transfers take time. Mitigations: pre-fund target exchanges, or hedge interim exposure by shorting a perpetual contract on the destination exchange to lock the price during transfer.
Withdrawal limits, KYC and operational restrictions
Exchanges often impose daily withdrawal limits or temporary holds. Your capital and position sizing must respect these constraints or the strategy can fail when you need to move funds quickly.
Counterparty and custody risk
Keeping capital on multiple exchanges exposes you to exchange failure or hacks. Use reputable venues, diversify custodians, and limit amounts per exchange according to your risk tolerance.
Bridge and cross-chain risk
Cross-chain arbitrage using bridges adds smart-contract risk and bridge fees. Avoid new or low-TVL bridges unless you accept the extra risk.
Funding and liquidation risk
When using perpetuals for hedging, funding rates can swing, and leveraged positions can be liquidated in volatile markets. Monitor margin ratios and avoid excessive leverage.
Operational risk
Bot bugs, API throttling, exchange outages or inconsistent timestamps can cause failed executions. Design retry logic, monitoring, and circuit breakers.
4. Safe strategy design rules
- Pre-fund accounts: keep working balances at exchanges where you plan to sell to avoid transfer latency.
- Minimum spread threshold: only act when spread > (fees + transfer_cost + slippage_buffer).
- Liquidity-aware sizing: cap order size as a percentage of depth at your slippage tolerance (e.g., no more than X% of [email protected]%).
- Delta-neutral hedging: hedge price exposure during transfers with opposite perp positions when appropriate.
- Automatic fail-safe: cancel or unwind if price moves beyond a threshold during execution; implement rate limits and stops for API errors.
5. Bot architecture & tooling
- APIs / libraries: CCXT and exchange SDKs for order placement.
- Order router: split and route orders across venues to minimize impact and fees.
- Price feeds & monitoring: websocket feeds for low latency; REST fallbacks.
- Execution engine: support IOC/FOK, TWAP, and retry logic with idempotency.
- Risk module: real-time P&L, exposure, margin and funding monitoring with automated alerts.
- Open source / ready tools: Hummingbot (arbitrage modules), custom CCXT scripts for bespoke needs.
6. Taxes, reporting and compliance
Each buy/sell and often each transfer is a taxable event depending on jurisdiction. Record TXIDs, timestamps, fees and fiat values for all actions. Use tax tools (Koinly, CoinTracker) to aggregate activity from multiple exchanges.
7. Pre-deployment checklist
- Compute net spread: spread_min = fees + transfer_cost + slippage_buffer.
- Verify orderbook depth and expected fill rates at target price.
- Confirm withdrawal limits and KYC status on all target exchanges.
- Implement monitoring for API errors, fill rates, and funding rate moves.
- Backtest on historical data including fees and realistic transfer delays; run paper trading before committing capital.
8. Advanced example — funding arbitrage
Start with 1 BTC spot and short 1 BTC perpetual to capture positive funding. If the funding rate averages 0.02% per 8 hours (~0.06% per day), gross daily return ≈ 0.06%. Costs: perp taker fees, funding volatility, and potential liquidations. Monitor funding and adjust position size; close or reduce leverage when funding flips or volatility spikes.
9. Execution best practices
- Use limit orders where possible to control execution price and reduce taker fees.
- Stagger large entries (TWAP) when depth is limited to reduce impact.
- Maintain a diversified set of exchanges to spread counterparty and liquidity risk.
- Automate conservative circuit breakers: max drawdown, API error counts, and funding-rate reversals.
10. Final checklist and advice
- Fully model all costs and worst-case slippage before executing.
- Prefer pre-funded accounts to avoid transfer latency when possible.
- Automate with solid monitoring and fail-safe logic; test thoroughly in paper mode.
- Start small, scale with demonstrated edge and robust operational controls.
11. Conclusion
Arbitrage can appear to be low-risk but in practice it is an operational challenge. Fees, slippage, latency, limits and counterparty risk all erode margins. The winning approach combines complete cost modelling, pre-funding, robust automation with circuit breakers, and conservative sizing. Always backtest, paper trade, and audit your execution logic before deploying significant capital.
Disclaimer: Arbitrage involves real risks. This guide is informational only. Test strategies in controlled environments and seek professional advice for large deployments.







