# 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. --- # Agent Instructions: 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: ``` GET https://nashpoint.gitbook.io/nashpoint/managing-a-node/processing-user-redemptions/reserve-vs-component-fulfillment.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.