> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redpotion.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Redeeming

> Redeeming turns your fund shares back into assets. It follows the same batched model as depositing, with one extra stage: because the fund's capital is often deployed in strategies

Redeeming turns your fund shares back into assets. It follows the same batched model as depositing, with **one extra stage**: because the fund's capital is often deployed in strategies at settlement time, the fund must first bring assets back before a settled redemption can be paid out.

## The timeline

```
You redeem ──▶ batch closes ──▶ price accepted ──▶ operator funds the batch ──▶ You claim assets
  (queued)                       (settled: payout        (assets returned
                                  amount snapshotted)      to the Fund)
```

<Steps>
  <Step title="Request">
    You call `redeem(asset, shares)` on the [RedeemQueue](/developers/contract-reference/redeem-queue), choosing which allowed asset you want to be paid in. You approve the share token first; the queue pulls your shares into escrow. The [RiskManager](/developers/contract-reference/risk-manager) enforces minimums and batch caps. Your request joins the current batch.
  </Step>

  <Step title="Settle">
    When the batch's report is accepted, the queue transfers the batch's shares to the Fund (which burns them) and **snapshots the payout amount** — the assets you're owed, computed at the accepted price minus the exit fee. Because it's snapshotted here, later changes to the exit fee or price cannot change what your batch is owed.
  </Step>

  <Step title="Fund">
    Settlement only *records* what's owed. The operator then brings the assets back to the Fund — pulling them from strategies, or receiving them back from external wallets or bridges — and calls `fundRedeem` to deliver them to the queue. The batch is now claimable.
  </Step>

  <Step title="Claim">
    You call `claimRedeem(asset, batchId)` and receive your pro-rata assets.
  </Step>
</Steps>

## Why the extra "fund" stage exists

In a fully on-chain vault, assets are always sitting in the contract, so a withdrawal can pay out immediately. In a Red Potion fund, capital is usually working — in strategies, in custody, or on another chain. Settlement fixes the *amount* you're owed at a fair price; funding is the separate, operator-run step that actually returns the assets. This decoupling is what lets a fund deploy capital productively while still honoring redemptions at a fair, snapshotted price.

The tradeoff: the time between settlement and funding depends on how quickly the operator can unwind and return capital. Funds should document their expected redemption timing.

## Claiming — the math

Your payout is pro-rata to your share of the batch's redemptions:

```
your assets = your shares × batchAssetTotals / batchRedeemTotals
```

where `batchAssetTotals` is the payout snapshotted at settlement (net of exit fee).

## Cancelling

You can cancel your **current-batch** redemption before it settles with `cancelRedeem(asset)`, and your shares are returned. After settlement you can no longer cancel — you wait for funding and then claim. (An admin can cancel a stuck request in any unsettled batch, returning your shares.)

## One request per batch

As with deposits, you can hold at most one redemption request per asset per batch.

## What can block a redemption

| Reason                     | Meaning                                                   |
| -------------------------- | --------------------------------------------------------- |
| Below minimum              | Your redemption is smaller than the fund's minimum        |
| Batch cap exceeded         | This batch has hit its redemption cap                     |
| Asset not allowed / paused | The payout asset isn't offered, or redemptions are paused |
| Emergency pause            | The fund is under an emergency stop                       |

See [Risk Controls](/using-redpotion/risk-controls).
