Configure MetaMask Wallet for Rootstock
In this guide, you will learn how to download, install MetaMask, and set up custom networks.
Visit the metamask-landing.rifos.org tool to download/install Metamask, and add Rootstock custom networks or follow the steps in the video below.
Connect with MetaMask
- Open the MetaMask extension.
- In the network selector (top right corner), choose Custom RPC.
- Fill with these values to connect to Rootstock Mainnet or Testnet
| Field | Rootstock Mainnet | Rootstock Testnet |
|---|---|---|
| Network Name | Rootstock Mainnet | Rootstock Testnet |
| RPC URL | https://public-node.rsk.co | https://public-node.testnet.rsk.co |
| ChainID | 30 | 31 |
| Symbol | RBTC | tRBTC |
| Block explorer URL | https://explorer.rootstock.io/ | https://explorer.testnet.rootstock.io/ |
Now MetaMask is ready to use with Rootstock!
Next Steps
Try out the Rootstock Testnet:
If you would like to know more about the values used in the custom network configuration above, check out account based addresses on Rootstock.
Limitations
MetaMask does not yet fully comply with the technical specifications of account based addresses on Rootstock. Note that there are workarounds available, which allow most users to use MetaMask on Rootstock successfully.
MetaMask uses the Ethereum value for derivation path, and presently does not allow it to be configured. This means that if you use the same seed phrase in MetaMask and other wallets, you will get a different set of addresses. A workaround for this is to use custom derivation paths when using other wallets that support this feature.
MetaMask does not presently support EIP-1191 checksums. This means that if you use the addresses copied from MetaMask, you may encounter checksum validation errors. A workaround for this is to lowercase the addresses after copying them.
- Currency may be mistakenly displayed as
ETHwithin some screens of MetaMask. The Rootstock network usesRBTCas its cryptocurrency. - This tutorial uses Rootstock RPC API. You can connect to other nodes or use the Public Node by changing the RPC URL.
- The node must enable CORS for browser-based dApps to work.
- Please review the configuration file reference for CORS settings.