> For the complete documentation index, see [llms.txt](https://docs.ethosis.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethosis.org/robinhood-chain/why-robinhood-chain.md). # The case for Robinhood Chain Ethosis needs three things from its host chain: collateral that is an ordinary, self-custodied ERC-20; an issuer that is regulated; and Chainlink pricing for that collateral. Robinhood Chain provides all three, and adds something no competitor has, namely the distribution of the broker that issues the assets. The rest of this page is the detail behind that one point. ## Feature by feature The table draws on Robinhood's published documentation and material from the Arbitrum Foundation. | Feature | What Robinhood Chain provides | Relevance to Ethosis | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | Stack | Dedicated Arbitrum Nitro chain (Orbit) running in rollup mode, settling to Ethereum with blob data availability; canonical withdrawals take 7 days | Inherits Ethereum security; the usual Arbitrum tooling works unchanged | | Status | Mainnet since 1 July 2026 under chain ID 4663; roughly $540M TVL by mid-August 2026 (reported figures span $536M to $1.4B depending on source) | A live network with real assets and real users | | Deployment | Permissionless and EVM-equivalent; Solidity and Vyper, Foundry and Hardhat; Stylus (Rust and WASM) also available | Protocol contracts need no permission to deploy; Stylus serves the signature verifier | | Block time and fees | Blocks of roughly 250 ms, 100 ms latency via preconfirmations; median transaction around $0.001; gas denominated in ETH | Liquidations and originations land quickly; a fill across twenty offers remains cheap | | Sequencer | One sequencer run by Robinhood, first-come-first-served, with sanctions screening applied at the sequencer; forced inclusion via the L1 delayed inbox after 24 hours | Ethosis is built to tolerate a 24-hour outage; the Chainlink Sequencer Uptime Feed is available | | Native RWAs | **Stock Tokens**: 18-decimal ERC-20s issued by Robinhood Assets (Jersey) Ltd, backed 1:1 by shares held in US custody, offered in 120+ countries | The collateral set, issued by a listed broker | | Corporate actions | ERC-8056 `uiMultiplier()`: dividends are reinvested and splits are expressed as a shares-per-token ratio | Collateral value grows on its own; no dividend leaks away | | Oracles | Chainlink Data Feeds (24/5), Data Streams (v11 RWA schema with `marketStatus`), CCIP and the Sequencer Uptime Feed; the multiplier is included in the price | Production-quality pricing from the first day | | Stablecoins | USDG (Paxos, regulated under MiCA) is native and already used by Robinhood Earn on Morpho; USDe is present; USDC via CCTP *unconfirmed* | The settlement asset | | Account abstraction | ERC-4337 EntryPoints v0.6 through v0.8, EIP-7702 (ArbOS 40); Alchemy Gas Manager and ZeroDev | Gasless onboarding, approve and borrow in one batch, EIP-1271 offers | | Incumbent DeFi | Morpho Blue, Uniswap v2, v3 and v4, Lighter, Arcus, 1inch | A home for idle capital and liquidation liquidity are already in place | | Compliance layer | **Nothing on-chain** for Stock Tokens: no allowlist, no transfer hook; eligibility is applied in Robinhood's UI and at KYC'd primary issuance and redemption | Ethosis applies eligibility itself at the protocol boundary | | Ecosystem economics | Robinhood remits 10% of the chain's net revenue to the Arbitrum DAO; $1M sponsorship of Arbitrum Open House 2026 | Builders can access grants and audit subsidies | ## How the alternatives compare * Solana's tokenized stocks (Kamino, Jupiter Lend) sit in pooled markets under tight caps, and they are issued by third parties rather than by the broker whose users hold them. * Base gained tokenized stocks from Coinbase on 24 August 2026; they are more recent, and no lending stack has yet formed around them. * Ethereum mainnet has the richest DeFi of all, but no broker-issued equities of its own, and its gas costs make a twenty-lender syndicate uneconomic. Only Robinhood Chain brings the assets, the price feeds, the settlement currency, account abstraction and low fees together in one place, and pairs them with distribution from the broker that issues the collateral. ## Gaps Ethosis fills itself Making the case honestly means naming what the chain leaves undone: * Stock Token eligibility is not checked on-chain. Ethosis checks it through the [access registry](/architecture/eligibility.md). * Nothing shields users from a sequencer outage. Ethosis adds a grace period and the delayed inbox route; see [Sequencer and chain risk](/risk/sequencer-and-chain.md). * Price gaps that open while markets are closed are not priced in. Ethosis applies session-aware haircuts; see [Oracles and market sessions](/risk/oracles.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.ethosis.org/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.