Rate Limiting System Development for Crypto Exchange API

Note: when an API key sends 10,000 requests per second to the /order endpoint without a rate limiting system, the backend goes down in a minute. We design and implement protection that cuts off anomalous traffic while keeping the system responsive for legitimate users. Unlike off-the-shelf gateways, our solution accounts for the specifics of crypto exchanges: different limits for maker/taker, WebSocket connections, and bursts based on balance. On a real project with a peak load of 50k RPS, we reduced the number of rejected legitimate requests by 3x compared to the standard Nginx limit_req. The foundation is a combination of token bucket and sliding window log on Redis Cluster. The former allows short-term bursts, the latter provides accurate accounting within a sliding window.

Why rate limiting is critical for a crypto exchange?

The crypto exchange API is a prime target for bots and scripts. Without rate limiting, an attacker can:

• Launch a DDoS using a single key, utilizing all 10 Gbps of the channel
• Scrape all orders in seconds (data scraping) – up to 100,000 requests per minute
• Take down the /order endpoint with excessive requests, causing timeouts for legitimate traders

We've encountered cases where high-frequency traders accidentally sent 5000 requests per second to /balance, crashing the matching engine. Our system cuts off such anomalies without human intervention, with a latency of no more than 2 ms.

Which algorithm to choose for reliable rate limiting?

Token bucket provides flexibility: you set the refill rate (e.g., 100 tokens/s) and bucket size (burst up to 500 tokens) – bursts up to 5x the average limit pass without blocking. Sliding window log is more precise: it counts requests in a moving window and does not allow exceeding the limit even for a second. We combine both: token bucket for most endpoints, sliding window for critical ones (e.g., /withdraw). This gives the best protection and minimal false positives – 3x fewer than the standard limit_req.

What is included in the rate limiting work?

We deliver a complete set of deliverables:

• Architecture and rules documentation
• Access to Grafana dashboards (logs, metrics, alerts)
• Operations team training (2-3 sessions)
• Support during the deployment phase for 2 weeks

How we design the rate limiting system

Architecture and stack

Nginx configuration example

http {
    limit_req_zone $binary_remote_addr zone=api:10m rate=100r/s;
    
    server {
        location /api/v1/ticker {
            limit_req zone=api burst=50 nodelay;
            proxy_pass http://backend:8080;
        }
    }
}

Lua script for Redis (token bucket)

local key = KEYS[1]
local rate = tonumber(ARGV[1])
local capacity = tonumber(ARGV[2])
local now = redis.call('TIME')[1]

local bucket = redis.call('HGETALL', key)
local tokens = bucket[1] and tonumber(bucket[1]) or capacity
local lastRefill = bucket[2] and tonumber(bucket[2]) or now

local tokensToAdd = (now - lastRefill) * rate / 1000
if tokensToAdd > 0 then
    tokens = math.min(capacity, tokens + tokensToAdd)
    lastRefill = now
end

if tokens >= 1 then
    tokens = tokens - 1
    redis.call('HMSET', key, tokens, lastRefill)
    redis.call('EXPIRE', key, 10)
    return 1
else
    return 0
end

The implementation is based on the official example from Redis documentation — Token Bucket Lua script. For WebSocket connections, we configure a separate token bucket with a key by user_id and a limit of 10 messages per second. We use Redis Pub/Sub for synchronization between nodes.

Advantages of custom solution over ready-made gateways

Ready-made gateways like Kong or AWS API Gateway do not support custom limits for WebSocket, distinction of rights for maker/taker, or burst mechanism based on balance. Our solution is tailored for the exchange: you set the user tier (VIP gets 1000 r/s, regular 10), configure logic for each endpoint, and integrate with your billing or scoring system.

Step-by-step implementation: from analysis to monitoring

1. Load profile analysis. Collect logs for a month, determine request distribution across endpoints, peak hours, typical anomalies.
2. Rule design. Develop tier grid, limits for each route, exceptions for WebSocket.
3. Middleware implementation. Write in Go or Lua in Nginx – add a handler that checks the limit before passing the request to the backend.
4. Redis integration. Set up cluster, key TTL, pipelines to reduce latency.
5. Load testing. Run wrk and k6 up to 100k RPS, ensure the rate limiter does not become a bottleneck.
6. Dashboards and alerts. In Grafana visualize: number of rejected requests, violating keys, Redis resource usage. Set up alerts for threshold breaches.
7. Documentation and training. Hand over operations manual: how to add rules, manually disable blocks, analyze logs.

Estimated timelines

Full turnkey implementation: from 5 to 8 weeks depending on API complexity.

How do we guarantee stability?

We have been developing crypto exchange backends for over 5 years. During this time, we have implemented rate limiting systems for projects with a daily audience of >1 million users and peak load >50k RPS. We guarantee that your system will pass security audit and withstand any loads within the agreed capacity. Average infrastructure cost savings due to optimization reach 30%.

Contact us for a free consultation – we will assess your architecture and propose an optimal rate limiting scheme. Request an audit of your current system and receive a 10% discount.

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.