> 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/supported-markets.md).

# Supported Markets

**An ETF takes new risk only in Supported Markets: markets whose price mechanism is public, bounded and set by a party accountable inside the protocol. When a HIP-3 issuer stops pricing a market the fund holds, the ETF closes to new money and, past a published threshold, isolates that exchange's whole margin domain like a side pocket instead of letting a thin order book set NAV.**

Concentration is disclosed, not capped. Supported Markets is the first layer of [risk control](https://docs.openetf.xyz/how-it-works/risk-controls.md): [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md) checks every order against it before signing.

## Two tiers decide where an ETF can take new risk

Supported Markets is neither a hand-picked whitelist nor a copy of Hyperliquid's listings.

**Base criteria** are hard rules. A market qualifies only if all three hold:

* It trades on the Hyperliquid main exchange, or on the USDC-collateralized HIP-3 exchange of an issuer on the admission list.
* Its price mechanism is published with rate limits or bounds. A market priced internally from inception under such a mechanism, such as a pre-IPO perpetual (IPOP), qualifies.
* The price setter is accountable inside the protocol: validators price the main exchange, and HIP-3 issuers post slashable stake.

Markets priced only by their own order book, issuers off the list, and delisted, settled or dead markets are excluded. Spot qualifies only for USDC or an asset with a qualifying main-exchange perpetual.

**Screening rules** are public, versioned and identical for every ETF. They combine category rules with thresholds for volume, depth, open interest and price health, with no discretionary score. On testnet these thresholds are not enabled; admission there follows the base criteria and category rules. Additions, including a new issuer on the admission list, wait for a published notice period, and until one is published nothing is added. Removals apply at once and stop only opening and increasing; cancelling, reducing and closing stay permitted, though no fill is assured.

The Passport shows the current admission list, category rules, screening-rules version and notice period, with their history. Supported is not an endorsement or a promise of liquidity.

## Concentration is disclosed, not capped

No exposure cap applies to any market or category, and no fund-level leverage limit applies beyond Hyperliquid's own margin rules, so concentration and leverage are the Manager's choice. The Passport shows each held market's notional as a share of NAV.

## HIP-3 issuers are accountable, not insurers

An issuer submits prices under protocol limits and can halt a market and settle positions at the mark price; the Manager holds none of these powers. Slashed issuer stake is burned and compensates no trader. A settlement is booked like the Manager closing the position, the ETF page records the market, time and settlement price, and the market then leaves Supported Markets under the admission rules. How issuer prices, including prices set during an official closure, reach NAV is on [Pricing and valuation](https://docs.openetf.xyz/economics/pricing.md).

## A stopped issuer feed freezes the market and closes new subscriptions

Prices an issuer sets under its published mechanism, including during an official closure or a documented external-data outage, or for a market priced internally from inception, are normal operation while the issuer keeps pushing them. Price-quality signals, such as a widening mark–oracle gap or a price held at its bound, and prices that look off the mechanism go into the [price-health record](https://docs.openetf.xyz/economics/pricing.md#some-markets-are-priced-from-their-own-order-book) and do not freeze the market. Once OpenETF observes an issuer has stopped pushing prices on an unsettled market, the position becomes reduce-only. New subscriptions close, including added Manager Capital, with the reason and recovery conditions shown. Redemptions continue, priced on reads that still include that domain, so a reading pushed in the fund's favor can overpay an exiting holder at the expense of those who stay. The system no longer sells the stopped market for redemptions or a close, unless its domain has been isolated (below): the part of a redemption that depends on it waits until the issuer resumes, the market settles, the fund no longer holds it or its domain is isolated.

For a stopped feed, the reduce-only limit lifts when the issuer resumes or the market settles. The subscription closure lifts then too, or once the ETF no longer holds that market. The closure stops anyone buying shares at a NAV that a small order on a thin book has pushed down.

## A dead market is isolated, not priced

A held HIP-3 market is dead when its issuer has stopped pushing prices beyond the published threshold without settling; the ETF page shows the current threshold. No other test applies. OpenETF issues the determination receipt by rule, and anyone can check it against the issuer's published data. Dead-market determination is not yet enabled on testnet: no threshold is set there, so a stopped feed keeps the market reduce-only until the issuer resumes or the market settles, and subscriptions stay closed as described above.

The fund's pricing reads equity per margin domain, a separately margined account area such as the main exchange or one HIP-3 exchange, and not per asset. So the whole margin domain of that HIP-3 exchange is isolated, including positions in its markets that are still trading normally. In the determination block:

* The domain's equity reading, if positive, leaves the fund's assets and cost basis. The share count does not change.
* Every share outstanding then receives a pro-rata recovery right over the domain: a claim on whatever the domain later yields. An escrowed share's right belongs to the address that submitted the redemption; later subscribers receive none.
* NAV counts only the remaining domains. Redemptions pay in full cash at that NAV, and new subscriptions reopen.

Everything later in the domain, including fills, settlement, funding and liquidation, belongs to the recovery right. Proceeds are paid by the isolation snapshot, never back to the pool. A domain with negative equity creates no right.

Healthy positions in the domain stay open and reduce-only until they are sold, still exposed to price moves, funding and liquidation. A redeeming holder receives the rest of the fund in cash and keeps a recovery right for the domain, but cannot take the domain itself as cash at the normal NAV.

The domain stays reduce-only. While the ETF is Active, the Manager may reduce there but is not required to. If the domain is not fully disposed of 672 hours after isolation (counted from the isolation block, separate from any wind-down clock), a named platform role takes over its reduce-only disposal, without the platform trading fee, and the Manager stops trading there. That disposal depends on the platform being online. In Wind-down, reduction joins the system takeover; after Closed, the named platform role disposes of what remains. Proceeds go to the snapshot holders; realization, like any sale in an abandoned market, is not promised.

A market found dead during Wind-down is isolated the same way, outside the final snapshot. Isolation is irreversible. It does not start a Wind-down by itself, but the [warning line](https://docs.openetf.xyz/economics/fees.md#the-warning-line-starts-wind-down-before-fees-overwhelm-holders) is checked after it as after every accounting event, and a fund concentrated in the isolated domain, or already close to the warning line, can cross it. Each determination, transfer and distribution produces a [receipt](https://docs.openetf.xyz/transparency/receipts.md).

Next: [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md)
