> For the complete documentation index, see [llms.txt](https://turboflow.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://turboflow.gitbook.io/whitepaper/turboflow/rewards.md). # REWARDS TurboFlow’s incentives layer is designed to make participation more engaging, more visible, and more rewarding over time. Rather than relying on a single rewards mechanism, TurboFlow combines multiple incentive formats to support different kinds of user activity across the platform — from trading participation and streak-based rewards to public visibility and growth contributions. ### In this section #### Points A platform-wide rewards and participation system designed to reflect user activity across TurboFlow. #### Leaderboard A public performance layer that highlights standout activity and makes participation more visible across the platform. ### Why it matters TurboFlow’s incentives are designed to support more than just rewards distribution. They help create a market experience that is more active, more social, and more connected — giving retail users more reasons to participate, stay engaged, and grow alongside the ecosystem. --- # 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://turboflow.gitbook.io/whitepaper/turboflow/rewards.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.