> 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/how-it-works/risk-controls.md).

# Risk controls

**OpenETF's controls form three layers: Supported Markets and Managed Execution, enforced before every trade is signed, and the Mandate (Coming soon). At launch, no layer limits a fund's leverage or concentration beyond Hyperliquid's own margin rules.**

Together the layers limit where a fund's capital can trade, how every trade reaches the market and, once the Mandate launches, what the Manager has promised. Around them sit Manager capital at stake, rule-based exits and records anyone can check.

| Layer                                      | Question it answers                            | Enforced by                                                |
| ------------------------------------------ | ---------------------------------------------- | ---------------------------------------------------------- |
| 1. [Supported Markets](#supported-markets) | **Where** can the fund take risk?              | Published admission rules, checked on every order          |
| 2. [Managed Execution](#managed-execution) | **How** does a trade reach the market?         | OpenETF's signing path, the only way to trade an ETF       |
| 3. [Mandate](#mandate) *(Coming soon)*     | **Within what limits** does the Manager trade? | Managed Execution, against the Manager's published Mandate |

## Supported Markets

The first layer decides where investor capital can take new risk.

* **Base criteria.** A Supported Market trades on Hyperliquid's main exchange, or on a USDC-collateralized HIP-3 exchange run by an admitted issuer. Its price-setting method is published and bounded, and whoever sets its price is accountable inside the protocol. Markets priced only by their own order book are excluded.
* **Screening rules.** A published, versioned framework adds category rules and thresholds for volume, depth, open interest and price health. It applies identically to every ETF.

When a market stops working, the layer contains it. If a HIP-3 issuer stops pushing prices, the market becomes reduce-only and the ETF closes to new subscriptions. If the stop outlasts the published threshold, the fund isolates the whole margin domain of that HIP-3 exchange, much like a side pocket, including positions in its markets that are still healthy. Holders at that moment receive a recovery right, and later investors never buy into it. Dead-market determination is not yet enabled on testnet, where the market stays reduce-only until the issuer resumes or the market settles. [Supported Markets](https://docs.openetf.xyz/how-it-works/risk-controls/supported-markets.md).

## Managed Execution

The second layer holds every trade to the fund's rules. It is also one of the limits that keep the Manager from withdrawing, described [below](#what-stands-behind-the-layers), though trading can still harm the fund.

Every order from the Trading Terminal or the OpenETF API passes through [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md). It checks the caller, the action, the market and the fund's state, including cash reserved for redemptions, before signing. Unknown actions are rejected by default. The Manager directs trading but never receives the fund's Trading Agent Wallet. When checks cannot complete, new risk stops; a reduction goes through only when the service can show that it reduces risk, and otherwise signing is suspended.

## Mandate

**Coming soon.** The third layer turns a Manager's promises into checked limits. A [Mandate](https://docs.openetf.xyz/how-it-works/risk-controls/mandate.md) publishes limits on assets, leverage, exposure and order types. Managed Execution checks every trade against the Mandate before signing. Loosening a limit waits for public notice. The ETF page shows **Mandate: Active** only when every risk-changing path is covered.

## What stands behind the layers

**Assets the Manager cannot withdraw.** The Manager never holds the fund's trading key, the Vault contract has no Manager withdrawal function, and Managed Execution refuses every action outside the fund's rules ([why](https://docs.openetf.xyz/how-it-works/hypercore-hyperevm.md#why-the-manager-cannot-withdraw)). None of this prevents losses through trading: the Manager, or anyone who gains trading authority, can harm the fund by trading.

**Manager Capital at stake.** Every Manager starts with at least 100 USDC of their own capital, held as the same shares investors hold, and commits to a ratio *p* of at least 5% that can only be raised. The contract caps any Manager redemption and refuses any transfer that would take the Manager's holding below *p*. New investment can dilute the ratio, and the Passport shows the actual figure. The ratio counts shares at the Manager address; hedging in other accounts or an off-chain sale of the economic interest can offset the stake without changing the ratio. [Manager Capital](https://docs.openetf.xyz/managing/capital.md).

**Rule-based exits.** Holders redeem at any time with no lock-up, no minimum and no Manager approval. The system pays from idle cash and trims every position in proportion, and waiting requests share arriving cash in proportion to their shares. A wind-down has a hard deadline, and the system takes over no later than hour 672, or earlier if the Manager stalls. [Redeeming](https://docs.openetf.xyz/investing/redeem.md) · [Closing an ETF](https://docs.openetf.xyz/managing/closing.md).

**Records anyone can check.** Every subscription, redemption and daily accounting point leaves a [receipt](https://docs.openetf.xyz/transparency/receipts.md) that anyone can recompute. The [Passport](https://docs.openetf.xyz/transparency/passport.md) sources every field. Shares and recorded payments live onchain.

## What these controls do not cover

**Strategy results.** The layers limit where capital can trade and how it can move. They do not make a strategy profitable. Trades can lose money, and positions can be liquidated or hard to exit in thin markets.

**OpenETF's own operations.** Trading depends on OpenETF's signing service being available and secure. If a key were compromised and used outside the managed path, the response would rely on detection, revoking that authority, rotating keys and protocol-level limits.

**Service outages.** If OpenETF's application goes down, shares and recorded entitlements remain onchain, and fixed payments whose cash is already on HyperEVM can be claimed from the contract. Pricing new redemptions, and raising cash from open positions, currently run through the execution service and resume when it does ([Pauses and surviving rights](https://docs.openetf.xyz/risks-and-security/interruptions.md#recorded-rights-survive-a-backend-outage)). No layer promises a completion time.

[Who controls what](https://docs.openetf.xyz/how-it-works/control.md) sets out each party's role in detail.

Next: [Supported Markets](https://docs.openetf.xyz/how-it-works/risk-controls/supported-markets.md)
