TrustDex › Guides › LP tokens & burned liquidity
LP tokens & burned liquidity — why "LP burned" matters
Behind every DEX pool sits a stack of receipts, and whoever holds them can cash the whole pool out. "LP burned" means those receipts were destroyed on purpose. Here's why that's a big deal — and where its protection ends.
Rug pulls are usually described as a team "removing liquidity," but that phrasing hides the actual object involved. Liquidity isn't removed by magic; it's redeemed with a specific instrument — the LP token. Understand that instrument and the whole topic snaps into focus: who can rug, what locking really restrains, what burning really destroys, and which claims about "safe liquidity" can be checked in a block explorer rather than taken on faith. That's this guide.
See how a pool's liquidity is held
Paste a contract address — the report covers liquidity standing alongside the other risk fields.
Where LP tokens come from — and why they're the rug lever
An automated market maker pool is a shared pot holding two assets — say a new token on one side and SOL or a stablecoin on the other. Anyone who contributes to the pot needs proof of their share, so the pool mints them a receipt: an LP token, itself a transferable on-chain asset. Deposit a tenth of the pool's value and your receipts represent a tenth of everything inside, including the trading fees the pool collects along the way.
Redemption is the flip side. Present your LP tokens to the pool and it hands back your proportional slice of both assets at that moment's balance, destroying the receipts as it pays out. This is normal, healthy plumbing — it's how liquidity providers everywhere enter and exit. The danger comes entirely from who holds the receipts and how many.
On a brand-new token, the deployer typically seeds the entire pool alone, which means they start out holding essentially all of its LP supply. Follow the logic through: all the receipts, so the right to withdraw everything — including the real SOL or stablecoins that arriving buyers have been trading into the pot. The classic liquidity rug is nothing more exotic than the deployer redeeming their own receipts at the most profitable moment. Buyers keep their now-unswappable tokens; the deployer keeps the money side of the pool.
Every liquidity-safety mechanism you'll encounter is an answer to this one fact. Locks put the receipts in time-limited custody. Burns destroy them. And a pool with neither is a pool whose creator can close the casino whenever the take looks good — the standard first act in the on-chain sequence of a rug.
What burning LP actually does
Burning means sending the LP tokens somewhere they can never be spent from — a canonical dead address, or a true supply-reducing burn where the receipts are destroyed outright. Either way, the effect is identical and absolute: the claim those receipts carried is gone. The pooled assets stay in the pool, tradable forever, but no one holds the ticket that would let them be pulled back out through redemption. Not the deployer, not a hacker who later compromises the deployer's wallet, not anyone.
Notice what makes this signal special compared with most token "promises": it's a completed, irreversible action recorded on-chain, not a statement of intent. A roadmap can be abandoned and a lock can expire, but a burn already happened and can't un-happen.
One sentence to keep: a lock says "we can't touch the pool yet"; a burn says "no one can touch the pool, ever." Both refer only to the specific pool whose receipts were locked or burned.
Burned vs locked: the honest trade-off
| Burned LP | Locked LP | |
|---|---|---|
| Withdrawal risk | Eliminated for that pool | Deferred to expiry |
| Reversible? | No | Yes, when the timer ends |
| Trust required | None | The locker contract & its operators |
| Team flexibility later | Zero — pool is stranded there | Can migrate or restructure liquidity |
| Typical use | Meme launches proving intent | Projects with a long operational plan |
The permanence that makes a burn reassuring is also its cost. A team that burns can never move that liquidity to a deeper pool, a new DEX, or an upgraded token version — the deposit is stranded in place for good, and the fee income the position earns is typically forfeited along with it. That's why a burn is best read as a costly signal: it demonstrates the team has surrendered value it can never recover, which anonymous short-horizon launches use precisely because nothing else they say is checkable.
Verifying a burn instead of believing one
Because "LP burned" is such a persuasive phrase, it's also a favorite lie. Verification takes three steps. First, identify the right object — the LP mint of the token's main trading pool, not the project token itself (burning project tokens is a completely different, mostly cosmetic act). Second, look at where that LP supply lives: a real burn shows the receipts at a recognized unspendable address or subtracted from the LP supply altogether. Third, check the proportion. If the dead address holds most but a normal wallet still holds a slice, that slice remains a functioning exit sized to its share of the pool — the same arithmetic that governs partial locks.
A decent scan does this bookkeeping for you, but knowing what it's checking keeps you from being satisfied by a screenshot of somebody's burn transaction that turns out to cover a different pool, a token burn, or a rounding-error quantity of LP.
The trick that survives a burn: fresh unlocked liquidity
Here's the maneuver that catches people who stop reading at the badge. A burn binds one pool. Nothing stops the same team from later creating a second pool for the same token — seeded with new funds, receipts kept in hand — and steering the community toward it: "we've added deeper liquidity, trade here." As volume migrates to the new venue, the burned pool becomes an empty museum piece while the pool people actually use is fully pullable. The token still "has burned LP" in the sense that got quoted; it just doesn't matter anymore.
The defense is to ask the question per-pool, not per-token: for the pool where trading is actually happening today, what's the status of its receipts? Any liquidity event — a migration, a "v2 pool," a new pairing — resets that question to unanswered.
Edge cases worth knowing
Two wrinkles round out the picture. Pools seeded with the token on both practical sides of the deposit — the so-called single-sided or team-supplied setups common on launch platforms — can show impressive-looking liquidity that contains very little hard asset to begin with, so even a genuine burn there protects less real value than the headline number implies. And on concentrated-liquidity DEXes, positions are often represented as NFTs rather than fungible receipts; "burned" claims around those need the same scrutiny with slightly different mechanics. In both cases the underlying question is unchanged: who, if anyone, can convert the pool's contents back into their own wallet — and the answer determines how much comfort the word "burned" should buy. Launch-platform pools have their own risk quirks, covered in the pump.fun risk profile guide.
Verify before you size a position
Burn claims, authority flags, and holder spread — checked together in one pass.
Frequently asked
What is an LP token?
It is the receipt an AMM pool issues to whoever deposits liquidity. The receipt is itself a token, and redeeming it returns the depositor's proportional share of both assets in the pool. Owning LP tokens is owning the right to withdraw pooled funds — which is exactly the right a rug pull exercises.
What does it mean when a project says LP is burned?
The deployer sent the pool's LP tokens to an unspendable address, destroying the ability to redeem them. Nobody — the team included — can ever withdraw that pooled liquidity again through the normal path. It is the permanent version of a liquidity lock.
How do I verify that LP was really burned?
Find the pool's LP token mint, then check where its supply actually sits. A genuine burn shows all or nearly all LP supply at a recognized dead address or removed from supply entirely. If a meaningful slice still sits in a normal wallet, that slice is withdrawable and the burn claim is only partly true.
Does burned LP make a token rug-proof?
No. It removes the pool-withdrawal rug, and only for the specific pool whose receipts were burned. Insiders can still dump a large token allocation into the pool, a live mint authority can still print supply, and traders can be lured into a second, unburned pool later. It is one strong signal, not an all-clear.
Why would a team burn LP instead of locking it?
Burning is the louder commitment: no expiry date to game, no locker service to trust, no future discretion to worry about. Its cost is total — the team forfeits the deposit and usually its fee earnings — which is why serious long-horizon projects often prefer a long lock while throwaway meme launches burn.