RSK Token Bridge Troubleshooting Guide

See the Token Bridge FAQs

Visit the Mainnet Token Bridge or the Testnet Token Bridge




Note that what follows below are generic troubleshooting queries. To see more specific information, use the form above.

1 - Transferred tokens from Ethereum, and after 24 hours have not received tokens on RSK

Network: ETH to RSK

When: Current Block - Transaction Block Number < 5760

Answer: 24 hours is an approximation, it is not fixed. Wait until 5760 blocks have past since the transaction block number, plus 5 minutes.

2 - Transferred tokens from Ethereum, and after 24 hours have not received tokens on RSK

Network: ETH to RSK

When: Current Block - Transaction Block Number > 5760

Answer: Look in the RSK Explorer at the SAME ADDRESS on RSK. If you do not see the correct balance in the tokens tab, please share your Transaction Hash in the #tokenbridge channel on RSK Open slack (go to Open Slack Community to join.

3 - Transferred tokens from RSK, and after 24 hours have not received tokens on Ethereum

Network: RSK to ETH

When: Current Block - Transaction Block Number < 2880

Answer: 24 hours is an approximation, it is not fixed. Wait until 5760 blocks have past since the transaction block number, plus 5 minutes.

4 - Transferred tokens from RSK, and after 24 hours have not received tokens on Ethereum

Network: RSK to ETH

When: Current Block - Transaction Block Number > 2880

Answer: Look in Etherscan at the SAME ADDRESS on RSK. If you do not see the correct balance in the tokens tab, please share your Transaction Hash in the #tokenbridge channel on RSK Open slack (go to Open Slack Community to join).

5 - Transferred tokens from Ethereum to RSK, but do not see them in Liquality

Network: ETH to RSK

When: always

Answer: RSK has a different derivation path (m/44’/137’/0’/0) from Ethereum (m/44’/60’/0’/0). Liquality respects this convention. Copy your mnemonic or private key and use Metamask and add RSK as custom network, to get the same address as ethereum.

6 - Transferred tokens from RSK to Ethereum, but do not see them in Liquality

Network: RSK to ETH

When: always

Answer: RSK has a different derivation path (m/44’/137’/0’/0) from Ethereum (m/44’/60’/0’/0). Liquality respects this convention. Copy your mnemonic or private key and use My Ether Wallet or My Crypto with the RSK derivation path m/44’/137’/0’/0 to get the same address as RSK.

7 - Transferred tokens from Ethereum to RSK, but do not see them in Nifty

Network: ETH to RSK

When: always

Answer: RSK has a different derivation path (m/44’/137’/0’/0) from Ethereum (m/44’/60’/0’/0). Nifty respects this convention. In Nifty, add RSK as Custom RPC, to get the same address as ethereum, see: Resolve Nifty Issue.

8 - Transferred tokens from RSK to Ethereum, but do not see them in Nifty

Network: RSK to ETH

When: always

Answer: RSK has a different derivation path (m/44’/137’/0’/0) from Ethereum (m/44’/60’/0’/0). Nifty respects this convention. Copy your mnemonic or private key and use My Ether Wallet or My Crypto with the RSK derivation path m/44’/137’/0’/0 to get the same address as RSK.

9 - Why does it take 24 hours? Can it be faster?

Network: Both

When: always

Answer: This is for security measures. 24 hours is an approximation, it is not exact. We are working to reduce this time in the next version.

10 - Why can’t I choose the address?

Network: Both

When: always

Answer: Currently, it uses the token bridge always sends tokens to the same address on the other blockchain network, and so the sender and the receiver will always have the same address. You will have the option to send to another address in the next version.

11 - Metamask threw an error

Network: ETH

When: always

Answer: This is usually a timeout as the Transaction was not mined on the time expected by Metamask. This does not mean that transaction has not been mined. Please share your Transaction Hash in the #tokenbridge channel on RSK Open slack (go to Open Slack Community to join).

12 - I don’t see my transaction on the Token Bridge list

Network: N/A

When: always

Answer: The list is stored in the local cache, so it’s not shared across devices, and it’s erased if you clear your browser cookies and temporary files. You can be sure that if the transaction is mined the tokens will cross no matter what the list says. If this is not the reason why it is not there please let us know in the #tokenbridge channel on RSK Open slack (go to Open Slack Community to join).

13 - I used the Sovryn Token Bridge

Network: N/A

When: always

If you have used bridge.sovryn.app, note that this is not the same as the RSK Token Bridge. To get support, please ask on the Sovryn discord group.

14 - I sent RSK tokens to an Ethereum address

Network: N/A

When: always

Note that if you have tokens on the RSK network, such as RIF or RDOC, including “crossed” tokens such as rUSDT or rDAI, you should not send them to an Ethereum address in a regular transaction. This does not work! Instead, you should use the RSK Token Bridge to cross the tokens from one blockchain to the other.

If you have done this already, and sent the tokens to an address that is not under your control - where you do not have the private key or the seed phrase - then you have burnt the tokens, and they are not recoverable. If you have done this already, and sent the tokens to an address that is not under your control - where you do have the private key or the seed phrase - then it may be possible to recover your tokens.

15 - I have multiple wallets installed, but am only given one option

Network: N/A

When: always

Decentralised apps on websites, such as the RSK Token Bridge, interact with the blockchain network through a standard interface known as a web3 provider. Each browser wallet attempts to “inject” a web3 provider as soon as it is loaded. This means that if you have multiple browser extensions doing the same thing, one of them will override the other(s).

In order to avoid this problem, and if you already have multiple wallets installed, is to choose which wallet you wish to use, and disable the other ones. To do this in in Chrome, enter chrome://extensions/ in your address bar, which brings you to a settings screen that lists all of the browser extensions that you have installed. Click on the toggle button to disable all of the browser extensions that inject web3 providers, except for the one that you wish to use. After this go to the RSK token bridge again, and refresh.