> For the complete documentation index, see [llms.txt](https://docs.openetf.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openetf.xyz/managing/trading.md).

# Trading an ETF

**The Manager trades from the Trading Terminal or the OpenETF API, and OpenETF checks every trade and signs it with the fund's own trading key. No trading client can withdraw fund assets or send them to another owner, though trades themselves can lose the fund's money.**

When investors redeem, the system raises cash by fixed rules without taking over the strategy.

## Two clients share one execution path

The Trading Terminal is the Manager's workspace for one ETF; the [OpenETF API](https://docs.openetf.xyz/developers/api.md) serves the Manager's own strategies, bots or third-party terminals. Both submit the same intents through [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md), pass the same checks and pay the same fees.

Trades are signed by the fund's Trading Agent Wallet, a non-exportable key that only OpenETF's signing service can use, and only for trading actions and defined movements between the fund's own balances. In the first release neither client receives a Hyperliquid native API key, and API credentials are scoped to named ETFs and actions and can be revoked.

## Trading rights are not money rights

{% hint style="info" %}
The Manager cannot withdraw fund assets ([why](https://docs.openetf.xyz/how-it-works/hypercore-hyperevm.md#why-the-manager-cannot-withdraw)), though trading can still harm the fund. Managed Execution permits only orders, cancels, permitted leverage changes and defined movements between the fund's own balances, and rejects every other action from every client.
{% endhint %}

Every intent passes the [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md#checked-before-signing) checks before signing. Cash moves only between the ETF's own HyperCore account and its own HyperEVM address, and from there only to the holders it is owed to. Deploying new cash from HyperEVM to HyperCore, or moving collateral between the fund's own HyperCore balances, is itself such an intent: it passes the same checks, and its destination is always the fund's own account. This is the Managed Execution layer of [risk control](https://docs.openetf.xyz/how-it-works/risk-controls.md).

Positions, orders and cash reserved for exits share one ledger, so two actions cannot spend the same capacity. An optional [Mandate](https://docs.openetf.xyz/how-it-works/risk-controls/mandate.md) (Coming soon) adds the Manager's published trading limits to these checks.

## Redemptions are filled by rule, never by discretion

A redemption pays from idle cash first, and every redemption also trims each position by its share of the fund, so that, absent other flows, the remaining holders keep the same leverage and mix. Margin-using orders are cancelled only where a domain still cannot release the cash ([How redemptions are funded](https://docs.openetf.xyz/economics/redemption.md)). The Manager cannot pick who exits first, hold a request for a better price or reorder the queue.

Cash held for waiting redemptions cannot open positions. A submitted redemption cannot be withdrawn except during a valuation pause, when the system cancels unfilled orders placed for waiting redemptions ([Pauses and surviving rights](https://docs.openetf.xyz/risks-and-security/interruptions.md)).

In any margin domain above 10× notional leverage, a redemption first brings that domain below 10×: Hyperliquid lets margin leave only down to the larger of initial margin and 10% of notional, and OpenETF applies that limit to each margin domain.

## Only Supported Markets take new risk

Every intent is checked against Supported Markets; new markets join after a published notice period. A removed market stops opening and increasing at once; cancelling, reducing and closing stay permitted, though no fill is assured. No per-market exposure cap applies, and the Passport shows each market's share of NAV.

If a held HIP-3 market's issuer stops pushing prices, the market turns reduce-only and new subscriptions close; subscriptions reopen when the issuer resumes, the market settles, the ETF no longer holds that market or its domain is isolated. The Manager may reduce the stopped market but is not required to: a fill on a thin book can land far below the reading, and every holder shares the loss. Past the published threshold, the whole margin domain of that HIP-3 exchange, including positions in its markets that are still healthy, is isolated as a recovery right for the holders at that block. The Manager may reduce an isolated domain but is not required to, and a named platform role takes over disposal if the Manager does not finish it ([Supported Markets](https://docs.openetf.xyz/how-it-works/risk-controls/supported-markets.md#a-dead-market-is-isolated-not-priced)). Dead-market determination is not yet enabled on testnet, so there the market stays reduce-only until the issuer resumes or the market settles.

## Manager-initiated trades carry a 1 bp platform fee

It applies to supported perpetual fills in both directions and spot sells, at the same rate on Terminal and API. Spot buys and system orders for redemptions or Wind-down carry none ([Fees and costs](https://docs.openetf.xyz/economics/fees.md)).
