How to Add Robinhood Chain to MetaMask (Step by Step)

Adding a custom network to MetaMask takes about a minute. The part that deserves your attention is not the typing, it is where the numbers came from. Bad network details are one of the standard ways people get robbed, so this guide covers both: the settings themselves, and how to confirm they are the real ones.

The network settings

These are the mainnet parameters, checked against Robinhood’s developer documentation and confirmed by querying the endpoint directly on August 4, 2026.

Before you start

Two things are worth knowing before you touch anything.

Adding a network does not move funds. It tells your wallet where to send its queries. It grants nobody access to anything, and adding the wrong network by mistake does not drain a wallet on its own.

The risk is a malicious RPC endpoint. An endpoint you talk to can lie to you. It can display balances that are not there, return misleading gas estimates, or quietly point you at contracts you did not intend to use. That is why the source of the URL matters more than the act of adding it.

The chain ID is your safety net. Your wallet checks the ID the endpoint reports and refuses to add the network if it does not match what you entered. An endpoint pretending to be Robinhood Chain cannot quietly report a different chain to you.

Adding the network by hand

The wording differs slightly between the browser extension and the mobile app, but the flow is the same.

1. 1

   Open the network menu

   In the extension, click the network name at the top left of the MetaMask window. On mobile, open the menu and go to Settings, then Networks.

2. 2

   Choose to add a network manually

   Select Add network. MetaMask offers a list of popular networks first. Look for the option to add a network manually, usually a small link at the bottom of that list.

3. 3

   Fill in the six fields

   Copy the values from the table above. Enter the chain ID in decimal form, so 4663, not 0x1237. MetaMask normally fills the decimals field in for you.

   Paste the RPC URL rather than typing it. A single mistyped character in a hostname can land you on a domain someone else registered for exactly this purpose.

4. 4

   Save, and read any warning that appears

   MetaMask contacts the endpoint and compares the chain ID it reports against what you entered. A mismatch warning means something is genuinely wrong: either a typo, or an endpoint that is not what it claims. Do not click through it. Go back and check the URL.

5. 5

   Switch to the network

   Select Robinhood Chain from the network menu. Your ETH balance will almost certainly read zero at this point, which is expected. Balances are per network, and you have not moved anything here yet.

The one-click method, and its catch

Many sites offer an “Add to MetaMask” button that fills everything in for you. It uses a standard browser request, your wallet shows you the parameters, and you approve or reject them.

Convenient, and safe on the condition that you trust the page you clicked it on. A phishing site can trigger exactly the same request with its own RPC URL, and the dialogue will look completely normal.

So use it from Robinhood’s own documentation or from the official explorer, and read the parameters in the dialogue before approving. Whichever route you take, the chain ID needs to read 4663.

Aggregator sites that list network details for thousands of chains are useful, but they are community-maintained and do go stale. Treat them as a cross-check, never as the source.

Confirming it worked

Three quick checks, none of which require you to spend anything.

• The network name appearsin MetaMask’s network selector and your account page loads without an error.
• The chain ID matches.Reopen the network in MetaMask’s settings and confirm it still reads 4663.
• Your address exists on the explorer. Copy your address into the official explorer. A brand-new address with no history is normal. What you are checking is that the explorer and your wallet are describing the same chain.

Getting ETH onto the chain

An empty wallet on a new network cannot do anything, because every transaction needs a fee and fees are paid in ETH held on Robinhood Chain itself. ETH on Ethereum mainnet will not work.

The canonical route is the Arbitrum bridge portal, which Robinhood links from its own documentation:

• Deposits from Ethereum arrive in roughly ten minutes.
• Withdrawals back to Ethereum take about a week, because Arbitrum-based chains use a challenge period before a withdrawal can be claimed. On this chain that period runs to roughly six days and eight hours, after which you have to send a second transaction on Ethereum to claim the funds. This is normal and expected, not a fault. Plan around it.

Bridge a small amount first. Confirm it arrives. Then bridge the rest. The cost of testing is a few cents in fees, and the cost of not testing can be everything you sent.

Adding a token you cannot see

Wallets do not automatically know about every token. If you hold something and MetaMask shows nothing, the token simply has not been added to your list yet. Your balance is on the chain regardless of whether the wallet displays it.

To add one, find the token’s contract address on the official explorer, then use Import tokens in MetaMask and paste it in. The symbol and decimals fill in automatically.

Get the contract address from the explorer or from official documentation. Never from a direct message, a reply on social media, or a website you found while searching for it. Fake tokens with real-looking tickers are trivial to deploy, and this is precisely where people import them.

Using the testnet instead

If you are developing against the chain, or you just want to click through things without real money at risk, there is a public testnet.

Testnet ETH has no value and comes from a faucet rather than a bridge. Keep testnet and mainnet as separate entries in your wallet so you always know which one you are on.

When something goes wrong

“Chain ID returned by the RPC does not match.” Either you mistyped the chain ID, or the endpoint is not Robinhood Chain. Re-check both against the documentation. Do not override the warning.

Balance shows zero. Almost always the right answer. Check which network is selected, then look your address up on the explorer. If the explorer shows a balance and the wallet does not, the endpoint is having a bad day rather than your funds having moved.

Transactions hang as pending. On a chain producing a block roughly every 100 milliseconds, confirmation is close to instant. Something stuck for minutes usually points at the RPC connection. Removing the network and adding it again with fresh details clears most of these.

Tokens missing after adding the network. Import them by contract address, as above. Nothing is lost, the wallet simply does not know to look.

You added the wrong network.Delete it from MetaMask’s network settings. If you also interacted with a contract while connected to it, review and revoke that address’s approvals, and read our guide on phishing sites.

What adding a network does and does not do

Worth restating plainly, because the fear here is often pointed in the wrong direction.

• It does not give anyone access to your funds, expose your recovery phrase, or approve any spending.
• It does determine which server your wallet asks about balances, gas, and transactions, which is why the URL should come from the documentation rather than a search result.
• Nothing about thisshould ever involve typing your recovery phrase. Not to add a network, not to import a token, not to “verify” a wallet. If any page asks, it is stealing from you.

Once the network is in place, the next thing worth understanding is what you are actually paying for. Our guide to gas fees explains why the same transaction can cost different amounts on different days.