TrustDex › Guides › Pump.fun launch risk
Pump.fun launches — mechanics and the risk profile that comes with them
Bonding-curve launchpads industrialized the meme coin: same contract, same curve, same graduation ritual, thousands of times a day. That factory removes some classic scams entirely — and leaves others completely intact.
A token born on a pump.fun-style launchpad is a different animal from one a developer deployed by hand, and judging it with the usual checklist produces weird results — half the red flags can't occur, while the dangers that actually kill these trades don't appear on the contract at all. To evaluate a curve-launched token you need to know what the platform standardizes away, what it can't touch, and how the risk moves from code to people. That's the ground this guide covers.
Scan a launchpad token
Works before and after graduation — enter the mint to get a dated risk snapshot.
Pricing without a pool: how the bonding curve works
Before graduation there is no DEX pool, no pair, and no LP tokens — the launchpad's own contract is the only counterparty. It holds the token's supply and sells it along a bonding curve: a fixed formula in which each token bought raises the price of the next one, and selling back to the curve walks the price down the same slope. Cost basis is therefore purely positional. Whoever buys earliest on the curve pays the least, mechanically and by design, and everyone can see exactly how far along the curve a token has traveled.
This phase has one underrated property: the curve contract itself is the escrow. The SOL that buyers spend accumulates inside the program rather than in a wallet a creator controls, so "the dev pulled the liquidity" isn't a possible failure mode yet — there's no liquidity to pull, only a curve that can be sold back into.
Graduation: the moment the training wheels come off
When cumulative buying pushes the curve to its completion threshold, the token graduates (traders say it "bonded"). The platform closes the curve, takes the SOL it accumulated plus the remaining token supply, and deposits both into a real AMM pool where ordinary open-market trading begins. On current pump.fun-style flows the platform handles that migration itself and disposes of the pool's LP position under its standard procedure, rather than handing receipts to the creator.
Graduation is the correct moment to re-underwrite the token, because its structure just changed categories: bonding-curve math is gone, pool dynamics have arrived, and everything in the LP and burned-liquidity playbook now applies. Most launches never get here — the curve stalls, attention moves on, and the token quietly dies pre-graduation, which is itself the most common outcome to plan for.
What the platform switches off — and the loopholes it can't close
Because every launchpad token comes from the same factory template, the deployer never gets the dangerous knobs. Mint authority and freeze authority are disabled from the start, so the two classic SPL contract attacks — supply inflation and account freezing, covered in our authorities guide — are structurally impossible. There's no custom code, so there's nothing like a hidden transfer tax or a honeypot switch to audit for either.
What remains is everything a contract can't govern. A creator can still hold a large allocation bought in the first seconds of their own curve for almost nothing. Coordinated wallets can still stack the bottom of the curve and unload on everyone above them — the bundled-launch pattern in its natural habitat. And the entire economic engine is a social attention cycle: price rises while new buyers arrive from a feed, a group chat, or a trending tab, and reverses the moment they stop. None of that shows up as a red flag in the contract, because none of it lives in the contract.
Reframe it this way: launchpads solved token-code trust and left token-holder trust unsolved. The scan question shifts from "what can this contract do to me?" to "who is positioned to sell on me, and when?"
The survivorship math nobody posts about
The launches you hear about are the ones that worked, and the platform's volume guarantees you'll hear about some daily. But the funnel behind each winner is brutal: enormous numbers of curves launch, a small minority ever graduate, and of the graduates only a sliver still have meaningful volume weeks later. Multiplied out, tokens that produce durable gains are a rounding error of all tokens created — every survivor stands on a mountain of identical-looking failures that no one screenshots.
This math is the honest base rate for the category, and it means process beats picking. Any single launch is overwhelmingly likely to follow the modal path — a brief candle, then illiquidity — so sizing, exits, and the discipline to skip most launches matter more than any individual read. (Deliberately, no specific percentages here: the numbers drift month to month and anything quoted would be stale; the shape of the funnel is what's stable.)
Curve launch vs hand-deployed SPL: where the risk actually sits
| Risk vector | Launchpad token | Hand-deployed token |
|---|---|---|
| Mint / freeze abuse | Disabled by template | Depends on deployer |
| Custom contract tricks | No custom code | Must be checked |
| Pre-DEX liquidity pull | Curve escrows funds | N/A — pool from day one |
| Post-DEX liquidity handling | Platform-standardized at graduation | Deployer's choice — verify |
| Insider supply & bundles | Fully possible | Fully possible |
| Attention-cycle collapse | The dominant outcome | Equally dominant |
Read the columns top to bottom and the pattern is clear: the launchpad wins every row that involves code and ties every row that involves humans. That's a genuine improvement — fewer ways to be cheated is worth something — but the rows it ties are the rows where most of the money is actually lost.
A post-graduation checklist
When a token you're watching bonds, run through four questions before treating the graduation candle as a signal. Distribution: what do the top holders look like once you mentally group wallets funded from the same source — is the "community" actually five siblings of one deployer? Early-buyer behavior: are the wallets that bought the bottom of the curve holding, or already streaming out into the new pool's first hours? Pool reality: how deep is the new pool relative to the token's implied valuation, and does its liquidity disposition check out on-chain rather than in a screenshot? Momentum source: is buying arriving from anywhere identifiable, or was the graduation push itself the event? A scan bundles the measurable parts of this into one dated report — treat it as the snapshot it is, not a standing guarantee, and re-run it as the situation moves. If the token later goes quiet, the dead-token forensics guide covers reading the aftermath.
Snapshot a graduate before you commit
Holder spread, liquidity state, and risk level in one report — then swap non-custodially if it clears your bar.
Frequently asked
How does a bonding curve price a token before a DEX pool exists?
The launchpad's contract acts as the sole market maker: it sells tokens from a preset supply along a mathematical curve, so each purchase pushes the next price up and each sale pushes it down. Price is a pure function of how much has been bought from the curve so far — no pool, no LP tokens, no external liquidity yet.
What does graduation mean on pump.fun-style platforms?
When buying pushes the curve to its target threshold, the platform closes the curve and moves the accumulated funds plus remaining tokens into a real DEX pool, where open AMM trading begins. Reaching that milestone is called graduating or bonding, and it is the moment the token starts behaving like any other tradable pair.
If mint and freeze are disabled, why do most launchpad tokens still go to zero?
Because the platform only removes contract-level rugs. It cannot remove market-level ones: creators and coordinated wallets buying cheap on the curve and dumping on later entrants, attention evaporating after the pump cycle, and thousands of near-identical launches competing for the same buyers. Distribution and timing decide outcomes, not the contract.
Is a graduated launchpad token safer than a hand-deployed SPL token?
On contract mechanics, usually yes — authorities are disabled and liquidity handling is standardized rather than left to the deployer's honesty. On market structure, no: supply concentration, bundled early buys, and abandonment hit both kinds equally. The platform narrows the ways you can be cheated; it does not narrow the odds of losing.
What should I check after a token graduates?
Shift attention from the contract to distribution and liquidity: how concentrated the top holders are once related wallets are grouped, whether early same-block buyers are already exiting, and the depth and disposition of the new DEX pool. A scan at graduation gives a dated snapshot of exactly those fields.