Do you get native BTC or wrapped BTC when you swap ETH to Bitcoin? A live route test (18 October 2026)

Short answer: you get whatever destination token the route actually ends in, and the two are not the same product. On 18 October 2026 I pulled live quotes for 0.2 ETH to Bitcoin on Rango Exchange, between 05:08 and 05:13 UTC. The best route to native BTC (Bitcoin mainnet, no token contract) delivered 0.00589753 BTC through a single Harbor bridge leg, quoted at about 4 minutes. The same 0.2 ETH into wrapped BTC (WBTC, the ERC-20 contract on Ethereum) delivered 0.00590575 WBTC through a single KyberSwap DEX leg, quoted at about 45 seconds. Same input, same router, same morning: one result is claimable on the Bitcoin network, the other is a token on Ethereum that represents bitcoin.

So, can I swap ETH directly to native BTC? Yes. Can I end up holding a wrapped representation instead? Also yes, and usually faster. Which makes sense depends on what you plan to do with the output.

What is the difference between native BTC and wrapped BTC?

Native BTC lives on the Bitcoin blockchain. It has no token contract address, because it is the ledger asset itself, not a contract token. Bitcoin's developer documentation describes the block chain as an ordered and timestamped record of transactions, used to protect against double spending and modification of past records. A native BTC settlement only exists once the Bitcoin network has confirmed it, which is why routes into Bitcoin quote minutes, not seconds.

Wrapped BTC is a token on another chain that represents bitcoin held in custody. WBTC, the oldest and largest Bitcoin wrapper, is an ERC-20 contract on Ethereum at 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 (the same address Rango's routing response returns for the WBTC destination). It trades near the price of BTC because each WBTC is backed 1:1 by bitcoin in custody, and the claim is checkable: WBTC's transparency page, loaded 18 October 2026 at 05:06 UTC, showed 116,499.1908 WBTC in circulation against 116,511.9929 BTC in custodian reserves, both near $9.52 billion, with the custodian's Bitcoin addresses published for on-chain verification.

The practical differences:

Network: native BTC settles on Bitcoin; WBTC settles on Ethereum and a short list of other chains WBTC has expanded to, per WBTC's own site.
Counterparty: a WBTC holder depends on the custodian arrangement, and that arrangement has changed before. In August 2024 BitGo, WBTC's custodian, announced a move to multi-jurisdictional custody through a joint venture with BiT Global, with operations split across jurisdictions including Hong Kong and Singapore.
Usefulness: WBTC works inside Ethereum DeFi out of the box; native BTC only spends on Bitcoin.
Speed in a swap: routes ending in WBTC can stay on one chain and finish in seconds; routes ending in native BTC include a cross-chain leg into Bitcoin settlement.

What did the live route quotes show?

Method first: I used Rango's web app with quotes only, no wallet connected, nothing signed, so these are executable quotes, not executed fills. Every figure below comes from the routing responses the app returned, each with its request ID recorded. Rango re-prices on every request, so treat this as one morning's snapshot. Prices quoted are Rango's own price feed.

Test A: 0.2 ETH to native BTC, quoted 18 October 2026, 05:08 UTC, request ID 6c4cb023-1ef0-4df4-bb91-6c2f436d83fd:

Destination: BTC on blockchain BTC, no token address (native settlement).
Output: 0.00589753 BTC, about $481.9 at the quote's own prices (ETH $2,413.64, BTC $81,717), on a $482.7 input.
Route: one swapper, Harbor, a bridge leg, one signature.
Quoted time: 240 seconds, with the route's own historical stats from 78 seconds minimum to 1,508 seconds maximum.
Itemized costs shown: a swapper fee of 0.00000236 BTC (about $0.19) from output, and an Ethereum network fee of about 0.0000076 ETH (under $0.02) from the source wallet.
All-in price impact shown: -0.799540 USD, about -0.16 percent.

Test B: 0.2 ETH to WBTC on Ethereum, quoted 05:10 UTC, request ID 822349b4-6123-4ee7-9127-41531e9c52b2:

Destination: WBTC, ERC-20 on Ethereum at 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599.
Output: 0.00590575 WBTC, about $481.8 at the quote's own prices (ETH $2,412.91, WBTC $81,576).
Route: one swapper, KyberSwap's Ethereum aggregator, a DEX leg, no bridge, one signature.
Quoted time: 45 seconds, historical stats 15 to 180 seconds.
Costs shown: an Ethereum network fee of about 0.0000268 ETH (about $0.06); no bridge leg, so no bridge-side fee line.
All-in price impact shown: -0.814537 USD, about -0.16 percent, nearly identical to the native route.

Test C: the unwind, 0.00590575 WBTC to native BTC, quoted 05:12 UTC, request ID d01df0b5-4dc4-451f-b04e-25c0b2d752b7:

This continues Test B: the exact WBTC from Test B sent on to Bitcoin mainnet, to measure the wrapped-then-unwrapped journey.
Output: 0.00587699 BTC, about $480.2 at the quote's own prices (WBTC $81,568, BTC $81,704).
Route: BobGateway aggregator with an internal bridge leg (WBTC to BTC), still one signature from the user's side.
Quoted time: 120 seconds for the outer quote, with the internal bridge leg estimated at up to 588 seconds, historical stats 22 to 697 seconds.
Costs shown: an Ethereum network fee of about 0.000024 ETH (about $0.06), a USDT swapper fee line of 0.004812 USDT, and a BTC swapper fee line of 0.0000066 BTC (about $0.54).
All-in price impact shown: -1.546625 USD, about -0.32 percent.

What changes when your route ends in a wrapped asset?

Ending in native BTC quoted about $481.9 of output; ending in WBTC quoted about $481.8 in its own prices. The gap was roughly $0.15 on a $482 trade, small enough to flip between quotes, and nothing here suggests an open-ended strategy.

Time was the real difference: about 4 minutes quoted into native Bitcoin against 45 seconds into the same-chain token. A swap ending in WBTC finishes when Ethereum confirms it. A swap ending in native BTC finishes when Bitcoin does, and Bitcoin settlement is a different machine, which is why the Harbor route quoted 240 seconds while listing 1,508 seconds in its worst-case historical range.

Then there is the asset itself. WBTC is a claim on custodied bitcoin, with the custody exposure that implies; native BTC is an unencumbered Bitcoin mainnet balance, with no token contract between it and the network. Neither is wrong. They are different products a "BTC" label on a quote screen can hide.

One trap I nearly fell into while planning this test: unit counts. Test B returned more units than Test A (0.00590575 against 0.00589753), but each WBTC unit carried a slightly lower quoted price. Convert outputs to a common unit at the quote's own prices before crowning a winner. Both routes here landed within about a third of a percent of each other.

What changes when you start from wrapped BTC instead of native?

Test C answers it from the other side. Carrying the WBTC from Test B on to Bitcoin mainnet through BobGateway's bridge leg produced 0.00587699 BTC, about $1.7 less output, roughly 0.35 percent across the combined journey, than the single native ETH to BTC route in Test A, and its stitched bridge leg carried its own multi-minute estimate. Every wrap layer in a path adds a counterparty, a step, and its own fee line; unwinding one in reverse costs the same way.

The wrapped route did not need manual unwrapping, though: the route listed as one user flow with one signature, with the bridge leg stitched underneath. So the honest answer to "do I need to unwrap WBTC manually to get native BTC": in the route I pulled, no, the router handled it, but the composite trip was still slower and lower-output than quoting ETH to native BTC directly. Rango's route comparison pages, like https://rango.exchange/swap/eth-to-btc, exist so you can see those alternatives side by side before signing.

How do I check whether a route ends in native or wrapped assets?

Four checks, under a minute once you know them:

Read the destination token row like a fingerprint. Native BTC shows blockchain BTC with no token contract. WBTC shows blockchain ETH plus a token address. A contract address there means your output is a contract token, whatever its name says.
Compare quoted time against the destination chain. A sub-minute quote into something labeled Bitcoin usually ends on Ethereum or another smart-contract chain, because real Bitcoin settlement needs confirmations.
Count the legs and signatures. Each extra swapper is another fee line and another failure point. The native route needed one bridge leg; the unwind route still needed one signature, but its stitched bridge carried its own multi-minute estimate.
Check warnings and slippage before signing. All three quotes showed zero warnings, but warnings exist for frozen routes and unstable pairs.

When does WBTC make sense anyway?

WBTC exists so Bitcoin-denominated value can work inside Ethereum's contract environment: lending, liquidity pools, collateral. If you will deploy the position into Ethereum DeFi the same day, WBTC is the point, not a compromise, and it is why its circulating supply still sat at roughly $9.5 billion in 1:1 reserve parity on the morning I checked.

If the plan is to exit into Bitcoin itself, the morning's numbers say skip the wrapper and quote the native pair:

Native destination: 0.00589753 BTC, about 4 minutes quoted, all-in impact about -0.16 percent.
Wrapped destination: 0.00590575 WBTC, about 45 seconds, all-in impact about -0.16 percent, but the output is a custody-dependent token.
Wrapped start, native end: 0.00587699 BTC after a second hop, all-in impact about -0.32 percent, up to roughly 10 minutes at the inner leg.

Do I receive native BTC or wrapped BTC when I swap ETH on Rango? You receive exactly what the destination token row says, and both were reachable in one signature in my tests, with the native leg costing a few minutes and the wrapped leg keeping your exit option. Read that row before you compare prices.

Method and sourcing notes

All route figures come from Rango's own routing responses captured 18 October 2026 (05:08, 05:10 and 05:12 UTC), request IDs 6c4cb023-1ef0-4df4-bb91-6c2f436d83fd, 822349b4-6123-4ee7-9127-41531e9c52b2 and d01df0b5-4dc4-451f-b04e-25c0b2d752b7. Quotes were not executed, output values use Rango's quoted prices, and the numbers are one-morning snapshots. WBTC reserve and supply figures are from WBTC's transparency page as displayed 18 October 2026 at 05:06 UTC. Custody statements come from BitGo's own announcement, not third-party summaries. Fees quoted are the itemized lines each route displayed; this piece makes no claims beyond them.

Sources:

Rango swap page for the tested pair: https://rango.exchange/swap/eth-to-btc
Rango Learn, how to swap crypto: https://rango.exchange/learn/crypto-basics/swap-crypto-rango
Rango Learn, cross-chain aggregators and fees: https://rango.exchange/learn/decentralized-finance/crosschain-aggregators-gasfees-transaction
WBTC official site and transparency page: https://wbtc.network/ and https://wbtc.network/transparency
BitGo's WBTC multi-jurisdictional custody announcement: https://www.bitgo.com/resources/blog/bitgo-to-move-wbtc-to-multi-jurisdictional-custody-to-accelerate-global/
Bitcoin developer documentation, block chain and payment processing: https://developer.bitcoin.org/devguide/block_chain.html and https://developer.bitcoin.org/devguide/payment_processing.html