> 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/research/audit-signals.md).

# Audit Signals

**Audit signals are inline risk markers on every Research row — percentages and indicators that flag what needs a closer look before a trade.**

<figure><img src="/files/2qQAnDasAJgkQU3dGTM6" alt="Audit signals inline on a Research row"><figcaption><p>Audit and holder-related signals surfaced inside the Research row.</p></figcaption></figure>

Audit signals live inside the Audit column on every Research tab. Some rows show a single percentage; others surface holder-related indicators alongside it. The same vocabulary feeds the audit and holder filters on the filter panel, so what you see on a row is what you filter on.

Treat audit signals as *triggers for review*, not as approval labels. A clean-looking row can still hide risk one click away; a noisy-looking row may make sense once you read the token page. The signals are inputs to your decision, not the decision itself.

{% hint style="success" %}
**Inline markers, not approval labels**

Read audit signals as "open the token page and look closer" — not as "safe to trade".
{% endhint %}

## WHAT AUDIT SIGNALS FLAG

Use audit signals to spot the kinds of risk that don't show up in price and volume alone.

* **Holder concentration** that doesn't match a real distribution.
* **Insider / bundled supply** indicators above your floor.
* **Migration progress** that's unusual for the row's age.
* **Activity that doesn't match liquidity or volume** — TXNS without depth.
* **Contract-level risk markers** surfaced by the terminal.

## RELATED FILTER FIELDS

The filter panel exposes the same risk vocabulary as ranges — combine signals on the row with floors and caps on the filter for a much sharper shortlist.

* **Audit** — overall audit gate.
* **Migration Progress** — bonding-curve / migration state.
* **Dev Holding** — share held by the dev wallet.
* **Snipers Holding** — share held by sniper wallets.
* **Insider Holding** — share held by flagged insiders.
* **Bundler Holding** — share acquired via bundlers at launch.
* **Top 10 Holders** — concentration in the top 10 wallets.
* **Number of Holders** — total holder count for the pair.

## HOW TO READ A ROW

A signal in isolation is barely useful — read it in context against the rest of the columns.

* Compare the audit percentage with **Live Liquidity** and **Volume**.
* Read **TXNS** with the buy / sell split — one-sided activity is its own flag.
* Check holder-related signals: concentration, insider %, bundler %, top-10 %.
* Open the [Token Page](/graphdex-docs/trading/token-page.md) for the deeper context.
* Never approve a wallet prompt you don't fully understand.

## WHAT AUDIT SIGNALS DON'T DO

* They don't guarantee a token is safe.
* They don't approve a row for trading.
* They don't replace your own review.
* They don't override your Trading Settings — slippage, priority, bribe still apply.

{% hint style="warning" %}
GraphDex surfaces risk signals. It cannot guarantee that a token is safe, liquid, or profitable. You remain responsible for reviewing each token and deciding whether to trade.
{% endhint %}

## FAQs

<details>

<summary>Where do audit signals appear?</summary>

In the **Audit** column on every Research tab — and as a row of holder-related percentages inline on rows that surface them. The same vocabulary feeds the filter panel's audit and holder filters.

</details>

<details>

<summary>What does the audit percentage actually mean?</summary>

It's a risk and activity indicator surfaced by the terminal — read it relative to the row's Liquidity, Volume, TXNS, and holder split. The UI doesn't expose the full formula; treat it as a glance signal that earns deeper review.

</details>

<details>

<summary>Are audit signals an approval label?</summary>

No. They flag what needs a closer look — they don't say "safe to trade". Always confirm on the [Token Page](/graphdex-docs/trading/token-page.md) and review [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md) before sending an order.

</details>

<details>

<summary>Can I filter by audit signals?</summary>

Yes. The filter panel exposes **Audit** as a gate, plus ranges for **Migration Progress, Dev Holding, Snipers Holding, Insider Holding, Bundler Holding, Top 10 Holders**, and **Number of Holders**. See [Filters and Metrics](/graphdex-docs/research/filters-and-metrics.md).

</details>

<details>

<summary>A row looks clean — can I trade without opening the token page?</summary>

Not recommended. Audit signals are inputs to a decision, not the decision. The token page carries the chart, holders, transactions, and order panel — that's where a trade actually starts.

</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/research/audit-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.
