# Node Owner & Rebalancer Roles Two key roles are required for the operation of a Nashpoint Node: * Node Owner * Rebalancer The relationship is analogous to an investment mandate, where the Node Owner defines the strategy and constraints, while Rebalancers handle execution within those parameters. All rebalancer actions must comply with the Node's configuration and can only occur during designated rebalancing periods. ### Assigning Roles Any address used to deploy a Node is initialized as the Node Owner. This role can be transferred to another address after deployment if required. The Rebalancer is a whitelisted role with privilege access to interact with smart contracts external to Nashpoint on behalf of the Node. At launch this will be service provided by Nashpoint's offchain keeper system, but over time can be extended to include multiple participants. ### Node Owner The Node Owner is responsible for strategic control of the Node, including: * Setting investment strategy and component allocations * Authorizing routers and rebalancers * Configuring key parameters like reserve ratios and fees * Managing protocol integrations * Setting risk parameters and trading constraints ### Rebalancer Rebalancers are authorized operators who: * Execute the Node's investment strategy * Maintain target allocations across components * Operate within defined rebalancing windows * Manage reserve levels according to targets * Handle redemption fulfillment from components --- # 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/user-documentation/node-owner-and-rebalancer-roles.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.