TLDR
Binance is tightening sanctions compliance by blocking transactions with HTX, EXMO and other platforms in line with new EU, UK and US restrictions.
- From 23 Aug, Binance will hold or block transfers involving 16 named platforms, closely mirroring recent EU Russia sanctions and US Treasury designations.
- Tokens from these platforms can still trade on Binance, but moving funds between Binance and those services becomes risky or impossible for many users.
- The move reflects growing regulatory pressure on Binance, and more upstream filtering of counterparties is likely as sanctions and AML rules harden.
Deep Dive
1. What Binance Is Doing
Binance has announced it will stop processing transactions involving HTX (formerly Huobi), EXMO and 10 other platforms from 23 August, with earlier cutoffs already applied to five smaller services such as Shelbit and Aban Tether Exchange, citing recent regulatory developments. One detailed recap lists the affected names and notes that attempted transfers after the date may be held for compliance review and trigger wallet restrictions.
The list closely matches entities in the European Unions latest Russia sanctions package, which bans transactions with 14 crypto-related service providers suspected of helping Russia evade restrictions, plus Shelbit and Aban Tether, which the US Treasury sanctioned on 7 Aug for Iran-linked activity. Multiple reports highlight that Binances cutoff timing and naming aligns with the EU regulation and US actions rather than an independent blacklist it devised itself. Coverage of the sanctions package makes that link explicit.
2. Impact On Users And Flows
Crucially, this is not a blanket delisting of coins on Binance. Spot trading for related tokens can continue, but users are being warned that transfers to or from the named platforms may be frozen and reviewed, with some wallets restricted while checks are carried out, according to the announcement cited by Cointelegraph.
This mainly hits people who move funds between venues (for arbitrage, OTC flows or access to local on?ramps) and brokers that use multiple exchanges as counterparties. EXMO has indicated it will shut down rather than fight its designation, while HTX is contesting sanctions and negotiating with UK and EU authorities, creating further uncertainty about cross?platform flows.
If you use HTX, EXMO or the other named services, assume transfers via Binance may be disrupted after 23 August and check alternative routes or venues ahead of time.
3. Regulatory Context And Whats Next
Binance is already under an intensive compliance monitor after paying about 4.3 billion dollars in a 2023 US settlement over AML and sanctions violations, with senators now asking for updates on its monitorship; that history is referenced in recent analysis. Aligning its counterparty filters with EU and US lists helps demonstrate proactive compliance to regulators who expect large exchanges to block sanctioned entities upstream.
More broadly, the EUs travel?rule and sanctions regimes, plus UK and US enforcement, are pushing exchanges to treat sanctions screening as a core part of market access. If additional platforms or wallet clusters emerge in future sanctions packages, similar blocks are likely. Users should watch for: new names added to Binances restricted list, any expansion beyond Europe?focused measures, and how HTXs and other platforms legal challenges to sanctions resolve.
Confidence: high multiple independent outlets report the same Binance notice, dates and sanction-linked lists.
Conclusion
Binances decision to block transactions with sanctioned platforms is less about reshaping its token listings and more about aligning its operations with increasingly strict EU, UK and US sanctions and AML rules. The practical effect is to choke off cross?exchange and on?ramp flows involving those services, while keeping trading inside Binance largely intact. For crypto users and brokers, the signal is clear: sanctions compliance is becoming a first?order constraint on how and where funds can move, and major venues will increasingly enforce those constraints at the gateway.
