Overview: What PumpView Signals Actually Do
PumpView is a real-time Solana DEX trade scanner that ingests swaps directly from Pump.fun, PumpSwap, Raydium (CPMM, CLMM, launchpad), Meteora (including dynamic pools), and other venues without deliberate sampling delay. It scores tokens with an 8-factor Buy Score and a 4-signal wash trading detector, and lets you build custom signal strategies that fire when your conditions are met. 【turn0search0】【turn0search2】
Signals in PumpView sit on top of two core surfaces:
- Early Scanner – visualizes new launches as bubbles (size = recent volume delta, color = activity score, ring color = buy vs sell pressure). 【turn0search0】
- Hot Tokens – ranked list with Buy Score (0–12), volume, market cap, candle changes, green-streak info, and wash %. 【turn0search0】
Your strategies can watch both: for example, "alert me when an Early Scanner token later becomes a Hot Token with Buy Score ≥ X and low wash". 【turn0search2】
This article focuses on practical tips for designing PumpView signal strategies that:
- Focus on organic momentum instead of fake volume
- Respect bonding curve vs post-migration behavior
- Use risk filters (age, wash, dev/sniper behavior) to avoid obvious traps
- Fit different trading styles: scalp, intraday momentum, and swing
1. Start With One Clear Playbook Per Strategy
PumpView lets you create multiple custom strategies, each with its own filters and alerts. 【turn0search0】 A common mistake is to cram every idea into a single "catch everything" setup.
Instead, define one job per strategy:
- Scalp / first-move strategy
- Watches Early Scanner only
- Tight age window (seconds/minutes from first trade)
- Very strict wash and sniper/dev filters
-
Goal: catch the first clean push and exit quickly
-
Intraday momentum strategy
- Watches Hot Tokens
- Requires Buy Score above a threshold and recent green candles
- Allows some wash but caps it
-
Goal: join established trend with defined risk
-
Post-migration continuation strategy
- Watches tokens that have already left the bonding curve (100% bonding curve / migrated)
- Filters for age (e.g., migrated within last X minutes) and rising wallets/volume
- Goal: catch Raydium/Meteora continuation moves after Pump.fun graduation
Keeping strategies single-purpose makes it easier to:
- Understand why a signal fired
- Adjust thresholds without breaking everything
- Compare performance between ideas over time (PumpView tracks signal performance with ATH% and live PnL-style metrics for 24h after fire). 【turn0search0】
2. Use Buy Score as a Gate, Not a Prediction
PumpView’s Buy Score is built from multiple real-time factors: buy dominance, market cap vs volume, multi-DEX presence, price trend, TPS context, and wash impact. 【turn0search0】 In Hot Tokens, tokens with Buy Score ≥ 7 and low wash are described as the strongest leads. 【turn0search0】
Practical tips:
-
Don’t chase every score bump.
Use Buy Score as a minimum gate (e.g.,score >= 7) rather than buying the second it flips from 5 to 6. -
Combine score with trend and wallets.
A high score with flat price and flat holder count is weaker than a slightly lower score with: - Rising 1m/5m candles
-
Increasing unique wallets / holders
-
Avoid overfitting to 12/12.
Designing a strategy that only fires on 11–12 scores will miss many real moves. It can be useful for a "moonshot" strategy, but for day-to-day trading, a band like 7–10 with strict risk filters is more realistic.
Example filter core for a Hot Tokens strategy:
- Buy Score ≥ 7
- 1m or 5m candle change > 0
- Wallet count increasing over last few minutes
- Wash % below your tolerance (see next section)
3. Treat Wash Score as a Hard Risk Filter
Wash trading on Solana is a known problem: tools like VoluDex explicitly sell simulated volume to help tokens appear active on analytics sites. 【turn0search24】 Academic work on Solana memecoins also shows that early trading patterns can be used to detect fraudulent behavior and rugs. 【turn0academia25】
PumpView’s wash trading detector uses four signals to estimate how much of the volume is likely fake, exposing a wash % for each token. 【turn0search0】 The exact formula is proprietary, but you can still use it systematically.
Practical tips:
- Decide your wash ceiling per strategy.
- For scalps on fresh launches, you might require very low wash (e.g., only signals under a strict %).
-
For intraday momentum, you can accept some wash (market-making, bot activity) but still cap it.
-
Combine wash with volume/MC sanity.
External scanners like Solana Token Scanner flag extreme volume-to-liquidity ratios (e.g., >150x) as likely wash. 【turn0search8】 In PumpView, if you see: - High volume,
- High wash %,
-
But flat or declining holder count,
treat it as a red flag. -
Never treat low wash as safety.
A clean contract and low wash do not mean a token is safe or a good buy. Other tools (RugCheck, PumpFunBot, etc.) make the same point: a green or clean score is not a guarantee. 【turn0search8】【turn0reddit20】 Use wash as one filter, not the only one.
Concrete strategy rule example:
"Fire only if Buy Score ≥ 7, wash % below my ceiling, and wallets/volume are both rising in the last N minutes."
4. Exploit New On-Chain & Momentum Filters
PumpView recently added more granular filters for strategies, including:
- Token age
- Bonding curve % (100 = migrated)
- Dev & sniper sold %
- Callers in 60s / 5m
- 30s change in Score, market cap, and wallets
- With the rule that unknown data never passes a filter — if PumpView doesn’t have a value, it won’t silently let a token through. 【turn0search5】
How to use these effectively:
a) Token Age & Bonding Curve %
Bonding curves on Pump.fun and similar launchpads behave very differently from post-migration Raydium/Meteora pools. Many scanners now separate early-stage bonding-curve tokens from later stages because the risk and behavior profiles are different. 【turn0search9】【turn0search10】
In PumpView strategies, you can:
- Build pre-migration plays:
- Token age in seconds/minutes
- Bonding curve % < 100
-
Strong buy dominance and rising wallets
-
Build post-migration plays:
- Bonding curve % = 100 (migrated)
- Age since migration within your window
- Volume and wallets accelerating on Raydium/Meteora
This separation helps avoid mixing bonding-curve roulette with DEX continuation in one strategy.
b) Dev & Sniper Sold %
Research on Solana memecoins has surfaced coordinated sniper cohorts that repeatedly buy early across launches. 【turn0academia26】 Many tools now track sniper and dev behavior (e.g., early exits, heavy selling) as risk signals.
PumpView exposes dev & sniper sold % as filters. 【turn0search5】 Practical usage:
- For early strategies, require dev and sniper sold % to be below your threshold. If insiders are already exiting hard in the first minutes, you probably don’t want that alert.
- For later-stage momentum, you might relax this a bit but still cap it to avoid obvious exit-liquidity setups.
c) Short-Term Deltas (30s Change in Score, MC, Wallets)
Short-term changes help you catch inflection points:
- 30s change in Buy Score
- 30s change in market cap
- 30s change in wallets
Instead of only looking at absolute values, build rules like:
- "Score ≥ 7 AND 30s Score change > 0" — rising quality, not just high.
- "Wallets up by at least N in the last 30s" — new buyers are actually arriving.
- "MC up in 30s but wallets flat" — more likely a few large buyers or spoof-y behavior; treat with caution.
Because unknown data never passes a filter, you won’t accidentally let through tokens where these deltas can’t be computed. 【turn0search5】
5. Connect Signals to a Real Execution Plan
PumpView strategies can be wired to alerts and, via integrations, to autotrade flows (e.g., DeFi Solana Bot for automatic execution when a signal fires). 【turn0search0】 That makes it even more important that your strategy logic matches how you actually trade.
Practical alignment tips:
- Define entry behavior explicitly.
When a signal fires, will you: - Market buy a fixed SOL amount?
- Ladder entries?
-
Wait for a retest on a lower timeframe?
-
Pre-define exits.
Other Solana signal bots size exits based on signal strength (e.g., tighter stops for mid-tier signals, looser for top-tier). 【turn0reddit13】 You can mirror this idea manually: - For borderline signals (just over your threshold), use tighter stops and closer take-profit.
-
For high-conviction signals (much higher than your minimum), allow more room but still define invalidation.
-
Avoid over-triggering.
If your strategy is firing constantly, you’ll either: - Ignore most alerts, or
- Overtrade.
Tighten filters (age, wash, dev/sniper, deltas) until the alert frequency matches what you can realistically handle.
6. Use Signals as a First Screen, Not a Final Decision
Across the Solana tooling ecosystem, a consistent design pattern has emerged:
- Scanner / signal first,
- Manual or semi-manual decision second.
Examples:
- PumpFunBot offers a free read-only scanner with authorities, route/curve state, and a risk score, explicitly saying a clean scan is not a safety guarantee. 【turn0reddit17】【turn0reddit21】
- PumpZone and similar tools emphasize that a green badge means "passed checks", not "good buy". 【turn0reddit22】【turn0reddit23】
You should treat PumpView signals the same way:
- Signal fires – token meets your quantitative filters.
- You quickly check:
- Contract basics and authorities (RugCheck, PumpFunBot scanner, Solscan).
- Liquidity and LP ownership/locks.
- Holder distribution (are there a few huge wallets?).
- Socials / narrative if you care about that.
- Only then decide whether to enter, size, and where to place stops.
PumpView helps by:
- Surfacing wallet histories and PnL for callers and wallets you follow, so you can see if a "smart" wallet is actually profitable. 【turn0search0】
- Tracking signal performance (ATH% and live drawdown) for 24h after fire, so you can learn which setups work for you. 【turn0search0】
7. Iterate With Real Results, Not Vibes
Because PumpView logs signals and their subsequent performance, you can treat each strategy as an experiment rather than a fixed belief. 【turn0search0】
A simple iteration loop:
- Start small.
- One scalp strategy, one intraday strategy.
-
Conservative size or paper-trading.
-
Collect a meaningful sample.
- Don’t judge a strategy on 3 signals.
-
Aim for dozens of fires before making big changes.
-
Review winners vs losers.
For each strategy, look at: - Average ATH% after signal.
- Typical drawdown after entry.
-
Common traits of losers (e.g., wash just under your ceiling, dev sold % spiking, wallets flat).
-
Tighten or relax filters based on data.
- If most losers had higher wash, lower your wash ceiling.
- If you’re missing many strong runs because of overly strict age, relax it slightly.
-
If winners tend to have fast wallet growth, increase your minimum wallet delta.
-
Version your strategies.
- Keep a note: "Strategy A v1: wash < X, age < Y, etc."
- When you change it, call it v2 and track separately.
Over time, this turns PumpView from a noisy alert feed into a personal, data-backed playbook.
Conclusion: Build Narrow, Testable Strategies
PumpView’s signal system is designed around real on-chain data: multi-DEX swaps, Buy Score, wash detection, bonding curve progress, dev/sniper behavior, and short-term deltas in score, market cap, and wallets. 【turn0search0】【turn0search5】 Used well, it can drastically cut the time you spend manually refreshing launch feeds and charts.
To get real value from it:
- Give each strategy one clear job (scalp, intraday, post-migration).
- Use Buy Score as a gate, not a guarantee.
- Treat wash % and dev/sniper sold % as hard risk filters.
- Separate bonding-curve plays from DEX continuation plays.
- Align signals with a concrete execution and risk plan.
- Always treat signals as a first screen, followed by quick manual checks.
- Iterate based on logged signal performance, not gut feel.
If you approach PumpView like a quant lab instead of a hype feed, your strategies will become more consistent, and your alerts will start to feel less like noise and more like actionable, testable edges in the Solana memecoin chaos.