> 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/developer-documentation/overview.md). # Overview ### What is NashPoint NashPoint is a DeFi protocol designed for asset managers (Owners) to permissionlessly create and manage custom investment strategies onchain through Nodes. Each Node custodies user deposits and the underlying assets, following rules defined by the Node Owner. Owners specify parameters including the selection of underlying assets (components), reserve ratio, management fees, rebalancing frequency, and tracking error. Nodes can be offered as investment products to customers, who deposit assets through a standard ERC-4626 interface and withdraw asynchronously via an ERC-7540 interface. All user funds and investments are securely held within the Node contract. ### Balance Sheet Management NashPoint custodies user funds within secure smart contracts, supplemented by offchain balance sheet management services. These offchain services execute Node investment strategies defined by Owners, allocating user deposits into underlying assets based on specified target ratios and rebalance schedules. Withdrawals are processed similarly, either from the Node’s reserve or by redeeming from underlying investment assets, ensuring efficient liquidity management. ### User Funds Redemptions Each Node is linked to a unique Escrow contract created simultaneously with the Node. Users withdrawing funds submit a redemption request, transferring their shares to the Escrow contract, and the request status is marked as Pending. During defined rebalance windows, the protocol's Rebalancer fulfills these requests from either the Node's reserve or underlying investments. Once fulfilled, shares are burned, assets are transferred to the Escrow, and the request status updates from Pending to Claimable, allowing users to retrieve their assets. Shares and asset movements remain synchronized to ensure accurate accounting. --- # 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/developer-documentation/overview.md?ask=&goal= ``` `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.