THORChain Defends Permissionless Design Amid Stolen Funds Claims
THORChain has rejected criticism from on-chain tracking platform MistTrack over the use of its decentralised cross-chain protocol to move funds allegedly stolen from exchanges including Bybit and Bitget. The protocol said it was saddened by the recent exchange attacks but stressed that THORChain, like Bitcoin, Ethereum and BNB Chain, is decentralised and permissionless. It argued that such protocols cannot unilaterally block transactions or refuse service to specific addresses. THORChain also questioned what responsibility Bitcoin, Ethereum and BNB Chain should bear when they process funds known to be stolen. The response followed a call from Bitget CEO Gracy Chen for THORChain to stop serving attacker-controlled addresses. The dispute highlights the tension between crypto compliance demands and the censorship-resistant design of decentralised infrastructure. Traders may monitor further action from exchanges, blockchain analytics firms and regulators, as any restrictions on cross-chain liquidity could affect token flows and market confidence.
Neutral
The immediate market impact is likely neutral. THORChain’s response does not announce a protocol exploit, token sale or operational shutdown; it mainly restates the network’s permissionless architecture. That limits the direct fundamental effect on RUNE or the wider crypto market. However, the dispute creates short-term reputational and regulatory risk. If exchanges or analytics firms pressure THORChain to block specific addresses, the protocol could face liquidity fragmentation, reduced cross-chain activity or a community dispute over censorship. Similar controversies involving mixers and privacy-focused infrastructure have often produced temporary token volatility when exchanges impose restrictions or regulators intensify scrutiny. In the short term, traders may react to any decision by major exchanges, law-enforcement agencies or THORChain validators, while monitoring cross-chain volumes and RUNE liquidity. Over the long term, the case could influence how decentralised protocols approach sanctions screening, front-end controls and legal risk. A forced move toward permissioned access could weaken the protocol’s core value proposition, while continued unrestricted use could increase compliance pressure. Unless the dispute leads to concrete service restrictions or regulatory action, broader market effects should remain limited.