Bitget, THORChain Clash Over Hacker Address Blocking
Bitget asked THORChain to block addresses tied to stolen funds after hackers routed assets through the protocol and into Bitcoin. THORChain declined, citing its permissionless design and reinforcing the tension between exchange recovery efforts and DeFi censorship resistance.
Bitget has pressed THORChain to block wallet addresses linked to a recent hack after stolen assets were routed through the cross-chain protocol and converted into Bitcoin. The exchange’s request quickly sharpened a familiar debate in crypto: whether decentralized infrastructure should intervene when illicit funds move through permissionless rails.
THORChain rejected the appeal, saying its design does not permit censorship or discretionary address blacklisting. The response underscores a core trade-off in decentralized finance, where protocols are built to minimize gatekeeping even when that limits their ability to respond to security incidents.
For Bitget, the episode adds pressure to its recovery and containment efforts. For THORChain, it reinforces a long-standing position that protocol-level neutrality is a feature, not a flaw, even as that stance draws scrutiny when stolen funds are involved.
The dispute arrives as broader market sentiment remains constructive, with the Fear and Greed Index in greed territory. Still, the case is likely to keep attention on exchange security, cross-chain liquidity routes and the practical limits of post-hack remediation in DeFi.
Market Telemetry & Impact
Algorithmic Transparency & E-E-A-T ComplianceAutomated Fact-Checking
This intelligence report is generated and verified by the Squaby Algorithmic Fact-Checking Engine without manual human intervention. It strictly isolates on-chain risk vectors, market liquidity data, and OSINT sentiment streams. All data is processed for institutional clarity and educational purposes only. This content does not constitute financial or investment advice.
Deconstruct Early-Stage Web3 Token Audits & Vesting Cliffs
Learn to evaluate on-chain liquidity locks, contract audit ratings, and founder KYC verifications.