Robinhood Chain: Three Things the Docs Don't Say
Originally published on xroot.dev . I spent a day reading Robinhood Chain with eth_call instead of reading about it. Three things turned up that no documentation page mentions — and one of them is a mistake I made first. Robinhood Chain went live on 1 July 2026: an Arbitrum Orbit L2 settling to Ethereum, ETH for gas, ~0.02 gwei, and — unusually for a chain run by a regulated US brokerage —…
Here are three important findings about the Robinhood Chain that are not mentioned in the documentation:
1. The Chain ID is 0x1237 (4663) and it is an Arbitrum Orbit L2 that settles to Ethereum with ETH gas fees around 0.02 gwei. Unlike most chains run by regulated US brokerages, the Robinhood Chain allows genuinely permissionless deployment.
2. The chain is operated by Robinhood, as evidenced by the publicly accessible precompiles in the Arbitrum Owner Public contract at address 0x...006b. Two distinct addresses correspond to chain owners and transaction filterers. The transaction filterer EOA has made 6,092 filter calls, all succeeding, indicating active usage of the chain's permission control mechanism.
3. An ABI (Application Binary Interface) does not provide a complete picture of a contract's functionality. It only enumerates the functions that can be called, but does not reveal any internal restrictions or modifiers. In the case of Robinhood's tokenized stocks, which are ERC-20 tokens, the ABI search did not find any functions related to transfer restrictions.
However, the contract source code explicitly contains a modifier called "onlyNotBlocked" that checks for account blocking before allowing a transfer. Therefore, even though the ABI did not show any transfer restrictions, the source code reveals that such restrictions are in place.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
