Rug Stop logoRUGSTOP

How to Check if a Solana Token Is Safe Before You Ape

A trader's pre-buy checklist. Run every box before size goes on — most rugs fail at least one of these in the first ten seconds.

7 min read · updated Jun 14, 2026

You found a ticker in a Telegram, the chart is vertical, and your finger is hovering over buy. Before you ape: thirty seconds of due diligence kills most of the rugs that drain wallets on Solana. Here's exactly what to look at, in the order that matters.

TL;DRPaste the mint into a scanner and read two things first — can the dev still mint or freeze, and is the liquidity actually locked. If either fails, nothing else matters. Scan a token now.

1. Can the dev still print more supply? (mint authority)

Mint authority is the on-chain switch that lets whoever holds it create new tokens out of thin air. If it's still active, the dev can 10x the supply the second you're in profit and dump it on your bid. A legit launch revokes it. An active mint authority is the single most common hard rug on Solana — treat it as an automatic pass until it's burned.

2. Can they stop you from selling? (freeze authority)

Freeze authority lets the holder freeze your token account so your bag becomes unsellable — a classic honeypot: buys go through, sells revert. You can be up 5x on paper and unable to take a cent out. Like mint, a clean project revokes freeze authority. If it's live, assume the exit can be slammed shut at will.

3. Is the liquidity locked or burned?

Liquidity is the pool of SOL you actually sell back into. If the dev still holds the LP tokens, they can pull liquidity — yank the SOL out and leave you holding a token that trades against nothing. You want LP that's burned (gone forever) or locked (time-released by a contract). Unlocked dev-held liquidity is a rug waiting for a catalyst.

4. Who actually owns the float? (holder concentration)

Pull the top holders. If a handful of wallets — or one bundle of wallets funded from the same source — hold 40%+ of supply, the chart is theirs, not yours. They decide when it dumps. A healthy distribution has the pool and burn addresses up top and real holders spread out behind them.

5. Has the dev already sold?

A creator who dumped their own allocation in the first hours is telling you everything. Dev sold is a behavioural red flag that no amount of green candles fixes — if the person who made the token doesn't hold it, ask why you should.

6. Did snipers eat the launch?

On pump.fun, sniper bots buy in the same block the token is created and capture a big slice of supply before any human sees it. If snipers grabbed 20–30%+ at launch, early hype is just them distributing to you. Check how much the launch cohort captured — and how much they've already sold.

7. Does the on-chain story match the vibe?

Last, line up the narrative against the facts. Brand-new mint with a 9-figure 'market cap'? That's a thin pool and a big supply number, not real money. Socials added five minutes ago? Founder wallet linked to three prior rugs? The chart can be faked; the chain can't.

The 30-second checklist

  • Mint authority revoked — supply can't be inflated
  • Freeze authority revoked — your sells can't be blocked
  • Liquidity burned or locked — the pool can't be pulled
  • No single wallet or bundle owns the float
  • Dev still holds — hasn't dumped their bag
  • Snipers didn't capture most of the launch
  • Market cap, socials and founder history pass the smell test

Signals, not guarantees.Passing every check lowers your odds of getting rugged — it doesn't make a token a good buy or a safe one. Probabilistic signals can be wrong, and a clean contract can still nuke on a dev's whim. Size accordingly.

Do it in one paste

Running these by hand across Solscan, DexScreener and a block explorer takes minutes you don't have when a token is moving. Rug Stop pulls all seven from the chain in one scan and shows two separate scores — a safety read and a smart-money read — with the evidence behind every line, never a bare SAFE/SCAM verdict. Paste a mint and scan it.

Check this on a real token →

Scan a token

Keep reading