> For the complete documentation index, see [llms.txt](https://docs.useicaria.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useicaria.xyz/robinhood-chain/why-robinhood-chain.md). # Why Robinhood Chain What Robinhood Chain offers that makes it the right ground for Icaria to stand on. It comes down to one thing: RWAs on Robinhood Chain are ordinary ERC-20s, self-custodied, issued by a regulated party and priced by Chainlink feeds. That combination is exactly what a venue anchored to an oracle requires, and no other chain currently puts it together, let alone puts it together next to a broker's own distribution. ## Property by property Robinhood's documentation and the Arbitrum Foundation are the source for what follows. | Property | Robinhood Chain | Why it matters to Icaria | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | | Stack | A dedicated Arbitrum Nitro (Orbit) chain in rollup mode, settling to Ethereum with blob data availability and a 7-day canonical withdrawal | Ethereum's security, plus the standard Arbitrum toolchain | | Status | Live on mainnet since 1 July 2026 as chain ID 4663, with roughly $540M TVL by mid-August 2026, though sources range from $536M to $1.4B | Real assets and real users, already there | | Deployment | Open to anyone and EVM-equivalent, covering Solidity and Vyper, Foundry and Hardhat, with Stylus available for Rust and WASM | Nobody stands between the venue's contracts and the chain | | Block time and fees | Blocks around 250 ms with roughly 100 ms latency through preconfirmations, a median transaction near $0.001, and gas paid in ETH | A quote that is seconds old has not gone stale, and sub-cent settlement keeps small swaps worth doing | | Sequencer | One sequencer operated by Robinhood, first-come-first-served, screening sanctions at that layer, with forced inclusion through the L1 delayed inbox after 24 hours | Design for a 24-hour outage; the Chainlink Sequencer Uptime Feed is available | | Native RWAs | **Stock Tokens**: ERC-20 at 18 decimals from Robinhood Assets (Jersey) Ltd, backed one for one by shares under US custody, available in over 120 countries | The universe the venue trades, issued by a listed broker | | Corporate actions | ERC-8056 `uiMultiplier()`, which reinvests dividends and expresses splits as shares per token | No dividend administration, and no ex-dividend cliff to get wrong | | Oracles | Chainlink Data Feeds at 24/5, Data Streams on the v11 RWA schema with `marketStatus`, CCIP and the Sequencer Uptime Feed, with the multiplier already inside the price | Anchor pricing and session awareness at production grade from the outset | | Stablecoins | USDG from Paxos, MiCA-regulated and native, already the lending dollar on Morpho; USDe present; USDC over CCTP still *unconfirmed* | The quote asset | | Account abstraction | ERC-4337 EntryPoints v0.6 through v0.8 and EIP-7702 on ArbOS 40, with Alchemy Gas Manager and ZeroDev | Onboarding without gas, and approve plus swap inside one user operation | | Incumbent DeFi | Morpho Blue, Uniswap v2, v3 and v4, Lighter, Arcus, 1inch | Arbitrage participants and aggregator flow are on-chain already | | Compliance layer | **Nothing on-chain** for Stock Tokens, with neither allowlist nor transfer hook; eligibility lives in Robinhood's interface and in KYC'd primary issuance and redemption | Icaria enforces eligibility itself, at the protocol boundary | | Ecosystem economics | 10% of chain net revenue remitted by Robinhood to the Arbitrum DAO, plus $1M sponsoring Arbitrum Open House 2026 | Grants and audit subsidies are reachable for builders | ## What is missing everywhere else today * Solana's tokenized equities, the xStocks distributed by Kraken, trade mostly on centralised books and generic AMMs, and third parties rather than the broker holding the users do the issuing. * Base got tokenized equities from Coinbase on 24 August 2026, recently enough that no venue layer has been built over them yet. * Ethereum mainnet holds the deepest DeFi of all, but broker-issued equities are not native to it and gas makes small RWA swaps pointless. Assets, pricing, quote asset, account abstraction and fee profile arrive together on Robinhood Chain, and the broker issuing those assets brings its distribution with them. ## Where the chain leaves work to us Being clear about the gaps is part of making the case: * Stock Token eligibility goes unenforced on-chain. Icaria enforces it through the [eligibility registry](/architecture/eligibility.md). * No protection against a sequencer outage is offered. Icaria provides it through the recovery grace and the delayed inbox route. See [Sequencer and chain risk](/risk/sequencer-and-chain.md). * Closed-market gaps go unpriced. Icaria prices them through the regime engine. See [Trading regimes](/protocol/trading-regimes.md). * The DEXs already deployed treat an RWA like any other token, which is the gap the venue exists to close. See [Why now](/introduction/why-now.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.useicaria.xyz/robinhood-chain/why-robinhood-chain.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.