Robinhood Chain
What Robinhood Chain is, and why Zerion is built on it
An Arbitrum Layer-2 on Ethereum, with ETH for gas and stock tokens on-chain. What the chain is, where each fact comes from, and the one small contract Zerion keeps on it.
- Written by
- Zerion team
- Published
- Reading time
- 4 min
On this page
Zerion is a social trading app. You follow traders, post calls, run agents, and every call gets a score. The records behind those scores live on Robinhood Chain. This post explains what the chain is, using its public documentation and launch material as sources, and then exactly what Zerion puts on it.
One thing first: Zerion is an independent project. It is not affiliated with, endorsed by or sponsored by Robinhood Markets, Inc. We build on Robinhood Chain the way any developer can, through its public endpoints.
The short version
Robinhood Chain is an Arbitrum Layer-2 chain built on Ethereum. It uses Ethereum blobs for data availability and ETH as its native gas token (Robinhood Chain docs). Public mainnet went live on 1 July 2026 (Arbitrum DAO factsheet).
For an app like ours, that comes down to three things:
- It is an EVM chain. Solidity contracts, standard wallets and libraries such as viem work the way they do on Ethereum.
- Its data is published on Ethereum. The chain posts its transaction data to Ethereum as blobs, so the information needed to check it doesn't depend on one company's servers.
- Gas is paid in ETH, not in a separate token.
How it was built
According to the launch factsheet, the chain was built with Offchain Labs, the company behind Arbitrum. It runs at 100 ms latency, which it reaches through configurable block times and preconfirmations. In general terms, a preconfirmation is an early acknowledgement that a transaction has been accepted and ordered, given before the block that contains it is final.
The same factsheet says the testnet processed more than 200 million transactions before mainnet opened.
What runs on it
Stock Tokens. The factsheet describes Stock Tokens restructured as tokenised debt securities, self-custodied through the Robinhood Wallet and available 24/7 across more than 120 countries. They are not available in every jurisdiction, so whether you can hold them depends on where you live. The first version, now called Classic Stock Tokens, launched on Arbitrum One in June 2025.
DeFi at launch. Launch partners include Uniswap for trading through an automated market maker (AMM), Morpho for lending, and Paxos with the USDG stablecoin.
For coverage of launch day itself, see The Block's launch report.
Connecting to it
The connection docs list two networks.
Mainnet
- Chain ID:
4663 - Public RPC:
https://rpc.mainnet.chain.robinhood.com - Explorer: robinhoodchain.blockscout.com
Testnet
- Chain ID:
46630 - Public RPC:
https://rpc.testnet.chain.robinhood.com - Explorer: explorer.testnet.chain.robinhood.com
The public RPC endpoints are rate-limited and not meant for production traffic. They are fine for trying things out and for light reads; an app under real load should use a dedicated RPC provider.
Why Zerion is built on it
Zerion is about calls on stocks and crypto, and about agents that trade for you inside limits you set. Four reasons the chain fits:
- The markets are there. Stock tokens and crypto sit on the same chain, next to AMM liquidity and lending. A social trading app wants its records next to the markets they are about.
- Records anyone can check. A call hash or a policy hash on a public chain can be verified with the explorer, without trusting our database.
- Small writes, confirmed quickly. What we write is tiny: 32-byte hashes. That is the kind of traffic a Layer-2 is built for, and fast confirmation means a signed call shows up while you are still looking at it.
- Plain EVM tooling. One Solidity contract, viem in the app, and standard EVM wallets.
What Zerion puts on-chain
Everything goes through one small contract, VolleyLog. It holds no funds. It records three kinds of things.
Call hashes. When you post a call, Zerion computes a hash of the fields that define it: the call's id, your handle, the asset, long or short, the horizon, the entry price and the time it was posted. If you choose to, your own wallet sends that hash to VolleyLog with postCall(callHash). The contract emits an event with your address, the hash and the block time. That proves the call came from your wallet and existed at that time, without putting the call itself on-chain.
Agent policy hashes. If you run an agent, you register the keccak256 hash of its guardrail policy with registerPolicy(agent, policyHash, expiresAt), and remove it with revokePolicy(agent). This is the only thing VolleyLog keeps in storage. Your agent needs a quiver, not your keys covers it in detail.
Merkle checkpoints. From time to time Zerion's server anchors the Merkle root of a batch, such as a set of resolved calls, with checkpoint(root, count, kind). One 32-byte root commits to the whole batch, and any single entry can later be proven to be part of it. Only the contract owner, Zerion, can write checkpoints.
Call posts and checkpoints are events only, with no storage, which keeps them cheap.
What stays off-chain: prices, the scoring itself, profiles and the leaderboard. Scores come from public price data, as explained in Every call is scored like an arrow. The chain proves who called what, and when.
Reading from the chain
The site reads Robinhood Chain through the public RPC listed above. The live block number and gas price shown on the site come straight from it. Because that endpoint is rate-limited, those figures can occasionally lag.
Zerion is pre-launch, and its first season is planned for testnet.
Sources
- Robinhood Chain docs: Connecting. Chain IDs, RPC endpoints, explorers, gas token and data availability.
- Arbitrum DAO factsheet: Robinhood Chain mainnet launch. Launch date, Offchain Labs, latency, testnet volume, launch partners and Stock Tokens.
- The Block's launch report. Coverage of the mainnet launch.

