THORChain restarts swaps on 10 networks; three remain paused as RUNE gains 15%

The restart has a chain-by-chain boundary

The current status response supports a narrower statement than “THORChain is fully back.” AVAX, BASE, BCH, BTC, DOGE, ETH, LTC, TRON, XRP and ZEC each showed false for both the halted and chain_trading_paused fields in our 18:49 SGT observation. BSC, GAIA and SOL showed true for both fields. The global_trading_paused field was false in all 13 entries.

These are flags from one timed observation. They describe the network state returned then. They do not show whether an individual's swap completed, whether a receiving exchange credited a deposit, or whether a particular account can use a product. Readers can inspect the official THORChain querying guide for the chain relevant to their transfer.

The endpoint was reached through the gateway linked by THORChain's own documentation. The official querying guide explains the fields and tells users never to send funds when halted is true. This is also why a working route involving Bitcoin does not settle a question about Solana.

Cointelegraph's earlier report likewise described trading and transaction signing as available on 10 of 13 listed external networks, with BNB Smart Chain, Cosmos Hub and Solana still carrying warnings. Our later endpoint observation independently confirms the same split for the two flags we checked. It does not independently confirm the report's market-price calculation.

The combination of fields gives a useful way to read a route. For a hypothetical Ethereum-to-Solana swap, the ETH entry was open under the checked flags, but SOL was still halted. Looking only at ETH would miss the restriction on the other side. A Bitcoin-to-Ethereum route had two open entries in the same snapshot, although an individual swap would still need a valid quote and current receiving instructions. These examples apply the observed flags; they are not records of completed swaps.

Treat a missing status differently from a false status. Our table contains 13 returned entries, so its conclusion is limited to those entries. If your intended network cannot be found in the current response, this snapshot supplies no affirmative answer about that route. Likewise, an open chain field does not reveal whether a receiving exchange has enabled deposits for the asset on that chain. Check the exchange's receiving screen separately before selecting it as the destination.

What triggered the pause

According to Cointelegraph's account of the protocol's explanation, a one-block Ethereum reorganization removed a 10 ETH deposit that THORChain had already credited. The swap did not meet its price limit. A refund was then issued against funds the vault had not received, while the sender's actual deposit was also refunded.

The resulting extra payout was 10 ETH, according to that report, and an automatic pause followed. Node operators subsequently paused trading across multiple networks while developers investigated. We attribute this sequence to the report; the network flags alone cannot establish the cause or reconstruct the refund transactions.

For a reader with a pending transfer, the distinction matters. The pause was connected to how an inbound deposit and refund were handled. A price recovery in RUNE cannot demonstrate that an old refund has reached its destination. The relevant evidence for that question is the particular transaction and refund record.

The restart is the new development in this story. It should be read alongside the remaining three paused entries, rather than as an all-clear statement for every route. The status check gives a practical boundary for the news: most listed networks were open under the checked flags, while three were still halted.

Before sending another transaction

Start with the sending chain and the chain on which you expect to receive the asset. Look up both in the current network status. If the intended route includes BSC, GAIA or SOL, our observation is a reason to check for a later reopening before attempting it. THORChain's documentation explicitly says not to send funds when the halted flag is true.

Next, obtain a fresh destination through the interface you independently opened. The official guide says Asgard vault addresses change regularly and must not be cached. A destination copied for an earlier attempt should therefore not be treated as a standing transfer instruction. Do not manually reuse a vault address from a screenshot, article or old transaction to work around a paused interface.

Check the receiving address format as well. The guide lists supported formats by chain and includes restrictions on particular address types. For example, it says Litecoin MWEB addresses are unsupported, and tells users not to swap to smart-contract addresses for the listed EVM chains. A network changing from halted to open does not remove its address-format conditions.

Finally, review the quote and the destination shown for this actual attempt. These are reader checks derived from the restart's chain-specific boundary and the official transfer documentation. They are not instructions to bypass a pause or force a transaction through a disabled route.

If you already have a swap or exchange deposit pending

Retain the transaction identifier, sending chain, intended receiving chain and the destination used. Then inspect the specific transaction's state through the service used for the swap. A general status page answers whether a network is paused; it does not identify the final state of your own transfer.

If the intended destination is an exchange deposit address, open that exchange's deposit record independently and compare the asset and network with the intended output. Check whether the account has credited the transfer before treating the balance as available to sell. Avoid sending another transfer merely because the first balance has not appeared.

For an order that depends on the pending asset, check the balance actually usable in the trading account. Keep a planned sell order separate from an expectation that a delayed transfer will arrive at a particular time. Neither the Cointelegraph report nor our status response supplies an arrival time for a reader's transaction.

The NexuAlpha liquidation board and funding-rate board are separate tools for reviewing trading exposure. We do not quote a RUNE liquidation total or funding rate here because no such figure was established by the sources used for this article. The network restart is the verified subject of this update.

Read the 15% move with its timestamp

Cointelegraph described RUNE near $0.64 and approximately 15% higher over the previous day. A report-time price change and a later network-status snapshot measure different things. We have kept the price attribution attached to its source instead of presenting it as a fresh executable quote.

The report associates the rally with the reopening. Our network check establishes the route flags, not why every buyer traded RUNE. It also does not establish how much of the day's move followed the restart. A trader comparing the report with an exchange chart should use the chart's own market and time window.

The next operational development to watch is a change in the remaining BSC, GAIA and SOL entries. An updated protocol explanation could also add detail to the refund incident. Until those changes are published and checked, the concrete action remains to inspect the chosen route and any existing transaction before sending more funds.

Quick answers

Are all THORChain networks open?

Our 18:49 SGT check returned 10 open entries under the two checked flags and three halted entries: BSC, GAIA and SOL. It supports a partial restart.

Does an open flag prove my swap completed?

No. The network response contains chain status. Check the individual transaction and, where relevant, the receiving exchange's deposit credit separately.

Can I reuse a vault address saved before the halt?

THORChain's official guide says vault addresses change regularly and must not be cached. Obtain current transfer instructions from the interface and check the chain's halt status before sending.

Is $0.64 a current trading quote?

It is the approximate RUNE price reported by Cointelegraph. This article's independent observation concerns network flags, not a later market quote.