Composable Pools
A pool token can be registered as a Reserve Asset in another pool. Each portfolio in the resulting hierarchy retains its own accounting state.
For example, USD.cav can be held inside an equity portfolio alongside equity tokens. That equity pool’s LP Token can then be held inside a broader aggregate portfolio.
Roles change with the pool
| Context | Role of the equity pool token |
|---|---|
| Its own equity pool | LP claim on the equity pool’s backing. |
| An aggregate pool holding it | Reserve Asset that can be bought or sold through that aggregate pool. |
A Reserve Asset trade in the aggregate pool transfers the portfolio token. The receiving account holds that portfolio token after settlement. Redemption is a separate liquidity action in the token’s own pool.
Prices and liquidity remain local
Each pool has its own reserves, scales, elasticity, and fees. The quantity of a portfolio token available in a parent pool is different from the liquidity inside the child portfolio.
An order in one pool only uses the assets registered there. Cross-pool workflows need explicit calls and quotes for each participating pool; each layer settles against its own state.
Example portfolio families
Stablecoins can form a dollar-linked portfolio. Currency, commodity, and equity tokens can form category portfolios. Their LP Tokens can become holdings of an aggregate portfolio.
These are composition patterns. Deployments identifies what is currently available; the current Robinhood app manifest publishes USD.cav.