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 vs Component Fulfillment
    • 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. Managing a Node
  2. Processing User Redemptions

Reserve vs Component Fulfillment

When a redemption request is fulfilled, the system supports two separate fulfillment paths, each impacting the reserve and component balances differently:

  1. Node.fulfillRedeemFromReserve Fulfills the redemption directly from available cash reserves without liquidating components. This approach may result in current cash reserves dropping below the target reserve level.

  2. Router.fulfillRedeemRequest Fulfills the redemption by liquidating component holdings to maintain ideal cash reserve levels. However, this reduces the component balance, potentially leaving it below its target allocation.

Important: Developers and users should understand these distinct paths clearly, as each has implications for cash reserve management, component allocations, and reinvestment capabilities.

PreviousProcessing User RedemptionsNextReserve Management

Last updated 19 days ago