> For the complete documentation index, see [llms.txt](https://docs.rip.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rip.xyz/hypurr-vault/deposit-redemption.md).

# Deposits and redemptions

Both are requests, not instant swaps. Your assets or shares move to the vault when you submit. Settlement follows a NAV report and queue processing.

## Deposit HYPE or WHYPE

1. Open the vault's **Deposit** tab and select HYPE or WHYPE.
2. Enter an amount and check the current fee, minimum, and estimated shares.
3. Approve WHYPE spending if needed. Native HYPE deposits wrap automatically.
4. Confirm the deposit request. The vault holds the assets and assigns the request to the current epoch.
5. After the next report finalizes that epoch, the keeper processes eligible deposits in first in, first out order and mints rHYPURR to the receiver.

You do not need to claim shares after processing. Your final share amount uses the epoch NAV and the deposit fee recorded with the request.

```
Net deposit = deposit amount - deposit fee
Shares received = net deposit / epoch NAV per share
```

## Redeem rHYPURR for WHYPE

1. Choose **Withdraw** and enter the number of shares.
2. Review the fee and estimated payout, then confirm the request.
3. The vault holds your shares and tags the request with the current epoch.
4. After the next report finalizes that epoch, the keeper processes eligible redemptions in queue order. It burns redeemed shares and sends WHYPE to the receiver.

```
Gross payout = shares redeemed × epoch NAV per share
Net payout = gross payout - redemption fee
```

The redemption fee rate is locked when you submit the request. Calculations use integer token units, so rounding can affect the result. To receive native HYPE after redemption, unwrap WHYPE through **Tools > Wrap HYPE**.

## How long will it take?

Check the next scheduled NAV update on the vault page. A report makes requests eligible for processing; it does not guarantee they finish at that time. Signing, confirmations, retries, queue length, and available WHYPE can extend the wait.

The keeper processes deposits before redemptions. Each queue follows first in, first out order and uses the NAV saved for each request's epoch. Later reports do not reprice a finalized request.

## What if there is not enough WHYPE?

The keeper can pay part of the redemption at the head of the queue if the payout meets the contract's minimum partial amount. The remaining shares stay pending at the same epoch NAV. Later redemptions wait until that request completes.

New deposits or manager transfers can add WHYPE. Excess unreserved liquidity can be swept to the manager under the vault's configured rules. NFT sales and manager funding take time, so a redemption may span several processing cycles.

## Can I cancel?

Only the requester can cancel, while the request is pending and its epoch is still current. The next NAV report finalizes that epoch and closes the cancellation window. Cancellation also requires the vault to be unpaused.

* A cancelled deposit returns WHYPE, even if you originally deposited native HYPE. The deposit fee goes to the treasury.
* A cancelled redemption returns shares minus a fee in shares, using the rate locked at submission.

Cancellation does not refund the request fee or network gas. After finalization, the request remains in the queue; it cannot be cancelled just because it has not finished processing.

## Fees

The vault page shows current deposit and redemption rates. Review them before signing. The portfolio also bears a <code class="expression">space.vars.rhypurr\_trading\_fee\_bps / 100 + "%"</code> protocol fee on manager NFT purchases and sales, and a 10% protocol fee on airdrops received by the vault. These portfolio fees affect NAV rather than appearing as an extra deduction from each deposit.

[Open Hypurr Vault](https://www.rip.xyz/rhypurr) or [compare vault redemption with ProjectX trading](https://docs.rip.xyz/hypurr-vault/trading.md).
