Base Bridge for $MASQ on Superbridge

Superbridge is the official Optimism powered Superchain bridge for roll-ups (L2s), featuring Base

Currently there are no native bridges for $MASQ from Polygon directly to Base - this will require bridging back to Ethereum using the official Polygon bridge at: https://portal.polygon.technology

The MASQ team are researching reliable methods for this in the future.

Head to https://superbridge.app/

Click on “Connect” to connect the wallet holding your MASQ Tokens on the Ethereum Network.

Here we have selected the MetaMask Wallet.

Upon connecting your wallet you will see the screen below. Ethereum is shown on the left hand side of the screen as this is the chain we will be bridging from.

Base is shown on the right hand side as this is the chain we will be bridging our tokens to.

In the Grey box below the Chain information you will see the token selection drop down menu. In the screenshot it is currently set to “ETH”

This serves as a REMINDER to bridge over a small amount of ETH to the Base Chain for gas.

To Bridge MASQ Tokens, Click the Drop Down Token Menu, Search for “MASQ”

Click on the MASQ icon, Enter the amount of MASQ Tokens you wish to Bridge.

Ensure the “To Address” under the grey box is the wallet address you wish your bridged MASQ tokens to be received on. (by default this should match the wallet you are connected with)

Then Click Deposit.

Gas fees will be detailed and you will have to accept 3 tick boxes with regards the bridging and click deposit once more. Once done it should take between 3-5 minutes for your tokens to be bridged across from the Ethereum network and deposited to your “To Address” on the Base chain.

That should be your Bridging complete. 🙂

If you do wish to interact with your bridged tokens, as stated above, you will need to bridge some ETH. (All gas fees are dramatically lower on Base chain)

For bridged tokens to show in your wallet you will need to ensure:

1. You have added the Base Network to your wallet. (you can use chainlist.org )

2. You have added the Token Contract Details - 0x45D9C101a3870Ca5024582fd788F4E1e8F7971c3