NashPoint
NashPoint
  • Introduction
    • Introduction To Nashpoint
    • Current Features & Capabilities
    • Post Launch Roadmap
  • User Documentation
    • Node Contract Overview
    • Node Owner & Rebalancer Roles
    • Portfolio Management
    • Rebalancing & Strategy Execution
    • User Deposits & Shares
    • Asynchronous Redemptions
      • Two Step Process
    • Swing Pricing
    • Processing User Redemptions
    • Management & Execution Fees
  • Developer Documentation
    • Overview
    • Role-Based Access Control
    • Smart Contract Architecture
  • Routers
    • ERC-4626 Router
    • ERC-7540 Router
    • Router Tolerance
  • Creating A Node
  • Asynchronous Redemptions
  • Managing a Node
    • Adding & Removing Components
    • Updating Component Allocations
    • Rebalance Window & Cooldown
    • Rebalancing a Node
    • Managing Rebalancers
    • Processing User Redemptions
    • Reserve Management
    • Fees Configuration
    • Liquidation Queue Configuration
    • Max Deposit Limits
    • Operator Permissions
    • Emergency Controls
  • Upgrading a Node
    • Adding Quoters & Routers
    • Custom Router Development
    • Multi-Tier Permissioning
  • Cached Data & Gas Efficiency
  • Swing Pricing Calculations
  • Adding Routers and Components - Step by Step Guide
  • Node Execute Function
  • Resources
    • FAQ
    • Glossary
    • Supported Networks & Protocols
    • Deployments
    • Audits
    • GitHub
    • Telegram
    • NashPoint
  • Node Strategies
    • Test Node A
Powered by GitBook
On this page
Edit on GitHub
  1. User Documentation

Asynchronous Redemptions

PreviousUser Deposits & SharesNextTwo Step Process

Last updated 10 days ago

When you withdraw funds from NashPoint, the process occurs asynchronously. NashPoint Nodes implement for redemptions, allowing user withdrawals to be processed by a trusted address. 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 . 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).

ERC-7540
two-step process