Robinhood Chain Testnet: Chain ID 46630 & Faucets

Last updated: October 24, 2026

Endpoint and plans: Robinhood Chain RPC endpoint.

At a glance

What you see

You want to try a contract or a bot on Robinhood Chain before spending real ETH, and you find two chain IDs, two sets of URLs and several faucets. A faucet refuses your address, a wallet rejects the network because the chain ID does not match the RPC, or a script written against testnet quietly sends to mainnet after a config change.

Why this happens

Robinhood runs two separate networks with separate chain IDs: mainnet 4663 and testnet 46630. Its connection guide lists a public RPC and a sequencer feed for each, warns that the public endpoints are rate-limited and not recommended for production, and lists a delayed sequencer feed for mainnet only. Test ETH has to come from a faucet, and faucets set their own rules. Alchemy's Robinhood testnet faucet, checked on 13 Oct 2026, drips 0.1 ETH every 24 hours, requires at least 0.001 ETH on Ethereum mainnet and "sufficient activity on Ethereum Mainnet", turns away wallets that already hold a significant amount of testnet tokens, and needs no Alchemy account. The faucet at faucet.testnet.chain.robinhood.com sits behind a browser security check and publishes no amount or cooldown. Wallets and signing libraries compare the chain ID you configured with the one the RPC returns, so a testnet URL with chain ID 4663 (or the reverse) fails before anything is sent.

Testnet vs mainnet: what changes

What to do

1. Point your tools at the public testnet RPC https://rpc.testnet.chain.robinhood.com with chain ID 46630, network name "Robinhood Chain Testnet" and currency ETH.
2. Get test ETH: Alchemy's faucet (0.1 ETH per 24 hours, needs 0.001 ETH and activity on Ethereum mainnet, no account) or the faucet at faucet.testnet.chain.robinhood.com. If one refuses your address, check its eligibility rule before retrying — waiting does not change a mainnet-balance requirement.
3. Keep the network in one place — an environment variable or a named network in your config — so that switching networks changes the chain ID, the RPC URL and the explorer together, never one of them alone.
4. Before every deploy or send, call eth_chainId on the RPC you are about to use: 0xb626 means testnet, 0x1237 means mainnet. The command below prints the decimal ID.
5. When you move to mainnet, swap the three values from the table above and re-run the eth_chainId check; contracts deployed on testnet do not exist on mainnet and must be deployed again.

cast chain-id --rpc-url https://rpc.testnet.chain.robinhood.com
# 46630  -> testnet
# 4663   -> mainnet

curl -s https://rpc.testnet.chain.robinhood.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# {"jsonrpc":"2.0","id":1,"result":"0xb626"}

When this is not our problem

Faucet eligibility, amounts and cooldowns are set by whoever runs each faucet, and the testnet itself is operated by Robinhood. Triport serves Robinhood Chain mainnet (chain ID 4663) only and does not proxy the testnet: use Robinhood's public testnet RPC above while you build, and a Triport keyed endpoint of the form https://triport.io/r/<YOUR_KEY>/robinhood once you move to mainnet.