LP Burn
The permanent destruction of liquidity pool tokens, making it impossible for anyone to withdraw the underlying liquidity and drain the trading pool.
Definition
LP burn refers to the irreversible removal of liquidity pool (LP) tokens from circulation by sending them to a burn address (typically the null address on Solana). When a liquidity pool is created on a DEX like Raydium, the depositor receives LP tokens representing their ownership share of the pool. Whoever holds those LP tokens can redeem them to withdraw the underlying assets — the token and SOL — from the pool at any time. If a developer holds unburned LP tokens, they can drain the entire pool in a single transaction, instantly removing all buy-side liquidity and collapsing the price. Burning the LP tokens makes this impossible: no one can redeem what doesn't exist. LP burn is therefore a necessary safety condition for most memecoin risk frameworks, and the absence of a burn is one of the most common rejection flags in automated token screening.
What happens mechanically during an LP drain
When a memecoin launches on Raydium, the deployer creates a liquidity pool by depositing the token and SOL (or USDC). In exchange, Raydium mints LP tokens to the depositor. These LP tokens are redeemable claims on the pool's assets. A developer who keeps LP tokens can call Raydium's "remove liquidity" instruction at any time, withdrawing all the SOL from the pool and leaving holders with a worthless token they cannot sell. This is the classic liquidity rug, and it executes in one transaction — under one second on Solana.
Burning the LP tokens to the null address severs this redemption right permanently. No wallet can remove the liquidity because no wallet holds the LP tokens.
LP burn vs LP lock
LP tokens can also be locked in a time-lock contract rather than burned. A lock prevents withdrawal until the lock expires — reducing immediate rug risk but creating a future unlock event that may trigger selling. Key differences:
- Burn (preferred): permanent, verifiable on-chain, no future risk. The gold standard for memecoins with no planned migration.
- Lock: depends on the contract's trustworthiness and the lock duration. A 30-day lock on a memecoin is weak; a 1-year lock from a reputable locker (e.g. Streamflow, Unicrypt) is stronger. Always verify the lock is on-chain, not a verbal claim.
pump.fun graduation and LP burn
One of pump.fun's safety properties is that when a token graduates to Raydium (reaches ~$69,000 in bonding curve volume), the protocol automatically burns the LP tokens. This makes graduated pump.fun tokens safer than many manually launched tokens in this specific dimension — the liquidity rug risk is eliminated at graduation. However, LP burn does not address concentration risk, mint authority, or freeze authority, so graduation is not a comprehensive safety check.
In MemeAssist's telemetry, over 100 tokens were rejected in a single week for pools with 0% of LP burned or locked — making it the second most common rejection flag after holder concentration.
Frequently asked questions
How do I verify that LP tokens are burned?
On Solscan, find the liquidity pool address for the token and look at the LP token mint. Check the holders of the LP token — if the burn address (1111...1111 or similar null address) holds 100% of LP tokens, they are burned. MemeAssist shows LP burn status automatically in the token report.
Can LP tokens be partially burned?
Yes. A developer might burn 80% of LP tokens and retain 20%, which still allows them to remove a significant portion of the liquidity. Any unburned LP held by an identifiable wallet is a risk proportional to the percentage held. 100% burned is the only truly safe outcome.
If LP is burned, can a rug still happen?
Yes — through other mechanisms. The deployer can still dump concentrated token holdings into the pool (a supply dump rather than a liquidity drain). Mint authority, if not revoked, can inflate supply. LP burn eliminates the liquidity-withdrawal rug vector but does not protect against supply-side rugs.