How to add Robinhood Chain to MetaMask (chain ID 4663)

The Editor·9 min read·Updated 31 Aug 2026

Add Robinhood Chain to MetaMask manually with chain ID 4663 and the official RPC, verify you are on the right network, and fix tokens that fail to appear.

Add Robinhood Chain to MetaMask manually: Settings → Networks → Add a network → Add a network manually, then enter the name Robinhood Chain, RPC URL https://rpc.mainnet.chain.robinhood.com/, chain ID 4663, currency symbol ETH, and explorer https://robinhoodchain.blockscout.com. MetaMask does not bundle the network, and as of 31 August 2026 the Chainlist one-click add may not work.

The exact parameters

FieldValue
Network nameRobinhood Chain
New RPC URLhttps://rpc.mainnet.chain.robinhood.com/
Chain ID4663
Currency symbolETH
Block explorer URLhttps://robinhoodchain.blockscout.com

Chain ID 4663 is 0x1237 in hexadecimal; MetaMask accepts either form. The testnet is chain ID 46630 with the RPC https://rpc.testnet.chain.robinhood.com. Do not mix them up — a testnet balance is not money.

The currency symbol is ETH because Robinhood Chain uses ETH for gas rather than a separate chain token. That trips people up on the way in: there is no "HOOD" gas token to acquire first, and any site telling you to buy one is not describing this chain.

Why the one-click methods may fail right now

The standard advice for any EVM network is to use Chainlist: connect a wallet, search the chain, click add. A Chainlist entry for 4663 exists, but as of 31 August 2026 its RPC table was rendering empty, which means the add button has nothing to hand MetaMask. If you land on that page and the RPC column is blank, that is what you are looking at — not a browser problem on your end.

MetaMask's own X account has published an add-network link for Robinhood Chain, so the network is officially blessed even though it is not bundled in the default list. That link works when it works, but it is still an external page injecting a network configuration into your wallet, so the verification step below applies either way.

The manual route has one real advantage over any button: you know exactly what you added, because you typed it. Given that malicious network configurations are a live phishing technique — a hostile RPC can lie to your wallet about balances and simulate transactions incorrectly — typing five fields is cheap insurance. If you want the broader version of that threat model, we cover it in phishing sites that mimic explorers, bridges and DEXs.

Adding it in the MetaMask browser extension

Open MetaMask and click the network selector at the top left, which shows your current network. Choose Add network. MetaMask will show its list of popular networks; Robinhood Chain will not be in it. Scroll to the bottom and click Add a network manually.

Fill in the five fields from the table above. Paste the RPC URL rather than typing it, including the trailing slash, and paste the explorer URL the same way. MetaMask validates the RPC as you go: it calls the endpoint and reads back the chain ID it reports. If what the endpoint reports does not match the 4663 you entered, MetaMask refuses to save, and that refusal is the wallet doing its job. Click Save.

MetaMask should switch to the new network automatically; if not, select it from the dropdown.

On MetaMask mobile the path is Settings → Networks → Add network → Custom networks, with the same five fields. The mobile app is stricter about URL formatting than the extension, so if it rejects an RPC that the extension accepted, check for a stray space at the start or end of what you pasted.

Verify you actually added the right network

Three checks, none of which take more than a few seconds, and skipping them is how people sign transactions on a chain they are not on.

First, open MetaMask's network detail view for Robinhood Chain and read the chain ID back. It should say 4663. A network configured with the correct name and the wrong chain ID is the classic setup for a spoofed network.

Second, send nothing and check the RPC responds. Switch to the network and let the balance load. A balance of 0 ETH displayed cleanly means the RPC answered. A spinner that never resolves, or a persistent "could not fetch" error, means the endpoint is not responding for you — see the fallback below.

Third, cross-check a real transaction. Once you have bridged in, take the transaction hash from MetaMask's activity tab and look it up on robinhoodchain.blockscout.com. If the official explorer knows about your transaction, you are on the chain you think you are on. Third-party explorers such as robinscan.io and hoodscan.pro exist, but neither is officially vetted, so use Blockscout for verification specifically.

If the official RPC is slow or unreachable

There is a public alternate endpoint at https://rpc.nodeflare.app/robinhood/public. It requires no API key and is rate-limited to roughly two requests per second — comfortable for a wallet, useless for anything automated.

To switch, edit the existing Robinhood Chain network in MetaMask rather than creating a second entry. Two networks with the same chain ID confuses the wallet's network switching and produces the specific frustration of a dApp connecting to the wrong copy. MetaMask allows multiple RPCs per network in recent versions; if yours does, add the alternate as a second endpoint and select it, which lets you flip back without re-entering anything.

Persistent RPC failure looks identical to being offline: balances do not load and transactions do not broadcast. Before assuming the chain is down, try the alternate endpoint, then load https://robinhoodchain.blockscout.com in a browser tab — if the explorer is producing fresh blocks, the chain is fine and the problem is between you and the RPC.

When a token you own does not appear

This is the most common follow-up problem, and it is almost never a lost token.

MetaMask only shows ERC-20 balances for tokens it knows about. On a chain with hundreds of thousands of deployed tokens and no comprehensive default list, that means most memecoins you buy will not appear on their own. Your balance exists on-chain regardless of whether the wallet renders it.

To make it visible, get the token's contract address from the launchpad, the Meme Central feed or the explorer's token page — not from a chat message — then in MetaMask choose Import tokens, paste the address, and let it resolve the symbol and decimals automatically. Do not override the decimals it returns unless you know why you are doing it; a wrong decimal setting displays a wildly wrong balance and panics people into selling.

If the token still shows zero after importing, work through it in order. Confirm you are on chain 4663 and not on Ethereum or Arbitrum, where the same address may hold nothing. Confirm the transaction actually succeeded by finding it on Blockscout rather than trusting the wallet's activity list. Confirm the address you imported matches the one you bought — ticker impersonation means several contracts can carry the same symbol, and the difference is in the middle of the address, not the four characters at each end. And confirm the tokens went to the address you are looking at, since bridging and swapping across multiple accounts in one wallet is an easy way to look at the wrong one.

A nonsense balance rather than a missing one is the decimals problem; re-importing with the contract's own decimal value fixes it.

What adding the network does not do

It does not give you any ETH. An empty network is an empty network, and you still have to bridge in — where the choice of bridge matters more than most guides admit, because the canonical route has a multi-day withdrawal delay. That is covered in how to bridge to Robinhood Chain.

It does not make MetaMask the best wallet for this chain. Robinhood Wallet has native support with no configuration at all, plus a gas policy where Robinhood covers costs above $5 on in-wallet swaps on this chain, announced 9 July 2026 and ongoing rather than promotional. Rabby handles custom EVM networks at least as well as MetaMask and shows better pre-signature simulation. Phantom's EVM mode is reported not to support Robinhood Chain because it covers a fixed chain set — a single-source claim we could not confirm — and Coinbase Wallet's status is genuinely unpublished either way, so test with a trivial amount. The wallet comparison for Robinhood Chain has the full picture.

And it does not make anything you buy safe. A configured network is plumbing. The chain itself does not reach Stage 0 on L2BEAT's rollup maturity framework — critical contracts can be upgraded by an externally owned account, and fraud proofs rely on two whitelisted validators — and none of that changes based on how carefully you typed an RPC URL. The rest of the context is in what Robinhood Chain is, and the buying path itself in how to buy memecoins on Robinhood Chain.

Frequently asked questions

What is the Robinhood Chain RPC URL?

The official mainnet RPC is https://rpc.mainnet.chain.robinhood.com/. A public alternate with no key required, rate-limited to about two requests per second, is available at https://rpc.nodeflare.app/robinhood/public. The testnet RPC is https://rpc.testnet.chain.robinhood.com. Always verify that whichever endpoint you add reports chain ID 4663 back to your wallet.

Does MetaMask support Robinhood Chain by default?

No. Robinhood Chain is not in MetaMask's bundled network list and must be added as a custom network. MetaMask's own X account has published an add-network link for it, so the network is recognised rather than unofficial, but you still add it yourself — either through that link or, more safely, by entering the five parameters manually.

Why does Chainlist not work for Robinhood Chain?

A Chainlist entry for chain ID 4663 exists, but as of 31 August 2026 its RPC table was rendering empty, leaving the add button with no endpoint to pass to your wallet. This may be fixed by the time you read this. If the RPC column on the page is blank, add the network manually instead of retrying the button.

I added the network but my token balance is missing. What now?

Import the token by contract address rather than expecting it to appear — MetaMask only displays tokens it has been told about. If it still reads zero, verify on robinhoodchain.blockscout.com that the transaction succeeded, that you are looking at the receiving address, and that the contract you imported is the exact one you bought rather than a same-ticker impersonator.


The check that matters more than your RPC settings

Once the network is configured, the useful question stops being technical and becomes whether the token you are about to buy has liquidity somebody can pull. A fixed-term lock through Team Finance, built by TrustSwap — which also builds Meme Central — holds LP tokens across Robinhood Chain, Ethereum, Polygon, Base and BNB, and appears as a verified badge on the token's page in the Meme Central feed, so you can check it in one glance rather than reading a contract. It settles one question only: a lock cannot stop a deployer selling the supply they kept, and it is no substitute for reading holder distribution yourself.


Nothing here is financial, legal or tax advice. Memecoins are extremely high-risk: most lose most of their value, and the majority of tokens launched never reach a decentralised exchange at all. Never spend money you cannot afford to lose entirely. Meme Central does not recommend any specific token. Data described as Meme Central's own reflects tokens indexed by Meme Central and is not whole-market data.

Not financial advice. Memecoins are extremely high risk.

·Community RulesMeme Central aggregates public launchpad data.