> For the complete documentation index, see [llms.txt](https://whitepaper-old.steakhut.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper-old.steakhut.finance/developer-docs/lbstrategy.md). # LBStrategy ## Manager Functions Strategies created with a `keeper` account can configure a number of key parameters within the strategy. The `keeper` and `owner` are the key trusted entities within the Strategy. In order to be Whitelisted the Owner should be set to the SteakHut Master MultiSig Address. Whilst the keeper role may be maintained by a manager. The keeper may control and alter the underlying TraderJoe Dex V2 position. Users should always review who holds the keeper role and perform due diligence on this role holder. (SteakHut will vet these keepers before whitelisting) One should only put funds into "managed" vaults if they have some information about the manager account: the manager could be fully controlled by a DAO (token voting), or could simply be a project's multi-sig, or be locked in a smart contract that automates rebalances under a certain codified strategy, or be trusted by the user for some other reason. ***More on this is coming very soon!*** --- # 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://whitepaper-old.steakhut.finance/developer-docs/lbstrategy.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.