> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/help-center/rewards-and-points-faq.md). # 🎯 Rewards & points FAQ ### How do I earn points? Quests (first buy +5, first launch +20, first referral +25), daily quests (a trade +3, $10 volume +10), achievements, referral activity (+25 per active referred trader) and creator bonuses when your tokens graduate. ### What are points for? Three things: your **leaderboard rank**, periodic **BNB rewards** funded by the platform's 0.3% rewards fee stream, and **allocation weight** on the Airdrop page. ### Is the airdrop confirmed? When? The Airdrop page shows your points, rank and share of the total — that's your projected allocation weight. Token generation and snapshot details will be announced separately; until then, treat weight as a projection, not a promise. ### Can I lose points? No. Points are recorded in an append-only ledger, and every grant is idempotent — nothing is double-counted, nothing is taken away. ### How do streaks work? Trade at least once a day to build your streak. A 7-day streak earns the 🔥 Week Warrior badge (+20 points). --- # 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.fyuz.fun/help-center/rewards-and-points-faq.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.