> For the complete documentation index, see [llms.txt](https://docs.stablepad.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stablepad.app/earn/rewards.md). # Rewards The Rewards program tracks the activity that makes STABLEPAD grow and turns it into points. Points are earned through real use of the platform, and a live leaderboard ranks every participant. ## How you earn points Trade, buying and selling coins on the platform. Launch, creating new coins. Refer, bringing new users to STABLEPAD. Hold, keeping positions in coins whose liquidity is locked and rug proof. The more you do across these, the more points you accumulate. Because every coin here launches into a locked Uniswap v3 pool, holding is a real signal, not an exploit, since the liquidity behind your position cannot be pulled. ## The points leaderboard The Rewards page shows a leaderboard of point holders, refreshed regularly, with the total points across all users and your own rank once your wallet is connected. It is the clearest view of who is most active on the platform. ## Why points matter Points are the record of early participation. Farming them now builds standing for what the program grows into. Keep trading, launching, referring, and holding to move up the board. --- # 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://docs.stablepad.app/earn/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.