No. BOB Gateway takes native BTC directly: you send real bitcoin in one Bitcoin transaction, and a solver delivers the asset you asked for on the destination chain. Wrapped BTC only appears if you deliberately choose a wrapped token, such as WBTC on Ethereum, as the asset you want to receive.
That answer is worth slowing down on, because "moving BTC to another chain" hides an important detail. Native BTC only exists on the Bitcoin network, so every cross-chain route is really a choice about what you end up holding and who you trust along the way. This article walks through what "native" means at each step of a Gateway swap, which other services work the same way, how the three main wrapped BTC models actually differ, and when wrapping is still the better tool.
What "native" means at each step
BOB Gateway is an intent-based swap protocol, not a lock-and-mint bridge. According to BOB's route guide for moving native BTC, a swap works like this. You request a quote and get a signed quote with a guaranteed minimum output. You create an order and receive a unique Bitcoin deposit address for it. You sign one Bitcoin transaction to that address. Once the deposit confirms, the solver delivers your output in a single transaction, and if it cannot, your BTC is refunded. The destination chain's gas comes out of the quote, so you do not need to hold that chain's gas token to receive your asset.
Notice what never happens in that flow. No custodian mints a token against your BTC, no wrapped asset passes through your wallet, and you never have to acquire WBTC or tBTC before you start. Compare that with manual wrapping, where you first send BTC to a bridge or custodian, receive a wrapped token, and only then swap or use that token yourself. Gateway removes that first step rather than improving it.
One honest caveat: a swap changes what you hold. If you swap BTC into ETH or a stablecoin, you no longer have bitcoin exposure, whereas a wrapped token keeps your exposure and adds an intermediary. Which of those you want decides which route fits, as the sections below show.
Which Bitcoin bridge supports native BTC without requiring wrapped assets?
Four services take native BTC straight from a Bitcoin wallet and deliver a destination asset in one flow, with no wrapping step imposed on you:
- BOB Gateway. Native BTC in, your chosen asset out on 12 chains including Ethereum and Base, per BOB's route guide (routes checked 30 October 2026).
- Garden Finance. Your BTC is locked in a hash time-locked contract and a solver locks the matching destination asset, so the swap settles on both sides or refunds. Garden describes this flow in its write-up of its native Bitcoin routes on LI.FI.
- THORChain. Liquidity pools hold native assets, so you send BTC to a vault and receive native ETH or another native coin. THORChain's own docs stress that you swap real coins, not synthetic versions.
- Chainflip. Validators run threshold-signature vaults and swap native BTC directly for ETH, SOL or stablecoins, as Chainflip's guide to native asset swaps explains. One limit worth knowing: Chainflip's supported chain list, checked 30 October 2026, does not include Base.
One service deliberately sits outside this list. tBTC also starts with native BTC, but its entire product is minting a wrapped token, so it belongs in the comparison below rather than here.
The three wrapped models, compared honestly
If you do end up holding wrapped BTC, the question that matters is who holds the real bitcoin behind your token. The three models most people meet are these:
| Token | Who holds the BTC | How redemption works |
|---|---|---|
| WBTC | BitGo, a licensed custodian, in multi-signature cold storage | Only identity-verified merchants can mint and burn, so holders redeem through a merchant or sell the token |
| cbBTC | Coinbase, in its own custody | Coinbase customers send cbBTC back to their Coinbase account, where it converts 1:1 into BTC |
| tBTC | No single custodian; a rotating group of Threshold node operators using threshold signing | Burn the tBTC and the signer group releases BTC to your Bitcoin address |
The table shows that all three tokens track the same underlying asset while asking you to trust very different parties, from one custodian, to one exchange, to a rotating set of independent signers.
WBTC is the oldest and most liquid option. BOB's guide to wrapped BTC notes that BitGo holds the underlying BTC and that WBTC has been the DeFi default since 2019, with deep liquidity across Aave, Uniswap, Curve and most other major protocols. The WBTC site adds that every token is backed 1:1 by bitcoin in custody and verifiable through an on-chain proof of reserves, and that only verified institutions approved through DAO governance can mint and burn. The tradeoff is a single point of failure: if BitGo were hacked, sanctioned or shut down, WBTC holders would feel it.
cbBTC swaps the custodian, not the model. Coinbase's cbBTC page states that its wrapped assets are backed 1:1 and held in custody by Coinbase, and Coinbase's help pages list cbBTC on Base, Ethereum, Solana and Arbitrum. It is the natural choice if you already live in the Coinbase and Base ecosystem and are comfortable trusting a large, regulated, publicly traded company. It is still one company.
tBTC removes the single custodian. Threshold's tBTC documentation describes a randomly selected group of node operators securing deposited bitcoin through threshold cryptography, with a threshold majority required before any coins move and the operator selection rotating every two weeks. Minting and redemption each cost 0.2 percent. The tradeoff, as BOB's wrapped BTC guide puts it, is thinner liquidity, fewer protocol integrations and smart contract risk in place of custodian risk.
When wrapping still makes sense, and when a direct swap fits better
Wrapping makes sense when you want to keep bitcoin exposure while putting it to work. Posting WBTC as collateral in a lending market, or supplying a BTC pair on a DEX, is only possible with a token that tracks BTC, and for that job the deepest liquidity usually wins even if the custody model is plain. Choose the model whose trust assumptions you can live with, and size the position accordingly.
A direct swap fits better when you actually want the other asset: ETH to pay gas and use Ethereum DeFi, a stablecoin to spend or park value, or cbBTC on Base. Routing that through a wrap first adds a custodian and a step for no benefit. The exchange route is worse still, since it takes four steps across two accounts: deposit, sell, buy and withdraw.
Gateway itself shows the two ideas are not enemies. It has a dedicated BTC to WBTC route on Ethereum for people who genuinely want the wrapped token, quoting delivery in about 10 minutes, and the same route runs in reverse when you want native BTC back. Wrapping becomes an outcome you choose, not a prerequisite you are forced through.
Bottom line
BOB Gateway does not require wrapped BTC. You send native bitcoin in one transaction and receive the asset you picked, on Ethereum, Base or another supported chain, with a refund if the swap cannot complete. Hold wrapped BTC when keeping bitcoin exposure inside DeFi is the goal, and pick between BitGo, Coinbase and Threshold based on who you are willing to trust. Swap directly when the destination asset is what you actually want.
Top comments (0)