If you are choosing how to move BTC into ETH, compare the ETH you will receive after every fee, then weigh custody and settlement risk against that amount. The three common routes—a centralized exchange, a wrapped-asset bridge followed by a DEX swap, and a native cross-chain swap—settle differently, so the best quote is not always the best fit. For the mechanics of a direct route, how thor swap routes BTC into ETH shows the kind of deposit-to-delivery flow you are comparing here.
When does a centralized exchange fit?
A centralized exchange is usually the clearest choice if you already have an account, can deposit BTC, and want an order book or limit order. You deposit BTC, trade it for ETH (or trade through a fiat or stablecoin pair), then withdraw ETH to your wallet; the exchange holds custody between deposit and withdrawal.
Its advantage is price control: a liquid BTC/ETH book can give you a visible spread and let you set a limit. Its costs include the BTC network fee, trading fee, spread, and ETH withdrawal fee. If the exchange lacks a BTC/ETH pair and you trade BTC to a stablecoin and then to ETH, account for two spreads and two trade fees.
This route fits when the exchange’s net output is competitive and you accept custody and account requirements. It fits poorly when you need self-custody throughout, cannot use the venue, or the deposit and withdrawal queues make the total wait unpredictable. Check the exact withdrawal network: an ETH balance credited on an exchange is not the same as ETH delivered to your own Ethereum address.
When is a wrapped-BTC bridge plus DEX better?
This route is useful when you want to execute on Ethereum’s own DEX liquidity and are willing to hold a bridged representation of BTC during the process. First BTC is locked or otherwise secured under the bridge’s design, and a token representing BTC is issued on Ethereum; you then swap that token for ETH in a DEX pool or order book.
Its fit depends on the specific wrapped asset and bridge, not on the ticker alone. Check who controls the backing BTC, how withdrawals are authorized, whether the token is redeemable one-for-one, and whether the Ethereum DEX has enough depth for your size. A bridge can be technically live while its wrapped token trades below BTC parity or has thin liquidity.
Price the two legs separately: bridge and Bitcoin transaction costs, then Ethereum gas and DEX price impact. You also take smart-contract, validator or custodian, and wrapped-asset depeg risk. This route is a poor fit if you specifically need native ETH quickly, do not want exposure to the bridge’s backing model, or the wrapped token’s DEX depth is too shallow.
When does a native cross-chain swap suit the trade?
A native cross-chain swap suits you when you want to send BTC and receive ETH without first taking delivery of wrapped BTC on Ethereum. The protocol observes the Bitcoin deposit, executes swaps against cross-chain liquidity, then sends ETH to your destination address. In a THORChain route, for example, the economic path can be BTC-to-RUNE followed by RUNE-to-ETH through two liquidity pools; the intermediate asset is part of settlement, not a wrapped BTC balance in your wallet.
A service such as THORSwap gives you a single cross-chain swap flow for that task: you specify the source and destination assets and the service routes the swap through available cross-chain liquidity. The route avoids a separate bridge-and-DEX sequence, but it still depends on pool depth, source-chain confirmation, protocol execution, and destination-chain delivery. A simple one-flow experience does not mean instant settlement or zero execution risk.
Pool-based routing charges more when your trade consumes a larger share of pool depth. THORChain’s slip-based fee rises with trade size relative to liquidity; its streaming swaps can split a large trade into smaller internal executions, reducing price impact at the cost of waiting longer. That can suit a patient, larger trade. A smaller trade or one that needs a firm completion window may favor a faster route if its quoted output is better.
How do you compare the real cost?
Use the same input amount and destination address, then compare the net ETH delivered—not a headline rate. Include source-chain fees, trading or liquidity fees, bridge costs where relevant, destination gas or withdrawal costs, and any affiliate charge shown in a quote. Also compare the quote’s minimum-output protection and expiry: a quote that can move materially before execution is different from a limit order that waits for your price.
For a quick check, suppose 0.1 BTC is worth $10,000 at your reference price and ETH is $4,000. The no-cost equivalent is 2.5 ETH. If a route quotes 2.46 ETH after its stated deductions, its shortfall is (2.50 − 2.46) ÷ 2.50 = 1.6%; repeat with your own market prices and quoted output. This is a comparison, not a prediction: BTC and ETH prices can move while a deposit confirms.
For any route, verify the BTC address and amount before broadcasting, and use an ETH address you control on the intended network. Bitcoin deposits usually need multiple confirmations, while the receiving protocol may impose its own safety margin; an unusually low-fee BTC transaction can therefore delay execution and leave a stale quote or a pending swap. For thor swap, the deciding check is the same as for other native routes: compare the expected ETH after pool impact and network costs with the custody and timing trade-offs you are willing to accept.