THORChain and Bitget: What the Power to Pause Means for Decentralization
Evidence at a glance: Bitgets loss figure comes from its September 25 statement. The dispute is described in September 27 reporting; technical claims about halt controls are checked against THORChain documentation. The Bitget hack has created a much larger argument than whether one protocol should blacklist one wallet. It has exposed a core distinction between permissionless operation and the technical ability to intervene. Bitget said that approximately $387.5 million had been transferred to attacker-controlled addresses during its September 24 security incident. Its September 25 update said the upward revision reflected more complete accounting, not additional theft. Bitgets statement September 27 reporting described a dispute over routing funds associated with the incident through THORChain. It reported that Bitget sought intervention, THORChain defended permissionless operation, and OKX founder Star Xu challenged the comparison with Bitcoin. These positions are attributed to that reporting. Dispute coverage A separate, verifiable technical question is whether THORChain has operational controls for emergencies. The protocols own documentation confirms that such controls exist. The dispute raises a concrete governance question: If a protocol can stop, but chooses not to stop, is that censorship resistance — or a governance decision?THORChain Is Not Architecturally the Same as Bitcoin Bitcoins base-layer consensus does not require a









