You must give approval to the bridge contracts to access and send ERC-20 tokens. This is similar to Uniswap or another DEX that asks for approval to spend your tokens.
You can give this permission on a per transaction basis, or you can unlock an unlimited amount to transfer with the infinite unlock option. Infinite unlock saves on transaction fees, but does introduce security risk if the contract is compromised. A 3rd party may have the ability to access all funds rather than a finite approved amount.
Set Infinite Unlock
1) Go toand select Settings.
2) Toggle Infinite Unlock and Click Save. When you process your next unlock, the transaction will allow all transfers of that token without needing to unlock again.
MetaMask Unlock/Approvals
You will notice when approving an unlock you are presented with options for the unlock in MetaMask. On the first screen you will see a message confirming you allow the contract to interact with and withdraw the selected token (in this case the xBRICK token). Note the prior URL here, the correct url is.
Click Edit Permission to see details. From this screen you can set a Custom Spend Limit if you like. Notice the difference when Infinite Unlock is selected, giving permission to withdraw an unlimited amount.
Tokens minted natively on xDai are now available to bridge to other destination chains, including Ethereum, BSC and POA. Note that you will need to pay gas costs for the destination chain (which can be quite high for Ethereum) with the destination currency (such as ETH or BSC) when bridging.
Bridging requires 2 steps:
Unlock the Token (allow the application to transfer)
Request the Transfer (requires 2 transactions, 1 from sending chain and a second on destination chain to claim)
Here we show the bridging steps to transfer STAKE on xDai to STAKE on BSC. The chain names are appended, so the bridged token is called "STAKE on xDai on BSC".
What you need:
A you want to swap.
A small amount of xDai to complete the transfer. .
BNB on the Binance Smart Chain. You can now get BNB by transferring.If you have BNB on BEP2 you can also swap it to BSC.
If planning to bridge so you can trade an asset on BSC or xDai (Honeyswap, BaoSwap etc), check liquidity for that asset on the chain where you want to trade prior to bridging.
In the example below we bridge STAKE on xDai to BSC, but there may not be enough liquidity for trading STAKE on BSC. In this case you can bridge it back to the originating chain (or if its a supported stablecoin swap on ).
Honeyswap liquidity pair resource:
Bridge STAKE from xDai to BSC
1) Go to the OmniBridge at
Connect your web3 wallet to the xDai Network. Select the BSC <-> xDai Bridge networks from the dropdown.
Select the token you want to bridge from your wallet on xDai to BSC.
Select the amount.
2) Confirm the Unlock tx in MetaMask (note previous url. Current url is)
3) Once Unlock tx is complete, Request button will become active. Click Request and Confirm in MetaMask.
4) Continue with the Transfer (noting that there are 2 transactions to complete, one on xDai and a 2nd on the BSC chain).
5) Confirm in MetaMask. You can set GWEI to 1 to reduce costs.
6) Wait for Block Confirmations and Signature Collections. Once complete, you will see the message to switch the network to the Binance Smart Chain.
7) Once you switch networks, you will see the claim button.
Click Claim to initiate claim the process.
If the claim button does not work for some reason, you can click on the linked sending tx hash to process execute the transaction in the live monitor.
7a) If using ALM, click on the Execute Button to finalize the claim.
8) Once Claimed, you can click on the Receiving Tx to find your transaction on BscScan.
7) To add STAKE to your BSC wallet, click on the Token Name, Copy the address, then go to custom token in MetaMask and add the address.
works well for this (however Trust Wallet does not yet support xDai, so once you swap you'll need to send BNB from your Trust Wallet to your BSC address in MetaMask for this tutorial).
Click Unlock (note: you can also enable infinite unlocks. Click Settings to enable infinite unlocks from this address rather that unlocking a specific amount to transfer).
The Binance-Peg Dai Token can be bridged to xDai using the beta BSC-xDai Omnibridge. However, this process DOES NOT mint native xDai. Instead, the Dai Token from BSC is bridged across networks.
Using xDai tools, it only takes a few steps to convert Binance-Peg Dai to xDai. The process can also be completed in the reverse direction where xDai is converted to Binance-Peg Dai. Once converted from xDai, Binance-Peg Dai can be bridged back to BSC.
This option gives users the ability to convert Dai/xDai when mainnet bridging fees are expensive. A similar process should also be considered for Binance-Peg USDC tokens.
Token Addresses:
Dai
(Named Dai Token from BSC)
USDC
(Named USDC Coin from BSC)
Tools Used:
: Convert xDai to wrapped xDai / unwrap wrapped xDai)
: Swap stable tokens on xDai
: Bridge (in Beta) between xDai and Binance Smart Chain
xDai -> BSC: Swap xDai to Binance-Peg DAI Example
1) Convert xDai to wxDai using the WrapEth Tool.
Go to
set MetaMask to the xDai Chain Network
Enter the amount of xDai to wrap
2) Swap wxDai for Binance-Peg Dai on xDai using Component.
Go to
Connect your Web3 Wallet (MetaMask) to the application and confirm you are connected to the xDai network.
Press the Swap tab and select the WXDAI/DAI [BSC] pair.
The same process can be used to swap USDC to USDC (BSC)
3) Move to BSC (if desired) with the BSC Bridge
You can to bridge with the Omnibridge. Note you will need some BNB on the Binance Smart Chain to complete the process (to pay the claiming fee). If you have BNB on BEP2 you will need to swap it to BSC.
BSC -> xDai: Swap Binance-Peg Dai to xDai
You will follow the same process in reverse to convert Binance-Peg Dai from BSC to xDai.
1) Bridge Dai from BSC to xDai.
You can to bridge with the .
2) Swap Dai (BSC) token for wxDai using Component.
Go to
Connect your Web3 Wallet (MetaMask) to the application and select the xDai network.
Press the Swap tab and select the Dai [BSC]/ wxDai pair. Follow the instructions in section 2 above to approve 2 transactions and swap.
3) Unwrap wxDai into xDai with Wrapeth.
Go to
Set MetaMask to the xDai Chain Network.
Select the Unwrap wxDai tab and enter the amount of wxDai to wrap.
Press Swap. You will need to approve the first transaction with amount to swap or you can select unlimited.
Complete this first approve transaction in Metamask.
Press Swap again and confirm the second transaction to swap.
Once complete, add Binance-Peg Dai on xDai to your MetaMask custom tokens. The address is 0xFc8B2690F66B46fEC8B3ceeb95fF4Ac35a0054BC and in BlockScout it is called Dai Token on xDai.
The default bridge mode sends funds to the same address across chains. However, it is easy to specify another address to receive funds on the chain you are bridging to. This may be desirable when sending funds from a multi-sig wallet (like Gnosis Safe), or as a transfer method to another address on a secondary chain.
Set an Alternate Receiver:
Click on the Advanced link. A text field will appear.
Paste in the 0x.... address you are transferring funds to on the receiving chain.
Proceed with the Request.
Claims on the receiving chain can be completed using any address with enough funds. Copy the tx hash from the first transaction (it will be linked during tx processing or when complete in the history tab of the bridge. You can also find in your MetaMask wallet) and paste into to search and execute.
Another option is to connect to the bridge with the alternate receiver's address - the claim will be linked under History.
While most tokens can be freely transferred between chains, there are several exceptions where token properties create bridge-related issues.
Bridge operations are disabled for .
can still be bridged, but any accrued inflation IS NOT returned to the user upon bridge exit.
Rebasing Tokens
Rebasing tokens include an elastic function where supply can be increased or decreased at regular intervals. If these tokens are bridged, supply impacts could result in inequities on either side of the bridge. In some cases this could result in a bridge balance reduction and the inability for users to exit.
To prevent this, we have disabled bridging capability for rebasing type tokens. A partial token list is included below.
Name
Symbol
Address
Inflationary (Eth 2.0 Staking) Tokens
Inflationary tokens accrue additional value over time. While they are locked in the bridge contract this value will accrue, but will remain on the balance of the bridge upon exit. Inflation will not be returned to a user's balance. This maintains the 1 to 1 ratio of bridged tokens necessary for OmniBridge functionality.
Users are free to bridge these tokens but need to be aware that any accrued inflation will not be added to their balances. Usage of the accumulated inflation will be determined at a later time by bridge governors.
A partial token list of inflationary tokens is included below.
The Binance Smart Chain (BSC) Omnibridge allows users to move ERC20 tokens between Gnosis Chain and BSC. It is available as a dropdown item from the OmniBridge UI.
See the submenu items for more:
(does not require BNB to process)
BSC OmniBridge and OmniBridge UI are beta software, use at your own risk.
You will need xDai and BNB on the Binance Smart Chain to complete a bridge transfer.
Bridge Interfaces
🌉
Tokens bridged cross-chain are appended with the "on xDai" or "on BSC". There are instances where bridging across multiple chains creates token names such as "" for example.
Double bridging also can result in multiple instances of the same token on a single chain. For example, USDC can be bridged to xDai from Ethereum and also bridged to xDai from BSC. This results in 2 separate USDC token instances on xDai. These tokens cannot be merged into a single instance after they are minted.
is an available tool to swap between stable tokens. This can be used to convert:
/
You can view different instances in BlockScout - tokens are labeled with the ETH or BSC label depending on where they were bridged from.
The xDai to BSC Bridge now supports wrapped BNB (WBNB) to BNB conversions directly from Gnosis Chain. Tokens are transferred AND unwrapped to native BNB during the bridging process!
Swap your token(s) for WBNB on xDai
Bridge WBNB to BNB on Binance Smart Chain (BSC)
Use this BNB for transactions on BSC (including bridging additional tokens from xDai to BSC).
1) Swap for WBNB
Use a DEX to swap your token on xDai for WBNB. In this example we use to convert xDai to WBNB.
1) Go to . Connect your MetaMask wallet to xDai and select the pairs you want to trade. In this example we will swap XDAI to WBNB, but you can swap any token with enough liquidity to WBNB.
2) WBNB may not be in the Token Dropdown. To add, copy in the WBNB address on xDai - - and select the token.
3) Enter in the amount to Swap and you will see the amount you will receive in WBNB. Click the swap button to continue.
4) Confirm the swap on Honeyswap and then in MetaMask.
2) Bridge WBNB to BNB on Binance Smart Chain (BSC)
Once your swap is complete, you will move WBNB across the bridge to receive BNB on BSC.
1) Go to the Omni Bridge
Select BSC <-> xDai from the Dropdown. Your MetaMask should still be connected to the xDai Chain.
Choose Wrapped BNB on xDai and enter the amount you want to bridge.
Toggle to Receive BNB. When your transaction is bridged, the WBNB is also unwrapped on the Binance Smart Chain as a part of the transaction! This gives you native BNB on BSC.
2) Click to Continue and confirm the transaction in MetaMask.
3) While transaction is processing, you can view progress in the ALM Monitor (optional)
4) Once complete, switch to the Binance Smart Chain in MetaMask in order to claim.
If you have not added BSC to MetaMask yet, you can or use the following params for MM custom network (Network Name: BSC Mainnet New RPC URL: ChainID: 56 Symbol: BNB Block Explorer URL: )
5) Claim your tokens and confirm in MetaMask.
Note: you may see an Insufficient Funds warning in MetaMask for a few moments while unwrap is processed, added to your account and reflected on MM. This should resolve fairly quickly and you can proceed.
6) Once the claim is processed, you will have native BNB in your wallet on the Binance Smart Chain. You can use this for transactions as needed, and to pay tx costs for bridging over other tokens from xDai.
You can also bridge in the opposite direction, moving native BNB on Binance Smart Chain to wrapped BNB on xDai. In this case, BNB is the first token in the list if BSC is the active network in MetaMask.
