THORChain Rejects Bitget's Request to Freeze Hacker Addresses
THORChain declined Bitget's request to block addresses tied to the exchange's $387.5 million September breach, allowing the attacker to swap approximately $6 million in ETH for Bitcoin across 27 transactions. The decision underscores the protocol's resistance to censorship, even in response to exchanges seeking to halt stolen-fund movement.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
The Swaps and Bitget's Failed Request
On-chain analysis reviewed by CoinDesk identified 27 successful swaps totaling roughly 2,390 ETH converted to 75.2 BTC—valued at approximately $6 million to $6.3 million depending on the time of conversion—routed through THORChain after Bitget requested the protocol block the attacker's addresses. Bitget, which suffered a $387.5 million theft on September 24, explicitly asked THORChain to prevent the hacker from using its cross-chain routing services to launder the stolen funds.
THORChain rejected the freeze request. The protocol's operators did not publicly state a reason for the denial, but the decision aligns with THORChain's design principle: it operates as a permissionless liquidity protocol without centralized control points that can selectively exclude users or addresses.
What This Reveals About Protocol Design Trade-offs
The incident illustrates a core tension in decentralized finance. Permissionless protocols resist capture and censorship but also cannot distinguish stolen funds from legitimately held assets once they enter the network. THORChain's refusal to freeze addresses is consistent with how other decentralized systems respond to similar requests—Ethereum nodes do not halt transactions tied to flagged addresses, and Bitcoin miners do not reverse confirmed blocks based on law enforcement requests alone.
Bitget and other centralized exchanges retain the ability to delist assets or refuse to accept Bitcoin or ETH received from flagged sources, adding a friction layer for the attacker's final exit to fiat. Whether that barrier will prove sufficient remains unclear.
Why It Matters
For Traders
Cross-chain protocols like THORChain will not halt transactions for regulatory or law enforcement requests, so traders relying on these routes for asset movement should plan accordingly.
For Investors
The event reinforces that decentralized protocol operators face mounting pressure to adopt freezing mechanisms—a design shift that could fragment the ecosystem but also expose protocols to regulatory liability.
For Builders
Permissionless DEXs and routers must anticipate that stolen-fund requests will increase; defensible policy responses now matter as much as technical architecture.
This article is for information only and is not financial advice. Read the full disclaimer.
