All pages
Powered by GitBook
1 of 11

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Reverse Bridging

New Documentation here : https://docs.gnosischain.com/

The information in this page may be outdated.

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:

  1. Unlock the Token (allow the application to transfer)

  2. Request the Transfer (requires 2 transactions, 1 from sending chain and a second on destination chain to claim)

See this

OmniBridge tutorial to learn more
Bridging AGVE minted on xDai to BSC

Set Custom RPC Endpoints

New Documentation here : https://docs.gnosischain.com/

OmniBridge: ERC20 Token Transfers

This document was moved : https://docs.gnosischain.com/bridges/tutorials/using-omnibridge/

OmniBridge + Gnosis Safe App

OmniBridge custom app instructions

This document was moved : https://docs.gnosischain.com/bridges/tutorials/using-omnibridge/safe

Alternate Receiver

Set bridge to transfer funds to another address

New Documentation here : https://docs.gnosischain.com/

The information in this page may be outdated.

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:

  1. Click on the Advanced link. A text field will appear.

  2. Paste in the 0x.... address you are transferring funds to on the receiving chain.

  3. 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.

https://alm-xdai.herokuapp.com/

Infinite Unlock

Option to approve all token transfers

New Documentation here : https://docs.gnosischain.com/

The information in this page may be outdated.

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.

Exceptions and Special Cases

Rebasing and Inflationary tokens

New Documentation here :

The information in this page may be outdated.

While most tokens can be freely transferred between chains, there are several exceptions where token properties create bridge-related issues.

https://omni.gnosischain.com/
Without Infinite Unlock Set
With Infinite Unlock Set
Bridge operations are disabled for
.
  • Inflationary tokens 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

    Ampleforth

    AMPL

    0xd46ba6d942050d489dbd938a2c909a5d5039a161

    DIGG

    DIGG

    0x798d1be841a82a273720ce31c822c61a67a601c3

    Auric Network

    AUSCM

    0x1c7bbadc81e18f7177a95eb1593e5f5f35861b10

    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.

    name
    symbol
    address

    Lido Staked Ether

    stETH

    0xae7ab96520de3a18e5e111b5eaab095312d7fe84

    StakeHound Staked Ether

    STETH

    0xdfe66b14d37c77f4e9b180ceb433d1b164f0281d

    ankrETH

    AETH

    0xe95a203b1a91a908f9b9ce46459d101078c2c3cb

    https://docs.gnosischain.com/
    Rebasing tokens

    Benchmark Protocol

    MARK

    0x67c597624b17b16fb77959217360b7cd18284253

    Based Money

    $BASED

    0x68a118ef45063051eac49c7e647ce5ace48a68a5

    rbase.finance

    RBASE

    0xe8b251822d003a2b2466ee0e38391c2db2048739

    Ditto

    DITTO

    0x233d91a0713155003fc4dce0afa871b508b3b715

    Base Protocol

    BASE

    0x07150e919b4de5fd6a63de1f9384828396f25fdc

    USDf

    USDf

    0x05462671c05adc39a6521fa60d5e9443e9e9d2b9

    xBTC

    XBTC

    0xecbf566944250dde88322581024e611419715f7a

    Debase

    DEBASE

    0x9248c485b0b80f76da451f167a8db30f33c70907

    Coil

    COIL

    0x3936ad01cf109a36489d93cabda11cf062fd3d48

    Dollars

    USDX

    0x2f6081e3552b1c86ce4479b80062a1dda8ef23e3

    RMPL

    RMPL

    0xe17f017475a709de58e976081eb916081ff4c9d5

    Rebased

    REB2

    0x87f5f9ebe40786d49d35e1b5997b07ccaa8adbff

    VELO Token

    VLO

    0x98ad9b32dd10f8d8486927d846d4df8baf39abe2

    Tokens of Babel

    TOB

    0x7777770f8a6632ff043c8833310e245eba9209e6

    Rise Protocol

    RISE

    0x3fa807b6f8d4c407e6e605368f4372d14658b38c

    Soft Link

    SLINK

    0x10bae51262490b4f4af41e12ed52a0e744c1137a

    Ramifi Protocol

    RAM

    0xac6fe9aa6b996d15f23e2e9a384fe64607bba7d5

    GRPL Finance

    GRPL

    0x15e4132dcd932e8990e794d1300011a472819cbd

    Xdef Finance

    XDEF2

    0x5166d4ce79b9bf7df477da110c560ce3045aa889

    Antiample

    XAMP

    0xf911a7ec46a2c6fa49193212fe4a2a9b95851c27

    Cream ETH 2

    CRETH2

    0xcbc1065255cbc3ab41a6868c22d1f1c573ab89fd

    Binance ETH staking

    BETH

    0x250632378e573c6be1ac2f97fcdf00515d0aa91b

    Binance-Peg Dai Token on xDai

    Converting Binance-Peg Dai Token to xDai / xDai to Binance-Peg Dai Token on xDai

    New Documentation here : https://docs.gnosischain.com/

    The information in this page may be outdated.

    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.

    1. Go to

    2. set MetaMask to the xDai Chain Network

    3. Enter the amount of xDai to wrap

    4. Press Submit.

    2) Swap wxDai for Binance-Peg Dai on xDai using Component.

    1. Go to

    2. Connect your Web3 Wallet (MetaMask) to the application and confirm you are connected to the xDai network.

    3. Press the Swap tab and select the WXDAI/DAI [BSC] pair.

    4. Press Swap. You will need to approve the first transaction with amount to swap or you can select unlimited.

    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.

    1. Go to

    2. Connect your Web3 Wallet (MetaMask) to the application and select the xDai network.

    3. 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.

    1. Go to

    2. Set MetaMask to the xDai Chain Network.

    3. Select the Unwrap wxDai tab and enter the amount of wxDai to wrap.

    4. Press Submit.

    Once the tx is complete, and wxDai is deposited, you can add wxDai (0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d)

    to Custom Tokens in MetaMask.

  • 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.

  • Binance-Peg Dai Token on Binance
    Binance-Peg Dai Token on xDai
    Binance-Peg USDC Token on Binance
    Binance-Peg USDC Token on xDai
    Wrapeth
    Component Finance
    BSC Bridge
    https://wrapeth.com/
    https://xdai.component.finance/
    follow this tutorial
    follow this tutorial
    Omnibridge
    https://xdai.component.finance/
    https://wrapeth.com/
    Swap Tab with WXDAI and DAI [BSC] selected
    Unlock for swapping, you can allow unlimited approval or a smaller amount
    TX1 for approval
    Tx 2 to complete the swap (2nd time pressing Swap button)

    Binance Smart Chain

    New Documentation here : https://docs.gnosischain.com/

    The information in this page may be outdated.

    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

    🌉

    🌉BSC : Use it to see updated transaction status.

    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.

    Additional Information

    BSC OmniBridge Example

    Example transfer from xDai to BSC

    New Documentation here : https://docs.gnosischain.com/

    The information in this page may be outdated.

    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. 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).

    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

    1. Connect your web3 wallet to the xDai Network. Select the BSC <-> xDai Bridge networks from the dropdown.

    2. Select the token you want to bridge from your wallet on xDai to BSC.

    3. Select the amount.

    4. 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

    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.

    1. Click Claim to initiate claim the process.

    2. 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.

    🌉
    /
    .

    💡 More info on this process is available here.

    Converting WBNB to BNB automatically with a bridge transaction
    Using Component.Finance to exchange tokens to chain-compatible assets before bridging
    Example bridge flow
    OmniBridge live link
    Transaction Monitor
    STAKE on xDai on BSC
    Component.Finance
    Binance-Peg Dai Token
    wxDai
    Binance-Peg USDC Token
    Tokens bridged from Ethereum
    Tokens bridged from BSC
    BSC tokens list
    USDC on xDai

    MetaMask custom RPCs setup for xDai and for the Binance Smart Chain ( Network Name: BSC Mainnet New RPC URL: https://bsc-dataseed.binance.org/ ChainID: 56 Symbol: BNB Block Explorer URL: https://bscscan.com/) or find more detailed instructions here.

    ).
    token on the Gnosis chain
    Use the faucet if you just need some for transactions
    wBNB from
    Trust Wallet
    Component on xDai
    https://www.liquidityfolio.com
    https://omni.gnosischain.com/
    https://omni.gnosischain.com/
    Click on Token Name
    Copy Token Address
    Add as a Custom Token in MetaMask

    WBNB auto-conversion to BNB

    Bridge WBNB from xDai to BNB on BSC to begin transacting immediately on Binance Smart Chain

    New Documentation here : https://docs.gnosischain.com/

    The information in this page may be outdated.

    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!

    1. Swap your token(s) for WBNB on xDai

    2. Bridge WBNB to BNB on Binance Smart Chain (BSC)

    3. 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

    1. Select BSC <-> xDai from the Dropdown. Your MetaMask should still be connected to the xDai Chain.

    2. Choose Wrapped BNB on xDai and enter the amount you want to bridge.

    3. 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.

    Click Request to begin bridging.
    HoneySwap
    app.honeyswap.org
    0xCa8d20f3e0144a72C6B5d576e9Bd3Fd8557E2B04
    https://omni.gnosischain.com/
    easily add here
    https://bsc-dataseed.binance.org/
    https://bscscan.com/
    https://bscscan.com/tx/0x9e7df2fae52bd7a36eb46a4ed7d6461a66f91128012e1e26ed780d28797caf55bscscan.com
    https://docs.tokenbridge.net/bsc-xdai-amb/omnibridge-extensiondocs.tokenbridge.net
    OmniBridge Docs
    Traversing the ETH<>Polygon <>xDAI<>BSC Cross-Chain BridgesMedium
    Cross-Chain Bridging Tutorial
    Logo