> 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/points.md). # Points By trading on Helix, users can earn points based on a proprietary calculation of trading volume, products traded, and platform loyalty. This program rewards users who contribute to Helix’s ongoing success. The points program was officially announced on December 11, 2024. Historical protocol usage was also taken into account, enabling loyal users to earn additional bonus points. Season 1 ended at 0900 UTC on July 16, 2025. Active, loyal users may continue to earn bonus points in the future. Users are ranked by their accrued points and sorted into categories such as White Belt and Orange Belt. Every trader on Helix begins as a White Belt and can level up with regular use of the protocol. These categories currently follow a bell curve model, where the most elite active users achieve the highest ranks. Additional ranking categories may be introduced in the future. The criteria for earning points is updated regularly to ensure that genuine engagement with Helix is rewarded the most. Points are tracked daily, weekly, and in total on the points dashboard. Helix reserves the right to modify point distributions at its sole discretion, without advance notice. --- # 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/points.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.