> 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/glossary-and-faq.md).

# Glossary and FAQ

## Glossary

| Term                  | Meaning                                                                                                                                          |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Scout**             | A tracked wallet, chosen for how it behaves across the whole chain, not for its profit.                                                          |
| **Scout set**         | A named group of scouts, recomputed on a schedule. One set today (Scouts v8); more are coming.                                                   |
| **Crew**              | One operator behind one or more scout wallets. Several wallets of one person count as one crew.                                                  |
| **Signal**            | The first scout buy of a token. The token appears on the board at that moment.                                                                   |
| **Card**              | One token on the board.                                                                                                                          |
| **Lane**              | One of the three columns of the Feed, with its own filters, sort and sound.                                                                      |
| **Entry**             | The market cap a result is measured from. On a card: at the first scout buy. On the leaderboard with a threshold: when the threshold first held. |
| **Lane entry**        | The moment a lane's filters first held for a card. Drives Newest, the green rail and the sound.                                                  |
| **Peak**              | The highest confirmed market cap after the entry — held across two consecutive one-minute candles.                                               |
| **Multiplier (×)**    | Market cap ÷ entry. `now` uses the current cap, the headline uses the peak.                                                                      |
| **Dip before peak**   | The lowest point between the entry and the confirmed peak, as a percent of the entry.                                                            |
| **In position / out** | Whether a scout still holds at least 10% of what they bought.                                                                                    |
| **Re-entered**        | The token left the board and came back when scouts bought again.                                                                                 |
| **VSIG / TSIG**       | Volume in the signal minute; time since the signal.                                                                                              |
| **V5M / TX5M**        | Volume and swaps in the last five minutes.                                                                                                       |
| **T10 / Dev**         | Share of supply held by the top-10 holders; by the deployer.                                                                                     |

## FAQ

**I heard a sound but nothing new is at the top of the lane.** Check the lane is sorted by **Newest** and look for the card with the green left edge. If another lane made the sound, the toast at the bottom names the lane and the token. A sound always corresponds to a card that just entered *some* lane.

**Why did a card that has been on the board for hours jump to the top with a sound?** Because your lane has a Scouts or Crews threshold and the token just reached it. For that lane the card is new now. See [Sounds and new cards](/sounds-and-new-cards.md).

**My lane says 39 but the leaderboard says 30 with the same filters.** Different windows. The lane counts tokens that arrived on the board in the last 24 hours, returns included. The leaderboard counts signals whose first card fired in the last 24 hours. The difference is exactly the returned tokens.

**Why is a card dimmed?** Every scout has sold or moved out. The card stays visible until the 24-hour window closes. Turn on **Hide if all scouts left** in the lane filters to remove such cards.

**The peak on the card is lower than the ATH on the chart.** On purpose. We count a level only when it holds across two consecutive one-minute candles; a wick that lasted seconds is not a price you could have sold into.

**The multiplier is red.** The market cap now is below the entry. The colours: red below entry, white 1–2×, green 2–10×, gold 10–100×, platinum from 100×.

**I set a filter and the count went to zero.** A value that is unknown for a token never passes a filter. Tokens without a holder count fail `Holders at signal ≥`, tokens without a creation time fail `Age at signal`, and so on. Loosen the filter or remove it.

**Where are my lanes saved?** In your browser only. Another browser or device starts from the recommended presets.

**Why no sound right after opening the page?** Browsers block audio until you interact with the page. Click once on the board. The first load is also silent by design — nothing on it is new.

**Is this financial advice?** No. Scout Radar shows what tracked traders do. It does not predict prices or tell you to trade. Memecoins are extremely volatile; never risk more than you can afford to lose.


---

# 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/glossary-and-faq.md?ask=<question>&goal=<endgoal>
```

`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.
