Why this matters more than most people check
A rug pull isn't usually a one-time event for the person doing it. Serial ruggers launch, extract value, abandon, and repeat, often dozens of times, because each individual launch costs very little and a single successful rug can pay for a lot of failed ones. The same wallet address shows up across all of them, which means their history is fully visible on-chain, if you know to look.
What a deployer reputation check actually measures
| Field | What it tells you |
|---|---|
| launched | Total number of tokens this address has deployed |
| alive | How many of those still have real, active liquidity today |
| rugged | How many were abandoned or had liquidity pulled after launch |
| risk | A summary rating: none, low, med, or high, based on the pattern above |
A wallet that's launched 40 tokens with 38 rugged is a completely different signal than a wallet on its first launch. Neither is proof of anything about the specific token you're looking at right now, but the first is a pattern worth taking seriously.
How to check it yourself
Reading a clean deployer report correctly
No history and no red flags is not the same as a verified-safe track record, it just means there isn't enough history yet to judge. A brand-new deployer wallet on its first launch could be a genuine builder or could be a rugger who simply hasn't left a trail yet, since a fresh wallet has no trail by definition. Weight this signal alongside the others (liquidity lock, sellability), not as a standalone verdict.
Frequently asked
Can a deployer wallet change its behavior over time?
Yes, and reputation scoring reflects history, not a permanent character judgment. A wallet with a rough early history that's launched several clean, still-active tokens more recently shows that shift in its own numbers (alive count, recent launches). Read the full pattern, not just a single risk label.
Does a high launched count always mean higher risk?
No, some legitimate serial creators (agencies, prolific meme launchers) genuinely launch a lot of tokens. What matters is the ratio: launched vs. rugged vs. still-alive. A high launch count with a high alive rate and low rugged rate is actually a positive signal, more history to judge, and it's held up.
Is the deployer always the same as who currently controls the token?
Not necessarily. Ownership or admin roles can sometimes be transferred after launch. Deployer history tells you who created the contract and its initial conditions, worth knowing, but check separately whether any ongoing owner powers (tax changes, blacklists) still exist and who holds them now.
Where does ScanHood's deployer reputation data actually come from?
It's built by tracking every token each address on Robinhood Chain has deployed and following what happened to each one's liquidity afterward, not self-reported or claimed, derived directly from on-chain activity.