Noah

Request

View

THORChain

<p>The decentralized protocol says its permissionless design does not allow it to block wallets, reigniting debate over crypto's censorship-resistance principles.</p>
<p>Bitget disclosed a security breach that resulted in losses reported at $387.5 million. Following the hack, the exchange asked THORChain to block wallets connected to the attacker's funds. THORChain declined the request. The protocol said it does not censor transactions by design, framing the refusal as a matter of principle rather than technical limitation.</p>
<p>THORChain operates as a decentralized cross-chain liquidity network. It allows users to swap assets across different blockchains without relying on a centralized custodian. Its architecture depends on a distributed set of node operators who validate transactions according to protocol rules, not on any single company that can unilaterally intervene. That structure is central to how the network markets itself to users seeking alternatives to custodial exchanges.</p>
<p>The dispute highlights a recurring tension in decentralized finance. Exchanges and victims of hacks often want fast intervention to freeze or trace stolen assets before they can be laundered. Permissionless protocols, by contrast, are built specifically to avoid the kind of centralized control that would make such intervention possible. THORChain's response suggests it views blocking funds as incompatible with its core design, regardless of the circumstances prompting the request.</p>
<p>This is not the first time THORChain's approach to fund flows has drawn scrutiny. The network has previously been identified as a route used to move funds following other major hacks, drawing criticism from security researchers and exchanges alike. Supporters of the protocol argue that criticizing it for enabling fund movement misunderstands the nature of permissionless infrastructure, comparing it to blaming a public road for the actions of a getaway driver.</p>
<p>Critics take a different view. They argue that protocols with enough coordination among validators or node operators have some capacity to respond to clear cases of theft, even without full centralized control. They see THORChain's refusal as a missed opportunity to limit harm to hack victims, rather than a strict technical impossibility.</p>
<p>The debate now touches on broader questions facing the crypto industry. Regulators have increasingly pressed exchanges and infrastructure providers to demonstrate they can respond to illicit fund flows. Bitget's request, and THORChain's rejection of it, illustrate the gap between what regulators may expect and what genuinely decentralized protocols say they are able to deliver.</p>
<p>Bitget has not disclosed full details of how the hack occurred or what remediation steps it is taking for affected users. THORChain has not indicated any plan to reconsider its position in this case.</p>
<h2 id="market-impact">Market Impact</h2>
<p>The immediate market impact centers on confidence in Bitget's security posture and on how exchanges more broadly plan to respond when stolen funds move through decentralized protocols. A loss of $387.5 million is significant enough to draw attention to Bitget's risk controls and could affect user trust in the exchange in the near term.</p>
<p>For THORChain, the episode may sharpen scrutiny of RUNE and the network's role in facilitating cross-chain swaps, particularly among exchanges and compliance-focused market participants. Continued association with laundering routes after major hacks could influence how other platforms and regulators treat THORChain-linked liquidity going forward, even as the protocol maintains its refusal is consistent with its founding design principles.</p>
<p>The standoff between Bitget and THORChain underscores an unresolved question for decentralized finance: whether permissionless networks can, or should, act when their infrastructure is used to move stolen funds.</p>
<h2 id="frequently-asked-questions">Frequently Asked Questions</h2>
<h3 id="what-happened-to-bitget">What happened to Bitget?</h3>
<p>Bitget disclosed a hack resulting in losses reported at $387.5 million and asked THORChain to block wallets linked to the attacker.</p>
<h3 id="why-did-thorchain-refuse-bitget-s-request">Why did THORChain refuse Bitget's request?</h3>
<p>THORChain said its network does not censor transactions by design, framing intervention as incompatible with its permissionless, decentralized structure.</p>
<h3 id="has-thorchain-faced-similar-requests-before">Has THORChain faced similar requests before?</h3>
<p>The network has previously been identified as a route used to move funds after other major hacks, which has drawn criticism from security researchers and exchanges.</p>
<h3 id="what-is-the-broader-significance-of-this-dispute">What is the broader significance of this dispute?</h3>
<p>It highlights the tension between decentralized protocols' censorship-resistant design and calls from hack victims and regulators for intervention against illicit fund flows.</p>
<p>Originally reported by <a href="https://altcoingordon.com/thorchain-declines-bitgets-request-freeze-funds-387-5m-hack/" rel="noopener noreferrer nofollow">AltcoinGordon</a>, written by Noah Sullivan. Republished with permission.</p>
<p><a href="https://altcoingordon.com/thorchain-declines-bitgets-request-freeze-funds-387-5m-hack/" rel="noopener noreferrer nofollow">View the original on AltcoinGordon →</a></p>
<p>The post <a href="https://thecoinrise.com/thorchain-declines-bitgets-request-to-freeze-funds-after-387-5m-hack/" rel="noopener noreferrer nofollow">THORChain Declines Bitget’s Request to Freeze Funds After $387.5M Hack</a> appeared first on <a href="https://thecoinrise.com/" rel="noopener noreferrer nofollow">TheCoinrise.com</a>.</p>

THORChain Declines Bitget’s Request to Freeze Funds After $387.5M Hack

Table of Contents

TheCoinrise Media

Other articles published on Sep 28, 2026

Join our free newsletter for daily crypto updates!