Distinct networks with distinct state
Robinhood describes Robinhood Chain as an Ethereum-compatible Layer 2 built with Arbitrum technology. That technical relationship does not make it Arbitrum One: each network has its own chain identity, RPC endpoints, explorer context, transactions, and deployed contract addresses.
| FIELD | ROBINHOOD CHAIN | ARBITRUM ONE |
|---|---|---|
| Network identity | Chain ID 4663 | Separate Arbitrum One chain identity |
| Public RPC used here | rpc.mainnet.chain.robinhood.com | Not used for CHAIN4663 canonical decisions |
| Explorer used here | Robinhood Chain Blockscout | A separate explorer and contract namespace |
| Canonical Stock Token decision | Exact accepted contract on Chain ID 4663 | No cross-chain identity is inferred |
See the official connection documentation for current Robinhood Chain network parameters.
Can the same address exist on both chains?
The same hexadecimal address can appear in more than one EVM network, but it refers to state in that network's own ledger. Always bind an address claim to its chain ID.