> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/pulse/reading-signals.md).

# Reading Signals

**Each Pulse card compresses a token's recent activity into a handful of fields — learn them once, scan faster forever.**

<div align="center"><figure><img src="/files/8lUlmsCcRJFqsPsTLnjB" alt="Pulse three-lane view"><figcaption><p>Pulse cards arranged in the New / About to Migrate / Migrated lanes.</p></figcaption></figure></div>

Pulse is designed for quick scanning. Cards live in three lifecycle lanes — **New**, **About to Migrate**, **Migrated** — and each lane is a stream of tokens at a different stage. Once you can read a single card in two seconds, you can read the whole feed in a glance.

This page is the field guide for the values on every card.

{% hint style="success" %}
**Read fast, verify slow**

A Pulse card is a hypothesis, not a verdict. Open the [token page](/graphdex-docs/trading/token-page.md) before acting on what you see.
{% endhint %}

## The Core Fields

Every Pulse card carries four short metrics:

* **MC** — Market Cap shown by GraphDex.
* **V** — Volume in the card's context window.
* **F** — Fee or flow-related value shown by the terminal.
* **TX** — Transaction count.

Cards may also surface percentage values — holder concentration, dev share, bundled supply, recent buy / sell pressure. Treat these as **risk, activity, or distribution signals** that warrant follow-up, not standalone decisions.

## Lifecycle Lanes

The lane label tells you *why* a token is appearing in Pulse:

* **New tokens** — fresh on the feed. High volatility, low context, maximum uncertainty.
* **About to migrate** — flagged as approaching migration. The window before liquidity moves to its next home.
* **Migrated** — post-migration activity. New venue, new liquidity profile.

Same card, very different meaning depending on which lane it's in. Always read the lane first.

## External Links

Pulse cards can link out:

* **X search** for the token symbol — community signal.
* **Solscan** account pages for the token and contract — on-chain truth.

Use external links to verify context, but **don't treat social activity as proof of safety**. A trending ticker is a hypothesis, not an audit.

## What to Watch

When scanning a card, these comparisons surface the most useful information fastest:

* **MC vs V.** A low MC with high V suggests fresh liquidity rotation.
* **TX count.** Low TX on a hot card = thin trade history; high TX = active engagement (or bots).
* **Outliers.** A single field that's much larger or smaller than its peers is the thing to investigate.
* **Percentage signals.** Holder, dev, bundled — high values are risk markers.
* **Open in Trading.** If the card survives a 5-second read, open the token page before deciding anything.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/auDxLb3GSIVsuY5RI0FC"><strong>From Signal to Research</strong></a></td><td>The next step after a Pulse card catches your eye.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr><tr><td><a href="/pages/AVc6N5MIhAcmqbV8qsf1"><strong>From Signal to Trade</strong></a></td><td>The path from Pulse to a confirmed order.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr><tr><td><a href="/pages/ivf2Yli81NUiF5vCsxey"><strong>Audit Signals</strong></a></td><td>The risk markers Pulse percentages hint at.</td><td><a href="/files/JBN29ujDJykAmMONwLxK">/files/JBN29ujDJykAmMONwLxK</a></td></tr></tbody></table>

{% hint style="info" %}
A Pulse card is the start of a flow, not the end of one. The downstream pages — [Research](/graphdex-docs/research/research-overview.md) and [Trading](/graphdex-docs/trading/trading-overview.md) — are where signals turn into decisions.
{% endhint %}

## FAQs

<details>

<summary>What does the percentage on a Pulse card mean?</summary>

It depends on the field — holder concentration, dev share, bundled supply, or buy / sell pressure. Hover or open the card to see the exact label. Treat high values as risk markers worth investigating.

</details>

<details>

<summary>Why do the same fields look different in different lanes?</summary>

The lane is the context. A small MC in the New lane is normal; the same MC in Migrated is a different story. Always read MC, V, TX relative to the lane's expected baseline.

</details>

<details>

<summary>Is a trending ticker on X a buy signal?</summary>

No. Social activity is signal — not proof. Verify on-chain (Solscan, audit signals) before acting on a tweet.

</details>

<details>

<summary>How fresh are the Pulse numbers?</summary>

The feed updates in near real-time. Refresh the lane if you've been idle — fast-moving tokens can change category mid-session.

</details>

<details>

<summary>Which lane should I focus on first?</summary>

Depends on your style. Sniper-style traders watch \*\*New\*\* and \*\*About to Migrate\*\*. Discovery-oriented users may prefer \*\*Migrated\*\* where the noise is lower.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/pulse/reading-signals.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.