Deployer rug history — what the numbers mean
5 min read
Of all the signals Soliscope tracks, deployer history is the most predictive. Past behaviour is the best predictor of future behaviour — a wallet that has rugged six of its last ten launches is not reformed. The token name, the narrative, the community activity: none of it matters if the person pressing deploy has a 60% rug rate.
What the cluster shows
Soliscope groups the deployer wallet with every linked address — known alternate wallets funded by the same source, associated project wallets, and funder wallets — into a deployer cluster. The cluster history shows:
- Launch count — total tokens created across all wallets in the cluster
- Rug count — how many of those tokens ended with a price crash of more than 80%
- Rug rate — rug count divided by resolved launches
Grouping by cluster matters because serial ruggers rotate wallets. A fresh deployer address with zero history might look safe — but if its funding wallet has seeded thirty rugs, you're looking at the same operator under a new name.
Thresholds that matter
There's no universally safe rug rate, but Soliscope uses these as starting thresholds:
- 0 rugs, ≥3 launches — meaningful clean history. Not a guarantee, but positive signal.
- 1 rug — yellow flag. One data point, but worth noting.
- 2+ rugs — red flag. Pattern of behaviour.
- Rug rate >50% — exit signal regardless of launch count.
- New deployer (0 launches) — no history is not safe. Fresh wallets rug as often as veterans.
A new wallet with zero launches is genuinely ambiguous. Don't interpret it as clean — interpret it as unknown. The other signals matter more when history is absent.
Rug factory funders
A rug factory funder is a wallet that has sent SOL to many deployer wallets, each of which created tokens that went on to rug. The funder is the orchestrator — by using multiple fresh deployer addresses, the operator avoids having any single address accumulate a high rug rate in Soliscope or similar tools.
When Soliscope detects a rug factory funder in the cluster, it flags the launch at extreme risk regardless of the immediate deployer's history. The individual deployer wallet might have zero prior launches, but the chain of funding tells the real story.
This is the hardest signal to fake your way past: creating multiple fresh wallets is trivial, but the funding chain from a single source wallet is on-chain and permanent.
What to do with each risk tier
Exit or don't enter. Rug factory funder detected, or rug rate above 70% with multiple data points. The deployer has demonstrated a consistent pattern. No narrative changes this.
Strong scepticism warranted. Two or more rugs in history, or a rug rate above 40%. You need offsetting signals (smart money entry, very low concentration, strong curve traction) to even consider a position.
Normal caution. One prior rug, or a new deployer with unknown history. Other signals become the deciding factor.
Deployer has a clean or positive history with meaningful sample size. Still not a green light — all other signals apply.
The bigger picture
Deployer history is a strong negative filter — it eliminates bad bets efficiently. But it doesn't tell you which token will graduate. A clean deployer launching a token that gets bundled, has 90% concentration, and zero organic buyers is still a loss. Use deployer history to eliminate the worst options first, then apply the remaining signals to find something worth trading.
If you want to understand what happens after you clear the deployer check, read how to find gem tokens on Solana.
See deployer history live on every token → Open the Soliscope feed