Loading route...
Swap>
Swap BTC.b to TON
Pair route
SWAPBTC.b to TON
This route helps move value from BTC.b into the TON ecosystem when the user needs TON settlement without going through a centralized exchange account.
Non-custodialLive routeNetwork-aware routing
Pair intent
Useful when the user wants to move from BTC.b into native TON for on-chain activity in the destination ecosystem.
Send
BTC.b on Avalanche
Receive
TON on TON
Live swap card
Swap BTC.b to TON with the route prefilled.
Current rate
Select a valid pair to fetch a live variable rate
You send
Network
Select network
Variable rate creates the shift first. The shift page shows the deposit range before funds are sent.
You receive
NetworkSelect network
Live unit rate
--
Current live rate before the shift is created.
Deposit rule
[warning] Select a pair to see the live min and max deposit range before you create the shift.
Status note
After you create the order, the app redirects to a dedicated shift screen with the QR code, countdown, waiting state, and live status polling.
Live route context
Builder first, then route-specific timing and limit context.
Send
BTC.b on Avalanche
The route starts with the exact deposit asset and network selected for this page.
Receive
TON on TON
Settlement is sent to the destination asset and network defined by this route.
Timing
Provider-driven
Processing time depends on deposit detection, blockchain confirmations, route processing, and final settlement on TON.
Deposit limits
Live minimums
Minimums and maximums are route-specific and provider-driven, so they should be checked on the builder and confirmed again on the shift page.
How this swap works
1
Choose BTC.b on Avalanche as the asset you send and TON on TON as the asset you receive.
2
Enter the TON receiving address before creating the shift so settlement has a defined destination.
3
Create the shift, then send BTC.b within the allowed deposit range shown on the shift page.
4
Track the route until TON settlement is completed on the dedicated status screen.
Route-specific notes
This route is oriented toward entering the TON ecosystem, so destination wallet readiness matters before the shift is created.
Some routes can require memo-style destination details depending on the asset and receiving wallet, so the final instructions on the shift page should be checked carefully before sending funds.
Related routes
BTC.b to BTC
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
BTC to TON
Land in the same destination asset through a different source route, useful when the starting wallet or source network changes.
BTC.b to USDT
Use the same send asset but redirect value into a different destination asset and ecosystem.
USDT to TON
Alternative stablecoin route with a different source network, useful for comparing cost, wallet support, and network-specific deposit behavior.
BTC to ETH
Useful when the user wants to move from BTC into native ETH for on-chain activity in the destination ecosystem.
Explore tokens and networks
Explore BTC.b routes
View routes where BTC.b is the asset being sent or received.
Explore TON routes
See more swap paths that settle into TON.
Explore Avalanche routes
Review routes that start from the Avalanche network.
Explore TON routes
See destinations and routes that settle on TON.
Explore BTC to ecosystem-entry routes
Move up one level and review the full btc to ecosystem-entry routes family instead of a single route only.
Compare Stablecoin to ecosystem-entry routes
Review the adjacent stablecoin to ecosystem-entry routes family when the next decision could change the destination or landing intent.
Pair FAQ
Why move BTC.b to TON instead of using a custodial exchange?
This route is useful when the user wants to move Bitcoin value into another blockchain ecosystem while keeping the flow non-custodial from start to finish.
What is the minimum BTC.b to TON swap amount?
The minimum is provider-driven and route-specific. Always use the live builder and the shift page as the final source of truth before sending funds.
How long does BTC.b to TON usually take?
Processing time depends on deposit detection, blockchain confirmations, route processing, and final settlement on TON.
What happens if I send less than the BTC.b minimum?
Deposits below the allowed range can fail to settle normally and may require provider-side handling, so the live deposit rule should always be checked before sending.
Do I need any extra destination details before swapping BTC.b to TON?
Some assets and wallets require memo-style destination details, so the final shift instructions should always be checked before you send funds.
Do I need a TON wallet before swapping BTC.b to TON?
Yes. You should have a compatible TON receiving address on TON before you create the shift, because settlement is sent to the exact destination you provide.
Route disclaimer
Rates, minimums, and maximums are provider-driven and can change before the shift is created.
Always verify the deposit instructions on the shift page before sending funds.
The selected receiving network must match the destination wallet and asset route.
For BTC.b to TON, the live builder and shift page remain the final source of truth.