# Set Up Smart Signal Filters

### **Minimum Criteria – Filtering for Trust**

These act as **risk tolerance filters**. The higher your minimums, the stronger the fundamentals of the token you're targeting (but also potentially fewer signals).

#### ✅ **Minimum Market Cap**

* **Formula**: Token Price × Circulating Supply
* **Why it matters**: Market cap is a key indicator of size and perceived value. Larger cap memecoins are typically more stable, while smaller caps are more volatile but offer higher upside.

| Category            | Range (USD)  | Risk                    |
| ------------------- | ------------ | ----------------------- |
| **Low Cap memes**   | $100K – $25M | High risk / High reward |
| **Mid Cap memes**   | $25M – $100M | Moderate risk           |
| **Large Cap memes** | $100M+       | Lower risk, more stable |

***

#### 💧 **Minimum Liquidity**

* **Why it matters**: Liquidity reflects how much capital is in the pool. Low liquidity = higher slippage & higher rug risk. High liquidity = harder to manipulate price.

| Range        | Risk                             |
| ------------ | -------------------------------- |
| $50K – $250K | Risky, possible rugs             |
| $250K – $1M  | Decent entry zone                |
| $1M+         | Safer, more established projects |

***

#### 👥 **Minimum Holders**

* **Why it matters**: More holders mean wider distribution and less risk of whales dumping. It’s a proxy for decentralization and early community traction.

| Range   | Interpretation                            |
| ------- | ----------------------------------------- |
| 100–500 | Very early stage                          |
| 1K–3K   | Gaining traction                          |
| 10K+    | Broad-based participation, more stability |

***

#### 📈 **Minimum Volume**

* **Why it matters**: High daily volume = active trading = more price movement. Low volume = illiquid assets, risk of being stuck in a position.

***

### **Change Over Time – Spotting Breakouts**

These settings allow you to trigger signals **based on growth**, not just static thresholds — ideal for catching **momentum plays**.

#### 📊 **Market Cap Change**

* **What it shows**: % increase in value over time — a direct reflection of price movement.
* **Pro tip**:
  * Use **1h or less** for small caps (quick pumps/dumps)
  * Use **24h** for larger caps (sustained growth)

***

#### 💧 **Liquidity Change**

* **What it shows**: % increase in liquidity over a time frame.
* **Why it matters**: A spike in liquidity means new capital entering, often from LPs who believe in the project.

Use Case

***

+50–100% in 5–30 mins = likely whale or team adding liquidity

***

Set alerts to catch stealth launches or pre-pump setups

***

#### 👥 **Holders Change**

* **What it shows**: Increase in number of unique holders.
* **Why it matters**: Signals growing interest, community traction, and potential virality.

| Timeframe            | Use                                        |
| -------------------- | ------------------------------------------ |
| 1 Day                | Best for measuring organic growth          |
| 100+ new holders/day | Sign of viral momentum or strong marketing |

***

#### 📉 **Volume Change**

* **What it shows**: % increase in trading volume.
* **Why it matters**: One of the **strongest predictors** of incoming volatility — high volume often precedes price action.

Strategy Tip: Use with short timeframes (5–30 min) to catch breakouts early

***

### **Putting It All Together**

When setting up your **Signal Filters**, consider combining:

* **Minimum Liquidity** + **Liquidity Change** = Filters for "serious" tokens gaining traction
* **Minimum Holders** + **Holders Change** = Early signs of virality
* **Market Cap Change** + **Volume Change** = Momentum filters to catch spikes

***

### **Final Tips**

* **Start broad**, then narrow down as you test and learn.
* Use **shorter timeframes (5m–1h)** for small caps and **longer timeframes (1d)** for bigger caps.
* Combine **static thresholds** (minimums) with **velocity indicators** (change over time) for higher-quality signals.


---

# 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://snapx-2.gitbook.io/snapx-docs/guides/set-up-smart-signal-filters.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.