> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/rake-ecosystem/leaderboard.md). # Leaderboard The real-time RAKE leaderboard and the source-defined metrics it tracks. ## Launched-token visibility Every token launched through RAKE appears on the Leaderboard. The board makes post-launch activity visible beyond a token name and price. It records documented activity and fee-related metrics. It does not establish whether a token is safe, legitimate, or likely to succeed. ### Recorded metrics | Metric | What it represents | | ------------ | -------------------------------------- | | Trade volume | Trading activity for the token | | Holder count | Number of holders | | Total fees | Fees accumulated | | $RAKE burned | $RAKE burned from the token's fee flow | | $PONS burned | $PONS burned from the token's fee flow | | Last harvest | Most recent harvest timestamp | | Status | Alive or dead | ### Position in the lifecycle The Leaderboard is RAKE's visibility layer. It follows a token from launch through the documented fee flow. ``` Launch ↓ Token appears on Leaderboard ↓ Trading activity accumulates ↓ Fees accumulate ↓ Harvest occurs ↓ Burn metrics update ↓ Leaderboard provides visibility ``` The board exposes the documented signals around token activity, accumulated fees, harvest timing, and RAKE or PONS burns. It does not add to, or alter, the launch and fee-routing mechanics. --- # 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.rakelaunch.xyz/rake/rake-ecosystem/leaderboard.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.