CoinDCX Limits Futures Trading After Binance Security Breach Disrupts Liquidity

India’s largest crypto exchange, CoinDCX, has temporarily restricted new futures positions following a significant security incident at a major global liquidity provider. The exchange placed its futures market into a “reduce-only” mode, meaning traders cannot open new positions or increase the size of existing long or short bets.

Existing positions remain manageable: users may add or remove margin on their trades, and open orders will continue to execute. CoinDCX emphasized that deposits and withdrawals are functioning normally and that customer funds remain secure.

Why the change was made

CoinDCX cited “recent developments impacting a global liquidity provider” as the reason for the precautionary measure. Although the provider was not named in the initial announcement, CoinDCX later confirmed to media that the disruption was related to Binance. The move illustrates how disturbances at a central liquidity venue can constrain risk-taking across connected platforms—even when those platforms’ internal systems and balances are not directly compromised.

How it affects traders and liquidity

The restriction is limited to futures trading and is temporary; no timeline for resuming normal operations has been provided. CoinDCX sources a meaningful portion of its futures liquidity from large international venues, including Binance, streaming order books for USDT-margined perpetuals and routing activity accordingly. That dependency helps explain the swift precaution.

Scale and context

While CoinDCX participates in both spot and futures markets, its combined 24-hour volume is relatively modest compared with global leaders like Binance and Deribit—reportedly just over $1 million in the most recent 24-hour snapshot per CoinGecko. Nonetheless, the exchange’s action highlights broader market contagion risks.

About the Binance incident

Binance, the world’s largest cryptocurrency exchange, disclosed a major security incident on Oct. 29–30 that impacted roughly $6.3 billion in crypto assets. Early findings pointed to a compromised DevOps engineer’s laptop that permitted unauthorized withdrawals; Binance stated there was no evidence of private-key leakage. Read all of CoinDesk’s coverage of the Binance hack here.