Filters

News Pulse runs every potential mint through a chain of filters. Failed filters mean no alert — and for the auto-trader, no trade.

1. Pump.fun mint check

Address must end in pump. Non-pump.fun mints (Raydium-direct, launchlab, PumpSwap) have different MC math and pump.fun’s API can return junk values for them.

2. Fresh-funded dev wallet (1 hour)

If the creator’s wallet had its first ever on-chain transaction within the past hour, the mint is skipped entirely. No alert, no MC tracking.

This catches the most common rug pattern: fund a brand-new wallet with 5 SOL, deploy a token, dump, abandon wallet.

Failsafe: if the funding-age data can’t be retrieved (Helius indexing lag), the mint passes through. Better to let a marginal alert through than to silently block during an API hiccup.

3. 2-hop launder pattern (first-deploy only)

A more sophisticated obfuscation: fund an OG wallet (which has prior pump.fun deploys), have it route SOL through a fresh single-use shell wallet, which then funds the actual dev wallet.

The bot traces this chain via Helius’s funded-by endpoint. If:

• Dev was funded by a wallet with ≤2 lifetime txs (shell signature)
• That shell received and forwarded the same amount in the same slot (atomic pass-through)
• The shell’s funder has ≥1 pump.fun deploy in their history

…then we have a confirmed 2-hop launder. The mint:

• Is alerted with a 🕵️ 2-hop launder warning visible
• Is blocked from auto-buying by the trader bot

Gated to first-deploy only (deploy_count == 1). Established creators with the same trace pattern are usually legit hot/cold wallet splits, not rugs.

4. Creator blacklist

A small static list of known-rug-pattern creator addresses. These mints don’t fire News Pulse and aren’t auto-traded.

5. Mint age (auto-trader only)

The internal trader bot skips mints older than 14 days. You still get the alert; you just won’t see a position open.

6. MC threshold

The fundamental filter — must cross $20,000 USD market cap. See Tiers & Thresholds.

How they compose

Filters run in order, and any failure short-circuits the rest. So a non-pump.fun mint is rejected before we even fetch creator data; a fresh-dev mint is rejected before we run the launder check.

The order is optimized for cheap-failures-first: we want to spend zero RPC calls confirming rejections that could be made from local data.