{"id":3033,"date":"2026-10-30T23:15:14","date_gmt":"2026-10-30T23:15:14","guid":{"rendered":"https:\/\/smartcryptosecurity.com\/?p=3033"},"modified":"2026-10-30T23:15:14","modified_gmt":"2026-10-30T23:15:14","slug":"the-great-defi-divide-thorchain-under-fire-and-near-intents-intervenes-amid-387-5m-bitget-hack-fallout","status":"publish","type":"post","link":"https:\/\/smartcryptosecurity.com\/?p=3033","title":{"rendered":"The Great DeFi Divide: THORChain Under Fire and NEAR Intents Intervenes Amid $387.5M Bitget Hack Fallout"},"content":{"rendered":"<p>The crypto industry is grappling with a profound ideological rift following the massive security breach that struck cryptocurrency exchange Bitget on September 24. In the wake of the exploit, which saw a staggering $387.5 million in digital assets stolen, the illicit funds began rapidly moving across various blockchain networks. A significant portion of this capital targeted decentralized cross-chain swap platforms, bringing long-simmering debates regarding protocol neutrality, moral responsibility, and the true meaning of permissionless technology directly into the spotlight.<\/p>\n<p>The flashpoint of this controversy centers on how different decentralized finance (DeFi) architectures respond to illicit activity. When the stolen funds began traversing THORChain, Bitget Chief Executive Gracy Chen publicly appealed to the decentralized liquidity protocol, urging it to refuse service to addresses linked to the attackers. &quot;The industry is watching,&quot; Chen warned in a public statement shared on social media. <\/p>\n<p>Yet, THORChain flatly refused to intervene. This refusal immediately ignited a furious debate between stakeholders who believe blockchain protocols bear a moral obligation to block stolen funds and protect the broader ecosystem, and those who hold the traditional cypherpunk ideals of decentralized, censorship-resistant technology as sacred. <\/p>\n<p>Having previously watched validators and users observe as the Bybit hackers funneled $1.2 billion through the protocol, the stance of THORChain\u2019s core contributors has become glaringly transparent. Boone Wheeler, a protocol contributor, explained the architectural reality to reporters, stating that a truly permissionless system is inherently blind to the origin of transactions. &quot;A truly permissionless protocol can do nothing when it encounters known stolen funds \u2014 it is blind to their provenance,&quot; Wheeler said. &quot;If THORChain were able to block specific stolen funds, it would not be permissionless.&quot;<\/p>\n<figure class=\"article-inline-figure\"><img decoding=\"async\" src=\"https:\/\/s3-images.ctmedia.io\/media\/article-covers\/2026\/10\/01M3V8TZXTY569YW4G499PZ1BJ\/magazine-bi-weekly-cybersecurity2.jpg\" alt=\"Furious debate about THORChain vs NEAR shows idealism has limits\" class=\"article-inline-img\" loading=\"lazy\" \/><\/figure>\n<h3>Where Does Permissionlessness End?<\/h3>\n<p>Critics, however, have been quick to point out apparent contradictions in this hardline stance. Skeptics argue that THORChain has not always been quite so strictly idealistic. In May, validators voted to halt the entire chain after an automated system triggered an emergency shutdown following an exploit that drained over $10 million from one of the protocol\u2019s vaults. <\/p>\n<p>This duality has created a contentious environment where the definition of decentralization is constantly tested by real-world security crises. In stark contrast to THORChain\u2019s hands-off approach, NEAR Intents\u2014a cross-chain transaction competitor\u2014chose to actively intervene. Its automated security layer, known as SHIELD, successfully identified more than $50 million in attempted transaction flows tied to the Bitget incident. During execution, the system managed to halt $503,000, though approximately $166,000 successfully passed through the protocol before it could be intercepted. <\/p>\n<p>Furthermore, NEAR opted to waive its share of Bitget\u2019s recovery bounty. Alex Shevchenko, the general manager of NEAR Protocol, defended the platform&#8217;s architectural balance. &quot;NEAR Protocol is permissionless: anyone can build on it, transact on it, and become a validator,&quot; Shevchenko noted, adding that while no one needs permission to hold assets or deploy contracts, &quot;that does not mean every application built on NEAR must process every request.&quot;<\/p>\n<p>Despite this nuance, NEAR Intents has also come under heavy fire from purists who argue that any form of intervention demonstrates that the platform is not genuinely permissionless or decentralized. Critics suggest that exercising intervention capabilities\u2014even through automated defenses\u2014opens the door to expectations that the network should exert similar controls more broadly. <\/p>\n<p>However, legal experts suggest that the automated nature of these defenses provides a distinct operational safeguard. Yuriy Brisov, a crypto attorney, noted that because systems like SHIELD operate without a manual compliance team or human controllers making subjective decisions, they may still fall securely within the legal protections typically afforded to decentralized protocols. &quot;There is no compliance team, people who sit there and control the operation manually,&quot; Brisov observed. &quot;This is a smart solution, and that\u2019s what we recommend to all the DeFi companies.&quot;<\/p>\n<figure class=\"article-inline-figure\"><img decoding=\"async\" src=\"https:\/\/s3-images.ctmedia.io\/media\/content\/2026\/10\/01M3VAMS85EN9HX0NRQTRJEF2M\/gracy.png\" alt=\"Furious debate about THORChain vs NEAR shows idealism has limits\" class=\"article-inline-img\" loading=\"lazy\" \/><\/figure>\n<h3>Permissionless Does Not Necessarily Mean Neutral<\/h3>\n<p>Bitget\u2019s Gracy Chen acknowledged that while different protocols operate under varied architectures, governance models, and technical capabilities, a critical distinction exists between maintaining neutral permissionless infrastructure and actively facilitating the movement of known illicit funds. Pointing to the proactive measures taken by NEAR Intents, Chen expressed appreciation for their response and confirmed that Bitget would pursue appropriate legal and recovery procedures for those assets.<\/p>\n<p>Bitget\u2019s overarching goal following the disaster is to understand what is technically and governance-wise possible when stolen assets are definitively identified, questioning whether the broader digital asset industry can forge collaborative frameworks to combat systemic exploits. &quot;Permissionless infrastructure does not necessarily mean there can be no mechanisms for detecting and responding to known illicit flows,&quot; Chen argued.<\/p>\n<p>Complicating THORChain\u2019s absolute defense of its neutrality is the undeniable reality that the protocol has previously demonstrated an ability to intervene during critical emergencies. Post-mortem reports following the May exploit revealed that the protocol is intentionally programmed to automatically halt activity when internal solvency checks detect an insolvency event. During such moments, node operators can leverage broader emergency controls to temporarily pause trading, signing, and overall network operations.<\/p>\n<p>Wheeler maintained that a firm consensus exists among THORChain\u2019s decentralized network of nodes regarding the paramount importance of remaining permissionless. Halts, he emphasized, are strictly reserved for active technical issues or structural threats to the protocol itself. Furthermore, Wheeler highlighted that the network simply possesses no built-in functionality to screen individual addresses or specific transactions, framing this omission as a deliberate design choice intended to ensure true permissionlessness.<\/p>\n<h3>NEAR Intents Provides a Contrasting Model<\/h3>\n<p>While THORChain positions itself at the uncompromising, cypherpunk end of the spectrum, the NEAR ecosystem occupies a more pragmatic middle ground, balancing open participation with active financial integrity measures. Shevchenko explained that the SHIELD security layer is specifically engineered to apply targeted controls to supported flows using real-time on-chain data, internal anti-money laundering databases, and intelligence provided by third-party risk analysis firms.<\/p>\n<figure class=\"article-inline-figure\"><img decoding=\"async\" src=\"https:\/\/s3-images.ctmedia.io\/media\/content\/2026\/10\/01M3WZQ7BNP45PRT1A766YS38X\/omid.jpg\" alt=\"Furious debate about THORChain vs NEAR shows idealism has limits\" class=\"article-inline-img\" loading=\"lazy\" \/><\/figure>\n<p>&quot;SHIELD not only protects NEAR Intents but the whole cross-chain ecosystem it serves,&quot; Shevchenko said, noting that major hacks drain vital capital and user trust from the wider on-chain economy. By actively screening for stolen funds and restricting money laundering channels, proponents argue that such systems safeguard the long-term health of the blockchain space. The efficacy of this AI-based defense was further demonstrated when SHIELD identified suspicious behavior behind a subsequent Omni deposit-withdrawal exploit totaling $3.8 million, prompting an immediate halt to the activity.<\/p>\n<p>For Bitget, the ideal path forward involves ecosystem-wide cooperation wherever technical and legal avenues allow. Chen suggested that such collaboration could encompass transaction tracing, information sharing, freezing assets where underlying infrastructure permits, and supporting formal law enforcement recovery operations.<\/p>\n<h3>The Cost of Drawing the Line<\/h3>\n<p>Conversely, ardent libertarians and foundational cypherpunks argue that compromising on permissionlessness introduces catastrophic systemic risks. Jo\u00ebl Valenzuela, head of business development for Dash, insists that true permissionless protocols cannot afford to draw arbitrary lines when stolen funds are identified. &quot;Permissionless protocols, quite frankly, should not draw the line anywhere when stolen funds are identified, because being able to do so at all makes them permissioned,&quot; Valenzuela stated.<\/p>\n<p>While conceding that watching stolen funds move freely is deeply painful for victims, Valenzuela warned that allowing protocols to selectively intervene opens a dangerous Pandora\u2019s box that could eventually facilitate the censorship of innocent users. Instead, he argued that centralized and high-level financial entities holding billions of dollars in custody must drastically harden their own security measures, viewing decentralized exchanges as the inevitable evolutionary path forward.<\/p>\n<p>Max Shannon, a senior research associate at Bitwise Europe, noted that formative protocols like THORChain and NEAR are still actively earning market trust, making their respective stances on hack proceeds a critical part of their brand identity. Shannon predicted that THORChain\u2019s refusal to block funds will likely result in more money laundering activity migrating away from NEAR Intents and toward THORChain. <\/p>\n<figure class=\"article-inline-figure\"><img decoding=\"async\" src=\"https:\/\/s3-images.ctmedia.io\/media\/content\/2026\/10\/01M3VAHCRJFHTT1E168773CAGB\/tc1.png\" alt=\"Furious debate about THORChain vs NEAR shows idealism has limits\" class=\"article-inline-img\" loading=\"lazy\" \/><\/figure>\n<p>&quot;Credible neutrality at all costs,&quot; Shannon observed, remains a foundational cypherpunk ideal championed by a vocal minority of crypto builders and users. &quot;They rarely ask why it is valuable, when it is valuable, or what it costs. This is the core difference between NEAR Intents and THORChain.&quot;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The crypto industry is grappling with a profound ideological rift following the massive security breach&#8230;<\/p>\n","protected":false},"author":23,"featured_media":3032,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[418],"tags":[560,1911,416,1644,2568,2566,2272,365,886,2567,428,424,5,427,425],"class_list":["post-3033","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-defi-security","tag-amid","tag-bitget","tag-defi","tag-divide","tag-fallout","tag-fire","tag-great","tag-hack","tag-intents","tag-intervenes","tag-near","tag-protocols","tag-security","tag-thorchain","tag-yields"],"_links":{"self":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3033","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3033"}],"version-history":[{"count":0,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3033\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/media\/3032"}],"wp:attachment":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}