THORChain Swap Recovery Brings Major Networks Back Online
The THORChain swap recovery is underway after a technical problem forced the cross-chain protocol to pause activity across several networks.
In its November 4 update, THORChain said swaps had resumed on networks including Bitcoin, Ethereum, Litecoin and Dogecoin following the release of version 3.21.1. The project listed BNB Smart Chain, Cosmos Hub and Solana as still halted at the time.
That is a meaningful improvement from the weekend, when the protocol paused multiple routes while developers investigated an erroneous refund. But the recovery was not complete: THORChain also said some active nodes had yet to install the update, which could affect swap performance.
As covered in Bitnxt’s earlier report on the THORChain halt, the incident began with a discrepancy in an Ethereum vault—not with Bitcoin or Ethereum themselves shutting down.
Which THORChain Networks Were Back Online?
THORChain’s November 4 announcement listed the following as available for trading:
Status in THORChain’s update | Networks or native asset |
|---|---|
Trading resumed | Avalanche, Base, Bitcoin Cash, Bitcoin, Dogecoin, Ethereum, Litecoin, THORChain’s native RUNE, Tron, XRP Ledger and Zcash |
Still halted | Cosmos Hub, BNB Smart Chain and Solana |
The count can be confusing. The list of 11 available entries includes RUNE, THORChain’s native asset. Excluding that native entry gives 10 external networks—the basis for the “10 of 13” figure reported by BSCN and Cointelegraph.
This was a snapshot, not a permanent guarantee that every route would remain available. Before submitting a swap, users should check the THORChain network status page and their chosen interface.
Important: A halt on a THORChain route does not mean the underlying blockchain itself has stopped processing transactions.
What Caused the THORChain Halt?
The problem began on October 31 at 11:34 UTC, according to THORChain’s incident account.
Ethereum experienced a one-block reorganisation, often called a reorg. This happens when a recently recorded block is replaced by another version of the chain’s recent history.
A 10 ETH deposit appeared in the block that was later discarded. THORChain had already observed and credited the deposit, but it did not reach the accepted version of Ethereum’s chain in that form.
The associated swap then failed to meet its specified price limit, triggering a refund. THORChain said its vault paid out 10 ETH it had not received, while the sender’s actual deposit was also refunded.
The result was an unexpected 10 ETH shortfall in the affected vault.
For readers less familiar with Ethereum, the network was co-founded by Vitalik Buterin. A short reorganisation can occur on a blockchain; in this case, the problem described by THORChain was how its own system handled the changed transaction history.
Was the Missing 10 ETH Recovered?
Yes. THORChain said the recipient returned the extra 10 ETH, restoring the affected vault’s balance.
The protocol also said its automatic solvency checker detected the discrepancy and halted Ethereum swaps. Node operators then stopped Ethereum transaction signing and applied broader precautionary halts while developers investigated.
Returning the funds solved the immediate balance shortfall. It did not, by itself, prove that the underlying software issue had been resolved. That required changes to the protocol and decisions by node operators about when to reopen routes.
Why Does the 3.21.1 Update Matter?
THORChain connected the reopening of several swap routes to its 3.21.1 update.
In its official recovery announcement, the project said 14 active nodes had not yet upgraded. It added that all active nodes needed to update to address swap performance issues.
That is why “swaps have resumed” should not be read as “the recovery is complete.” A route may be available while the network still works through upgrades and performance checks.
The exact status of each route can change. The dashboard content available during this research did not provide a consistent, independently verifiable live snapshot of the post-update state, so readers should check the current status directly before transacting.
Why Did RUNE Rise?
RUNE rose as news of the reopening circulated. In the post shared with Bitnxt, BSCN reported that the token was trading near $0.63, up approximately 13.7% over the previous 24 hours.
Separately, Cointelegraph reported a snapshot of around $0.64 and a roughly 15% daily gain, citing CoinMarketCap. The figures differ because prices and rolling 24-hour comparisons change over time.
The timing suggests that the reopening may have improved market sentiment, but it does not prove that the recovery alone caused the price increase. Crypto prices can move for several reasons, including trading activity and broader market conditions.
How Is the Binance Hack Connected?
The THORChain disruption also had an unexpected connection to the earlier Binance hack.
Blockchain analytics firm Chainalysis said the emergency pause inadvertently delayed the movement of funds stolen from Binance through THORChain. The halt affected ordinary users as well; it was not described as a targeted action against a particular wallet.
The FBI has attributed the Binance theft to North Korean cyber activity, as explained in Bitnxt’s Binance hack recovery update.
THORChain’s role in handling attacker-linked transactions had already attracted attention after the Bitget breach. In Bitnxt’s earlier Bitget coverage, the protocol said its emergency controls could pause trading more broadly but could not selectively freeze one address’s swap.
The two situations are different: the Bitget dispute concerned a request to block identified transactions, while the latest halt followed a technical safety issue.
Bitnxt’s Take: A Restart Is Progress, Not the Final Test
Getting major swap routes back online is encouraging, especially for users who rely on THORChain to move between different blockchains. The return of the extra 10 ETH also resolved the immediate vault shortfall described by the protocol.
But the incident shows how a relatively small accounting error can create a much larger operational disruption. A cross-chain protocol does not only need to process transactions correctly when every connected network behaves as expected; it also needs to handle moments when a network’s recent history changes.
For Bitnxt, the next things to watch are whether the remaining node operators complete the upgrade, when the three halted integrations reopen, and whether THORChain publishes further detail on the fix and its testing.
RUNE’s rebound may reflect renewed confidence. The stronger evidence will be stable operations over time.
