Furious debate about THORChain vs NEAR tests crypto ideals
The furious debate about THORChain centers on Bitget’s roughly $387.5 million hack recovery fight. THORChain refused to block attacker-linked swaps, while rival NEAR Intents halted hundreds of thousands in flows via SHIELD. The clash asks whether permissionless protocols must never intervene when stolen funds are identified. That split now defines a wider industry argument over ideals versus practical recovery, as covered across Fintech & Crypto Alerts.
Key Takeaways
- After Bitget’s Sept. 24 hack, some of the roughly $387.5 million in stolen funds moved toward THORChain cross-chain swaps.
- THORChain refused CEO Gracy Chen’s appeal to deny attacker-linked addresses, citing true permissionlessness.
- NEAR Intents’ SHIELD flagged more than $50 million in attempted Bitget-linked flows, stopping $503,000 while $166,000 passed.
- Critics note THORChain halted itself in May after a vault exploit drained over $10 million, complicating its non-intervention stance.
- Observers warn blocked flows may simply migrate to protocols that will not screen stolen funds.
What sparked the furious debate about THORChain?
Bitget was hacked on Sept. 24. Stolen funds quickly began moving across chains, with some headed to THORChain, a decentralized cross-chain swaps platform.
Chief executive Gracy Chen publicly asked the platform to refuse service to attacker-linked addresses, saying the industry was watching. THORChain refused. According to Cointelegraph Magazine, the refusal reignited a fight between moral-duty blockers and cypherpunk defenders of permissionless tech.
THORChain had already watched Bybit hackers funnel $1.2 billion through the protocol. Developer Boone Wheeler said a truly permissionless system is blind to provenance and cannot block specific stolen funds without ceasing to be permissionless.
How did NEAR Intents respond differently?
NEAR Intents, a cross-chain competitor, intervened. Its automated SHIELD layer identified more than $50 million in attempted flows linked to the Bitget incident, stopped $503,000 during execution, and said $166,000 still passed through.
NEAR also waived its share of Bitget’s recovery bounty. General manager Alex Shevchenko argued the base protocol remains permissionless, but applications need not process every request. SHIELD used public onchain data plus internal AML signals and third-party intelligence.
Crypto lawyer Yuriy Brisov said the automated design—with no manual compliance team—could still fit protections often associated with decentralized protocols. Chen said Bitget appreciated NEAR’s response and would pursue legal and recovery steps for those assets.
Does permissionless tech mean never intervening?
Chen drew a line between permissionless infrastructure and facilitating known stolen funds. She said detection and response mechanisms can still exist when illicit flows are identified.
Critics undercut THORChain’s absolutism by pointing to May, when validators halted the chain after an automated solvency trigger during an exploit that drained over $10 million from a vault. Wheeler countered that node consensus supports permissionlessness and that halts are only for active protocol problems, with no address-screening tooling by design.
Dash’s Joël Valenzuela argued that any ability to block stolen funds makes a protocol permissioned and risks broader censorship. Bitwise Europe’s Max Shannon said refusing to process hack proceeds is a sound stance for protocols still earning trust, and that laundering flows may shift from NEAR Intents toward THORChain.
The Bitget episode shows idealism has a price: choose non-intervention and risk becoming a preferred exit ramp, or intervene and face charges of abandoning decentralization.