# Asynchronous Redemptions

When you withdraw funds from NashPoint, the process occurs asynchronously. NashPoint Nodes implement [ERC-7540](https://eips.ethereum.org/EIPS/eip-7540) for redemptions, allowing user withdrawals to be processed in batched cycles. This lets Node owners include a wider variety of assets—such as Real World Assets (RWA)—that cannot always guarantee instant redemption.

Instead of immediate processing, your withdrawal follows a [two-step process](https://nashpoint.gitbook.io/nashpoint/user-documentation/asynchronous-redemptions/two-step-process). When you request a withdrawal, your shares are securely transferred to an Escrow contract, and your request enters a **Pending** state. During a specific rebalance period, NashPoint's trusted Rebalancer fulfills pending requests by moving assets from the Node’s reserve or underlying investments into the Escrow. After fulfillment, your request status updates to **Claimable**, allowing you to complete the withdrawal by retrieving your assets from Escrow.

**ERC-7540**: An extension of ERC-4626 enabling asynchronous withdrawals, supporting a broader range of assets including RWAs.

**Escrow Contract**: Securely holds user shares and assets during withdrawals, ensuring accurate tracking and asset protection.

**Request Redemption:** Use `requestRedeem()`to start the redemption process. This transfers shares the the escrow address and signals to the protocol and offchain autotmation that assets need to be withdrawn

**Request Status**: Represents the state of your redemption request—initially **Pending** (awaiting processing) and later **Claimable** (assets ready to withdraw).