Bridge AVAX on Avalanche to WBTC on Arbitrum
Compare deBridge and routes from GUM in one place. Choose your networks, tokens and receiving wallet, then track delivery.
Bridge tokens
Explore routes ↗Available routes
Live comparisonFind your way across
Enter an amount to compare available providers for this exact pair.
Highest expected output is shown first. Source gas and additional costs are separate, so compare the full cost and arrival estimate. Results do not cover every bridge. Unknown costs are not zero.
Need a different route? Change the networks or search by token address, then compare again. Browse Bitpont routes.
Your bridge activity
Transfers started in this browser appear here. Source confirmation does not mean destination delivery.
AVAX on Avalanche → WBTC on Arbitrum
This route exchanges assets across two networks. The receiving wallet must support Arbitrum and the exact destination asset. Keep AVAX on the source network for transaction costs.
0x0000000000000000000000000000000000000000Native asset identifier0x2f2a2543b76a4166549f7aab2e75bef0aefc5b0fA saved route page does not guarantee liquidity or a transfer time. Provider support, minimum amounts and costs are checked with each live quote. Review fees and bridge risks. Wait for delivered or refunded status before repeating an unresolved transfer.
Reverse this route ↗AVAX from Avalanche to WBTC on Arbitrum
This selection combines a network transfer with a change of asset: you pay AVAX on Avalanche and request WBTC on Arbitrum. The quote compares the supported providers for your amount. A listed page is a route reference, not a promise of liquidity or a fixed exchange rate.
How to bridge AVAX to WBTC
- Select the amount of AVAX to pay from Avalanche. Keep AVAX available for source transaction costs.
- Compare the receiving amount, minimum output, provider costs and estimated arrival on Arbitrum.
- Connect a compatible EVM source wallet and enter a receiving address that supports Arbitrum.
- Review the exact assets, recipient and wallet steps. Approve only the transaction you reviewed, then follow destination delivery in bridge activity.
Receiving WBTC on Arbitrum
The receiving address needs to support the selected WBTC contract on Arbitrum. Receiving this token does not necessarily provide ETH for a later transfer or swap.
Two EVM networks can use the same address format. Matching address text does not mean the funds arrived on the intended network.
Choose a compatible wallet →Questions about this bridge pair
Can I bridge AVAX from Avalanche directly into WBTC?
Request a quote for this exact selection. The provider must support both the cross-chain transfer and the destination asset conversion. If no quote is available, change the amount or receiving asset and compare again. A route available now can become unavailable later.
How much will I receive, and what are the fees?
The comparison shows the current WBTC output, any supplied minimum, and known provider and gas estimates. Missing costs stay unknown. Because AVAX is also the source gas asset, leave enough outside the transfer for transaction costs. Read how bridge fees are displayed.
Why is my source transaction confirmed but the transfer still pending?
Source confirmation is not destination delivery. Check the saved transfer in bridge activity and the receiving Arbitrum wallet. Do not submit the same transfer again while its result is unresolved. Get help checking a pending transaction.
Compare the full transfer
The same ticker on two networks does not mean the same token address. Review the source asset, destination asset, minimum receive amount and recipient before approving. Keep the source network’s native token for gas; you may also need the destination native token to move funds after arrival.
Follow destination delivery
A source transaction confirmation is one step. Check bridge activity for delivery or a refund. If the result is unresolved, inspect the recorded transaction before trying again.
Bridge and wallet help ↗