Release status & roadmap
Recorded deployments, implemented features, and work that remains outside the current release.
As of September 10, 2026, the project records a mainnet deployment for fixed community baskets, native ETH creation and trading, and an optional liquidity helper. This is separate from completing every production qualification step or making every implemented interface available in a hosted application.
Status at a glance
| Area | Recorded or implemented status | What that establishes |
|---|---|---|
| Fixed community baskets | Mainnet community and native factories recorded | Addresses exist for permissionless funded basket creation |
| ETH mint/redeem trading | Mainnet native router recorded | A configured route can buy or sell through underlying-token markets |
| Optional ETF liquidity | Mainnet liquidity helper recorded; API activation recorded September 9 | Pool discovery and funding-quote checks passed in the activation record |
| ETH and USDG pool trades | Implemented in the reviewed code | Availability depends on a matching API release and executable pools |
| Browser trial | Implemented on Robinhood testnet | Wallet-signed setup and testnet basket flows can be exercised |
| Managed official baskets | Separate code and local tests exist | No managed deployment is included in the recorded mainnet set |
| $RRR | Prelaunch information page and simulator | Token and new revenue model are not deployed |
| Independent audit | None reported | Local verification does not complete this review requirement |
The address reference contains the deployment table. Public reads on September 10 independently confirmed network identity and code presence at the four platform addresses. Creation receipts and compiled-bytecode checks remain evidence from the deployment record.
What the deployment record demonstrates
The September 8 record reports successful deployment of the community factory, native factory and native trading router. It also reports a later local mainnet-fork test of launch, buy and sell using those addresses. The test checked backing, issuance-fee rounding, refunds and payments; its trades were confined to a local fork.
The liquidity helper was subsequently deployed, and the September 9 activation record reports successful API health, configuration, pool discovery and WETH/USDG funding quotes. That activation did not fund a public ETF pool. A provider must contribute actual shares and quote assets for a pool to have usable liquidity.
Public explorer source verification remains pending in the deployment record. This documentation did not independently confirm the currently hosted frontend release or complete wallet transactions on mainnet. Implemented functionality should therefore be distinguished from a feature observed working in the live app.
Current product scope
The recorded mainnet contracts support fixed community baskets. A basket has a fixed constituent set, and later proportional minting or redemption follows its actual reserves. Trading or adding a pool does not restore launch target weights.
Stock-token discovery has been added using Robinhood’s registry, with on-chain identity and route checks. Registry inclusion is not a universal compatibility guarantee, an issuer eligibility determination, or proof that any requested trade can execute. Each token’s restrictions and available markets still matter.
Optional integrations are configuration dependent. For example, USDG pool trading requires the API to advertise that settlement token and provide the corresponding quote route. A frontend upgrade alone cannot supply a missing backend capability or create liquidity.
Remaining qualification work
The production roadmap calls for evidence tied to the exact release, including independent security review, public deployment verification, supported-wallet testing, transaction reconciliation, durable metadata and index recovery, monitoring and recovery exercises, and product and issuer-specific review where applicable.
The roadmap’s initial readiness table describes an earlier frontend-only baseline. Later implementation and deployment records supersede that baseline where they provide newer evidence. Unchecked roadmap items are not automatically a statement that no implementation exists, and code or a deployment address does not automatically satisfy a release gate.
Planned extensions
- Managed baskets: require a separately qualified price source and trading venue, official deployment, operator infrastructure and review of the additional authority and policy constraints.
- Broader token support: requires testing actual transfer behavior, issuer restrictions and executable exits. A familiar ticker or ERC-20 interface is insufficient.
- $RRR and protocol revenue: require the token, trading route and fee/buyback mechanics described in $RRR status.
- Product and operational improvements: include the gaps listed under known limits, supported-wallet validation and stronger release evidence.
No launch dates or completion percentages are committed by this reference. Each extension should publish its actual scope and evidence when available.