LP burn vs LP lock: which one actually protects you from a rug?

"Liquidity burned 🔥" is the most abused sentence in memecoin marketing. Sometimes it's true. Often it's a half-truth — 60% burned, 40% sitting in the deployer's wallet, ready to pull. And "locked" isn't automatically safe either: a 3-day lock on a token you plan to hold for a month is a countdown timer, not protection. This guide explains what each mechanism really does, how to verify it on-chain, and the tricks deployers use to fake it.

1What liquidity is, in one paragraph

When a token launches on a DEX like Raydium, the deployer pairs it with SOL or USDC in a liquidity pool. In return they receive LP tokens — receipts that can be redeemed to withdraw the underlying funds. Whoever holds the LP tokens controls the liquidity. If they redeem them ("pulling liquidity"), the pool empties, the price goes to zero, and buyers are left holding unsellable tokens. That's the classic rug. Everything else — burn, lock, nothing — is just a statement about where those LP tokens are.

2LP burn: permanent, but only as strong as the percentage

Burning means sending the LP tokens to a burn address (an address with no known private key, like 1nc1nerator… on Solana). Once burned, that liquidity can never be withdrawn. It's the strongest form of protection because it's irreversible — no timer, no trusted party.

The catch is that burn is all-or-nothing only if the number is 100%. A deployer who burns 75% of LP and keeps 25% can still pull a quarter of the pool — and if they accumulated most of the token supply for free at launch, that's more than enough to nuke the chart.

3LP lock: flexible, but read the fine print

Locking means depositing the LP tokens into a third-party locker contract for a set period. The deployer can't withdraw until the lock expires. This is common for more "serious" projects that want liquidity flexibility later (migrating pools, adjusting pairs) — a legitimate reason burn doesn't allow.

But a lock is only as good as three details:

4The fake-burn tricks that fool scanners

Three patterns show up constantly in rug teardowns:

1. Partial burn marketing. The deployer burns a loud, screenshot-able transaction — but it covered 40% of LP. Always compute the burned share yourself: LP tokens at the burn address ÷ total LP minted.

2. Burn of the wrong pool. The token has two or three pairs (e.g., one on Raydium, one on Meteora). The deployer burns the LP of a tiny dust pool and keeps the main pool's LP. Check every pool with meaningful liquidity, not just the one linked on the token page.

3. Burn, then re-add. On some pool types a deployer can burn LP publicly to farm trust, then rely on the fact that they control most of the token supply instead — they don't need to pull liquidity to dump on you. LP safety and holder concentration are separate checks; passing one doesn't excuse failing the other.

5Burn vs lock: the practical verdict

Rule of thumb: for a memecoin, prefer ≥95% burned or ≥95% locked for 6+ months with a known locker. Anything below that isn't "a bit risky" — it means the rug option is deliberately being kept open.

6The 60-second verification workflow

Before buying, run these in order:

1. Find every pool for the token with real liquidity (not just the first one listed). 2. For each pool, check LP token distribution: how much is at a burn address, how much in a locker contract, how much in a regular wallet. 3. If locked, note the expiry date and the locker's identity. 4. Cross-check with holder concentration — safe LP plus a 40% insider supply is still a bad trade. 5. Size the position as if the weakest pool's LP could vanish tomorrow, because it can.