Want to use Bitcoin-secured smart contracts without leaving your familiar MetaMask setup? Adding Rootstock to MetaMask takes less than two minutes, and once it’s done you can interact with dApps on a network that anchors its security to Bitcoin itself. The catch is that a few outdated guides still list the wrong currency symbol and explorer, so it’s worth doing this with the current, officially documented settings.
This guide walks you through exactly what Rootstock is, why you might want it in your wallet, and the full step-by-step setup — including how to verify the connection actually worked and the mistakes that trip people up most often. By the end, you’ll have Rootstock Mainnet (and optionally the testnet) sitting in your MetaMask network list, ready whenever you need it.
id=”what-rootstock-is”>What Rootstock Is
Rootstock — often still called RSK, its original name — is a smart-contract platform that operates as a Bitcoin sidechain. In plain terms: it is an EVM-compatible network, which means it runs the same kind of code as Ethereum, but its security is anchored to the Bitcoin network. Bitcoin miners can “merged mine” Rootstock alongside Bitcoin, meaning much of the hash power that secures Bitcoin also helps secure Rootstock, without miners having to choose between the two.
The native currency of Rootstock is RBTC, not ETH. RBTC is pegged one-to-one with BTC through a two-way peg mechanism: you lock real BTC on the Bitcoin chain and receive RBTC on Rootstock, which you can later convert back. Because the network is EVM-compatible, the same Ethereum wallet addresses you already own work on Rootstock — your MetaMask address on Ethereum Mainnet is the identical address on Rootstock. Tools you’re used to — MetaMask, Solidity contracts, most Ethereum developer tooling — work there with minimal adjustment.
One point of confusion worth clearing up early: you’ll see both “Rootstock” and “RSK” used everywhere, including inside wallet apps. They refer to the same network. The rebrand from RSK to Rootstock happened a while back, but older guides and some network listings still say RSK. If you see RSK Mainnet offered as a network option, that’s Rootstock Mainnet.
Why Add Rootstock to MetaMask
MetaMask doesn’t ship with Rootstock pre-installed the way it ships with Ethereum Mainnet or a handful of popular chains. So you have to add it yourself — which is also the point: you’re the one choosing which networks your wallet trusts. Here’s why Rootstock tends to make the cut for people who bridge between the Bitcoin and Ethereum ecosystems:
- Bitcoin-anchored security: Rootstock inherits security from Bitcoin’s mining network via merged mining, giving it a different trust profile from standalone new chains.
- Same address, zero migration: Your existing MetaMask address works on Rootstock as-is. There’s no new wallet to create and no new recovery phrase to manage.
- EVM familiarity: Smart contracts, dApps, and tooling behave the way they do on Ethereum, so the learning curve is nearly flat if you already use MetaMask.
- RBTC as gas: Transaction fees are paid in RBTC, which tracks BTC’s price one-to-one through the two-way peg — a model some users prefer over native tokens whose prices move independently.
That’s not to say it’s for everyone. Rootstock has a smaller dApp ecosystem than the biggest EVM chains, and bridging BTC into RBTC is its own process with its own considerations. But if you want to experiment with Bitcoin-flavored DeFi or simply hold RBTC in a wallet you already trust, adding the network is the first step. For general safety habits around switching networks, it’s worth reading our guide to switching networks in MetaMask safely before you start hopping between chains.
Before You Start
You need three things, and none of them take long to arrange:
- MetaMask installed. The browser extension or the mobile app — both support custom networks. If you haven’t set it up yet, install it only from the official MetaMask site by typing the address yourself; never follow a search-ad link to a wallet download.
- Your wallet unlocked. You’ll need to be able to open MetaMask’s network settings, which requires unlocking the wallet with your password.
- The correct network parameters. This is the whole article in miniature. Here they are, as of this guide’s writing — always cross-check against Rootstock’s own documentation before pasting:
| Field | Rootstock Mainnet | What it means |
|---|---|---|
| Network name | Rootstock Mainnet | The label shown in your network dropdown |
| RPC URL | https://public-node.rsk.co | The server MetaMask talks to — type this yourself, don’t click a link to it |
| Chain ID | 30 | The network’s unique identifier; MetaMask rejects duplicates |
| Currency symbol | RBTC | Shown next to your balance; gas is paid in RBTC |
| Block explorer URL | https://explorer.rootstock.io | Where you can look up transactions; some sources also list https://explorer.rsk.co |
For the testnet — useful if you want to practice without real funds — the settings are: Network name Rootstock Testnet, RPC URL https://public-node.testnet.rsk.co, Chain ID 31, symbol tRBTC, explorer https://explorer.testnet.rootstock.io. Testnet RBTC can be obtained from Rootstock’s faucet at no cost, which makes it a genuinely safe sandbox.
Method 1: The One-Click Add
If you’d rather not type network parameters by hand, the one-click route lets a trusted chain directory propose the network and have MetaMask fill in the fields for you:
- Open your browser and navigate to a reputable chain-listing site — for example Chainlist or Revoke.cash, which both maintain an entry for Rootstock. Type the site’s address yourself rather than following a link from a forum or social post.
- Connect your MetaMask wallet when the site prompts you, and search for “Rootstock” or “RSK” in the directory.
- Click the “Add to MetaMask” button next to the Rootstock entry.
- MetaMask will pop up showing the proposed network details. Read every field before approving — confirm the chain ID is 30, the RPC URL points to https://public-node.rsk.co, and the currency symbol is RBTC. Only then click Approve.
- MetaMask typically switches to the new network automatically. Confirm it did — the network selector should now show Rootstock.
This method is convenient, but step 4 is non-negotiable. A one-click add is still you granting a site permission to configure your wallet, and while Chainlist and similar directories are generally reputable, phishing copies exist. Never approve network details you didn’t read.
Method 2: Add Rootstock Manually (Step by Step)
Manual entry takes about a minute and gives you full control. Nothing is hidden, and there’s no third-party site involved:
- Open MetaMask and unlock your wallet.
- Open the network selector — it’s the dropdown at the top of the extension window, usually showing your current network (e.g. “Ethereum Mainnet”).
- Click “Add network”, then choose “Add a network manually”. This opens the custom network form with empty fields.
- Fill in the fields with the parameters from the table above:
- Network name: Rootstock Mainnet
- New RPC URL: https://public-node.rsk.co
- Chain ID: 30
- Currency symbol: RBTC
- Block explorer URL: https://explorer.rootstock.io
- Double-check the chain ID. This is the single most important field — if you mistype it, MetaMask will either reject the entry or, worse in some wallets, connect you to the wrong network.
- Click Save. MetaMask adds the network and usually switches to it immediately.
On the mobile app, the flow is similar: open MetaMask, tap the network selector at the top, choose “Add network,” then tap the option to add a custom network and fill in the same fields. For a walkthrough of the same pattern on other chains, our Polygon setup guide and Soneium setup guide show the identical form with different parameters.
| One-click add | Manual add | |
|---|---|---|
| Speed | ~30 seconds | ~2 minutes |
| Typing risk | None — fields auto-fill | You must type the RPC URL and chain ID exactly |
| Trust required | You must trust the listing site and read the proposal carefully | No third party involved |
| Best for | Users who find chain directories convenient | Users who prefer to control every field |
How to Verify You Did It Right
Adding the network is only half the job; confirming it works is what keeps you from discovering a problem the first time you try to move funds. Run through these checks:
- Check the network selector. The dropdown at the top of MetaMask should show “Rootstock Mainnet” (or whatever name you entered) and indicate you’re connected to it.
- Check the currency symbol. Your balance area should show RBTC as the unit. If it shows ETH, something is off — several older guides mistakenly used “RSK” or left the symbol wrong, so this is the check that catches a bad setup.
- Confirm your address is the same. Copy your wallet address while on Rootstock and compare it to your Ethereum address — they should be identical, because EVM networks share the same address format. A different address would indicate you’re looking at a different wallet, not a different network.
- Look up the network on the explorer. Visit the block explorer address you entered (type it yourself) and search for your address. If the explorer loads blocks and your address page renders, the RPC endpoint is healthy and the chain ID matches the real network.
- Send a tiny test transaction first. Before moving any meaningful amount, send the smallest possible transfer to yourself or to an exchange deposit address you control, and confirm it arrives. If it does, the plumbing works end to end.
- Try switching back and forth. Switch to Ethereum Mainnet and back to Rootstock once or twice. Each switch should be instant and your balances on each network should display independently.
If the explorer won’t load or transactions hang, the usual culprit is a mistyped RPC URL — a single wrong character breaks the connection entirely. Re-open the network settings, retype the URL carefully, and save again.
7 Mistakes to Avoid
- Using “RSK” as the currency symbol. Old guides (including one widely copied from Binance Academy’s early tutorial) listed the symbol as RSK. The correct native currency symbol is RBTC. A wrong symbol won’t break the connection, but it makes balances and gas displays misleading.
- Mistyping the chain ID. Chain ID 30 is Rootstock Mainnet; 31 is the testnet. Entering 31 while expecting mainnet puts you on the test network, where real RBTC won’t appear and nothing you do involves real funds. Always match the chain ID to your intent.
- Confusing mainnet and testnet RPCs. https://public-node.rsk.co is mainnet; https://public-node.testnet.rsk.co is testnet. They differ by one word. Double-check which one you pasted.
- Approving a one-click add without reading the proposal. Phishing sites mimic chain directories to inject malicious RPC endpoints. If you approve without reading, a rogue RPC could theoretically serve you false chain state — always verify chain ID 30 and the official RPC URL before clicking Approve.
- Assuming ETH pays for gas. Because the address is identical to your Ethereum address, it’s easy to assume your ETH balance carries over. It doesn’t. Gas on Rootstock is paid in RBTC, and your Rootstock balance starts at zero until you move RBTC onto the network.
- Sending tokens to your address on the wrong network. Same address, different networks — this is the classic trap. RBTC sent to your address while your wallet is set to Ethereum Mainnet isn’t visible and isn’t usable until you switch networks; the funds aren’t lost, but they’re inaccessible on the wrong chain until you select the right one.
- Trusting explorer links from chat. Block explorer phishing is a real category of attack: a fake explorer can show fabricated “transaction confirmed” pages. Type the explorer address yourself — https://explorer.rootstock.io — and bookmark it once you’re sure it’s correct.
FAQs
The Bottom Line
Adding Rootstock to MetaMask is a two-minute job: either use a reputable chain directory with a careful review of the proposal, or enter the parameters manually — chain ID 30, the public-node.rsk.co RPC, RBTC as the symbol — and verify with a small test transaction. The details that matter most are the chain ID and the currency symbol, which is where outdated guides go wrong.
Once it’s set up, your existing address works as-is, and you get access to Bitcoin-anchored smart contracts from the wallet you already know. Just keep the anti-phishing habits that protect every network you add: type URLs yourself, never share your recovery phrase, and treat every unsolicited “support” message as hostile.
This guide is for education only — not financial advice.
