What Is a Native Bitcoin Swap?

Key Takeaways

• A native Bitcoin swap exchanges real BTC directly for another asset, with no wrapped or custodial token standing in for it at any point.

• Wrapped Bitcoin versions depend on a custodian holding reserves. When FTX collapsed in 2022, the wrapped soBTC token depegged to near $8,000, less than half BTC's price at the time.

• Wrapped Bitcoin versions depend on a custodian holding reserves. When FTX collapsed in 2022, the wrapped soBTC token depegged to near $8,000, less than half BTC's price at the time.

• A native swap on BOB Gateway settles BTC to USDT, USDC, or ETH in a single transaction with no wrapping step, for a total cost of roughly 0.025% on the swap.

A native Bitcoin swap is a transaction where real BTC, the actual asset on the Bitcoin blockchain, is exchanged for another asset on another chain, without first converting that BTC into a wrapped or custodial representation of itself.

That distinction sounds small. It is not. Almost every way people have historically moved Bitcoin's value into Ethereum, Solana, or other DeFi ecosystems has required wrapping it first: locking real BTC with a custodian, receiving a token that represents a claim on that BTC, and then using the token instead of the asset. A native swap skips that step entirely. The Bitcoin moves as Bitcoin. What comes out the other side is the result of a direct swap, not a redemption of a claim ticket.

Understanding why this matters requires understanding what wrapping actually costs in technical and risk terms, and what has had to be built to make the alternative possible.

What “Native” Actually Means in This Context

In crypto, the word native refers to an asset existing on its own original chain rather than as a representation on a different chain. Native BTC is Bitcoin on the Bitcoin blockchain, secured by Bitcoin's own proof-of-work consensus, with no smart contract, custodian, or bridge standing between the holder and the asset.

The moment BTC needs to move into a place where it can be used, like an Ethereum DeFi protocol that wants collateral, the historical default approach has been wrapping. A custodian holds real BTC in reserve. In exchange, the user receives a token, most commonly WBTC, on the destination chain. The canonical technical documentation for this model describes how minting works: a merchant sends BTC to a custodian's deposit address and submits an on-chain mint request, and burning WBTC triggers the custodian to send the redeemed BTC back to the merchant's Bitcoin address. The peg holds as long as the custodian honors redemptions and reserves remain intact. That is the structural tradeoff: an Ethereum-compatible token, in exchange for trusting a third party to keep doing its job.

A native Bitcoin swap removes that intermediary step. There is no wrapped token sitting between the BTC and the destination asset. The swap happens directly: real BTC goes in, the destination asset comes out, and at no point does a custodian hold a claim that the user is relying on to be honored later.

Why Wrapping Introduces Risk That Native Swaps Avoid

The case for native swaps is grounded in what has actually happened to wrapped assets when the custody arrangement behind them broke down. When FTX filed for bankruptcy in November 2022, soBTC, a wrapped Bitcoin token issued on Solana through FTX and Alameda, depegged severely, trading near $8,000, less than half of BTC's actual price at the time. Holders of the wrapped token had no reliable path back to the underlying BTC because the entity responsible for honoring redemptions was collapsing. The token did not fail through a smart contract bug or a market crash. It failed because the custodian backing it stopped functioning as a going concern.

The pattern across wrapped assets and the bridges that move them is the same: centralizing trust in a single custodian, multisig, or bridge contract creates a concentrated point of failure. A properly designed native swap removes that point of failure from the path between the user's Bitcoin and the asset they want.

Why Native Bitcoin Swaps Are Technically Hard to Build

If removing the custodian were simple, every wrapped Bitcoin product would already have done it. Bitcoin's scripting language was deliberately designed without the complex programmability that Ethereum and similar chains use, which constrains its ability to natively support DeFi-style smart contracts or multi-chain interoperability logic.

This is the technical reason native Bitcoin swaps required new infrastructure rather than simply being available from day one. Bitcoin was not built to directly verify what happens on another chain, and building that verification capability without falling back to a trusted custodian is the actual engineering problem.

Intent-based bridging has become popular in the Ethereum space as the rise of countless L2s requires a new form of interaction that should remain abstract of the underlying chain(s). While intent-based bridging is available on EVM and other chains with Turing-complete smart contracts, intents have eluded the Bitcoin space thus far.

To solve the Native BTC swaps problem, BOB proposed Bitcoin intents as a two-way solution to allow users, DAOs, builders and anyone else to seamlessly interoperate between Bitcoin and EVM/Non-EVM turing complete chains, in a secure and trustless manner.

How a Native Bitcoin Swap Actually Works

BOB Gateway is a working example of this infrastructure in production. It is a Bitcoin intent and RFQ-based swap protocol that lets users swap BTC on the Bitcoin network directly for assets on connected chains, including Ethereum, Base, and BNB Chain, and swap back in the other direction.

• Intents instead of direct contract calls. Rather than requiring Bitcoin itself to execute complex logic, the user expresses an intent, what they want to swap and what they want to receive, and a network of solvers competes to fill that intent at the best available rate. The solver model also explains why native swaps can offer competitive rates: instead of routing through a single fixed pool, the swap pulls from whichever liquidity provider currently offers the best execution.
• Trust-minimized verification instead of a custodian's word. BOB Gateway settles using onchain verification of Bitcoin transactions directly, rather than relying on a custodian or oracle to attest that a deposit happened. For onramps, the protocol verifies Bitcoin network confirmations. For offramps, verification goes further - an onchain Bitcoin light client checks cryptographic proof of the transaction directly on the destination chain. In both directions, nobody has to be trusted to report what happened on the Bitcoin network.
• A single transaction from the user's side. The complexity of routing across chains, finding the best liquidity, and settling the destination asset all happens behind one Bitcoin transaction from the user's side. BOB Gateway verifies the transaction, executes the swap on the destination chain, and routes through the best available path across chains, liquidity sources, and decentralized exchanges.

The result is a swap where the asset that moves is BTC itself, the verification is cryptographic rather than custodial, and the experience is one transaction rather than a multi-step wrap-then-bridge-then-swap process. For a full breakdown of the fee and settlement-time differences across non-custodial protocols, see

For a full breakdown of fee and settlement-time differences across non-custodial protocols, see BTC to USDT Swap Fees Compared: BOB Gateway, THORChain and Near Intents.

What Is the Difference Between a Native Swap and a Bridged or Wrapped Swap?

The terms get used loosely enough in crypto that it's worth separating them precisely, because each describes a different point on the trust spectrum.

A wrapped swap mints a representative token on a destination chain backed by BTC held with a custodian. The token trades freely in that chain's DeFi ecosystem, but its value depends entirely on the custodian continuing to hold and eventually release the backing BTC. That is the exact dependency that failed when soBTC depegged.

A bridged swap, in the traditional sense, moves an asset across chains using a bridge contract, often a multisig or validator set that locks the asset on one side and mints or releases an equivalent on the other. This is structurally similar to wrapping, just generalized beyond Bitcoin specifically, and it inherits the same concentrated point of failure the bridge exploit research above identifies as the source of billions in losses.

A native swap is neither. There is no intermediate token minted on the user's behalf and no bridge contract holding a pooled reserve an attacker could drain in one transaction. The swap settles by verifying the actual Bitcoin transaction cryptographically and releasing the destination asset based on that verified proof. For a deeper comparison of how custodial, atomic-swap, wrapped, and native mechanisms differ mechanically, see How Bitcoin Swaps Actually Work and Custodial vs. Non-Custodial Bitcoin Swaps.

What Native Bitcoin Swaps Are Actually Used For

The most direct use case is the simplest: a Bitcoin holder who wants exposure to a stablecoin or a different chain's ecosystem without trusting a custodian with their BTC first. BOB Gateway's initial swap release supported direct BTC swaps into USDC, USDT, and ETH on Ethereum and Base, covering the most common reason someone would want to move out of BTC: accessing dollar-denominated liquidity or a different asset's price exposure without going through a centralized exchange. See Cheapest Way to Convert Bitcoin to USDT in 2026 for a full cost breakdown of this specific use case.

Beyond simple swaps, native BTC infrastructure is positioned as the foundation for using Bitcoin as collateral in DeFi without wrapping it first. BOB's documentation describes building financial applications using native Bitcoin as collateral, including lending protocols, yield strategies, and liquidity pools with native BTC pairs.

This extends beyond simple swaps too. BOB has implemented custom actions on destination chains using LayerZero's messaging infrastructure, so a native BTC send can route through to a destination chain and execute an arbitrary action automatically, such as depositing directly into a lending protocol on Base. The native swap can be the first step in a more complex DeFi action, still requiring only a single Bitcoin transaction.

For developers and protocols rather than individual holders, BOB Gateway is available via an API and an SDK that exchanges, wallets and DeFi protocols can integrate to offer native BTC functionality without building the underlying verification and routing infrastructure themselves. Any product that integrates the SDK inherits the same trust-minimized settlement model.

Why This Matters for Anyone Holding Bitcoin

Bitcoin has the deepest liquidity, the longest security track record, and the most recognized brand of any crypto asset. For years, the tradeoff for using that asset productively beyond simply holding it was accepting custodial risk on top of Bitcoin's own security.

Native swaps remove that tradeoff. The infrastructure that makes a native Bitcoin swap possible, intent-based routing, cryptographic verification through on-chain light clients, and single-transaction settlement, means a Bitcoin holder can access another chain's assets or DeFi protocols without first deciding to trust a custodian with their BTC.

This does not mean every risk disappears. Smart contracts on the destination chain still carry their own audit and security considerations, and the protocols implementing native swap infrastructure are still relatively new compared to Bitcoin itself. But the specific risk that defined wrapped Bitcoin for years, a custodian or bridge operator failing and leaving holders with a depegged or irredeemable token – is structurally removed when the swap verifies the Bitcoin transaction directly rather than trusting an intermediary's attestation.

For a Bitcoin holder deciding how to move value into DeFi, a native swap answers a simple question: can I get from BTC to the asset I want without handing my Bitcoin to someone else first. The infrastructure now exists to answer yes. See BOB Gateway for a working example. For the broader picture of what building the Bank of Bitcoin looks like, see BOB’s Bank of Bitcoin vision.