> 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/user-documentation/management-and-execution-fees.md). # Management & Execution Fees NashPoint charges two fees: an **annual management fee** and an **execution fee**. The annual management fee, set by each Node Owner, is charged yearly based on the total assets held in a Node and is split between the Node Owner and the NashPoint protocol according to a protocol-defined percentage. The execution fee is a separate fee collected entirely by the protocol whenever assets are invested into underlying components. Execution fees do not apply to withdrawals made to fulfill user redemptions. Both types of fees are deducted from the Node’s reserve assets. Node Owners can control execution fee frequency by adjusting the rebalance parameters of their Nodes. In future execution fees will be shared with Solvers that rebalance the protcol. **Annual Management Fee:** A yearly fee charged based on the Node's total asset value, split between the Node Owner and NashPoint protocol. **Execution Fee:** A fee charged by NashPoint protocol when user funds are invested into underlying strategies. This fee applies during asset allocation but not during withdrawals. **Solver:** An off-chain or on-chain agent that autonomously executes investment strategies or rebalancing actions defined by Node Owners. Solvers compete to efficiently allocate assets, optimizing returns and liquidity management across NashPoint Nodes. --- # 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/user-documentation/management-and-execution-fees.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.