THORChain Denied Responsibility for Bitget Theft Funds
The decentralized protocol argued its permissionless architecture precludes intervention in illicit transfers.
Updated on Sept. 27, 2026 in Cybersecurity
Live Poll
Should decentralized finance protocols block transactions involving stolen funds?
THORChain has rejected responsibility for processing funds linked to a theft from the exchange Bitget. The protocol maintains that its design structure functions like Bitcoin, Ethereum, and BNB Chain.
Why it matters
The dispute highlights the friction between decentralized, permissionless networks and the demand for exchange-level intervention during security incidents. THORChain asserts that as a trustless protocol, it operates without the central authority required to block specific transactions.
THORChain underwent a 39-day service suspension following a prior security incident. The protocol maintains that its permissionless architecture functions identically to Bitcoin, Ethereum, and BNB Chain, preventing centralized control over asset flows.
The players
THORChain
A decentralized, permissionless cross-chain liquidity protocol that facilitates asset swaps without central oversight.
Bitget
A cryptocurrency exchange that recently reported a theft of funds from its platform.
The details
THORChain operates as a decentralized, permissionless protocol, a system where transactions occur without a central intermediary or gatekeeper. Community members have challenged this defense by citing the network's previous 39-day service suspension, which demonstrated an ability to halt operations following a prior attack. The protocol counters that its current architecture is designed to function fundamentally as a trustless environment for cross-chain liquidity.
Timeline
The network suspended services for 39 days in the past.
THORChain rejected responsibility for the Bitget theft transfers in September 2026.
The Tech Race
This conflict sits at the center of the ongoing struggle to define decentralized governance versus regulatory necessity. It updates the precedent set by the protocol's 39-day service suspension in 2021, marking a shift toward strict adherence to permissionless design.
Users interacting with decentralized liquidity protocols should note that transaction finality is governed by code rather than centralized recovery mechanisms. This incident reinforces that assets moved through permissionless rails remain beyond the control of the underlying network.
The takeaway
The incident demonstrates the real-world implications of prioritizing permissionless architecture over custodial control. Observers should track whether the community continues to demand emergency intervention capabilities in future protocol governance votes.
Further reading
For more on how decentralized protocols handle network security, visit the Cybersecurity section.
Live Poll
Should decentralized finance protocols block transactions involving stolen funds?
