Key Takeaways
- • CoinDCX, India's largest crypto exchange, placed its futures market in "reduce-only" mode, barring traders from opening new positions or increasing existing long or short bets, after a security incident at Binance disrupted a key liquidity provider.
- • CoinDCX confirmed to CoinDesk that the liquidity provider is Binance, though the exchange did not name it publicly in its announcement on X.
- • Deposits, withdrawals and customer funds remain operational and unaffected, according to CoinDCX; no timeline has been given for restoring normal futures trading.
- • Binance reported an estimated $6.3 billion impact from the Oct. 29–30 incident, with early findings pointing to a compromised DevOps engineer's laptop that enabled unauthorized withdrawals; Binance said there was no evidence of private-key leaks.
- • CoinDCX's futures market is small relative to global venues, with combined spot and futures volume of just over $1 million over the past 24 hours per CoinGecko, though it routes significant futures liquidity through Binance order books.
Summary
CoinDCX has temporarily restricted new futures positions following a security incident at Binance, the world's largest cryptocurrency exchange, which disrupted a liquidity provider CoinDCX relies on. In a post on X shortly before publication, CoinDCX said it had placed its futures market in "reduce-only" mode, citing "recent developments impacting a global liquidity provider." A CoinDCX spokesperson subsequently told CoinDesk that the provider was Binance.
Under the restriction, traders cannot open new positions or increase the size of existing long or short bets. They can still add or reduce margin on existing positions, and open orders continue to execute. CoinDCX said deposits and withdrawals are functioning normally and customer funds are safe. The restriction applies only to futures and is described as temporary, though no timeline for a return to normal trading has been provided.
CoinDesk reports that CoinDCX aggregates a significant share of its futures liquidity from large global venues, including Binance, and that its institutional materials describe systems that stream Binance order books for USDT-margined perpetuals. The exchange's futures business is modest by comparison with global platforms such as Binance and Deribit; combined spot and futures volume over the prior 24 hours was just over $1 million according to CoinGecko.
Binance reported a major security incident on Oct. 29–30 with an estimated impact of about $6.3 billion in crypto assets. Early findings pointed to a compromised DevOps engineer's laptop that enabled unauthorized withdrawal transactions, and Binance said there was no evidence of private-key leaks. The episode illustrates how a disruption at a primary liquidity venue can quickly constrain risk-taking on connected platforms even when their own systems and customer balances are not directly affected.
Under the restriction, traders cannot open new positions or increase the size of existing long or short bets. They can still add or reduce margin on existing positions, and open orders continue to execute. CoinDCX said deposits and withdrawals are functioning normally and customer funds are safe. The restriction applies only to futures and is described as temporary, though no timeline for a return to normal trading has been provided.
CoinDesk reports that CoinDCX aggregates a significant share of its futures liquidity from large global venues, including Binance, and that its institutional materials describe systems that stream Binance order books for USDT-margined perpetuals. The exchange's futures business is modest by comparison with global platforms such as Binance and Deribit; combined spot and futures volume over the prior 24 hours was just over $1 million according to CoinGecko.
Binance reported a major security incident on Oct. 29–30 with an estimated impact of about $6.3 billion in crypto assets. Early findings pointed to a compromised DevOps engineer's laptop that enabled unauthorized withdrawal transactions, and Binance said there was no evidence of private-key leaks. The episode illustrates how a disruption at a primary liquidity venue can quickly constrain risk-taking on connected platforms even when their own systems and customer balances are not directly affected.
Go deeper than the headline
Research every firm in this story, track the ones that matter and get the daily briefing — free for 7 days.