Blog / EXECUTION / NATIVE BTC

Native BTC Swaps Without Wrapping

Wrapped Bitcoin is a claim on BTC sitting somewhere else. A native BTC swap moves real Bitcoin and settles the asset you picked on the other side. Here is the difference, the failure modes of wrap paths, and how RAVN handles it.

Native path versus wrap path
Native path versus wrap path

Quick answer

Native BTC swaps without wrapping means you start or end with real Bitcoin on the Bitcoin network, not a wrapped stand-in you must mint first. Destination assets settle as the canonical token on their chain (ETH, SOL, USDC on the chain you chose, and so on). On RAVN, eligible venues race in parallel. Ranking targets best execution: net take-home after costs, not a headline mid-market price.

Wrapped BTC is not Bitcoin

People say "BTC on Ethereum" when they mean wBTC, cbBTC, or another IOU. Those tokens can trade, LP, and collateralize. They still sit on top of a mint, burn, and custody design. That is a different asset class from a UTXO on Bitcoin mainnet.

Native BTCWrapped BTC (e.g. wBTC, cbBTC)
ChainBitcoinUsually EVM or another smart-contract chain
What you holdBitcoin UTXOsA token that claims 1:1 backing
Typical useSettlement, self-custody, exitsDeFi, EVM liquidity, collaterals
Extra trustBitcoin consensus + your keysMinter, custodian, or protocol design of the wrap

Neither is "wrong." Confusing them is wrong. If you want ether, SOL, or USDC, wrapping BTC first is often an extra hop you did not ask for. If you want mainnet Bitcoin out, a wrap on Solana or Ethereum is not the finish line.

How people usually leave Bitcoin (and what breaks)

  • CEX. Deposit BTC, trade, withdraw. Works. Custodial while funds sit on the exchange. KYC is normal.
  • Wrap then use DeFi. Mint or buy wBTC or cbBTC, then swap on an AMM. Fine when you need that token. Bad when you thought you were selling Bitcoin for ETH or SOL in one clean step.
  • Bridge aggregators. Optimized for chain count. Many paths still touch wraps or multi-hop bridge designs. Native Bitcoin is hard or missing.
  • Native execution layer. Sell or buy real BTC against destination liquidity through venues built for that job. One quote interface. Canonical asset out.

RAVN is built for the last path. Constraints that hold on every route: no RAVN custody, no RAVN settlement contracts, no wrap as the product default, canonical destination asset.

What "canonical asset" means on a BTC route

Canonical means the real asset users expect on that chain, not a synthetic RAVN invented:

  • InNative BTC on Bitcoin when BTC is the origin.
  • OutETH as ether, SOL as Solana native, USDC as the USDC contract on the chain you selected, BTC as mainnet Bitcoin when BTC is the destination.
  • NotA RAVN-minted receipt token or a forced wrap hop you did not choose.

If you deliberately select wBTC or cbBTC as the destination, that is a different trade. The product language for default BTC corridors is native in, canonical out.

How RAVN executes native BTC without a wrap hop

  1. You request a quote for a pair that includes native Bitcoin (for example BTC to SOL, SOL to BTC, BTC to ETH, BTC to USDC).
  2. RAVN detects a BTC cross-chain route and queries eligible venues in parallel.
  3. Live native-BTC capable venues include Garden Finance (HTLC atomic swaps), Relay, and NEAR Intents when the pair is supported. They are complements: coverage and speed differ by pair and size.
  4. The smart order router ranks by best execution: net output after estimated costs, speed when quotes are close, and firm or gasless properties when those still win on the guaranteed floor.
  5. You complete one execution type: often DEPOSIT (send BTC to a venue address) or TRANSACTION / SIGNATURE on the non-BTC leg, depending on the winner.
  6. Status moves pending to processing to success (or refunded / failed). Destination is the asset and chain you selected.

RAVN does not hold the BTC in a company wallet. Settlement sits on independent venue rails. Integrators branch on a single executionType field.

Wrap path vs native path (same user goal)

Goal example: turn Bitcoin into SOL you can use on Solana.

StepTypical wrap pathNative path on RAVN
1Get BTC onto a venue that mints or sells a wrapQuote BTC to SOL directly
2Hold wBTC or cbBTC (or bridge)Venues race Garden, Relay, NEAR Intents
3Swap wrap to SOL on another marketOne ranked quote, one execution flow
EndSOL, after extra hops and wrap riskCanonical SOL, if that is what you selected

Fewer hops is not magic. It is fewer places to mis-select a chain, mis-read a token, or sit in a wrap you never wanted.

When wrapping still makes sense

  • You need BTC exposure inside a specific EVM protocol that only lists wBTC or cbBTC.
  • Your treasury policy is written around a named wrap contract.
  • You are LP or borrow against that exact collateral type.

Use a wrap when the wrap is the product. Do not use a wrap as a silent default when the product should have been ETH, SOL, or USDC.

Fees, gas, and what native BTC costs

  • Direct app users: zero RAVN markup. Venue spread and network costs still apply.
  • Integrator API: native BTC sits on the highest published bps tier. Fees show in the quote.
  • Gas: RAVN adds no gas markup. Deposit and on-chain routes use standard network gas where required. RFQ gasless behavior applies on eligible EVM RFQ legs only, not as a blanket claim on every BTC route.

Bitcoin confirmations set a floor on timing. Quotes and in-app status are the source of truth for a specific fill.

Pair guides that use this model

Try it in the app

Live in beta. Parallel venues, best execution, canonical assets. RAVN never holds your funds.

FAQ

What is a native BTC swap?

A native BTC swap uses real Bitcoin on the Bitcoin network on at least one side of the trade, and delivers the destination asset as the canonical token on its chain. You are not forced through wBTC or cbBTC as an intermediate product RAVN requires.

Is wBTC the same as Bitcoin?

No. wBTC is an ERC-20 token on Ethereum backed by a custody and mint process. It is useful in DeFi. It is not mainnet Bitcoin in a UTXO wallet.

Does RAVN ever give me wrapped BTC?

Only if you select a wrapped asset as the destination on purpose. Default product language is canonical asset on the destination. For Bitcoin as destination, that means native BTC.

Which venues handle native BTC on RAVN?

Eligible native BTC routes race Garden Finance (HTLC atomic swaps), Relay, and NEAR Intents when the pair is available. The smart order router picks best execution across them.

Is this the same as a bridge?

No. Classic bridges lock and mint representations. RAVN routes through RFQ, intents, solvers, and native-BTC venues that settle the real destination asset without a RAVN-operated lock-and-mint bridge.

Continue reading