Step-by-step guide
Swapping AVAX to BTC is often about repositioning between two crypto assets without sending funds through multiple platforms.
On ZyroShift, this route is currently prefilled as AVAX on Avalanche to BTC. BTC currently supports 2 settlement networks on ZyroShift, and the examples below use Bitcoin as the sample selection. This step-by-step guide uses the current route context so you can check networks, timing, and destination details before creating the order.
Network options
You send
AVAX
AVAX currently has one supported send network only: Avalanche.
The source network stays preselected because there is only one available send rail.
You receive
BTC
BTC currently supports 2 settlement networks on ZyroShift.
Choose the destination network that matches your receiving wallet.
Choose the rate mode first
Use Variable Rate when you want to create the shift first, then send a deposit amount that stays inside the live min/max range for the route.
You choose AVAX, its source network, BTC, and the destination network first.
You enter the BTC receiving address, then press SHIFT.
After the order is created, ZyroShift shows the deposit address, QR code, and the live min/max range for the amount you can send.
Use Fixed Rate when you want to lock the quote first. ZyroShift then expects you to send one exact deposit amount within the quote window.
You enter the exact AVAX amount before creating the order.
You also enter the BTC receiving address before pressing SHIFT.
After the order is created, the deposit address and QR stay tied to that exact amount, and the fixed quote is only valid for 15 minutes.
Step-by-step guide
These deterministic visuals mirror the swap-card flow so the guide can show the route clearly without pretending to be a live quote.
⦿ Select AVAX as the coin you send
In this example, AVAX only uses Avalanche, so the source network stays preselected.
⦿ Select BTC as the coin you want to receive ➞ choose the destination network that matches your receiving wallet
ZyroShift currently supports 2 BTC settlement networks: Bitcoin and Liquid.
This walkthrough uses Bitcoin as the example selection, but it is only one of the available choices.
You send
AVAX
Coin
You receive
BTC
Coin
For Variable Rate, paste the BTC receiving address and then press SHIFT. For Fixed Rate, enter the exact AVAX amount first, paste the BTC receiving address, and then press SHIFT.
⦿ Once you press SHIFT, ZyroShift creates the order and shows the deposit address plus QR for the cross-network route.
If the order is Variable Rate, the next screen tells you the live min/max deposit range and lets you send any amount inside that range to the generated wallet address or QR.
If the order is Fixed Rate, the next screen tells you to send the exact locked amount to the generated wallet address or QR before the 15-minute timer expires.
⦿ Send AVAX exactly as the order requires
On the created shift page, copy the provided deposit address or scan the QR code, then open your own wallet app or exchange app and send AVAX. Variable Rate lets you send the amount you want as long as it stays within the shown minimum and maximum, while Fixed Rate requires the exact amount shown on the quote.
Deposit address
Copy the address or scan the QR code in your wallet app.
Minimum
Example minimum AVAX
Maximum
Example maximum AVAX
Receive address
bc1qreceiveexampleaddress7btc2wallet4
Rate mode
Variable Rate
After the deposit is sent, wait for detection, confirmation, and final settlement. Many faster routes settle in roughly 20 seconds to 1 minute after the deposit is detected, but Bitcoin confirmation time, route conditions, or destination-network load can still make the full process take longer.
Illustrative status screen
Once the deposit confirms and the route settles, the shift moves to the completed state.
Completed shift example
You received BTC
Amount received
Example BTC settlement
Deposit detected
Confirmed on source network
Settlement sent
Delivered on Bitcoin
Status
Order complete
Pair snapshot
Current prefilled route
AVAX on Avalanche -> BTC, then choose the destination network that matches your receiving wallet. The examples below use Bitcoin as the sample selection.
Source network selection
AVAX uses Avalanche as the send network in this example, so the source side stays preselected.
Primary use case
Usually used to rebalance between AVAX and BTC.
Destination network context
BTC currently has 2 supported settlement networks on ZyroShift, so the receiving wallet and selected destination network must match. The walkthrough uses Bitcoin as the sample destination, not as the only available choice.
Timing reality
The final timeline depends on deposit detection, confirmation depth, route processing, and settlement on the destination network you choose. The examples below use Bitcoin as the sample settlement rail.
Why users swap AVAX to BTC
Rebalance between AVAX and BTC when market conviction changes.
Access applications, ecosystems, or liquidity that are easier to reach with BTC.
Move from one crypto position to another without splitting the route into multiple manual transfers.
Fees and timing
Network cost starts with the send side. When AVAX is sent on avax, congestion can change the effective cost of getting the route started.
The final BTC amount can still move with route liquidity, provider fees, and slippage conditions at the moment the order is processed.
Always treat the live builder and the shift page as the source of truth for minimums, maximums, and order instructions before funds leave your wallet.
Network compatibility
Make sure the receiving wallet supports BTC on the exact destination network you choose. The examples in this guide use Bitcoin, but that is only one of the supported rails.
If you change the destination network, update the receiving address to match that exact network instead of reusing an address from a different BTC rail.
Never send the source asset to the receiving address. The deposit address is generated only after the order is created and must be followed exactly.
Common mistakes to avoid
BTC exists on multiple rails, so the receiving wallet has to match the destination network you choose. A wallet that only supports one version of BTC should not be used for another.
If the send transaction spends more on network cost than expected, the amount that actually reaches the route can fall below the live minimum. That is especially important when the source side starts with AVAX.
The deposit address, live limits, and route details should always be rechecked on the created order page before funds move. Treat that screen as the operational source of truth.
Ready to act on the live route?
This guide explains the process. The live builder and the created shift page remain the operational source of truth for rates, deposit rules, and final execution details.
Related routes
Reverse route
Looking for the reverse path?
Move in the opposite direction while keeping the same pair context available from a dedicated route page.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Pair FAQ
It can be, provided you verify the route details, use the exact deposit instructions created for the order, and confirm that the receiving wallet supports the destination network.
Completion time depends on deposit detection, network confirmations, route processing, and final settlement. For this route, the shift page is the best live reference before you send funds.
Source-chain network cost, route fees, slippage, and available liquidity can all influence the final amount that settles to the destination wallet.
Because BTC can settle on multiple networks, the receiving wallet has to support the exact network you choose on the route. This walkthrough uses Bitcoin as the example destination, but a mismatch between address and selected rail can delay or break settlement.
Requirements depend on the route provider and compliance checks applied at execution time. Review the live flow and route terms instead of assuming every pair behaves the same way.
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 AVAX to BTC, the live builder and shift page remain the final source of truth.
