Running the Exchange · Part 2Liquidity Management

The Zero-Sum Balancing Act

How crypto exchanges manage hundreds of assets against a single risk ceiling in real time, and what it actually takes to keep that balance invisible to the customer.

6 min read📅June 16, 2026📊Liquidity Management⚙️Operations
Raajeev Reddy
Raajeev Reddy

Engineering leader with 15 years leading engineering organizations across blockchain, digital health, and media platforms.

Why this is harder than it looks from the outside

In Part 1, we used a bank analogy to frame the core tension. When 1,000 customers each ask for $1,000,000 at the same time, the local branch cannot serve them from the till. Someone has to go to the central vault, coordinate the release, and move the cash. Hard enough with one currency. Now run that same problem across hundreds of assets simultaneously, on different blockchains, with prices moving in real time, regulatory pools isolating funds by jurisdiction, and no closing bell to pause for reconciliation. That is what liquidity management looks like at a major centralized exchange.

The hot wallet does not hold one asset. It holds hundreds. Each asset has its own per-asset limit and all of them sum to one total ceiling. The real problem is not staying under that ceiling. It is continuously recalibrating each asset’s individual limit so that customer withdrawals for any specific asset are never blocked, even as multiple forces push the balance out of alignment simultaneously and without warning.

The forces that break the balance

Price movement. Bitcoin rises 20% overnight. You have not moved a single coin but your BTC allocation inside the hot wallet is now worth $60M more than it was. The total hot wallet value breaches the ceiling and you must sweep BTC back to cold storage. The compounding problem is that BTC withdrawal demand is also rising because of that same price movement. You now have less BTC in the hot wallet to serve those withdrawals precisely when demand is highest. Recalibrating the per-asset limit for BTC without starving customer withdrawals requires real-time judgment, not a static rule.

Deposit surge.Thousands of customers deposit funds simultaneously during a market rally. Every deposit lands in the hot wallet first before being swept to cold storage. As inflows accelerate across multiple assets at once, the hot wallet balance climbs toward and past the ceiling across several assets simultaneously. Adjusting one asset’s per-asset limit forces a reconsideration of all the others because the total ceiling does not move.

Market activity driven rebalancing.An AI coin spikes on social media. Withdrawal demand for that asset jumps overnight. The exchange needs to increase that asset’s hot wallet allocation immediately to serve those withdrawals without delay. But because of the zero-sum constraint, increasing one asset means reducing another. And it is rarely just one asset in isolation. When one AI coin spikes, correlated assets in the same category often follow. The exchange has to predict that second-order effect and pre-position multiple assets simultaneously before the demand actually arrives. Getting this wrong means customers on a high-activity asset face delays at exactly the moment they are most engaged with the platform. This is where social sentiment signals stop being a nice-to-have and become operationally critical.

Regulatory isolation requirements.Different jurisdictions require that their citizens’ funds be completely segregated from all other customer funds at both the hot wallet and cold wallet level. Not mixed, not pooled, not offset. Fully isolated in dedicated wallets. Canada requires approximately 80% of Canadian citizen funds to be fully isolated from corporate funds, US citizen funds, and all other customer pools. MiCA in Europe requires approximately 90% isolation for European citizen funds. When a new jurisdiction goes live or an existing regulation changes, it triggers a wave of fund movements that have nothing to do with price or deposit volume. The exchange is not running one unified hot wallet. It is running multiple isolated pools in parallel, each with its own ceiling and per-asset limits, governed by different regulatory frameworks simultaneously. A restore needed for the European pool may land at exactly the same moment as a sweep required for the main pool, creating competing demands on the cold wallet signing process with no natural way to prioritize one over the other.

A fifth, smaller factor is over-restore. When pulling funds from a cold wallet address that holds more than needed, the excess moves to the hot wallet and must be swept back immediately. This compounds the problem but is not a primary driver.

Diagram 1 — The Forces That Break the Hot Wallet Balance
Balanced state: all assets within per-asset limitsBTC $300METH $250MUSDC $200MUSDT $150MOther $100MTotal = $1,000M. All per-asset limits in balance.Force 1: BTC rises 20% overnightBTC $360M ▲ETH $250MUSDC $200MUSDT $150MOther $100MTotal $1,060M. BTC must be swept. But BTC withdrawal demand is also rising.Force 2: Deposit surge across multiple assetsBTC $320M ▲ETH $290M ▲USDC $240M ▲USDT $180M ▲Other $100MTotal $1,130M. Multiple assets must be swept simultaneously.Force 3: AI coin spikes. Correlated assets must be pre-positioned.BTC $270M ▼ETH $220M ▼USDC $200MUSDT $150MAI coins $160M ▲Total = $1,000M. BTC and ETH reduced to make room for AI coin pre-positioning.
The real hard problem: It is not just staying under the total ceiling. It is continuously recalibrating the per-asset limit for hundreds of assets in real time, without ever blocking a customer withdrawal on any single asset, while multiple independent forces push the balance out of alignment simultaneously.

How exchanges manage the balance

No single tool solves this. Exchanges layer these approaches incrementally or in parallel, in whatever combination matches their scale and risk appetite.

📊Pattern analysis

The data team analyzes deposit and withdrawal patterns on a weekly cadence. Daily is too human-intensive and rarely shifts the needle enough to justify it. Weekly gives enough signal to catch meaningful changes without drowning the team in noise. The analysis studies which assets spike in bull versus bear cycles, on which networks those spikes form, and how the shape of each spike differs across market conditions. A Bitcoin rally moves differently than a stablecoin surge driven by risk-off behavior. Understanding those shapes is what allows per-asset limits to be set with precision. This process is intentionally human-driven because patterns require interpretation, not just computation.

🤖ML and AI prediction

Machine learning adds a forward-looking layer by predicting threshold breaches before they happen. The inputs go well beyond historical transaction data to include gas price trends across networks, social media sentiment from Twitter and crypto-native communities, and broader market mood signals. When sentiment shifts rapidly around a specific asset, when gas prices climb ahead of a known event, or when institutional chatter signals a large incoming flow, the model flags it early. A human reviews the signal and decides whether to act.

The clearest example of why this matters came during the Bitcoin and Ethereum ETF launches. At Coinbase, I supported the infrastructure that handled that moment. It was the first time we saw billions of dollars move in a single day from institutional and prime customers repositioning around the launches. No historical pattern would have predicted that shape of demand. Social signals, regulatory news feeds, and institutional relationship data all had to work together to give the team enough lead time. Stablecoin flows tell a quieter but equally important story. Large USDC and USDT movements often precede major market shifts as institutions rotate between risk-on and risk-off positions. Tracking those micro movements across chains gives the model a leading indicator that price data alone would miss.

⚠️Institutional curveballs

Even well-tuned models get surprised. Institutional customers sometimes need to move large sums on short notice for reasons entirely unrelated to market conditions. They may be funding a campaign, rebalancing between custodians, or responding to a regulatory deadline. Once a request is verified and risk-assessed, completing it in a few hours is a reasonable and responsible target. For exchanges with deep, trusted relationships, minutes may be achievable when all signals look clean. Seconds is a future state the infrastructure and regulatory frameworks have not yet reached. That is the honest position of the industry today.

🚨Anomaly guardrails

Prediction catches the expected. Guardrails catch everything else. When any asset breaches a threshold outside predicted patterns, automated alerts fire simultaneously across engineering, operations, and finance. All three functions are equal stakeholders in the response. Engineering assesses the technical state. Operations coordinates the restore or sweep. Finance validates the risk exposure. No single function owns the decision. A smaller exchange may run only guardrails and weekly pattern reviews. A larger one may run all approaches in parallel. The right configuration is the one the team can operate and trust under pressure.

Diagram 2 — Anomaly Response: Three Equal Stakeholders
Threshold anomalyAlert fires across all three functionsEngineeringAssesses technical stateOperationsCoordinates restore or sweepFinanceValidates risk exposureAll three are equal stakeholders. No single function owns the anomaly response.

The road to automation

Most exchanges are somewhere between pattern analysis, ML prediction, and active guardrails. Full automation is the north star, but getting there requires surviving enough bull and bear cycles with the guardrails in place to trust the model completely. That trust cannot be shortcut.

1
Manual

Humans monitor and act on every threshold event

2
Pattern analysis

Data team reviews weekly and adjusts limits

3
ML prediction

Models predict breaches. Humans review and act.

4
Guardrails

Anomaly alerts fire across engineering, ops, and finance

5
Automation

System acts autonomously within tested guardrails

There is also a risk in automation that is rarely discussed openly. If a hot wallet is compromised during a period of fast automated cold-to-hot flows, funds can drain before the system registers what is happening. Once a transaction is confirmed on chain, it is confirmed. There is no rollback and no mechanism to claw back funds unless a smart contract was pre-positioned to protect against that scenario. In the fiat world, fund recovery is difficult but possible through institutional coordination. On chain, that capability is years away and depends on regulatory frameworks maturing across multiple governments simultaneously. Prevention is the only real defense, which is exactly why earning the right to flip the automation switch takes as long as it does.

Next in this series: The coin selection problem. How exchanges decide which wallet addresses to use when processing withdrawals, why the wrong choice locks funds and blocks transactions, and how the solution looks surprisingly similar to garbage collection in software engineering.
Raajeev Reddy
Raajeev Reddy

Engineering leader with 15 years leading engineering organizations across blockchain, digital health, and media platforms.

← All writing