Thorchain, which refused to block the Bitget hacker's address, has no individual transaction function.

THORChain declined Bitget’s request to block transactions from the exchange’s hacker-linked addresses, saying the protocol cannot filter individual addresses or single swaps because its vaults are jointly managed by validators. The dispute follows a May 15 exploit that drained $10.7 million from a THORChain vault by abusing a GG20 signing vulnerability, prompting automated checks to halt transactions and signing on some chains and node operators to pause the entire network for about five weeks. THORChain is a cross-chain swap protocol whose shared vault model means any exclusion rule would have to apply network-wide rather than per transaction. The standoff matters because it highlights the tension between decentralized infrastructure and exchange-led recovery efforts after hacks. What to watch next is whether Bitget pursues alternative recovery routes or pushes for a protocol-level filtering mechanism.