Bridging to Avalanche
Bridging is the process of moving a token from one chain to another. This process usually requires 2 transactions.
- 1.Depositing the token onto a Bridge
- 2.Bridge transferring the token to your destination chain into your wallet
As the transactions are done on 2 different chains, it could take 10min ~ 24 hours depending on the traffic of the chain.
During this process, you can check on your deposit transaction hashes for the status. Or go to the FAQs if your transactions are taking more than 24 hours.
If your bridge is taking less than 4 hours, just be patient it will likely arrive soon. If your transaction takes longer than 4 hours, you may need to force the transaction through using the Anyswap Explorer Tools. There could be many reasons why the bridge is not going through, but you can try: 1. Go to https://anyswap.net/explorer 2. Click the Tools tab 3. Fill in the details of your attempted bridge and click "send" 4. This should automatically push your transaction through
This means that there was not enough liquidity when AnySwap got to your bridge request. When bridging to and from Avalanche, there needs to be an equal amount of the tokens you are bridging on the receiving chain. For example, if you are bridging 500 USDC from BSC to Avalanche, there needs to be 500 USDC in the Avalanche Bridge. If there is not, then the bridge will mint and give you anyXXX tokens, which you can convert into regular XXX tokens when sufficient USDC becomes available again. You may follow the below steps to convert anyXXX to the regular XXX tokens:
- 2.Click Remove
- 3.Choose a chain that has got liquidity - including the same destination chain if liquidity has increased enough
- 4.You will receive the new XXX token on the chain you chose
First, check if the status is "pending" in the recent activities history on your MetaMask. If so, and your request for depositing has been pending for more than 1hour, this may be happening because the gas setting is too low.
You can speed up this step of the process by rewriting your old transaction with a new one with higher gas by following these steps.
This is normal for bridging from some chains. It means that the source-chain version of the token is being burned, the bridge will remake the destination-chain version of the token next.
The form of USDC that Multichain/AnySwap accepts onto the bridge is called "USDC.e", because it is fast and cheaper to bridge. USDC.e on Avalanche is a "bridged form of ERC20 USDC" that was bridged via the Avalanche Bridge. For this reason, USDC.e is not the same as native ERC20 USDC. You can learn more about ".e" tokens on Avalanche here.
In general, when you are interacting with smart contracts and DApps in Avalanche, you want to use the token with .e at the end.
The current-generation Avalanche Bridge (AB) is predated by a previous bridge implementation called the Avalanche-Ethereum Bridge (AEB). The AEB bridge and AB bridge each have their own unique token sets. The AEB tokens have been deprecated in favour of the AB tokens. AB tokens have a
.esuffix. While a token's name and symbol are good references to differentiate the two, the only surefire way to verify a token is the contract address. The AB token contract addresses can be found here.