> For the complete documentation index, see [llms.txt](https://docs.iridius.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iridius.xyz/assets/asset-roadmap.md). # Asset roadmap The asset classes that come after Stock Tokens, and the preconditions each one needs. The venue expands one asset class at a time, in the order that each class's listing requirements can actually be satisfied on Robinhood Chain. A stage opens when the infrastructure is in place, not when someone announces that it will be. ## Stage 1: Stock Tokens, live with the tail expanding Tier A launched first. Tier B and C markets arrive in batches, each one held back until its feed is confirmed and its bytecode review is complete. This tail is where an RWA-specific venue proves its worth, since these are precisely the assets that pooled designs heavily cap or decline entirely, and precisely the ones that thin generic pools misprice worst. See the [Listing framework](/assets/listing-framework.md). ## Stage 2: tokenized treasuries At roughly $16B, tokenized US Treasuries are the largest transferable RWA category after stablecoins, so they are the obvious second class: a trader leaving equity exposure should be able to move into yield without leaving the venue. Before the first treasury market can open: * Robinhood Chain must have a treasury token, issued natively or bridged via CCIP, from a regulated issuer, freely transferable in the way USDY is rather than gated by an allowlist. * A Chainlink feed on Robinhood Chain must track NAV and point at that exact token. * The whole [listing checklist](/assets/listing-framework.md) must be met, together with the NAV addendum: NAV-type assets are quoted within a tight band around NAV, and the closed-regime logic defers to the fund's own accrual, because treasuries have no weekend gap of the kind equities do. If a token restricts transfers in its contract, the vault is deployed in its permissioned form and allowlisted by the issuer, so that eligibility is enforced both by the issuer's hooks and by Iridius's registry. ## Stage 3: tokenized gold PAXG-style gold trades continuously against a spot reference and has no sessions whatsoever, so it will be the simplest asset the venue ever lists: `OPEN` at all hours, with only feed cadence and inventory affecting the spread. The requirement is the same one that applies to every other asset, the exact token bridged to Robinhood Chain with its own Chainlink feed, plus a bridge review that covers the mint path, the custodian attestations and the bridge's pause behaviour. ## Stage 4: whatever the chain issues next Robinhood has indicated that private-market tokens and other RWA classes are coming to this chain. Whatever arrives is held to the same checklist. An asset that cannot pass it (because the token has no feed of its own, there is no session signal, or the issuer's terms are not disclosed) will not be listed, no matter how loud the demand. ## What will not be listed * Wrappers, vault shares or receipt tokens whose price would need to be calculated instead of fed. Pricing the exact token is non-negotiable; the July 2026 wGOOGLx episode is the case study, covered in [Lessons from RWA trading](/risk/lessons.md). * Synthetics without a regulated issuer and without one-for-one backing. * Any token whose bytecode review reveals transfer controls that were never disclosed. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.iridius.xyz/assets/asset-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.