How to investigate a Pump.fun token before and after migration
Check the exact mint, curve state, pool transition and wallet evidence without confusing migration, transfers or price collapse with a proven rug.
RugSignal editorial notes · Published · Updated · Source-based, not investment advice.
Start with identity and the trading venue
Investigate the exact Solana mint, not a name, ticker or a token's claim to be a Pump.fun launch. Compare the mint against an explorer and the venue you intend to use. A provider-reported pool creation time is not the mint's launch time. RugSignal can examine a supported Pump curve account; a missing or unsupported response is unknown, not proof that a token never used a curve.
Migration changes what evidence you need
A completed bonding curve and migration to another pool are lifecycle events, not automatic proof of fraud. Check the program, destination pool, transaction timing and which liquidity claim exists afterward. A snapshot of the old curve cannot establish control of a new pool. Conversely, disappearing liquidity without a supported migration explanation deserves investigation; absence of a provider row alone does not prove a malicious withdrawal.
Illustrative example: a transfer is not a sale
Illustration only, not a real investigation: a creator moves tokens to a second address. That observation supports a transfer claim. To call it a sale, identify supported swap execution and asset balance changes, exclude failed transactions and establish the route. Exchange deposits, pool operations, distributions and transfers between the creator's accounts can otherwise be misclassified. Neither a movement nor a shared funder proves who controls the destination.
Ask what prior launches actually establish
Developer history needs an attributable creator, a bounded but disclosed launch sample, observed launch times and independently evidenced outcomes. A provider's creator field, silent wallet or inactive token does not establish serial fraud. If history is incomplete, a percentage of dead launches cannot be treated as the full population. Related deployers and services can also complicate attribution. RugSignal retains unknowns instead of inventing a clean history.
Read controls, concentration and exit constraints together
Check mint/freeze permissions, supported Token-2022 extensions, sampled owner balances and applicable pool control. Concentration is not the number of people involved and can include unlabelled service accounts. A small quote may have little price impact while your full position has no useful route. Quote freshness and raw units matter. Risk-change alerts describe changed evidence, not a promise to observe every transaction or stop a loss.
Use a report as a dated investigation aid
Paste the mint into the free scanner, inspect source timestamps and missing checks, then compare the public methodology and liquidity guide. An entitled account can investigate sampled clusters or monitor supported risk changes. Reading a saved report never refreshes it. No scanner detects every mechanism, future abandonment or market failure; RugSignal's independent predictive accuracy remains unverified.
Sources and further reading
- Pump.fun: official public program and migration documentation
- Solana: token and authority model
- RugSignal: liquidity, quotes and limitations
Official protocol documentation explains capabilities; it does not certify an individual token. RugSignal-specific statements describe our current implementation.