> For the complete documentation index, see [llms.txt](https://wallet-basics-guide.gitbook.io/wallet-basics-guide-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wallet-basics-guide.gitbook.io/wallet-basics-guide-docs/thor-swap-choose-a-route-for-your-wallet-to-wallet-exchange.md). # thor swap: choose a route for your wallet-to-wallet exchange Use thor swap when you want to exchange assets across blockchains from your own wallet, such as native BTC for ETH, without depositing them on an exchange. For that transfer, [thor swap](https://thorswap.us) lets you swap and move assets between chains in one flow. Check a THORSwap quote for the asset you will receive, the total cost and the expected time. Three checks decide whether a route fits: * Confirm the exact asset and blockchain at both ends. * Compare the amount arriving in your wallet after fees, not just the exchange rate. * Check how the route handles delays, price changes and failed swaps. ### A cross-chain swap exchanges one asset for another A cross-chain swap is useful when the asset you hold and the asset you want live on different blockchains. If you hold BTC in a Bitcoin wallet and want ETH in an Ethereum wallet, a swap can deliver ETH directly to your receiving address. On a centralised exchange, you might instead deposit BTC, trade it, then withdraw ETH; each stage has its own address and network choice. The swap still has several stages underneath. You send the source asset, a route accesses liquidity to convert its value, and an outbound transaction delivers the destination asset. On a THORChain route, for example, the network observes the incoming BTC, swaps through its liquidity pools and sends native ETH out on Ethereum. You do not need to acquire the intermediate pool asset yourself. That distinction matters when comparing a swap with a bridge. A bridge may move a representation of BTC onto another chain while leaving you holding a wrapped token; a BTC-to-ETH swap changes the asset you own. Decide first whether you need ETH to spend on Ethereum or a version of BTC to use elsewhere. Those are different outcomes, even if both move value across chains. ### The exact assets and chains determine which routes work A route works only if it accepts your source asset on its actual chain and can deliver the asset you want on its destination chain. “ETH” can mean native ETH on Ethereum or ETH represented on a layer 2 network. An address that starts with 0x does not, by itself, tell you which network will receive the transfer. Start by reading the asset and network labels in your wallet, then match both ends of the proposed route to them. For a thor swap from native BTC to native ETH, check that the source is Bitcoin rather than a BTC token on another chain, and that the output is ETH on Ethereum. Check the receiving wallet supports that output network before using its address. Next, check the amount against the route’s current minimum and the funds needed to send it. Small swaps can fail to clear a route’s minimum after network costs, while a token sent from Ethereum needs some ETH in the sending wallet for gas. A wallet showing a $100 token balance cannot necessarily send all $100 if it has no ETH to pay for the transaction. For a large transfer, test the same asset pair at your actual size. A route that quotes a small swap may have too little liquidity for a much larger one. The practical check is the destination amount quoted for your intended input, not the mere presence of the pair in an asset list. ### The net amount received determines the real cost Compare routes by the amount expected in the destination wallet for the same source amount, then account for any source-chain fee paid separately. A cross-chain quote can include a trading or liquidity fee, price impact from the pools, an interface fee and a destination transaction fee. The source transaction fee is often paid by your wallet in addition to the amount being swapped. For example, suppose two routes each swap $1,000 of BTC. One quotes $988 of ETH and requires about $7 for the separate Bitcoin transaction; another quotes $984 of ETH and requires about $2. Accounting for that extra spend, the second route is ahead by about $1, despite its lower displayed ETH output. These figures are illustrative; Bitcoin fee rates and swap quotes move. Price impact also changes with trade size. A $200 swap may barely move a deep pool, while a $20,000 swap through a shallow pool can receive a noticeably worse rate. Compare the quoted output with the current market value of the input, then check the minimum received amount: that is the floor you are willing to accept if the price changes during execution. Some routes split a large swap into smaller swaps over time to reduce price impact. This can improve the average rate, but it leaves the trade exposed to market moves for longer. I would choose that route only when its expected gain matters more to me than receiving the asset promptly; I would compare its minimum output and estimated completion time with a faster route. ### Timing and route mechanics determine the risk you accept A cross-chain swap takes time because the source transaction must confirm before the route can process it and send the destination transaction. Bitcoin confirmation, additional checks against chain reorganisations and destination-chain congestion can all add delay. Treat an estimated arrival time as an estimate, especially when you need the ETH for a transaction at a specific moment. Read what happens between sending and receiving. A liquidity-pool route may hold funds in protocol vaults while it processes the swap; another route may use a different provider or an intermediate token. “From your own wallet” describes how you start and finish, but it does not mean your funds stay in that wallet during the transfer. Before sending, check the receiving address, network, quoted minimum output and refund terms together. If a swap cannot execute, a refund may return on the source chain after a fee, and it may take time. Keep enough of the source chain’s gas asset for the initial transaction rather than trying to empty the wallet to its last unit. Once sent, use the source transaction identifier to follow confirmation and the route’s progress; completion means the destination transaction has reached the receiving wallet. For a first wallet-to-wallet transfer, I would use a small amount that clears the route’s minimum, verify where it arrives, then repeat with the intended size and a fresh quote. ### Two common questions clarify the choice The purpose of the swap and the route behind its quote tell you what to compare. #### What is THORSwap used for? It is used to exchange crypto assets, including assets on different blockchains, through a wallet-based flow. A common case is turning native BTC into native ETH without making separate exchange deposit, trade and withdrawal transactions. It can also route through different sources of liquidity, so the asset pair alone does not tell you how a particular quote will execute. #### How does THORSwap compare with other cross-chain swap services? Compare the routes available for your exact pair, size and destination, then compare net output, completion time and what holds the funds during execution. Another service may quote a different liquidity source or deliver a wrapped asset instead of the native asset you wanted. The useful comparison is between current, like-for-like quotes, with source-chain costs and minimum received amounts included. Choose the route that delivers the exact asset on the exact chain you need, with an acceptable minimum output, total cost, wait and handling of a failed swap. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wallet-basics-guide.gitbook.io/wallet-basics-guide-docs/thor-swap-choose-a-route-for-your-wallet-to-wallet-exchange.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.