THORChain flags BASE and XRP trading as paused in November 7 checks
Source checked: 2026-11-07 · Editorial analysis published: 2026-11-07
The newly observed pauses differ from the November 5 snapshot. A BTC-to-XRP quote was rejected; BTC-to-LTC returned an estimate.
BASE and XRP show a trading pause
THORChain’s public inbound-address data showed BASE and XRP trading paused in our November 7 check. A retained November 5 snapshot had both routes unpaused. Bitcoin’s row remained unpaused, and a read-only Bitcoin-to-Litecoin quote returned an estimate. For miners who exchange earned coins through this service, the available route matters as much as the displayed market price.
THORChain is infrastructure for exchanging assets across different blockchains. BASE and XRP are identifiers in its chain list. The pause concerns trading through THORChain. It does not establish that either underlying network stopped producing blocks or processing its own transactions.
The comparison identifies a change between two observations. It does not establish the exact time the restrictions began or their cause. Both snapshots came from the Liquify public THORChain API; a separate provider could not be checked successfully. The article records what that endpoint returned, rather than claiming agreement across independent nodes.
Which controls changed
The endpoint listed 13 chain rows. BASE, XRP and Solana each had chain_trading_paused set to true and the aggregate halted flag set to true. Solana was already paused in the November 5 snapshot. The newly observed changes in this comparison were BASE and XRP.
The global trading-pause flag was false. The other ten chain rows, including BTC, BCH, LTC, DOGE and ZEC, showed no trading pause. These are chain-level status rows. A count of rows does not describe every token, pool, wallet integration or possible exchange path.
A second response from the same provider, the Mimir configuration, showed HALTBASETRADING, HALTXRPTRADING and HALTSOLTRADING enabled. The separate chain-halt controls for those three networks were zero. This distinction is why a service trading pause should be described precisely: different controls cover trading, chain operations and signing.
A quote provides a more practical check
We requested a quote for exchanging 0.001 BTC into XRP. A quote is a request for an estimated exchange outcome, not a transfer. The endpoint rejected it with HTTP status 400 and a message saying trading was halted and the swap could not be processed.
Using the same Bitcoin amount, a request for Litecoin returned an expected output amount. No wallet was connected and no funds were sent for either check. The successful response shows that an estimate could be obtained for that particular route at the observation time. It does not demonstrate a completed exchange.
The XRP pool endpoint still responded with pool information. Being able to read a pool, its balances or its displayed status does not cancel a chain trading restriction. An app that displays only a pool’s existence can therefore give a less useful picture than a fresh route quote together with the chain controls.
Why this matters for mining proceeds
A mining pool payment and a later exchange are separate steps. A miner may receive Bitcoin or another proof-of-work coin normally, then meet a restriction while trying to convert it into a different asset. This observation concerns that exchange stage; it supplies no evidence of a stoppage at a mining pool.
For an operator who uses THORChain, record the asset being sent, the asset being received and the time of the quote. Bitcoin being unpaused does not make a Bitcoin-to-XRP route usable when XRP trading is paused. The destination side is part of the same operation.
The BTC, BCH, LTC, DOGE and ZEC rows help narrow the check for common mining proceeds. They do not guarantee every path between them. A route may involve additional pool, liquidity or integration conditions. The specific quote response is the relevant next piece of information before an operator decides whether to use the service.
Read the current route rather than an old estimate
An earlier successful quote belongs to its own observation time. Exchange quotes can include temporary addresses, expiry times, fees and instructions. We do not reproduce the addresses or instructions from this test, because they were generated for an unexecuted request and are not standing payment details.
The useful sequence is to inspect current service status, request a current quote for the intended assets and distinguish a returned estimate from an accepted transaction. This is an explanation of the observed service state. No exchange was submitted, and the test says nothing about the settlement of an existing user transaction.
The November 7 result is specific: BASE and XRP were newly paused relative to our November 5 snapshot, Solana remained paused, and the tested Bitcoin-to-Litecoin estimate was available. A restart date and an official explanation for the new restrictions were not established in the checked responses. We will treat a later change as a new observation with its own timestamp.
Source: THORChain public API via Liquify ↗ · THORChain Mimir configuration ↗ · Read-only BTC to XRP quote ↗ · Read-only BTC to LTC quote ↗ · Official connection documentation ↗
Mining calculator ↗
