> For the complete documentation index, see [llms.txt](https://docs.digitaldon.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitaldon.net/how-the-analysis-works/profiles.md).

# Token profiles

A five-day-old token and a two-year-old token are not the same kind of object, and analysing them the same way produces confident nonsense on at least one of them.

So the analysis picks a profile from the token's age, and the profile decides what matters.

| Profile            | Age            | What it leans on             |
| ------------------ | -------------- | ---------------------------- |
| 🆕 **Fresh**       | under 14 days  | Volume and buy/sell pressure |
| 🌱 **Early**       | 14–60 days     | Trend plus momentum          |
| 🏛 **Established** | 60 days and up | The full indicator suite     |

Unknown age is treated as Established — the conservative default, since it avoids applying memecoin assumptions to something that might be a blue chip.

## Why the emphasis differs

On a **Fresh** token, a mean-reversion indicator is measuring the mean of about four days of trading, most of which was a launch. That mean has no authority. What *does* have authority is whether volume is still growing and whether buys outnumber sells — is anyone actually still here.

On an **Established** token, the reverse. There's real history, so the oscillators mean something, the moving-average stack means something, and the trend has been tested. Volume trend becomes noise on a mature chart and is weighted accordingly.

**Early** sits between them, because a three-week-old token is neither.

The weighting is also **asymmetric**: on a young token, growing volume is genuine information while a quiet hour is mostly noise, so the same signal is allowed to help the score more than it's allowed to hurt it. That asymmetry runs through the whole table, in both directions depending on the signal.

## Stripping launch candles

The other thing the profile controls is how much of the launch gets thrown away before anything is measured — a longer window for the youngest tokens, a shorter one for Early, nothing at all for Established.

Why: launch price action is a vertical line into a peak nobody will see again, followed by a cliff. Left in, it becomes the "resistance" every level is measured against, it drags every moving average, and it makes "−96% from ATH" look like a discount when it's just the shape of a launch.

**Safety valve:** if trimming would leave too little chart to analyse, the untrimmed frame is used instead. Better a noisy chart than no chart.

## The launch-spike flag

Trimming fixes the *analysis*, but the all-time high is still an interesting fact — and a misleading one when it was set in the first hour.

So the trimmed chart's high is compared against the untrimmed one. If the real peak lives entirely inside the launch window, the ATH was an artifact, and the card flags it.

Practical read: when that flag is up, ignore every "% below ATH" number on the card. It's measuring against a candle that existed for ten minutes and never recurred.

{% hint style="info" %}
The chart image has its own version of this discipline. It labels the highest bar on screen with the window it came from (`3W HIGH`) and only calls something an ATH when a real lifetime high was established separately. If that isn't available, it says nothing about the ATH at all.
{% endhint %}


---

# 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.digitaldon.net/how-the-analysis-works/profiles.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.