The Book · 27 Jul 2026
← Field guide
For builders

Build on Robinhood Chain: connect & deploy

Robinhood Chain is EVM-compatible: connect to mainnet (chain ID 4663) or testnet (46630) with standard tooling. ERC-4337 and EIP-7702 are first-class, and production apps should route through a provider, not the public RPC.

7 min read · Updated 2026-07-13

Connect

Robinhood Chain is EVM-compatible, so existing Ethereum wallets and clients work unchanged. There are two public networks:

  • Mainnet — chain ID 4663 (0x1237), RPC https://rpc.mainnet.chain.robinhood.com, explorer https://robinhoodchain.blockscout.com
  • Testnet — chain ID 46630 (0xb626), RPC https://rpc.testnet.chain.robinhood.com

The currency symbol is ETH — the gas token. One operational warning: the public RPC is rate-limited, and Robinhood's own terms say it is unsuitable for production. For anything real, use a provider (below).

Deploy with standard tooling

Because the chain runs Arbitrum Nitro, the standard Solidity toolchain works without modification: Hardhat, Foundry, ethers.js, viem, and Wagmi, in Solidity or Vyper. The full EVM opcode set behaves as on Ethereum, and Nitro allows larger contract-size limits than Ethereum L1, so contracts that bump against L1's bytecode ceiling have more room.

Unlike a chain that removes the native asset, Robinhood Chain keeps ETH as gas, so msg.value, BALANCE, and payable functions behave the way an Ethereum developer expects. The mental model is: this is Arbitrum-flavoured Ethereum, tuned toward financial apps.

Account abstraction is first-class

The chain treats account abstraction as a day-one primitive, which matters for a venue aimed at agentic and app-embedded trading. ERC-4337 is supported with published EntryPoint and SenderCreator addresses for v0.6, v0.7, and v0.8, so bundler-and-paymaster infrastructure works out of the box. EIP-7702-style delegation is supported too, letting an ordinary externally owned account pick up batching and sponsorship without migrating addresses.

Alchemy is a day-one partner providing both RPC and AA tooling, alongside QuickNode, Blockdaemon, dRPC, and Validation Cloud for node access. If you are building sponsored-gas flows, scoped session keys, or agent wallets, the standards and the infrastructure are already in place.


Keep reading

Related


Citations

Sources

  1. [1]Robinhood Chain Docs — Connecting to Robinhood Chain
  2. [2]Robinhood Chain Docs — Contract registry (EntryPoint addresses)
  3. [3]Alchemy — Robinhood Chain RPC & account abstraction

HoodL2 is a neutral, sourced reference. Every claim above is drawn from the cited sources; where a detail is uncertain it is omitted rather than guessed.


Answer-first

Frequently asked

What are Robinhood Chain's chain IDs and RPC URLs?
Mainnet is chain ID 4663 (0x1237) at https://rpc.mainnet.chain.robinhood.com; testnet is 46630 (0xb626) at https://rpc.testnet.chain.robinhood.com. The gas token is ETH and the explorer is https://robinhoodchain.blockscout.com. The public RPC is rate-limited and, per Robinhood, unsuitable for production.
Can I use Foundry, Hardhat, and viem?
Yes. Robinhood Chain runs Arbitrum Nitro and is fully EVM-compatible, so Hardhat, Foundry, ethers.js, viem, and Wagmi work unchanged, in Solidity or Vyper. Nitro also allows larger contract-size limits than Ethereum L1.
Does Robinhood Chain support account abstraction?
Yes, first-class. ERC-4337 is supported with published EntryPoint and SenderCreator addresses for v0.6, v0.7, and v0.8, and EIP-7702-style delegation is supported. Alchemy provides day-one RPC and AA tooling.