# Discovery Hub

## Use predefined strategies

Coming soon.

## Add filters

Coming soon.

## Edit columns position

##

## Filter rows

<figure><img src="/files/d2r6bbkDSHUdnUYvZOky" alt=""><figcaption><p>Filter rows</p></figcaption></figure>

For each filter you can set:

* Filter name
* Operator
* Value
* Timeframe (optional)

{% tabs %}
{% tab title="Filter Name" %}
**Filter name** specifies what exact filter you want to use. For example - *pair age*, which tells you how long ago a dex pair was created.&#x20;

> If you are not sure what a specific filter means, you can hover over the *info* icon or check out the [Filters guide](/features/discovery-hub/filters-guide.md)page.
> {% endtab %}

{% tab title="Operator" %}
**Operator** specifies how the filter behaves. In our example above, we only want token pairs that have *Security Score* **equal** to Good. And we only want token pairs that were created less than 10 days ago (*Pair age* **less than or equal to** 10). And we only want tokens whose *Price changed* by **more than or equal to** 50 in the **last 1 day**.
{% endtab %}

{% tab title="Value" %}
**Value** specifies the value for the filter. In the example we could set the *Pair age* to **10** days. Or **15**, or **2,** etc.
{% endtab %}

{% tab title="Timeframe" %}
**Timeframe** is used for some filters. In our example, the *Price change* is calculated by taking the current price and the price **1 day** ago. But we could also check the *Price change* for the last **7 days** or last **30 days.**
{% endtab %}
{% endtabs %}

If you want to add more filters you can click the *Add filter ...* or if you want to delete a specific filter, you can click the *X* sign.

## Sorting

<figure><img src="/files/GWx3OIeVzVeEgwBJUh4X" alt=""><figcaption><p>Sorting</p></figcaption></figure>

Inside this section, we can set the sorting order of our returned token pairs.

We can sort by specific filters or metrics and we can set the order to be **ascending** or **descending**.

In our example, we filtered the coins and sorted them so that the ones with **most** *New Buyers* are in the first rows.

## Filter configurations

<figure><img src="/files/IvZr6Y4sDF5uBek6u519" alt=""><figcaption><p>Filter configuration</p></figcaption></figure>

As you experiment with filters you will find a few good combinations (called **filter configurations**). One configuration might be good for finding gems that are really starting to go off. Another configuration might be good to help you find potential gems you want to keep your eye on.

On the right side of filters table you can **save** or **load** these configurations. By default we provide you with a few to get you started. These will be always available, but you are free to add your own.

## Other

<figure><img src="/files/II5pjIbwSipZ0LmkMrhV" alt=""><figcaption><p>Apply Filters button</p></figcaption></figure>

Once you are satisfied with your selected filters click the **Apply filters** button.  All the filters will be applied and the token pairs that pass every filter are returned back.

In our example the token pairs need to have **Security Score** *greater or equal to* Good and **Pair Age** *lower or equal to* 10 and **Liquidity Score** *greater than or equal to* Mediocre.

***

Once you are done with filters, you can **collapse** the table and focus on the token pairs.

<figure><img src="/files/GumqzupZsrVPQ5E22zPj" alt=""><figcaption><p>Collapse button</p></figcaption></figure>

***

If you want to check out every information we have about a specific token pair, you can do so in the [Token Analyzer](/features/token-analyzer.md)(check  out next section).

### Automatic removal of inactive and scam tokens

We automatically remove tokens with low liquidity (less than 5000$) and detect rug pulls, honeypots, and tokens created by the previous scammers.

### Show duplicated tokens

Our system parses blockchain data to display metrics for each liquidity pool separately. By default, duplicated pools (if multiple pools are found for the same token based on the filter results) are hidden and only the pool with the most liquidity is shown.  By clicking on the `Show similar pools` button all pools will be displayed.

<figure><img src="/files/ZrAx7XiNdJXhU4cznIGe" alt=""><figcaption><p>Show all pairs.</p></figcaption></figure>

<details>

<summary><strong>🎓 What is the difference between a token and a pool (pair)?</strong></summary>

A token is a digital asset issued on a blockchain, often following standards like ERC-20 on Ethereum. It represents a unit of value or utility. Its creation is an independent event that defines its supply and functionality.

A liquidity pool (or pair) is a smart contract that enables decentralized trading by holding reserves of two tokens, typically the token in question and a base asset (like WETH, SOL or a stablecoin). These pools use Automated Market Maker (AMM) algorithms to facilitate swaps and provide liquidity.

To draw an analogy, consider a token as an independently manufactured product. Liquidity pools are like different retail outlets where the product is sold.

Here are the key points:

* Multiple Pairings: A single token can be paired with various other tokens across different liquidity pools. Each pool acts as an independent market with its own liquidity depth, trading volume, and fee structure.
* Sequence of Creation: The token must be deployed to the blockchain before creating any liquidity pool. In practice, liquidity pools can be launched much later than the token, allowing for evolving market opportunities.
* Trading Dependency: Without an active liquidity pool, there is no mechanism for price discovery or trade execution. A token cannot be traded if it isn’t paired in a liquidity pool.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.blokiments.com/features/discovery-hub.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
