> For the complete documentation index, see [llms.txt](https://docs.helixapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helixapp.com/lp-rewards.md). # LP Rewards LP Rewards is a liquidity-providing initiative on Helix that lets users run eligible trading bot pairs and earn rewards based on the volume those bots generate. **How it works** * Each week, a new roster of eligible markets is announced. * If your trading bot operates on an eligible market, your address earns LP Rewards pro rata to the volume your bot generates versus the total bot-generated volume on that market for the week. * Rewards are calculated and distributed per market, based on all active, eligible trading bots during the round. **Restrictions** * Wash trading or any form of manipulative activity is strictly prohibited and will be disqualified from rewards. * Any volume generated by manual trading directly on the same subaccount that a trading bot operates on will be excluded. This will result in removal of the associated volume and rewards for that round. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.helixapp.com/lp-rewards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.