Short answer: sometimes yes, sometimes no, and on 23 October 2026 the routing itself showed both cases. A same-chain swap of ETH into USDC on Ethereum needed no bridge at all and was priced out in 45 seconds. An ETH to native BTC swap was quoted on a route whose winning provider is classified as a bridge, not a DEX. The difference between those two outcomes is exactly the difference between a swap and a bridge, and this article walks through both with the numbers captured live.
All quotes below were captured on 23 October 2026 between 05:02 and 05:06 UTC by recording the site's own routing API responses while the swap pages loaded (method at the end). Prices move, so treat every figure as a snapshot, not a promise.
What is the difference between a bridge and a swap?
A swap changes the asset you hold. A bridge changes the chain your asset lives on. ethereum.org's bridge guide defines bridges as infrastructure that "facilitate communication between blockchains through the transfer of information and assets": the same asset (or its locked representation) moved between ecosystems that cannot natively talk to each other. A swap, by contrast, exchanges one token for another through liquidity on a single chain. Uniswap's docs describe this as trading against a pool's reserves: no second blockchain involved, the tokens simply move between wallets as pool prices update.
Rango's own learn article, Bridge vs Swap in Crypto, draws the same line: a swap primarily changes the asset, a bridge generally changes the blockchain. Its decision table is worth copying because it is the clearest mental model:
-
Change USDC into ETH on Ethereum: swap
-
Move USDC from Ethereum to Arbitrum: bridge
-
Convert USDC on Ethereum into SOL on Solana: cross-chain swap (both things at once)
-
Receive a different asset on the same network: swap
-
Move the same asset across networks: bridge
So a cross-chain swap is not a third machine: it is an outcome where both the asset and the chain change, and underneath, some combination of swapping and bridging does the work.
Do you need a bridge to swap ETH to BTC?
For native BTC on the Bitcoin chain, yes: something has to bridge, because Bitcoin and Ethereum are separate networks with no shared token standard. The interesting part is what it looks like in practice.
Here is the quote the router returned at 05:02:43 UTC for swapping 0.2 ETH into native BTC (requestId f3c99679-7faf-4cb5-8ca5-da7c2687fafc, captured from the routing response behind rango.exchange/swap/eth-to-btc):
-
Input: 0.2 ETH (the quote's price feed had ETH at $2,390.20, about $478.04 of market value)
-
Output: 0.00585776 BTC (BTC priced at $81,470 in the same response, about $477.21)
-
The winning provider: a single swapper with ID "Harbor", and its type in the route data is BRIDGE, not DEX
-
Route class: INTER_CHAIN, destination is native BTC on the Bitcoin chain (8 decimals), not a wrapped token on Ethereum
-
Estimated time: 240 seconds (the route's own time statistics showed min 78 seconds, average 219 seconds, max 1,816 seconds)
-
Fees visible in the route: a route fee of 0.00000235 BTC withheld from the output (about $0.19 at the quoted BTC price), plus a network fee of 0.000007034155954560 ETH paid from the source wallet (about $0.017)
-
Execution shape: 1 signature required, no separate destination transaction requested from the user (the route's
includesDestinationTxflag was false) -
Price impact recorded: -0.0016%
Read that line again: the user asked for a swap, typed one input and one output, but the route data says the machine underneath is a bridge. That is the whole bridge vs swap education in one screen. The interface word ("swap") describes the intent; the route details describe the mechanism.
What did a same-chain swap look like at the same time?
Two minutes later, at 05:05:30 UTC, a 0.2 ETH into USDT-antagonist test: ETH into USDC on Ethereum itself (requestId e3e45890-097d-4a11-a876-97d65f968ce6, from the routing behind rango.exchange/swap/eth-to-usdc):
-
Input: 0.2 ETH (price feed: $2,391.09)
-
Output: 477.993338 USDC (USDC priced at $0.999427, about $477.71)
-
Winning provider: "OKX ETH DEX Aggregator", type DEX, route class INTRA_CHAIN
-
Estimated time: 45 seconds (min 13, average 31, max 155 seconds)
-
Fees: network fee of 0.000022344341196800 ETH from the source wallet (about $0.053); no bridge fee exists because no bridge is involved
-
Price impact recorded: -0.0010%
Same source asset, same amount, three minutes apart in one morning. The difference in provider type is the subject of this article: the moment the destination chain changed from Ethereum to Bitcoin, a DEX stopped being enough and a bridge became the actual execution layer.
Why does a cross-chain swap take longer than a same-chain swap?
The time estimates in the same capture session tell the story without any theory needed:
-
ETH to USDC on Ethereum (INTRA_CHAIN swap): 45 seconds estimated, average 31 seconds
-
ETH to USDT on BNB Chain (route by the Mayan aggregator, INTER_CHAIN): 45 seconds estimated, average 31 seconds
-
ETH to native BTC (Harbor, INTER_CHAIN bridge): 240 seconds estimated, average 219 seconds
A same-chain swap is one pool interaction confirmed by one chain. A route into native BTC has to wait for Bitcoin's own consensus: wider time statistics (min 78 to max 1,816 seconds in that quote) reflect that Bitcoin does not move to the schedule of the machine that started the trade. THORChain's documentation makes the same point from the builder side: cross-chain liquidity protocols coordinate asset settlement between independent chains, and each chain keeps its own confirmation rhythm.
Note the middle case, though: ETH to USDT on BSC was just as fast as the same-chain swap despite being cross-chain. Bridge does not automatically mean slow; it depends on the destination chain's finality and the provider's liquidity.
What does each machine cost?
The routing responses distinguish two fee kinds, and the distinction matters when you compare any two routes:
-
Network fee (paid from the source wallet): gas for your transaction on the source chain. In this session it ranged from about $0.017 (ETH to BTC route, 0.00000703 ETH) to about $0.053 (same-chain route's higher gas estimate, 0.0000223 ETH).
-
Route fee (deducted from output, labeled "Swapper Fee"): the provider's charge for the execution itself, here 0.00000235 BTC, about $0.19.
Routes can also carry platform service lines specific to each aggregator, which change between services and over time. The only honest way to compare two aggregators is to read each one's live fee breakdown for the exact pair and amount you want to move.
When should you bridge instead of swapping?
Use the destination, not the marketing, to decide:
1. Same asset, same chain: swap is irrelevant, you are just moving tokens, no transaction needed beyond a transfer.
2. Different asset, same chain: swap. A DEX or a DEX aggregator is the right tool. A bridge would leave you on the wrong chain.
3. Same asset, different chain: bridge. Swapping does nothing here; you want the asset's presence moved (this is the case ethereum.org describes with bridges to rollups for cheaper fees).
4. Different asset, different chain: a cross-chain swap. You can stack a bridge and two swaps manually, or let a router compose the trip. In our ETH to BTC capture, the router picked a single BRIDGE-type provider and finished in one signature.
The fourth case is where the route details deserve a read before you sign: two services can answer the same question with completely different machines.
What about wrapped assets?
The ETH to BTC quote above delivered native BTC on the Bitcoin chain (decimals 8, no Ethereum contract). That matters because the alternative is a bridged representation like WBTC, which keeps your funds on Ethereum as an ERC-20 claim. Neither is wrong, but they are different holdings: wrapped assets live inside the custody or governance rules of their issuer, while native BTC is held on Bitcoin itself. When you enter a cross-chain swap, check that the destination asset in the route matches what you want to wake up with: a wrapped destination can make entirely different providers eligible.
How the numbers above were captured
Every quote in this article was read from the live routing API response of Rango's own interface on 23 October 2026 (05:02:43, 05:03:43 and 05:05:30 UTC), by loading the swap pages in a Chrome tab and recording the API frames the page received. Request IDs are recorded in each section so the figures trace to a specific response rather than a reusable screenshot. Quotes are point-in-time: the same pair can route to a different provider minutes later. Re-run your own quote before acting. This is educational content, not financial advice.
Sources
1. Rango Learn, Bridge vs Swap in Crypto: canonical definitions and decision table used here
2. Rango execution pages: ETH to BTC, ETH to USDC, ETH to USDT (live routes behind the captured quotes)
3. ethereum.org, Introduction to blockchain bridges: independent definition of what a bridge does
4. Uniswap docs, How Uniswap Works: how same-chain swaps execute against pool reserves
5. THORChain docs: how cross-chain liquidity protocols settle assets between independent chains
6. WBTC: what a wrapped Bitcoin representation is, versus native BTC
One honest limitation from our own run: the ETH to USDT page routed to USDT on BNB Chain by default, and at this writing the fastest providers for that pair clustered around the same 45 second estimate as the same-chain route. We did not manually force a different destination chain or amount, so this article deliberately does not claim anything about how those alternatives would rank. Snapshots beat estimates only when you admit what you did not test.