What is the Robinhood Chain RPC URL?
The official public RPC for Robinhood Chain mainnet is https://rpc.mainnet.chain.robinhood.com, on chain ID 4663 (0x1237 in hex), with ETH as the gas token. The testnet uses chain ID 46630 and https://rpc.testnet.chain.robinhood.com. Robinhood's docs describe these public endpoints as rate-limited and not recommended for production, so an app or a bot should use a node provider or its own node.
This guide is for developers and bot builders. If you only want to add the network to a wallet, the Phantom and MetaMask guide is quicker, and what is Robinhood Chain covers the network itself. Values below were read from Robinhood's developer docs on 12 October 2026.
What are the Robinhood Chain network details?
Mainnet:
- Network name: Robinhood Chain
- Chain ID: 4663 (hex 0x1237)
- Currency symbol: ETH
- Public RPC: https://rpc.mainnet.chain.robinhood.com
- Block explorer: robinhoodchain.blockscout.com
- Sequencer: https://sequencer.mainnet.chain.robinhood.com
- Sequencer feed: wss://feed.mainnet.chain.robinhood.com, with wss://delayed-feed.mainnet.chain.robinhood.com as a delayed backup
Testnet:
- Network name: Robinhood Chain Testnet
- Chain ID: 46630 (hex 0xb626)
- Public RPC: https://rpc.testnet.chain.robinhood.com
- Block explorer: explorer.testnet.chain.robinhood.com
- Sequencer feed: wss://feed.testnet.chain.robinhood.com
The sequencer feed is a stream of sequenced transactions for nodes to consume. It is not a JSON-RPC endpoint, so you cannot call eth_ methods on it.
Which RPC providers support Robinhood Chain?
Robinhood's docs show Alchemy endpoints for both networks, an HTTPS URL and a WebSocket URL that each take your Alchemy API key, and name Chainstack, QuickNode, Blockdaemon, dRPC, Validation Cloud and GlobalStake as infrastructure providers that support the chain. NAVI has not compared their paid plans, so check limits and pricing with each provider before you commit.
If your code subscribes to new blocks, logs or pending transactions, you need a WebSocket endpoint. The docs list no public WebSocket RPC, only the keyed Alchemy ones, so plan on a provider account for subscriptions.
What did NAVI find when it tested public Robinhood Chain RPCs?
NAVI's backend reads Robinhood Chain through a fallback list of keyless endpoints. We tested them with read-only calls on 30 September 2026. Treat this as a snapshot, because public endpoints can change without notice:
- Official public RPC: eth_call with state override worked, and a burst of 40 requests went through without errors. There was no archive state (historical balance reads failed) and no debug or trace methods. eth_getLogs was capped at 100,000 blocks per request.
- dRPC public endpoint (robinhood.drpc.org): state override, archive reads and debug_traceCall all worked without a key. It was the most capable keyless option in our test.
- PublicNode (robinhood-rpc.publicnode.com): state override worked, but archive requests asked for a personal token.
- Pocket (robinhood.api.pocket.network): state override and archive reads worked; tracing did not.
State override matters if you simulate transactions without sending them, for example a buy and sell test on a new token. NAVI's honeypot checker depends on it.
How do you use the Robinhood Chain explorer and its API?
The mainnet explorer is a Blockscout instance at robinhoodchain.blockscout.com, with its API under /api/v2. In NAVI's checks on 30 September 2026 the API worked from a browser but answered scripts and servers with a Cloudflare challenge, so a backend may not be able to call it directly. Blockscout's paid PRO API asked for a key or a payment.
Etherscan's V2 API also lists chain 4663, with an explorer at robin.etherscan.io, and needs a free API key. For contract verification, Robinhood's docs point to Blockscout's verifier: https://robinhoodchain.blockscout.com/api/ on mainnet and https://explorer.testnet.chain.robinhood.com/api/ on testnet.
How do you deploy and verify a contract on Robinhood Chain?
Robinhood's docs say the chain is fully EVM-compatible and that Solidity and Vyper contracts deploy without changes using standard Ethereum tooling. They walk through Foundry and Hardhat and recommend deploying to testnet first.
- Foundry: deploy with the RPC URL as usual, then verify with forge verify-contract, passing --chain-id 4663, --verifier blockscout and --verifier-url https://robinhoodchain.blockscout.com/api/.
- Hardhat: add a robinhood network with the RPC URL and chain ID, then run npx hardhat verify --network robinhood with the contract address.
- Gas estimates: call eth_estimateGas as normal. The docs say standard estimation already covers both parts of the fee.
- Cheaper transactions: the docs recommend keeping calldata small, because the L1 part of the fee scales with calldata size.
What behaves differently from Ethereum?
Robinhood Chain runs on Arbitrum technology, so contracts that assume Ethereum mainnet behaviour can surprise you. From Robinhood's page on differences from Ethereum:
- block.number returns an estimate of the Ethereum L1 block number, updated periodically, not the Robinhood Chain block number.
- block.prevrandao (difficulty) returns a constant. Never use it for randomness.
- blockhash(n) is only reliable for recent blocks.
- block.coinbase returns the network fee account, not a block producer.
- Fees combine L2 execution gas with an L1 data fee for posting calldata to Ethereum.
- Contract size can reach 96 KB, against 24 KB on Ethereum.
- Arbitrum precompiles such as ArbSys and ArbGasInfo are available.
- Ordering is first come, first served by arrival at the sequencer. Priority gas auctions do not exist.
- Finality starts with a fast soft confirmation from the sequencer, then becomes hard once the batch is posted to and confirmed on Ethereum.
- Messages from L1 contracts arrive with an aliased msg.sender.
- Screening: the sequencer can exclude transactions linked to sanctioned addresses.
Blocks are quick. Blockscout's stats showed an average block time of about 101 milliseconds when NAVI checked on 30 September 2026, so avoid logic that assumes a fixed number of seconds per block.
Which core contract addresses should you know?
These addresses are in NAVI's chain registry and were checked on-chain on 30 September 2026. Confirm them against Robinhood's contracts page before you hard-code anything.
- WETH: 0x0bd7d308f8e1639fab988df18a8011f41eacad73
- USDG (Global Dollar, Paxos, 6 decimals): 0x5fc5360d0400a0fd4f2af552add042d716f1d168
- Multicall3: 0xca11bde05977b3631167028862be2a173976ca11
- Permit2: 0x000000000022d473030f116ddee9f6b43ac78ba3
- Uniswap v4 PoolManager: 0x8366a39cc670b4001a1121b8f6a443a643e40951
- Uniswap Universal Router: 0x204faca1764b154221e35c0d20abb3c525710498
- Pons V2 launch factory: 0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e
There is no Circle-native USDC on the chain. The bridged USDC that does exist had almost no liquidity in NAVI's check, so treat USDG as the stablecoin. Pons launches are covered in Pons launchpad explained.
How does NAVI use Robinhood Chain data?
NAVI reads Robinhood Chain through endpoints like these to power its token scanner, honeypot checker and token analytics, all free and without a wallet. If you are building a bot, the scanner is a quick way to sanity-check a token before your code trades it.
For costs on the network, read Robinhood Chain gas fees. For the risks of the chain itself, read is Robinhood Chain safe. NAVI is independent and not affiliated with Robinhood. Not financial advice.