Connect
Robinhood Chain is EVM-compatible, so existing Ethereum wallets and clients work unchanged. There are two public networks:
- Mainnet — chain ID 4663 (
0x1237), RPChttps://rpc.mainnet.chain.robinhood.com, explorerhttps://robinhoodchain.blockscout.com - Testnet — chain ID 46630 (
0xb626), RPChttps://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.
On the record in this article