THORChain, a decentralized trade, is being criticized as to the way it handles funds linked to main crypto exploits. The state of affairs got here into the image when Bitget CEO, Gracy Chen requested the decentralized trade to cease processing swaps from publicly recognized attacker addresses. Chen’s feedback elevate a easy query about whether or not a permissionless cross-chain protocol ought to block wallets which might be linked to a identified hack from transferring funds by way of its community.
THORChain, nonetheless, has pushed again as we speak, September 28, 2026, in an X publish. In line with the stated publish, the community states that its emergency halt is designed to guard the protocol throughout a safety incident, however it isn’t a software for selectively freezing particular person funds or blocking particular swaps. Furthermore, in line with a publish by Michael Perklin, pausing the community and stopping one recognized pockets are two completely different actions below the decentralized trade’s design.
Bitget Asks THORChain to Block Attacker Addresses
Bitget CEO Gracy Chen stated the trade’s attacker addresses are publicly listed and actively tracked. Additionally they formally requested THORChain to refuse service to these addresses. Gracy Chen argued that decentralization shouldn’t be used as a justification for facilitating transactions involving funds identified to be stolen. She commented that the crypto area of interest is watching how THORChain responds to the state of affairs and questioned what accountability the protocol ought to have when it’s conscious that funds originate from a significant hack.
The remarks adopted one other safety incident involving Bitgetwith funds linked to the Bitget exploiter reportedly being despatched by way of the THORChain for asset swaps and cross-chain transfers. Gracy Chen pointed to the sooner $1.6 billion Bybit hack, saying that just about $1.2 billion in stolen funds was allegedly traced by way of THORChain as attackers moved between chains. Bitget argues that the attacker addresses are already publicly recognized and being tracked by exchanges, blockchain safety companies, AML companies, and different members throughout the cryptocurrency area of interest.
Towards this backdrop, Chen questioned whether or not THORChain will proceed offering swaps involving these addresses. The actual downside just isn’t merely whether or not THORChain can establish these addresses. As an alternative, Bitget is asking what permission its protocol ought to take after addresses related to stolen funds have been publicly recognized.
Bitget’s request additionally emphasizes the problems of containing stolen crypto as soon as attackers start transferring property throughout a number of blockchains. With this cross-chain infrastructure can present instruments between completely different networks, exchanges and safety companies are more and more centered on motion monitoring of exploited hyperlink funds after main crypto hacks. For Bitget, the problem is due to this fact not solely whether or not the attacker addresses are identifiable, however whether or not protocols and processes at transactions ought to take additional measures as soon as these hyperlinks are publicly out.
THORChain Defines Its Position in Dealing with Stolen Funds
With as we speak’s publish, THORChain’s is explaining why a community halt is a crucial safety mechanism supposed to safeguard the protocol fairly than a software for freezing instruments or particular person swaps. Regardless of the 2026 exploit that resulted in $10.7 million being stolen from liquidity swimming pools, the attackers’ addresses weren’t blacklisted and had been due to this fact not restricted from swapping on .
The community is described as permissionless and created to not censor transactions. It characterizes THORChain as a impartial public good, reflecting the argument that blocking particular addresses would battle with its decentralized design and a network-wide halt can be utilized as an emergency response to safeguard the protocol, whereas blocking explicit addresses would present a special type of intervention.
Bitget’s remarks concentrate on the recurrent motion of funds linked with identified exploits. Chen argued that if attackers can repeatedly use THORChain to maneuver property throughout networks, together with swaps corresponding to ETH to BTC, the trade wants to think about what accountability the protocol ought to have when dealing with publicly recognized stolen funds.
The disagreement due to this fact emphasizes a wider stress between permissionless infrastructure and intervention in response to legal exercise, Bitget is looking for motion towards particular addresses whereas THORChain’s said design rules spotlight neutrality and resistance to censorship.
