> For the complete documentation index, see [llms.txt](https://nashpoint.gitbook.io/nashpoint/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nashpoint.gitbook.io/nashpoint/asynchronous-redemptions.md).

# Asynchronous Redemptions

### Overview

The protocol implements an asynchronous redemption system where withdrawal requests are processed in two steps:

1. User requests redemption (shares moved to Escrow)
2. Rebalancer fulfills redemption (assets moved to Escrow)

### Request Structure

```solidity
struct Request {
    uint256 pendingRedeemRequest;  // Shares pending redemption
    uint256 claimableRedeemRequest; // Shares ready to be claimed
    uint256 claimableAssets;       // Assets ready to be claimed
}
```

### Redemption Lifecycle

1. **Request Phase**

```solidity
function requestRedeem(uint256 shares, address controller, address owner)
```

* Shares are transferred to Escrow
* `pendingRedeemRequest` is increased
* `sharesExiting` is increased to track pending withdrawals

2. **Fulfillment Phase**

```solidity
function fulfillRedeemFromReserve(address controller)
function fulfillRedeemBatch(address[] memory controllers)
```

* Rebalancer processes request during rebalance window
* Can fulfill from reserve or liquidate components
* Updates request state via `finalizeRedemption`

3. **Claim Phase**

```solidity
function withdraw(uint256 assets, address receiver, address controller)
function redeem(uint256 shares, address receiver, address controller)
```

* User claims available assets from Escrow
* Decrements `claimableAssets` and `claimableRedeemRequest`
* Burns shares from Escrow

### Router Integration

Routers can process redemptions from their respective components using:

```solidity
function fulfillRedeemRequest(address node, address controller, address component)
```

* Processes component withdrawal
* Updates request state via Node's `finalizeRedemption`

For more details on the redemption system, see the full protocol documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nashpoint.gitbook.io/nashpoint/asynchronous-redemptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.