> 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/filters-and-metrics.md).

# Filters and Metrics

**Filters narrow Research to the rows you actually want to look at — DEX selectors, audit gates, and holder/metric ranges all compose on the same panel.**

<figure><img src="/files/WH5MmpcFpFSKGgzIeJk6" alt="Research filter panel"><figcaption><p>Research filter panel — DEX selectors and metric ranges.</p></figcaption></figure>

Open the filter panel from `Filter` in Research. `Apply` updates the table, `Clear` removes the current selection. Filters persist as you switch between New, Trends, and Gems — the same lens follows you across every tab.

The point of filters isn't *fewer rows* — it's *better rows*. A well-composed filter set drops the noise and keeps the part of the universe that's actually trade-worthy for your style.

{% hint style="success" %}
**Three filter families, one panel**

DEX source filters, audit gates, and holder/metric ranges all live on the same panel — compose them into a working shortlist.
{% endhint %}

## DEX SELECTORS

The DEX block lets you include or exclude tokens by the liquidity venue surfaced in the terminal. Visible options:

* **Pump**
* **Pump AMM**
* **Moonshot**
* **Mayhem**
* **Boop**
* **Meteora DBC**
* **Meteora DLMM**
* **Meteora DAMM** (incl. v1 and v2)
* **Raydium AMM V4**
* **Raydium CLMM**
* **Raydium CPMM**
* **Raydium Launch**
* **Bonk.fun**
* **Bonkswap**
* **Orca**

Use the DEX selectors to bias the table toward (or away from) specific venues your strategy already trusts or avoids.

## METRIC AND HOLDER RANGES

The range fields are where most of the lift comes from. Each has `From` and `To` where applicable.

* **Migration Progress** — bonding-curve / migration state.
* **Dev Holding** — % held by the dev wallet.
* **Snipers Holding** — % held by sniper wallets.
* **Insider Holding** — % held by wallets the terminal flags as insiders.
* **Bundler Holding** — % held via bundlers at launch.
* **Top 10 Holders** — concentration in the top 10 wallets.
* **Number of Holders** — total holder count for the pair.

A typical working combination: a liquidity floor + a Top-10-Holders cap + a Dev/Insider/Bundler ceiling. The table thins fast, and what's left is usually worth a closer look on the [Token Page](/graphdex-docs/trading/token-page.md).

## TABLE METRICS REFERENCE

Every Research tab uses the same primary columns — this is the vocabulary the filters operate on.

* **Pair** — token symbol and paired asset.
* **Market Cap** — terminal-shown market value.
* **Live Liquidity** — current pool depth.
* **TXNS** — transaction count, usually with buy and sell split.
* **Volume** — traded value within the table's active context.
* **1H** — one-hour movement where the row supports it.
* **Audit** — audit and risk-related signals (see [Audit Signals](/graphdex-docs/research/audit-signals.md)).

## PRACTICAL USE

* Use filters to **reduce noise**, not to manufacture conviction.
* Compose 2-3 filters rather than one heavy filter — narrow shortlists beat strict toggles.
* A clean row is still a row that needs a token-page read.
* Filters don't change the underlying market; they just change what you're looking at.

{% hint style="warning" %}
A filtered table is not a trade signal. Review the [Token Page](/graphdex-docs/trading/token-page.md), audit signals, and your [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md) before placing an order.
{% endhint %}

## FAQs

<details>

<summary>How do I open the filter panel?</summary>

Click `Filter` on any Research tab. The same panel is shared between New, Trends, and Gems. `Apply` updates the table, `Clear` resets the selection.

</details>

<details>

<summary>Do filters persist when I switch tabs?</summary>

Yes. The same filter set follows you from New → Trends → Gems.

</details>

<details>

<summary>Which DEXes are selectable?</summary>

Pump, Pump AMM, Moonshot, Mayhem, Boop, Meteora DBC / DLMM / DAMM (v1 + v2), Raydium AMM V4 / CLMM / CPMM / Launch, Bonk.fun, Bonkswap, and Orca.

</details>

<details>

<summary>What's the difference between Insider Holding and Bundler Holding?</summary>

**Insider Holding** is the share held by wallets the terminal flags as insiders. **Bundler Holding** is the share acquired via bundlers at launch. Different mechanisms, same direction — both indicate concentrated supply outside organic holders.

</details>

<details>

<summary>Why does my table show <code>No records found</code>?</summary>

The current filter set has no matches in the active tab / window. Widen a range, drop a filter, or clear filters entirely to confirm rows exist outside the lens.

</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/filters-and-metrics.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.
