THORChain, the decentralized liquidity protocol that facilitates cross‑chain swaps, has publicly rebuffed a request from the centralized exchange Bitget to block addresses it has flagged as potential hackers. The dispute came to light after a flagged address successfully executed an XRP‑to‑Bitcoin swap on THORChain’s network, demonstrating that the protocol’s filtering mechanism did not prevent the transaction.
Bitget’s request stemmed from concerns that addresses linked to illicit activity could compromise the security of the swap platform. The exchange argued that allowing such addresses to interact with the protocol could expose users to risk. THORChain’s leadership, however, maintained that its open‑source, permissionless design does not support selective blocking, and that any attempt to censor addresses would undermine the protocol’s core principles.
In the wake of the incident, OKX’s Star Xu weighed in on the broader debate. Xu criticized THORChain’s comparison of its security model to that of Bitcoin, suggesting that the two systems operate under fundamentally different assumptions. While Bitcoin relies on a massive, globally distributed network of miners to secure its ledger, THORChain depends on a set of validator nodes and a novel consensus mechanism to safeguard liquidity pools.
The episode highlights the tension between decentralization and regulatory pressure. On one hand, exchanges like Bitget seek to enforce compliance and mitigate risk; on the other, decentralized protocols prioritize openness and resistance to censorship. THORChain’s stance underscores its commitment to maintaining a neutral, non‑censoring environment, even when faced with external demands.
For users, the incident serves as a reminder that cross‑chain swaps involve inherent trust in the underlying protocol’s security. While THORChain’s architecture aims to provide robust protection against malicious actors, the platform’s refusal to block flagged addresses may raise concerns for those who prefer stricter compliance controls.
Ultimately, the dispute illustrates the evolving dynamics between centralized exchanges and decentralized infrastructure, as each navigates the balance between user safety, regulatory expectations, and the foundational ethos of decentralization.