> For the complete documentation index, see [llms.txt](https://docs.scoutradar.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scoutradar.xyz/leaderboard.md). # Leaderboard The Leaderboard is the board scored after the fact. It takes the signals of a time window, applies a preset — the same filters a lane uses — and tells you how those signals did: how many reached 2× or 5×, the typical peak, the typical dip you would have had to sit through. Use it to **test a preset before you put it on a lane**. ![The Leaderboard: model a preset on the left, the scored result on the right](/files/9QKeeWMvlslHQeDKGDqb) ## The panel **Model a preset** on the left. Set a scout set and any of the five signal filters (Scouts ≥, Crews ≥, Vol at signal ≥, Age at signal, MC at signal). The result recomputes as you type. `Start from a lane preset` copies one of your lanes' filters into the panel. `Reset` clears it. Only signal-time filters are offered here. That is deliberate: a preset must be built from what you could have known **when you would have acted**. Live values (market cap now, current holders) would let a preset peek at the outcome it is being scored on. ## The window `6H`, `12H`, `24H`. A signal belongs to the window if its **first card** fired inside it. A token that left the board and came back is counted once, by its first card — while a feed lane counts the return as a fresh arrival. That is why a lane's 24-hour count can be higher than the leaderboard's for the same filters. The header says how many signals pass: `30 of 776 signals pass · by first signal`. ## Entry: at signal, or when the preset held The key idea. There are two ways to score a preset, and the leaderboard tells you which one it is using in the title above the numbers: * **Entry: at signal.** No Scouts/Crews threshold set. Each passing signal is scored from the first scout buy: entry = market cap at the first scout buy. * **Entry: when the 10th scout bought.** A Scouts ≥ 10 (or Crews ≥ m) threshold is set. Each signal is scored from the moment that threshold first held: entry = market cap when the 10th scout bought, and the peak and the dip are measured **after** that moment. This is what you would actually have gotten trading that preset — not the multiple from the first scout, which you could not have seen. Signals that never reached the threshold, or that cannot be priced at that moment, are dropped from the second mode and the header shows how many. ## The numbers | Stat | Meaning | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Signals** | Signals that pass the preset in the window. | | **Tracked** | Of those, how many have a confirmed peak. Very young signals are not tracked yet. | | **Reached 2×** | Tracked signals whose confirmed peak was at least 2× the entry, and the share of tracked. | | **Reached 5×** | Same for 5×. | | **Median peak** | The middle confirmed peak multiple across tracked signals — half did better, half worse. | | **Dip before peak** | The typical (median) lowest point between the entry and the confirmed peak, as a percent of the entry. `-19%` means the typical trade went 19% under water before it peaked. Red when negative. | Peaks follow the same **two-candle rule** as the cards: a level counts only when it holds across two consecutive one-minute candles. ## Top 50 by max × The best signals of the window under the preset, ranked by confirmed peak multiple. | Column | Meaning | | ---------------------- | ------------------------------------------------------------------------------------- | | **Max ×** | Confirmed peak ÷ entry, coloured by the multiplier tiers. | | **Entry MC** | Market cap at the entry (at signal, or when the preset held). | | **Peak MC** | Market cap at the confirmed peak. | | **Time to max** | From the entry to the peak. | | **Entry after signal** | How long after the first scout buy the preset held (`+23m`). Only in the second mode. | | **Scouts / Crews** | Counts at the time of scoring. | | **Signal** | When the first card fired. | GMGN / AXM buttons open the token on those venues. ## How to read a result A preset that passes 30 signals with a median peak of 1.55× and 41% reaching 2× says: on a typical day, four in ten of these signals doubled from the moment you could have entered, and half of them peaked below 1.55×. Compare presets on the **same window**, and remember that a small number of signals makes every percentage noisy. --- # 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.scoutradar.xyz/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.