Delisting

Delisting closes your position for you, at a price fixed by the time the vote is held. Every position settles at that one price, a mechanism the docs note many centralised exchanges use.

Validator-operated perps settle at a price fixed before the vote

If the validators’ vote passes, positions settle, orders are cancelled and the meta entry stays (table). Say the vote is scheduled for 12:00 UTC: you settle at the time-weighted oracle price from 11:00 to 12:00, and later moves don’t count.

The averaging window closes at the scheduled vote time, not at settlement, and the oracle is published about every 3 seconds: anyone recording it can compute the settlement price in advance.

In the 28 September 2026 read, every delisted entry still had an asset context: funding, open interest and day volume "0.0", no impact prices, markPx still populated.

HIP-3 deployers halt their own markets

The deployer, not the validators, ends a HIP-3 market:

• haltTrading cancels an asset’s orders and settles its positions at the current mark price. It also resumes trading, recycling the asset, so dated contracts need no new auction slot each.
• Stake release: once all of a dex’s assets are settled, the required stake can be unstaked.
• New assets start halted: they need haltTrading with isHalted: false before trading.
• Losing the collateral asset: if validators vote a quote asset out of quote asset status, perp dexes using it as collateral are disabled too; if its own deployer disables it, they are not.
• Growth mode: validators disable ineligible growth mode perps by on-chain vote, which the docs compare to delisting.
• disableDex is in the deployer action list, with no documented effect.

Hyperps convert instead

A hyperp does not end at launch: shortly after its USDT pair lists for spot on Binance, OKX or Bybit, it becomes a normal perp on the usual oracle.

The numbers

Item	Validator-operated perp	HIP-3 perp
Who decides	validator vote	the deployer, with haltTrading
Settlement price	1-hour time-weighted spot oracle price before the scheduled vote time	current mark price
Open orders	cancelled (delistedCanceled)	cancelled
New orders	refused after settlement	refused while halted; trading can resume
meta entry	kept, isDelisted: true	kept, isDelisted available
Mainnet count, 28 September 2026	56 of 234 entries delisted	47 of 185 entries delisted across the three dexes read

Before and after a delisting

• Close first if the exit price matters, as the docs advise.
• Settlement realises PnL at the settlement price, and funding stops.
• HIP-3 settlement uses the mark, at a time the deployer picks. The mark is partly deployer supplied through setOracle, bound by the protocol’s clamps and by slashing for irregular operation (operating a perp dex).

Indexing delisted assets in code

• Keep delisted entries when indexing meta.universe. An asset id is its position there, so filtering first shifts every later asset and sends orders to the wrong market (asset ids).
• Check isDelisted before quoting, and treat delistedCanceled as terminal, not an error to retry.
• A delisted markPx is not tradable, since no new orders are accepted.

Notice periods and whole-dex delistings

• No notice period between vote and settlement is documented.
• HIP-3 counts include whole dexes: one of the three dexes read had all 23 of its assets delisted.

For the meta fields, including isDelisted, see Contract specifications. For the price a delisting settles against, see Oracles and mark prices.