Start typing to search this publication.
ONAR
Open menu

Subscribe to ONAR

Get new posts delivered straight to your inbox.

Can I swap SOL directly to Bitcoin? Native BTC vs wrapped BTC, tested live (19 October 2026)

onar avatar onar
7 min read

Yes. A direct SOL to BTC swap route exists, and I pulled it live from the Rango dApp on 19 October 2026 at 05:05 UTC. For 1 SOL, the routing response returned 0.00125917 BTC through a single bridge step, with the destination asset listed as BTC on the BTC blockchain and no contract address. No contract address means no wrapped representation: the output on that route is native Bitcoin.

That distinction is the whole point of this article. Native BTC and wrapped BTC are not interchangeable, and if you do not check which one a route delivers, you can end up holding a claim on Bitcoin instead of Bitcoin itself.

Below: what the live route showed, what native versus wrapped actually means, and how to check the destination asset of any cross-chain swap before you sign.

Can I swap SOL directly to Bitcoin?

Short answer: yes. 1 SOL went in, 0.00125917 BTC came out in the quote, and the whole route needed one signature.

The longer answer depends on what "directly" means. A swap from Solana to Bitcoin crosses two incompatible networks. Something has to carry value between them. On this route, a single swapper did the job: the response listed one step, swapper type "bridge", the swapper RelayProtocol, and the chain type "INTER_CHAIN". No second hop, no intermediate token in my wallet, no manual wrap step.

Rango itself is not the thing moving the funds. It is a cross-chain swap execution aggregator: it compares routes across many liquidity sources, DEXs, bridges and related infrastructure, then shows the routes that fit the pair you entered. Its published stats say it supports 80+ chains overall, and it has operated with a zero-exploit history since August 2021.

Will I receive native BTC or wrapped BTC when I swap from Solana?

On the route I tested, native BTC. Here is the evidence, straight from the routing response:

  • destination blockchain: BTC (the Bitcoin chain itself)

  • destination symbol: BTC

  • destination contract address: null (none)

  • destination decimals: 8, which is Bitcoin's native divisibility

  • destination USD price in the route feed: $82,718 at quote time

Wrapped Bitcoin behaves differently. WBTC is an ERC-20 token backed 1:1 by Bitcoin held in custody, per both wbtc.network and DefiLlama, whose methodology page describes its TVL as the BTC deposits in custody used to mint WBTC. DefiLlama put that collateral at $9.488 billion as of 18 October 2026, against an all-time high of $15.835 billion on 10 November 2021.

Two tests tell the two assets apart in seconds:

  • Native BTC has no contract address because it does not need one. It lives on the Bitcoin chain, and its smallest unit is the satoshi.

  • Wrapped BTC always carries a contract address on whatever chain it is minted to, because a smart contract holds the custody accounting.

In my capture, to.address was null on blockchain BTC. That is the native asset.

What did the live SOL to BTC route look like on 19 October 2026?

Method first, like any measurement: I opened the public swap page for the pair at rango.exchange/swap/sol-to-btc, entered 1 SOL in the widget like a normal user would, and captured the routing response the page itself sent (request id 8eb58152-3445-4861-8e2a-db28b9fae416, captured 2026-10-19 at 05:05 UTC). Everything below is from that single response plus the page's own displayed numbers.

The widget on the page showed:

  • input: 1 SOL, valued at about $105.63 in the route feed

  • output: 0.00125917 BTC

  • the page's own SOL/Bitcoin market chart showed a mid-market rate of 0.0012757 BTC at the same moment

The quote's fee lines:

  • network fee: 0.00001 SOL paid from the source wallet, about one tenth of a cent

  • swapper fee: 0.009597439 SOL, about $1.01, deducted from the output

  • overall price impact shown: minus $1.473975, or minus 1.39 percent

So the final output of 0.00125917 BTC, worth about $104.15 at the route's own BTC price, sat roughly 1.3 percent below the mid-market rate the page charted. That gap is the real cost of execution. The market exchange rate is not the price you get. Fees, liquidity and price impact are priced in before your output number appears.

One honest limitation of this test: it is one quote at one moment. Cross-chain pricing moves constantly, and a quote captured at 05:05 UTC is a snapshot, not a guarantee. Small amounts also carry proportionally larger relative costs, which is exactly what the numbers above show on a $105 trade.

!SOL to BTC swap widget on rango.exchange, 1 SOL to 0.00125917 BTC, screenshot taken 19 October 2026

What is the difference between native BTC and wrapped BTC?

The differences that matter at the destination are custody, environment and failure modes.

Custody. Native BTC is the asset. Nobody holds it for you. WBTC is a claim: a 1:1 backed token whose Bitcoin collateral sits with custodians, and whose minting and burning are managed processes. Being backed 1:1 is a design property, not a physics law. Trusting it means trusting the custody and audit arrangements behind it.

Environment. Native BTC can only live on the Bitcoin chain, where Bitcoin's own script and UTXO rules apply. WBTC lives on smart contract chains like Ethereum (and, per wbtc.network, on networks such as Tron, BNB Chain and Base), where it can plug into lending markets, liquidity pools and collateral systems that Bitcoin's base layer does not expose.

Failure modes. A native BTC holding fails only if you lose your keys or Bitcoin fails. A wrapped asset has the extra layer of whatever backs it. The ethereum.org bridge documentation describes this trade-off directly: bridges transfer assets and information between chains, and the mechanism differs from holding the asset natively. It does not tell you one is better. It tells you the two things are different instruments.

Neither answer is universally right, which is why routes should state their destination asset clearly.

When does a wrapped asset make more sense than native BTC?

If your goal is to hold Bitcoin as money or a reserve, take native BTC. That is what the tested route delivers.

If your goal is to use Bitcoin's value inside DeFi, a wrapped asset is the tool, and it is the more useful one there. You cannot post native BTC as collateral in an Ethereum lending market. WBTC exists precisely for that job, and its roughly $9.5 billion of collateral (DefiLlama, 18 October 2026) shows the size of that use case, even down from its 2021 peak of $15.835 billion.

The mistake to avoid is mixing the two goals without noticing. Sleep-walking from "I want Bitcoin" into "I hold an IOU on a smart contract chain" is not a routing failure. It is a reading failure. Check the destination.

How do I check which asset a route actually delivers?

Before you sign any cross-chain swap, check three fields:

  • destination chain: is it the Bitcoin chain, or an Ethereum-style chain?

  • destination token: does it say BTC, or WBTC (or another wrapped ticker)?

  • contract address: a contract address on the destination means wrapped. No address on Bitcoin means native.

In the quote I captured, all three said native: chain BTC, token BTC, no contract address. If a route had delivered a wrapped asset, that would not make it wrong; it would make it a different product, and it should be priced and chosen as one.

A second check that costs nothing: compare the route's quoted output against the mid-market rate on the same page, like the 0.00125917 output versus the 0.0012757 chart rate in my capture. If the executable output sits far below mid-market, you now know what execution is costing you before you commit.

How long does a SOL to BTC swap take, and what is the minimum amount?

From the same route response:

  • estimated time for the quoted swap: 30 seconds

  • the route's own historical time statistics: minimum 9 seconds, average 24 seconds, maximum 436 seconds

  • minimum input amount accepted on this route: 0.018925057 SOL, about $2 at quote time

  • signatures required: 1

Read those as what they are: an estimate and a historical spread, not a promise. A specific swap does not always take X minutes; network conditions on two different chains decide the actual time. But the numbers do say this route is fast by design, with a single signing step and no manual intermediate transactions.

The short version

  • can you swap SOL directly to Bitcoin? Yes, and the route I tested on 19 October 2026 delivered native BTC: chain BTC, symbol BTC, no contract address, in one step.

  • native or wrapped? Native on this route. Wrapped BTC (WBTC) is a 1:1 backed ERC-20 with custodial collateral, about $9.488 billion of it per DefiLlama on 18 October 2026.

  • what did execution cost? On a 1 SOL test, output landed about 1.3 percent below mid-market, with the fee lines and price impact shown above.

  • how do you verify? Check destination chain, destination token and contract address before signing.

Sources

  • Rango, SOL to BTC execution page (canon): https://rango.exchange/swap/sol-to-btc

  • Rango, How to Swap Crypto with Rango: https://rango.exchange/learn/crypto-basics/swap-crypto-rango

  • Rango, Bridge vs Swap in Crypto: https://rango.exchange/learn/crypto-basics/bridge-vs-swap

  • wbtc.network, WBTC official site (1:1 backing, custody, supported networks): https://wbtc.network/

  • DefiLlama, WBTC TVL and methodology: https://defillama.com/protocol/wbtc

  • ethereum.org, Introduction to blockchain bridges (update July 24, 2026): https://ethereum.org/en/bridges/

  • CoinGecko, price cross-check on 19 October 2026 at 05:06 UTC (BTC $82,508, SOL $105.23, within about 0.4 percent of the prices in Rango's route feed at quote time): https://www.coingecko.com/en/coins/bitcoin

*Live quote data in this article: Rango routing response request id 8eb58152-3445-4861-8e2a-db28b9fae416, captured from rango.exchange/swap/sol-to-btc at 2026-10-19 05:05 UTC. Quotes change; numbers above are a dated snapshot, not a standing offer.*

Subscribe to ONAR