> 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/investing/redeem.md).

# Redeeming

**A redemption turns shares into USDC at any time, with no lock-up and no minimum. Idle cash can fix the payment for part of it at once; the rest waits and prices at the NAV when its cash arrives.**

A submitted request cannot be spent twice or withdrawn, except for its unpriced part during a valuation pause.

The [redemption and liquidity risks](https://docs.openetf.xyz/risks-and-security/risks.md#redemption-and-liquidity-risk) set out what an exit can cost and how long it can wait.

## The page shows what may wait and what it costs before signing

Before signing, the redemption page shows the portion that may wait for cash, the exit adjustment fee rate that applies, and a note that the final amount follows NAV when cash arrives, not at submission. The receipt then records the actual deductions and amount.

## Submitting moves the shares into escrow

The shares go into contract escrow, out of the holder's name, where they cannot be transferred or reused. They keep sharing in gains, losses and fees until each portion is priced and burned. One wallet can have one pending redemption per ETF.

A submitted request is final, so no one can force the fund to sell and then walk away from the cost. Only during a valuation pause can the unpriced remainder be withdrawn.

## Part can be paid now, and the rest at a later NAV

Idle cash is confirmed cash the fund has not already reserved. The portion it covers, net of the exit adjustment fee, prices at once. The rest stays as shares while the fund trims every position in proportion to the request, and prices at the NAV that applies when that cash arrives.

For example, a holder redeems 600 of a fund's 1,000 shares at NAV 1.00, and the fund holds 400 USDC of idle cash. About 400 shares are fixed at 1.00 straight away. The other 200 or so keep moving with the fund and are paid at the NAV when the sales settle, which can be higher or lower. Selling costs reach the payout only through that NAV, shared by every share outstanding at pricing. [How redemptions are funded](https://docs.openetf.xyz/economics/redemption.md) covers the mechanism.

Payment and trimming are tracked separately. The request shows how much of it is fixed and paid. The trim sells every position by the redeemed fraction to keep the remaining holders' leverage, and it runs even when idle cash pays the whole request, except in a market whose issuer has stopped pushing prices, which the system does not sell; its proceeds go to the pool, where waiting requests share arriving cash pro rata.

## Waiting requests share arriving cash in proportion to their shares

{% hint style="info" %}
**Among waiting requests, queue position does not change anyone's share.** Each batch of arriving cash fixes the same fraction of every executable waiting request's remaining shares, at one NAV, and each request pays its own fee rate. Idle cash already in the fund at submission can cover a new request at once, but only from what the queue leaves.
{% endhint %}

The platform cannot pick the pricing block. Every executable waiting request is fixed in every pricing event, however small its slice; a blocked request is not. A minimum payout amount, shown on the ETF page, only decides when the automatic payment is sent: smaller fixed amounts stay backed and can be claimed at any time, and a fully fixed request is paid whatever its size.

## The exit adjustment fee stays with the holders who remain

Every priced portion pays an exit adjustment fee at a rate that rises with the fund's leverage, up to a cap. No one collects it directly: it stays in the pool for every remaining share, the Manager's included, and above the cost basis it also raises the accrued performance fee. An exit pays toward the selling costs it causes instead of leaving them to those who stay, though at high leverage, in thin markets or for spot holdings the fee may not cover them in full. The last shares out and Wind-down distributions pay none ([How redemptions are funded](https://docs.openetf.xyz/economics/redemption.md#the-exit-adjustment-fee-stays-with-the-holders-who-remain)).

## Pauses, Wind-down and dead markets change the path, not the rights

| Event                                              | Effect on a waiting request                                                                                                                                                                    |
| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Valuation pause                                    | No new selling starts for it, its open orders are cancelled, and the unpriced remainder can be withdrawn; pricing later resumes without resubmission, still pro rata within each pricing event |
| Wind-down                                          | Unpriced shares join the distribution as the requester's ordinary shares, with no priority and no exit adjustment fee ([Closing an ETF](https://docs.openetf.xyz/managing/closing.md))         |
| Issuer feed stopped                                | The part that depends on that market waits until the issuer resumes, the market settles, the fund no longer holds it or its domain is isolated; the rest prices as usual                       |
| Dead-market isolation (not yet enabled on testnet) | Escrowed shares earn a recovery right for the requesting address; the request then prices in full cash on the remaining assets                                                                 |

Fixed payments are untouched by all four ([Pauses and surviving rights](https://docs.openetf.xyz/risks-and-security/interruptions.md)).

Before a stopped HIP-3 market is determined dead, redemptions keep pricing on readings that include its domain, so a reading pushed in the fund's favor can overpay whoever is priced then, at the expense of those who stay ([Supported Markets](https://docs.openetf.xyz/how-it-works/risk-controls/supported-markets.md#a-stopped-issuer-feed-freezes-the-market-and-closes-new-subscriptions)).

## The Manager's own exit is capped

A Manager's redemption is capped by the commitment ratio; the part over the cap waits unpriced and uncharged and never delays other holders ([Manager Capital](https://docs.openetf.xyz/managing/capital.md#redemptions-and-transfers-have-different-ceilings)).

## Processing is designed to take seconds to minutes

Under normal conditions a redemption runs as separate steps over seconds to minutes, and the request shows which step it has reached. Instructions to HyperCore take a few seconds to execute, and a transfer back to HyperEVM lands in the next HyperEVM block. Market, protocol or service problems can stretch any step, and no fixed arrival time is promised.

In a tiny redemption, a position whose trim is below the minimum order size is covered from idle cash, or rounded up to the minimum trade unit when cash is short; the extra cash stays in the pool.

Next: [Getting paid](https://docs.openetf.xyz/investing/payments.md)
