Skip to main content

Robinhood Chain

Learn why to build on Robinhood Chain, its EVM compatibility, wallet setup, RPC limits, gas estimation, and best practices for production-ready dApps.

Written by Bruno

What is Robinhood Chain, and why build on it?

Robinhood Chain is an EVM-compatible Arbitrum L2 optimized for tokenized real-world assets—equities, ETFs, and other financial instruments represented onchain. It uses ETH as the native gas token and supports standard Ethereum tooling, making it well-suited for high-throughput onchain finance like swaps and aggregation across tokenized stock assets.

Is Robinhood Chain EVM-compatible for Ethereum tooling?

Yes. Robinhood Chain fully supports the EVM, so Solidity contracts and tools like Remix, Foundry, or Hardhat work with minimal or no changes. As an Arbitrum L2, it inherits standard Arbitrum tooling and behavior.

How to add Robinhood Chain to your Wallet?

Use the following chain ID and key token addresses:

Mainnet: Network name: Robinhood Chain Chain ID: 4663 Symbol: ETH Native ETH: 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee WETH: 0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73 USDG: 0x5fc5360d0400a0fd4f2af552add042d716f1d168

What liquidity sources are available on Robinhood Chain?

Robinhood Chain supports Uniswap v2, v3, and v4, plus Rialto, providing AMM liquidity across the chain's tokenized stock assets (~100 RH stock tokens) and core assets like WETH and USDG.

How do I get spot prices and route swaps on Robinhood Chain?

Use the 1inch contracts deployed on chain 4663:

1inch Router: 0x5A705DE8982235a7fa45bB83dCaCf03a211389C7 Spot Price Aggregator: 0x0fac1e0070647e35cdaa54de6b0bcd22c7cd2f9c

The Spot Price Aggregator returns onchain spot prices across the supported AMMs, while the Router handles swap execution and aggregation.

How to estimate gas on Robinhood Chain via JSON-RPC?

Use the standard eth_estimateGas JSON-RPC method against your RPC endpoint, or the 1inch Gas Price API. As an Arbitrum L2, total transaction cost includes both L2 execution gas and an L1 data/blob component, so estimate against a live endpoint rather than assuming a fixed gas price.

Did this answer your question?