THORChain: native swaps, settlement vaults, fees and protocol recovery

THORChain provides cross-chain swaps between supported native assets using its own settlement network and liquidity pools. The official swap website also offers routes through Maya Protocol. The network, that website and independent interfaces such as THORSwap are separate scopes: an interface’s quoted route, affiliate charge and contractual terms must be assessed for that interface. This profile centres on THORChain and its official swap website.[1]

The September 2026 network report records $2.40 billion of monthly swap volume and approximately 25,000 active wallets. It attributes $1.37 billion during 25–29 September to flows associated with the Bitget exploit. Those exceptional flows materially distort a simple adoption comparison. Wallet activity is not a count of verified people, registered accounts or customers of the official website.[5]

THORChain’s continuous pools determine execution through pool balances and slip-based pricing. There is no conventional maker/taker order-book account tier for an ordinary pool swap. A displayed market price, the route’s actual output and the minimum acceptable output are different quantities. The trade size relative to available depth affects the economic result.[24]

Protocol documentation also describes Trade Assets, which are internal credits backed by assets held outside ordinary pools, and Secured Assets for application-layer use. These should not be described as native coins already held in a personal wallet. Their redemption and protocol exposure differ from a simple completed outbound swap. Availability of a documented module is not evidence that every retail interface currently enables it.[28][29]

The developer specification includes configurable liquidity-fee floors and affiliate-related mechanics. It does not support one permanent percentage covering every asset, frontend and trade size. Streaming changes when some charges are assessed. A route comparison therefore needs the executable output, source transaction expense and any separately disclosed affiliate amount, rather than only a headline percentage.[14]

As a calculation example, suppose a $10,000-equivalent swap has $5 source gas, $12 liquidity cost, $10 affiliate cost and $3 outbound cost. The combined illustration is $30, or 0.30% of the assumed input value. These are invented inputs expressed in one common currency; they are not a THORChain tariff or a live quote. Token prices and the actual network charges can move before execution.[13]

Streaming ordinarily pays for one inbound and one outbound transfer while subdividing the internal execution. This differs from making many independent on-chain swaps. If execution fails before any component fills, the documented process refunds the input; after a partial fill, it can deliver acquired output and return unswapped input. Fees, minimum usable amounts and the actual failure path still matter.[15]

Funding a swap means making an on-chain transfer, not crediting a conventional exchange bank account. The wallet flow can require both a token approval and a subsequent swap authorisation. Those are separate permissions and transactions. The selected token, chain and destination must match the route; a similarly named token on another chain is not interchangeable for settlement.[23]

A valid quote does not establish that an arbitrarily small transfer will be processed. The integration guide supplies route-specific minimums, expected amounts and inbound details. It also separates source confirmation, internal execution, outbound scheduling and final network broadcast. A single advertised swap time cannot guarantee completion across every chain and queue state.[17]

Transfers below protocol dust thresholds can be ignored, and malformed instructions may not receive the intended treatment. The memo specification should be read before constructing a transaction outside a supported interface. A transaction hash proves a broadcast occurred; it does not prove that the intended swap has been accepted or that the recipient has received the destination asset.[19]

Limits can persist in the advanced queue until their condition is met or they expire. The documented default lifetime is 43,200 blocks, approximately three days, subject to configuration and the permitted custom cap. Expiry can settle a filled portion and refund the remainder. Closing a browser or disconnecting a wallet does not itself remove an on-chain instruction; cancellation must use the relevant supported transaction process.[16]

The official website says signing occurs locally or through an external-wallet transfer flow. It does not ask the user to deposit a private key into the interface. That describes the website’s role; it does not mean assets remain under the user’s sole control after the source transfer has been sent.[3]

THORChain settlement uses Asgard vaults controlled through threshold signing by node participants. Bifrost observes external chains, and consensus determines protocol action. Vault addresses can rotate. The security model therefore includes the external chains, observation software, node coordination and the signing implementation, alongside the user’s own wallet and the interface used to prepare a transaction.[12]

ADR 028 excludes ordinary LP positions from reductions, separately from saver, reserve and treasury positions. Affected savers can receive a haircut after reserve coverage is exhausted. It also addresses one stuck streaming swap. This accepted migration specification does not independently verify every wallet’s actual recovery or establish blanket reimbursement or deposit insurance.[10]

The July exploit report also states that the bug-bounty programme had been paused from 31 March 2026 for one year. Older emergency material mentioning a bounty should not be treated as proof of a currently active reward programme. A security report and a compensation claim are separate matters.[7]

The interface terms require adulthood or the applicable age of majority, lawful use and compliance with sanctions and jurisdictional restrictions. They describe no conventional account or identity-document onboarding. Absence of KYC does not establish legal access in every country, and the terms inspected do not provide a complete named-country eligibility matrix.[2]

The official interface supports connected-wallet and external-wallet modes. External mode supplies transfer instructions without a conventional wallet connection. Neither flow demonstrates eligibility for every asset, chain or third-party frontend; the selected route and locally available interface remain the operative scope. No bank-card or fiat account funding service is established by this swap workflow.[1]

The terms say contributors cannot reverse completed transfers. They include a dispute process and liability limitations. No independent ombudsman or compensation allocation was established; applicable legal rights remain jurisdiction-dependent.[2]

The terms identify no single corporate protocol operator. No independently verified exchange authorisation was established. Public accessibility does not demonstrate regulatory approval or statutory client-money protection.[2]

The network’s governance documentation distinguishes node configuration and Mimir voting from the choices made by individual application developers. Protocol variables can change chain support, limits and operational states. A frontend’s brand or software maintainer does not by itself identify the party controlling each network function.[22]

The official interface credits Unstoppable Wallet in its footer. That credit is not sufficient evidence of a specific contractual legal entity for every swap or of ownership of the THORChain protocol. The profile therefore does not invent a company headquarters, incorporation record or group licence from the software attribution.[1]

The May incident is separate from the earlier ThorFi debt restructuring. The token documentation describes approximately $210 million of historical claims converted into TCY, with one TCY corresponding to one dollar of eligible claim at allocation. Staked TCY participates in 10% of future protocol income under the described mechanism. Market value, income and immediate cash recoverability are different questions.[27]

Operator

Protocol contributors and independent node operators; no single corporate operator identified in the interface terms.

Exchange model

Decentralised

Service scope

Native-asset cross-chain swaps, liquidity pools and related protocol participation.

Client types

Not established

Pricing publication

Public and quoted pricing

Pricing scope

Published fee mechanics with route-specific gas, liquidity, affiliate and outbound amounts.

Funding scope

Supported on-chain assets; fresh route and destination details required for each transfer.

Custody and asset handling

Users authorise transfers; settlement assets enter threshold-controlled protocol vaults.

Client eligibility

Wallet-based interface access; age, sanctions and local-law conditions apply.

Support

Official contact page, community channels and technical issue reporting; no verified emergency dealing desk.

Authorisation and registration scope

No independently verified regulated exchange operator or customer compensation scheme established for this protocol.

Exchange metadata checked 20 Oct 2026Source 1Source 2Source 4Source 12Source 14Source 17Source 23Source 24Source 27

Liquidity documentation describes withdrawals back to the originating address and applicable network charges. Its general withdrawal availability must be read alongside current network pauses. RUNEPool adds its own maturity and backstop constraints; no fixed annual return or universally immediate exit is established here.[25][26]

The MCP documentation requires correctly scaled amounts and fresh route information. A conversational assistant can retrieve information through those tools, but the documented server does not autonomously execute a trade. No copy-trading mandate or AI custody authority is established by the existence of that integration.[31]

The terms allow access restrictions after extended inactivity but publish no numeric inactivity fee. Wallet recovery and browser preferences remain separate; no cross-device settings guarantee was established.[2]