> For the complete documentation index, see [llms.txt](https://solradar.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solradar.gitbook.io/docs/tracking-and-the-hall-of-fame.md). # Tracking & The Hall of Fame ### ATH-based tracking SolRadar tracks every called token's **all-time-high since the moment it was called**, not its current price. A token that spikes 5x and pulls back to 1.5x an hour later is still recorded as a 5x — because that peak genuinely happened, and price tracking that ignored it would be misleading in the other direction. ### 1.5x+ Hall of Fame A running board of every token that has reached 1.5x or higher since being called, refreshed every 3 hours and kept pinned in the channel. Resets at 00:00 UTC daily. ### Daily Recap At the close of every UTC day, SolRadar posts a full performance recap for the day that just ended: * **Total alerted** — every token called that day, across all tiers * **Reached 1.5x+** — how many of those hit the win threshold * **Win rate** — the percentage, calculated the same way every day * **Wins average profit** — the average multiple among the tokens that won This recap is posted and pinned regardless of whether the day was good or bad. There is no mechanism to selectively hide a weak day — the same calculation runs every time. --- # 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://solradar.gitbook.io/docs/tracking-and-the-hall-of-fame.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.