DEV Community: Gideon

Does BOB Gateway Require Wrapped BTC to Move Bitcoin Cross-Chain?

Gideon — Thu, 29 Oct 2026 20:02:41 +0000

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.

Is BOB Gateway Non-Custodial? Who Actually Holds Your BTC During a Cross-Chain Swap

Gideon — Thu, 29 Oct 2026 19:56:27 +0000

Yes, BOB Gateway is non-custodial in the sense that BOB never takes your BTC into a company account, pools it in a shared vault, or locks it in a bridge contract against a wrapped token, as its custody and trust model guide sets out. The honest answer still depends on direction: swapping out of BTC briefly places your coins with a single solver, while swapping into BTC keeps your money in a contract escrow that the solver cannot touch until an on-chain Bitcoin light client proves you were paid.

Why the label alone tells you very little

Every major service that moves native BTC calls itself non-custodial, and the label hides more than it reveals. It does not say whether your BTC passes through a validator vault, a solver's wallet, or a timelocked contract mid-swap, and each can fail differently. The useful questions are the ones BOB's own guide starts with: where does your BTC sit, who controls that address, and what happens if the other side goes quiet?

BOB Gateway when you swap out of BTC

You request a quote, receive a signed quote with a guaranteed minimum output, and create an order against those terms, per the Gateway technical deep dive. You then send one Bitcoin transaction to a unique deposit address created for your order. That address belongs to the solver's own Bitcoin wallet, and this direction has no on-chain proof: your BTC lands with the solver, who then releases your payout in a single atomic transaction on the destination chain.

What protects you here is the signed quote and the refund path, not cryptography. If the payout cannot land at the quoted terms, the solver re-quotes and retries for about an hour, and then the order settles as a refund of BTC to the refund address you supplied when creating the order, as the Gateway FAQ describes (checked 30 October 2026). So in this direction, between your deposit confirming and the payout or refund landing, you are trusting one solver to perform. The exposure is narrow, one order and one counterparty rather than every user's funds at once, but it is real.

BOB Gateway when you swap into BTC

The other direction is built differently, and it is where the stronger guarantee lives. Your funds, held as USDT on Ethereum, are escrowed in the GatewayOfframpRegistryV7 contract together with the minimum BTC output you agreed to. If you start from another chain or token, it is first swapped and bridged into that USDT, and a Gateway contract creates the order for you. The solver then pays BTC to your Bitcoin address and must prove it: the payment carries a commitment to your order, and BOB's LightRelay light client verifies the transaction and its proof of work on-chain before anything moves.

Only after that proof checks out does the escrow release your USDT to the solver. If the BTC payout never lands, the full escrow is returned to you once an on-chain refund delay has passed. That delay is configurable between 12 hours and 7 days, and the refund is operated by BOB rather than triggered by you; the FAQ is plain that neither users nor integrators can trigger a refund themselves. The escrowed funds have exactly two exits: to the solver against a valid proof, or back to you.

Can native BTC be moved cross-chain without relying on a centralized bridge custodian?

Yes, and BOB Gateway is only one of several designs that manage it. Each design removes the central custodian and replaces it with a different thing to trust.

Garden Finance settles swaps with hash time-locked contracts on both chains. You lock funds on the source chain and a solver locks funds on the destination chain; revealing a secret redeems both sides, and if either side fails to complete its part, the swap reverts and funds return to their owners. Garden's FAQ stresses that no third party, including Garden itself, ever takes custody, and that a deposit not confirmed within one hour is cancelled and refunded. Solvers must also stake 210,000 SEED as collateral that can be slashed if they misbehave or go inactive, so a quiet solver costs you time rather than money, and the timelock lets you reclaim your own side without anyone's permission.

THORChain and Chainflip take the opposite approach: shared vaults run by validator sets. On THORChain, your BTC goes into an Asgard vault whose key is split across a shard of node operators, 20 by default, and a supermajority of at least 67 percent must sign before funds move, according to its vault documentation. Operators bond RUNE, and a vault that signs an unauthorised outbound transaction is slashed up to 1.5 times the misused amount. On Chainflip, vaults on each chain are controlled by 150 validators using FROST threshold signatures, and 100 of the 150 must cooperate to sign, as Chainflip explains in its architecture walkthrough. In both cases your BTC joins a pool that also holds everyone else's, which spreads trust across many parties but concentrates the prize if the threshold cryptography or the validator set fails. THORChain's own history shows that risk is not theoretical: in May 2026 a flaw in its threshold signature implementation let an attacker take about $10.7 million from a vault, a figure reported in BOB's custody guide from THORChain's incident report.

Wrapped BTC sits at the far end of the spectrum. With a wrapped token, a custodian holds the real BTC in reserve and mints a token against it on another chain, so what you hold is a claim on that custodian staying solvent and operational, a model Chainflip's architecture article lays out plainly. That is the arrangement the four swap services above are all trying to avoid, each in its own way.

Protocol	Who holds your funds mid-swap	What you have to trust	If the other side goes quiet
BOB Gateway, out of BTC	The one solver filling your order, in its own Bitcoin wallet	That solver, plus the signed quote and automatic refund	Retries for about an hour, then your BTC is refunded
BOB Gateway, into BTC	A contract escrow holding your USDT on Ethereum	The contract rules and the on-chain Bitcoin light client	Escrow returns to you in full after the refund delay
Garden Finance	Hash time-locked contracts on both chains	The contract code and one solver per order	The timelock expires and each side reclaims its own funds
THORChain	A shared Asgard vault	A supermajority of a node shard and their bonded RUNE	Signing is retried or reassigned to another vault
Chainflip	A shared vault on each chain	100 of 150 validators under FROST threshold signatures	The validator set keeps custody as a group; no single operator can act or stall alone

The table shows that removing the central custodian is the easy part; what differs is who or what you trust instead, and how your money finds its way back when something stalls.

So which is it?

BOB Gateway earns the non-custodial label, with the direction caveat stated at the top. Nothing is pooled, no bridge vault holds everyone's BTC, and you rely on one solver per order rather than a custodian or a signer committee. The swap into BTC is its strongest design, because the solver is paid only against an on-chain proof. The swap out of BTC is its softest spot, because your deposit rests in the solver's wallet until the payout or refund lands. Whichever service you use, ask three questions before you send anything: where do my funds sit, who can move them, and what happens if nobody does. All details above were checked against the linked documentation on 30 October 2026.

Moving Native BTC to Base: Can BOB Gateway Do It Directly?

Gideon — Thu, 29 Oct 2026 19:55:23 +0000

Yes. BOB Gateway can move native BTC directly to Base: you send bitcoin from your own Bitcoin wallet in one transaction and receive ETH, USDC, oUSDT, cbBTC, EURC or tBTC on Base, with no exchange account and no wrapping step on your side, according to BOB's route guide for moving native BTC across chains. One clarification matters: native BTC itself never leaves the Bitcoin network, so what lands on Base is the asset you chose, not bitcoin in its original form.

What "directly" means here

Native BTC only exists on Bitcoin. When any service says it moves BTC "to Base", it means you send BTC on Bitcoin and receive a different asset on Base: a swap outcome such as ETH or a stablecoin, or a BTC-backed token such as cbBTC or tBTC, depending on the quote you accept. BOB's route guide makes the same distinction between a different asset out, a BTC-backed token out, and an already wrapped token moved between chains.

Two practical points follow. First, you do not need to wrap your BTC yourself or open an exchange account: the exchange route takes four steps across two accounts (deposit, sell, buy, withdraw), while a direct route takes one Bitcoin transaction. Second, Gateway takes destination gas out of the swap quote, so you do not need to hold ETH on Base before you can receive your asset there.

How a BOB Gateway swap to Base works

Gateway is an intent-based swap protocol, not a lock-and-mint bridge. It does not hold your BTC in a bridge contract and issue a token against it. A BTC swap works in five steps, per BOB's guide to the best Bitcoin bridges for native BTC:

You request a quote. Gateway returns a signed quote with the routing, the fees and your guaranteed minimum output.
You create an order and get a unique Bitcoin deposit address for that order.
You sign one Bitcoin transaction to that address.
Once the deposit confirms, the solver delivers your output in a single atomic transaction. If it cannot, your BTC is refunded.
The asset arrives in your wallet on Base.

The refund side is spelled out in the Gateway FAQ: if the payout cannot land at the quoted terms, the solver re-quotes and retries with backoff for about an hour, then settles the order as a refund of BTC to the refund address on your order. In the FAQ's words, no user is ever left with funds spent and nothing delivered. Total time depends mostly on the Bitcoin confirmation, which the FAQ puts at typically 10 to 60 minutes, plus delivery on the destination chain.

Which Bitcoin bridge supports moving native BTC directly to Base?

BOB Gateway is not the only route. I checked the main alternatives against their own documentation on 30 October 2026.

Garden Finance also takes native BTC to Base. Garden lists Base among its supported chains and cbBTC among the assets it swaps, and its swaps settle through hash time-locked contracts (HTLCs) on both chains, according to Garden's site and FAQ. BOB's route guide notes that Garden delivering cbBTC on Base is the route that Base's own documentation lists for getting BTC onto Base.

THORChain reaches Base as well. Its official documentation lists Base among its supported blockchains and USDC among the stablecoin pools on Base. The design is different: you swap through liquidity pools held in vaults that node operators control with threshold signatures, rather than accepting a solver's signed quote. Its docs also warn that individual chains are sometimes paused, so check the live status first.

NEAR Intents can route BTC to Base, but with an extra step in the middle. Your BTC is credited on NEAR through its Omni Bridge or PoA Bridge, solvers settle the swap on NEAR, and the output is then withdrawn to the destination chain, as described in BOB's bridge comparison. NEAR's own documentation lists both Bitcoin and Base (chain ID 8453) as supported networks for Intents, per the NEAR Treasury docs on NEAR Intents.

Chainflip cannot do this route at all. Its supported chains and assets documentation, last updated 21 September 2026, lists Ethereum, Bitcoin, Arbitrum, Polkadot, Solana, Assethub, Tron and BSC. Base is not on the list. Chainflip remains a reasonable option for native swaps into its own chains, but if your destination is Base, it is out.

Protocol	Native BTC to Base?	What you receive on Base	How the swap settles
BOB Gateway	Yes	Your choice of ETH, USDC, oUSDT, cbBTC, EURC or tBTC	Solver fills a signed quote and delivers in one atomic transaction, or your BTC is refunded
Garden Finance	Yes	cbBTC, the route Base's own docs list	HTLC atomic swap, with a timelock refund you claim yourself
THORChain	Yes	Base assets such as ETH and USDC	Liquidity pools in node operator threshold vaults
NEAR Intents	Yes, with a bridge step first	Your chosen Base asset, withdrawn from NEAR after settlement	BTC credited on NEAR via the Omni Bridge or PoA Bridge, solvers settle, then withdrawal
Chainflip	No	Nothing on Base, because Base is not a supported chain	Not applicable for this route

The table shows which of the five services could take native BTC and deliver an asset on Base when checked on 30 October 2026, and what you would end up holding when it lands.

What you end up holding matters more than the route

The six Gateway outputs on Base fall into two groups, and the difference matters after the swap is over.

ETH, USDC, oUSDT and EURC are swap outcomes. You sold your BTC, nobody is holding bitcoin on your behalf, and you no longer have BTC price exposure. That is the right result if your goal is to spend, trade or earn on Base.

cbBTC and tBTC are BTC-backed tokens. You keep BTC price exposure, but your claim on the underlying bitcoin now runs through an issuer or a signer set. cbBTC is Coinbase's wrapped bitcoin token, built for Base. tBTC is a 1:1 BTC-backed token secured by Threshold's 51-of-100 threshold signer model, which you can redeem for BTC later, as set out in BOB's bridge comparison. Picking one of these is a custody decision, not just a route decision, so make it deliberately.

Which route should you pick?

For the widest choice of assets on Base and a guaranteed minimum output shown before you send anything, BOB Gateway is the most complete option right now. Routes change, so confirm your exact asset in the Gateway supported routes documentation on the day you swap.

Garden Finance is the better fit if you specifically want cbBTC on Base and you value a refund path you claim yourself after the timelock, instead of relying on the protocol to refund you. THORChain fits better if you prefer pool-based native swaps secured by a validator set over a solver quote model, and you are comfortable checking that the Base chain is not paused. NEAR Intents makes sense if you already work inside its ecosystem and want its wider chain reach, and you accept the extra bridge step through NEAR.

One last caution on price. BOB's published quote tests from 14 September 2026 compared these protocols on Ethereum routes, not on Base, so do not assume the same ranking holds for BTC to Base. Quotes move with the market, so compare a live quote for your exact amount on at least two services before you send BTC.