> For the complete documentation index, see [llms.txt](https://docs.chamberfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chamberfi.com/concepts/supported-assets.md).

# Supported assets & protocols

A Chamber vault can only hold assets and interact with protocols that are on the **protocol-wide allowlist**. Managers pick from this allowlist at [vault creation](/manage/create-a-vault.md); the [Guard System](/security/guard-system.md) enforces the allowlist onchain at every trade. This page explains the shape of the allowlist and how it evolves.

## One vault, many asset classes

A single Chamber vault can hold **crypto, tokenized equities, commodities, and stablecoins together**. A manager isn't boxed into one asset class. Tokenized US stocks and ETFs (via Ondo Global Markets) sit alongside spot crypto, gold, lending positions, and leverage, all under the same Guard System rules and priced by the same [oracle layer](/concepts/oracles.md). This is what makes a cross-asset strategy (say, long tech equities hedged with a leveraged crypto short and idle cash earning lending yield) expressible in one onchain vault rather than spread across several venues.

Because a vault packages many assets into a single tokenized strategy, a Chamber vault can be a **private portfolio**, a **public strategy**, or a **thematic basket**: AI chips, AI compute, quantum computing, peptide medicines, broad-market ETFs, or a commodities sleeve. The manager builds and maintains it, and chooses whether to keep it private or open it to depositors through one [vault token](/concepts/vault-tokens.md): managers get a wider asset set to build with, depositors get a simpler way to access the strategy. Ondo Global Markets assets trade against public-market liquidity, so spreads stay tight enough to build and rebalance without heavy trading costs.

Tokenized equities and RWAs are currently an **Ethereum** feature; the rest of the categories below vary by chain (see [Chain capabilities](/manage/chain-capabilities.md)).

## Two allowlists, not one

There are two layers:

* **Protocol allowlist.** The set of smart contracts (DEXes, lending markets, yield venues) Chamber's Guard System allows any vault to interact with. Protocol-wide and updated by Chamber.
* **Vault's enabled assets.** The set of tokens and position types a single vault has turned on. Each vault enables up to **12 assets** at once, chosen from the protocol-wide asset list.

A trade has to pass **both**: the target protocol must be allowlisted at the protocol level, and the assets involved must be on the vault's own [enabled assets](/manage/permissions-access.md).

## Supported categories

The allowlist is organised by what kind of position the asset represents:

| Category                     | What it is                                              | Example assets / positions                                                   |
| ---------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **Crypto**                   | Spot ERC-20 tokens                                      | WETH, WBTC, ARB, OP, POL                                                     |
| **Tokenized equities & RWA** | Tokenized stocks & ETFs (Ondo Global Markets, Ethereum) | SPYon, NVDAon, MSTRon, COINon, TQQQon, …                                     |
| **Commodities**              | Tokenized commodity exposure                            | Gold, silver, oil, gas via Ondo (GLDon, SLVon, USOon…); XAUt; Toros GOLDBULL |
| **Stablecoins**              | Fiat-backed or overcollateralised stables               | USDC, USDT, DAI                                                              |
| **Lending**                  | Lending-market deposit positions                        | aTokens (Aave), cTokens (Compound)                                           |
| **Leverage**                 | Leveraged spot tokens                                   | Toros leveraged tokens (e.g. ETHBULL3X)                                      |
| **Liquidity provision**      | LP positions on allowed DEXes                           | Uniswap v3 LP NFTs, PancakeSwap CL positions                                 |
| **Yield**                    | Yield-bearing positions                                 | Pendle tokens, staked assets                                                 |
| **Perps (HyperEVM only)**    | Perpetual futures                                       | Via Hyperliquid on HyperEVM                                                  |

Which categories are available depends on the chain. See [Chain capabilities](/manage/chain-capabilities.md) for the per-chain matrix.

The Ondo tokenized-asset set on Ethereum is large and grows over time. The asset selector in the [Chamber app](https://chamberfi.com/) is the live source of truth for exactly what's enabled. The examples above are illustrative, not exhaustive.

> **Access.** Vaults that hold Ondo Global Markets assets are subject to eligibility, offering, and regional access rules, and may not be available in all locations. The tokens provide economic exposure to the underlying asset under Ondo's terms. See [Risks](/deposit/risks.md).

## How assets and protocols get onto the allowlist

Not every protocol or asset can be added. The Chamber team (and, via governance, the DAO) evaluates candidates against a rough set of criteria:

* **Security.** Established code, multiple audits, production track record.
* **Liquidity.** Enough market depth that the asset can be priced and traded without outsized slippage.
* **Oracle coverage.** A reliable [oracle feed](/concepts/oracles.md) exists (Chainlink, Pyth, TWAP, or, for tokenized RWAs, Ondo's attestation oracle).
* **Fit.** The asset or protocol solves a real strategy need that isn't already covered.

Additions happen iteratively. The list grows more than it shrinks, but nothing is permanent. A protocol can be removed from the allowlist if it's compromised, deprecated, or no longer safe.

## Wrapped vs native

Some tokens are only available in wrapped form:

* **ETH.** Vaults hold **WETH**, not native ETH. Deposits and withdrawals of ETH are wrapped/unwrapped at the edges.
* **BTC.** Vaults hold **WBTC** (or the chain-equivalent wrapped BTC). Chamber has no native-BTC integration.
* **Gas tokens.** POL on Polygon, ETH on Arbitrum, etc. The app handles the wrap for you.

This is a smart-contract constraint: ERC-20 is the standard Chamber's contracts speak. Native gas tokens aren't ERC-20.

## What's not supported

* **Arbitrary ERC-20s.** You can't enable a random memecoin via the app. If it's not on the allowlist, it's not available.
* **Arbitrary NFTs.** Vaults can't hold random NFTs as positions. The exceptions are integration-specific NFT positions (Uniswap v3 LPs and similar), which are held directly and priced/unwound by their dedicated [asset guards](/security/guard-system.md).
* **Assets on unsupported chains.** Each vault lives on one chain. If you want exposure on another chain, create (or deposit to) a vault on that chain.

## Related

* [Chain capabilities](/manage/chain-capabilities.md): per-chain support matrix.
* [Permissions & access](/manage/permissions-access.md): how managers set their vault's enabled assets.
* [Trading](/manage/trading.md): what categories and protocols look like in the trade UI.
* [Guard System](/security/guard-system.md): how the allowlist is enforced.