THORChain temporarily suspended trading across 10 blockchain networks after an Ethereum chain reorganization triggered an accounting discrepancy that left one of its vaults with a solvency shortfall. The incident involved a 10 ETH transfer that was initially recognized as a valid deposit but was subsequently removed from Ethereum’s canonical transaction history.
The disruption highlighted the risks associated with cross-chain transaction verification, particularly when blockchain reorganizations affect deposits that have already been processed by decentralized infrastructure. THORChain’s automated monitoring systems detected the resulting deficit and initiated trading restrictions to prevent further exposure while developers investigated the issue.
Ethereum Reorganization Triggers 10 ETH Accounting Shortfall
The incident began when a user initiated a 10 ETH deposit into THORChain. The transaction initially appeared in an Ethereum block, prompting the protocol to recognize the incoming funds and update its internal accounting records.
However, Ethereum subsequently experienced a chain reorganization, an event in which previously accepted blocks are replaced by an alternative version of the blockchain. As a result, the block containing the 10 ETH deposit was removed from the canonical chain.
Despite the transaction no longer being part of Ethereum’s confirmed transaction history, THORChain had already credited the deposit within its system. This created a discrepancy between the protocol’s internal accounting and the actual funds available in the corresponding vault.
The situation became more complicated when the associated swap failed to satisfy its specified price limit. The protocol therefore refunded the transaction rather than completing the exchange.
However, the vault had already transferred the equivalent 10 ETH without receiving a corresponding settled deposit. This left the vault with a deficit and created a temporary solvency issue.
The incident demonstrated how an Ethereum chain reorganization can create financial exposure for cross-chain protocols when deposits are credited before they achieve sufficient confirmation security.
THORChain Suspends Trading Across 10 Networks
THORChain’s automated solvency monitoring mechanisms identified the discrepancy after the vault’s available balance no longer matched its recorded obligations.
Following detection, the protocol halted Ethereum swaps to contain the immediate problem. Trading restrictions were subsequently extended to nine additional blockchain networks as a precautionary measure.
The broader suspension was intended to prevent potential complications across the protocol’s interconnected liquidity and settlement infrastructure while the underlying issue was being investigated.
Although the original discrepancy involved an Ethereum deposit, the decision to restrict multiple networks reflected the potential operational risks associated with cross-chain transactions. A problem affecting one part of a decentralized exchange’s infrastructure can require broader safeguards when different networks rely on shared protocol components.
The temporary suspension also highlighted the importance of maintaining accurate accounting records across independent blockchains, where transaction finality and confirmation mechanisms can differ.
User Returns 10 ETH, Restoring Protocol Solvency
The immediate financial shortfall was resolved after the user returned the missing 10 ETH to the protocol. The repayment restored the affected vault’s solvency and addressed the deficit caused by the unsuccessful transaction.
On October 31, THORChain halted trading on several blockchains.
An Ethereum block reorg caused THORChain to pay out 10 ETH that a vault never received. The automatic solvency checker caught the shortfall and halted ETH swaps. Within approximately two minutes, node operators halted ETH transaction signing, so no further ETH could leave the vaults.
Node operators then halted all chains as a precaution so core developers could investigate.
The 10 ETH has been returned by the user to make the vault solvent again.
Breakdown of what happened and next steps:
At 11:34 UTC Oct 31, Ethereum had a one-block reorg. A 10 ETH deposit to one of the vaults sat in the dropped block and never landed on the canonical chain.
THORChain had already observed and credited that deposit. The swap missed its price limit and was refunded, so the vault paid out 10 ETH it never received. The sender’s real deposit was refunded as well.
Every node detected the reorg. But the re-check that should have removed the deposit could not get a clear answer in time, so it was finalized.
The solvency checker halted ETH swapping automatically, then three node votes halted all ETH outbound payments.
All chains were then halted by three node votes as a precaution. Now that this is public knowledge, every time there is a block re-org on an external chain, a malicious actor could perform a new transaction with the same nonce and would be paid funds by the THORChain vaults.
Note: Three node votes can trigger emergency halts to protect network solvency. However, that action can be reversed by four counter node votes, then five node votes can reverse the reversal, and so on, maintaining a balance between decentralization and rapid emergency intervention. Halting a chain does not give those nodes control of the assets.
Core developers have been working on the necessary fixes.
Nodes will decide to re-enable chains as they are deemed safe.
Trading blockchains: AVAX, BASE, RUNE, XRPL
Halted blockchains: ATOM, BCH, BSC, BTC, DOGE, ETH, LTC, SOL, TRON, ZEC
— THORChain (@THORChain) November 1, 2026
However, restoring the missing funds did not automatically reopen trading across all affected networks. Developers continued working on technical improvements intended to prevent similar incidents, while node operators retained responsibility for determining when individual networks could safely resume operations.
This approach allows the network’s decentralized operators to assess the situation before restoring normal transaction processing.
Developers Focus on Preventing Future Incidents
The incident has renewed attention on the importance of transaction confirmation policies and reorganization protection in cross-chain systems. Protocols that process deposits across different blockchains must account for the possibility that transactions initially included in a block could later be reversed.
For THORChain, improvements to deposit verification and transaction settlement procedures are particularly important because its infrastructure facilitates asset transfers and swaps between independent blockchain networks.
The developers’ ongoing work is aimed at strengthening safeguards against similar accounting discrepancies and improving the protocol’s ability to handle unexpected blockchain reorganizations.
Although the returned funds resolved the immediate solvency issue, the resumption of trading depends on technical safeguards and the decisions of THORChain node operators across the affected networks.