> 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/advanced/leaderboard-archived/trading-competitions.md). # Trading Competitions From time to time, Helix will host trading competitions. These competitions will be based on PNL, trading volume, or both over the specified duration. For some competitions, winners will be chosen due to having the highest PNL (or volume), and for others, winners will be chosen at random where their number of entries is a function of their total PNL (or volume). In some cases, there will be multiple winners, perhaps a combination of the two. For example, a trading competition might award two grand prizes - one to the trader with the highest PNL on Helix over the specified time period, and one to a random trader that has made trades on Helix. To decide the latter winner, users may accrue entries - for example, one entry for every $10 of trading volume. At the end of the competition period, a winner would be chosen at random based on the total number of entries accrued by all participating wallets. On the Helix trading competition page, in this example all users would see their total PNL and entries accrued based on volume. These figures would be refreshed once per hour on the hour - like the overall leaderboard - and would not update in real time. At the end of the trading competition, the winner(s) will see a popup if their connected wallet has been deemed a winner. The popup will include information about verifying their identity and claiming their prize. Every trading competition will have clearly defined start and end dates, and will be governed by terms and conditions specific to that competition. --- # 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/advanced/leaderboard-archived/trading-competitions.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.