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.
Top comments (0)