> 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/manage/trading.md).

# Trading

Trade your vault from the Chamber app: swaps, liquidity, lending, leverage. TradingView charts your vault token.

Managers trade directly from the [Chamber app](https://chamberfi.com/). The trading UI is category-based: pick what kind of position you want to open, pick the protocol, execute. Your vault token's price is charted in TradingView so you can analyze vault performance with the full TradingView toolset.

This page covers manual trading. For bots and custom automations, see the [SDK](/build/sdk.md).

## Opening the trade view

From your vault page, click **Manage Vault**. You'll see tabs across the top, one per trade category:

* **Swaps:** spot-to-spot token swaps.
* **Liquidity:** LP positions on supported DEXes.
* **Lending & Borrowing:** supply and borrow on money markets.
* **Leverage:** leveraged positions via Toros.
* **Custom:** connect to any dApp via WalletConnect (within Guard System limits).
* **All:** everything, ungrouped, for quick access.

Each tab shows the protocols available **on your vault's chain** for that category. What's listed differs per chain. HyperEVM shows Perps and Spot; Base doesn't have Leverage; etc. See [Chain capabilities](/manage/chain-capabilities.md) for the full matrix.

## TradingView charts

Your vault token's price is charted in the standard TradingView interface: drawing tools, indicators, and timeframes all work as normal. Use it to analyze your vault's own performance over time, not just individual assets. Charts are for analysis only; they don't execute trades.

## Protocols by category

The set of supported protocols differs per chain. The **Manage Vault** screen in the app shows the full list for your vault's chain, grouped under the category tabs. That's the source of truth while you're trading.

See [Chain capabilities](/manage/chain-capabilities.md) for a high-level matrix of what each chain supports (Spot, Lending, Leverage, LP, Perps).

## Executing a trade

Selecting a protocol opens its native UI embedded directly in the Chamber app. You interact with the real protocol interface to build your transaction (enter sizes, set slippage, confirm), and sign it from the manager wallet (or the delegated [trader wallet](/manage/trader-delegation.md)).

Both sides of any trade must be in your vault's [enabled assets](/manage/permissions-access.md). If an asset isn't enabled, enable it first.

The Guard System checks every call onchain: enabled asset? approved protocol? Calling a function the guard actually allows? If anything fails, the transaction reverts before it can touch vault funds.

## Tokenized equities on Ethereum

Chamber vaults on Ethereum can hold tokenized stocks, ETFs, and commodity ETFs issued by [Ondo Stocks](/concepts/supported-assets.md). They behave like ordinary ERC-20s to trade, but three things differ from crypto assets and are worth planning around before you build a position.

**Pricing comes from Ondo's attestation oracle, not Chainlink or Pyth.** Nearly every Ondo token on Ethereum is priced this way. It's a slower-moving feed than a standard crypto price feed, so a vault holding these assets updates its NAV on that feed's cadence rather than tick by tick.

**An Ondo pause makes the asset temporarily unpriceable.** If Ondo pauses minting or redemptions for a token your vault holds, the price feed stops returning a price, and the vault can't compute [NAV](/concepts/nav-accounting.md) without it. While that lasts, deposits, withdrawals, and fee minting on your vault will fail. They resume when Ondo does. This is the main operational difference from a crypto-only vault: a pause on one held asset affects the whole vault, not just that position.

**Regional access rules apply.** Vaults holding Ondo Stocks tokens are subject to eligibility and regional access rules and may not be available everywhere. That constrains who can deposit, so it's worth deciding early whether a vault is meant for a broad audience.

Practical implications when building a cross-asset vault:

* Keep the enabled asset set tight. Each enabled asset adds gas to deposits, withdrawals, and NAV calculation, and the equity set is large enough to be tempting.
* Expect NAV to move in steps rather than continuously compared to a crypto-only vault.
* If uninterrupted deposits and withdrawals matter for your strategy, weigh that against holding assets whose pricing depends on an external issuer's pause switch.

See [supported assets](/concepts/supported-assets.md) for the asset list and [risks](/deposit/risks.md) for the depositor-facing version.

## Perps on HyperEVM

Perps are set up differently from the other categories, because the order book isn't on HyperEVM. Your vault lives on HyperEVM, and Hyperliquid's perps order book lives on HyperCore. To trade, the vault sends instructions across to HyperCore through a Hyperliquid system contract called CoreWriter, and the Guard System checks those calls like any other integration.

Perps run through [HyperEVM Trade](https://www.hyperevm.trade/), Chamber's Hyperliquid interface. Like the other protocol UIs it's embedded in the Chamber app, or you can open the site in its own window and connect your vault to it via [WalletConnect](#custom-trades-via-walletconnect).

Three things have to be in place before a perps trade goes through:

1. **Your vault is approved for the integration.** Perps are in early access, so the team enables them per vault. Until that's done, trades fail with "Vault not whitelisted for this integration". See [Chain capabilities](/manage/chain-capabilities.md) to request access.
2. **"Hyperliquid Perps Account" is one of your enabled assets.** You do this one yourself, and it's the step most managers miss. Enable it like any other asset (see [Enabled assets](/manage/permissions-access.md#enabled-assets)) and the vault's perps balance is priced into NAV. That asset's address is Hyperliquid's CoreWriter contract, which is why skipping it fails with "CoreWriter not enabled in vault".
3. **The market you want is approved.** Perps markets are approved onchain one at a time. If one you want isn't available, ask via **Support Chat** in the [Chamber app](https://chamberfi.com/).

### Moving capital in and out

Enabling the asset doesn't move any money. Your vault's USDC sits in its EVM wallet on HyperEVM, and perps trade against separate balances on HyperCore, so you have to move capital across before you can open a position.

The transfer panel in HyperEVM Trade shows four balances for your vault:

* **EVM Wallet:** USDC held by the vault on HyperEVM.
* **Spot:** your Hyperliquid spot balance.
* **Crypto Perp:** margin for crypto perps markets.
* **Real World Perp:** margin for real-world asset markets such as equities and commodities.

The panel takes a **From** and a **To**, so each move is one action: pick EVM Wallet → Spot to deposit, then Spot → Crypto Perp (or Real World Perp) to fund the account you want to trade against. Reverse the direction to bring capital back, which is what you do when you want to trade spot on HyperEVM again: Crypto Perp → EVM Wallet.

The two perp accounts are funded separately. Margin sitting in Crypto Perp doesn't back a Real World Perp position, so if you trade both, you fund both.

Within a single account the opposite is true: each perp account is cross-margin, so the whole balance backs every position you hold in it. A loss on one position reduces the margin behind the others, and a liquidation draws on the account as a whole rather than just the position that moved against you. Size positions with that in mind.

Only USDC moves across. Tokens the vault holds on HyperEVM stay on HyperEVM, so to put more capital behind a perps position, swap to USDC first, then transfer.

The perps account uses one of your 12 enabled assets, so a perps vault has 11 slots left for everything else. Plan for that if you want wide market coverage.

## Custom trades via WalletConnect

The **Custom** tab is a secondary way to interact with integrated protocols. Instead of using the embedded protocol UI on the main trade page, you connect your vault directly to the protocol's own site via WalletConnect and complete the trade there. Useful when you want to use a protocol feature that isn't surfaced in the embedded Chamber view.

The flow:

1. Open the dApp you want to use in a new tab and click its **Connect Wallet** button, choosing **WalletConnect**.
2. Copy the WalletConnect QR code or connection URI from the dApp.
3. Paste it into the **WalletConnect** field on the Chamber Custom tab.
4. Confirm the connection. The dApp now sees your vault address, not your personal wallet.
5. Trigger transactions via the dApp; they're signed from your manager (or trader) wallet and routed through the Guard System.

What you **can't** do via WalletConnect: route around the Guard System. Calls to disallowed contracts or unlisted assets revert onchain. Custom doesn't expand what's allowed. It's just a different entry point into the same protocols.

If you want a protocol or asset enabled that isn't supported yet, reach out via **Support Chat** in the [Chamber app](https://chamberfi.com/) and we can look into adding it.

## Deposits, withdrawals, and vault accounting

Trading changes what the vault holds, not its NAV (beyond slippage and fees). Depositor accounting is handled separately in USD via the [denomination asset](/manage/denomination-asset.md). Every swap, LP position, and leveraged token is priced against USD by the oracle layer so depositor shares reflect the vault's true value.

## Not covered here

* **Fees you pay as a manager trading:** gas only; Chamber doesn't charge a per-trade fee. Depositor-side fees (entry/exit/perf/mgmt) are in [Fees & performance](/manage/fees-performance.md).
* **Running a bot:** see the [SDK](/build/sdk.md) or call the contracts directly.
