Token
Explore BTC.B swap routes
Explore how BTC.B is used as both a destination asset and a funding asset across non-custodial swap routes with live network context.
Category: Bitcoin-native asset
Common role: Core destination asset
Supported networks: 1
Popular routes: 9
What is BTC.B used for in swaps?
BTC.B usually appears in swap routes as the destination for risk-off rotations or as the source asset when users want to deploy Bitcoin value into another ecosystem.
Bitcoin routes also carry their own timing and receiving-address considerations, so BTC hubs need to explain both route direction and settlement expectations clearly.
BTC.B route overview
BTC.B hubs need more than a simple route list because Bitcoin can act as both the destination for risk-off rotations and the source asset for moving value into another ecosystem. The pair direction, the route intent, and the network context all change how that path should be described. This page groups the strongest send and receive routes so users can scan Bitcoin exits, ecosystem-entry routes, and stablecoin landings without reading duplicate route copy.
Supported networks
Each supported network changes cost, compatibility, and wallet expectations. Use the right rail for the wallet or ecosystem you plan to use next.
Popular ways to swap from BTC.B
Move BTC.B into stablecoins
These routes reduce volatility by moving BTC.B into a stable landing asset.
Use BTC.B in another ecosystem
These routes start from BTC.B and end where another chain or app ecosystem needs native settlement.
Use BTC as the funding asset when the destination needs native BTC settlement on Bitcoin.
Bitcoin into other ecosystemsUse BTC as the funding asset when the destination needs native ETH settlement on Ethereum (ERC20).
Bitcoin into other ecosystemsUse BTC as the funding asset when the destination needs native TON settlement on TON.
Popular ways to receive BTC.B
Stablecoins into Bitcoin
Routes that move BTC.B into Bitcoin when users want a risk-off destination or a long-term BTC position.
Bitcoin into other ecosystems
Routes that move BTC into another ecosystem when users need native settlement on the destination chain.
Common route patterns
Bitcoin into other ecosystems
5
Routes that move BTC into another ecosystem when users need native settlement on the destination chain.
Bitcoin into stablecoins
2
Routes that land Bitcoin value back into BTC.B when users want to reduce volatility or prepare another transfer.
Stablecoins into Bitcoin
2
Routes that move BTC.B into Bitcoin when users want a risk-off destination or a long-term BTC position.
More BTC.B routes
Use BTC as the funding asset when the destination needs native BTC settlement on Bitcoin.
Move BTC into USDC when the goal is to reduce volatility or prepare value for the next transfer.
Move BTC into USDT when the goal is to reduce volatility or prepare value for the next transfer.
Use BTC as the funding asset when the destination needs native ETH settlement on Ethereum (ERC20).
Use BTC as the funding asset when the destination needs native TON settlement on TON.
Use BTC as the funding asset when the destination needs native XRP settlement on Ripple.
Start a BTC.B swap
Open the live builder, choose the network that matches your wallet, and create the shift from there.
FAQ
What role does BTC.B play in swap routes?
BTC.B can appear as a send asset, a receive asset, or both depending on whether users are entering its ecosystem, leaving it, or rotating through it as part of a broader route.
Do I need a dedicated BTC.B wallet before swapping?
Yes. The destination wallet or address format still needs to match the selected receive network, so the receiving setup should be ready before the route is created.
How do network choices change BTC.B swaps?
Network choice changes wallet compatibility, transfer cost, and sometimes memo requirements. That is why this hub highlights the supported network rails rather than treating every BTC.B route as interchangeable.
Can I use BTC.B in non-custodial swaps without creating an exchange account?
That is the core idea of these routes: the builder sets the pair and network context first, then the shift page handles deposit instructions and status tracking without turning the flow into a custodial exchange workflow.