Token Launch

Burned vs locked liquidity on Solana: what buyers verify

Cover image for Burned vs locked liquidity on Solana: what buyers verify

Burned liquidity on Solana is permanent; locked liquidity is held by a third-party contract until a date. How each works, how to verify a burn, and the limits.

By 8 min read1606 words

Key takeaways

  • An LP token on Solana is a fungible SPL token that represents a share of a liquidity pool's reserves and is the only way to withdraw that share.
  • Burning LP tokens on Solana destroys the claim on the pool permanently, so the liquidity they represented can never be withdrawn by anyone, including the creator.
  • Locked liquidity on Solana means the LP tokens sit in a third-party locker contract until an unlock date, so buyers must trust the locker and check when the lock expires.
  • A real LP burn on Solana is verified by a Burn or BurnChecked instruction on the LP mint and an LP supply at or near zero, not by a transfer to a dead-looking address.
  • Burned liquidity on Solana does not protect buyers from a developer who holds a large share of supply or from an active mint authority.

The short answer#

Burned liquidity means the LP tokens for a pool were destroyed, so that share of the pool can never be withdrawn by anyone. Locked liquidity means the LP tokens are held by a third-party contract that refuses to release them until a set date. A burn is permanent and depends only on the SPL Token program; a lock is temporary unless stated otherwise and depends on the locker.

Both address exactly one risk: the creator withdrawing the pool. Neither says anything about who holds the token supply or whether more can be minted.

What does an LP token represent?#

An LP token is a fungible SPL token that a liquidity pool mints to whoever deposits assets, as a receipt for their share of the reserves. On Raydium's standard pools, the older AMM v4 and the newer CPMM program, depositing SOL and a token into the pool mints LP tokens to your wallet from the pool's own LP mint. To withdraw, you hand LP tokens back and the pool pays out your proportional share of both assets.

Two consequences follow. LP tokens are the only claim on the reserves: no LP tokens, no withdrawal. And each pool has its own LP mint, with a supply that anyone can read. When a token launches, the creator usually deposited all the initial liquidity and so holds close to 100% of the LP supply. That wallet can empty the pool in one transaction. This is the classic rug pull, and it is the thing burning or locking is meant to rule out.

What does burning LP tokens do?#

Burning LP tokens destroys the claim while leaving the reserves in place. The Burn instruction of the SPL Token program reduces the holder's balance and the LP mint's total supply by the same amount. The pool does not notice: it keeps quoting prices and executing swaps. What changed is that the share of reserves those LP tokens represented can no longer be redeemed by the creator, by Raydium or by anyone who later obtains the creator's keys.

Things worth knowing:

  • There is no undo. No unlock date, no admin key, no support desk. The paired SOL or USDC is spent from the launcher's point of view.
  • Trading fees in a standard pool accrue to the reserves, so the burned share's fees are locked along with it.
  • A burn only covers the burner's share. Other providers who add liquidity later hold their own LP tokens and can withdraw them. "100% burned" at launch does not mean all future liquidity is permanent.
  • Partial burns are possible. What matters to buyers is the percentage of LP supply burned.

For launchers, the SOLTidy Burn LP Tokens tool shows what percentage of the LP supply your wallet holds and how much you are about to burn before you sign, builds a single BurnChecked instruction, and costs a flat 0.005 SOL per transaction. It hides NFTs so a position NFT cannot be burned by mistake. The spl-token burn command does the same job for the network fee alone if you are comfortable with the CLI.

What does locking liquidity do?#

Locking places LP tokens in the custody of a locker program that will not release them before a chosen date. The tokens still exist and the LP supply is unchanged; ownership of them has moved from the creator's wallet to an account the locker controls. When the lock expires, the creator can claim them back and withdraw the liquidity.

Lockers are third-party contracts, and that is the trade-off. A lock gives a team flexibility: liquidity can be migrated to a better pool after expiry, and some lockers let the owner keep claiming fees. In return, a buyer has to establish three things a burn never requires:

  1. Which program holds the LP tokens, and whether it is a known locker or just another wallet the team controls.
  2. When the lock ends. Time-limited locks are common, and a short one postpones the rug question rather than answering it.
  3. What powers the locker retains, such as upgrade authority or an admin withdrawal path.
Burned LPLocked LP
What happens to LP tokensDestroyed; LP supply dropsMoved to a locker's account; supply unchanged
DurationPermanentUntil the unlock date (sometimes extendable or permanent)
Trust requiredSPL Token program onlyThe locker program and its admins
Can liquidity be migrated later?NeverYes, after unlock
Fee claimsLocked in the pool with the reservesPossible with some lockers
How a buyer verifiesLP mint supply and the burn transactionLocker account, unlock date, locker's reputation
Works for concentrated liquidityNoOnly via the protocol's own lock
CostNetwork fee via CLI; 0.005 SOL per transaction via SOLTidySet by the locker
Main weaknessAbsolute: no recovery if the project winds downExpiry: the question returns on the unlock date

How do you verify an LP burn on an explorer?#

You verify a burn by checking the LP mint's supply and reading the burn transaction, neither of which requires trusting the team. Here is the process on Solscan or Solana Explorer.

  1. Find the LP mint. It is listed in the pool's details on Raydium and on the pool's explorer page. It is not the pool address and not the token's own mint.
  2. Check the LP mint's current supply. After a full burn by the sole provider it is at or near zero. A large remaining supply means someone still holds a withdrawable claim.
  3. Open the LP mint's holders. The creator's wallet should no longer appear. The free Holder Snapshot works on LP mints as well and lists exactly who holds the remainder, without connecting a wallet.
  4. Open the burn transaction. It should contain a Burn or BurnChecked instruction from the SPL Token program, on the LP mint, signed by the creator. Pasting the signature into the Transaction Decoder shows the instruction and the token balance change in plain language.
  5. Check the date. A burn from launch day is more reassuring than one that appeared after people started asking.

Incinerator address vs a real burn instruction#

Sending LP tokens to an "incinerator" or dead-looking address is a transfer, not a burn. The tokens still exist, the LP supply does not change, and their safety depends on nobody controlling that address. For a well-known incinerator address with no known private key that is a reasonable assumption, but it is an assumption you have to check: the address must be exactly the known one, not a lookalike vanity address the team generated. A real Burn instruction needs no interpretation, because the supply figure itself drops. That is why a true burn is the convention on Solana, and why screeners that report "LP burned %" compare circulating LP supply with the amount originally minted.

Why doesn't this apply to concentrated-liquidity pools?#

Concentrated-liquidity positions are not fungible LP tokens, so there is no LP supply to burn. A Raydium CLMM position and an Orca Whirlpool position are each represented by an NFT; a Meteora DLMM position is a program account tied to the owner's wallet. Each position has its own price range, so positions are not interchangeable and no percentage-burned figure can exist.

Destroying a position NFT does not produce a lock buyers can rely on. It can simply strand the funds and the fees they earn, and explaining it to buyers is harder than explaining a real lock. For these pools the credible option is the protocol's own locking feature where one exists; Raydium, for example, offers a lock for CLMM and CPMM positions that keeps fee claims available. If a token trades on a concentrated pool and the team says "LP burned", ask precisely what was burned and look at the transaction.

What does burned liquidity not protect against?#

Burned liquidity stops one exit and leaves every other one open. A locked pool is, in a sense, guaranteed exit liquidity for whoever holds the most tokens.

  • Developer supply. If the team kept 40% of the supply across a few wallets, they can sell it into the pool that cannot be withdrawn. The SOL leaves through swaps instead of through a liquidity removal, and the chart looks the same afterwards. Check holder concentration with the pool address excluded.
  • Active mint authority. A creator who can still mint can print new tokens and sell them into the burned pool. Any token's authorities can be read for free on the Revoke Mint Authority page or on an explorer, and mint authority vs freeze authority explains what to look for.
  • Active freeze authority. Liquidity you cannot sell into is no use to you.
  • Token-2022 extensions such as a permanent delegate or a transfer hook, which act on holders directly.
  • Thin liquidity. Burning 2 SOL of liquidity permanently locks 2 SOL. It does not make the pool deep.

All of these belong in one pass before buying, which I laid out as a pre-buy checklist for spotting rug pulls. If you are on the launching side, the order of operations, including when to burn, is in the token launch checklist. For what SOLTidy is and who runs it, see the about page.

Bottom line#

Burned LP is permanent, trust-free and verifiable in two clicks: the LP mint's supply and a Burn instruction. Locked LP is flexible but adds a contract to trust and a date to watch. Neither applies to concentrated-liquidity positions, where only the protocol's own lock is meaningful. And both answer a single question, whether the creator can withdraw the pool, so a careful buyer still checks the authorities and who holds the supply before treating "LP burned" as good news.

Questions & answers

What does LP burned mean on Solana?

LP burned means the liquidity provider tokens issued by a pool, normally to the token's creator, have been destroyed with the SPL Token program's Burn instruction. Those LP tokens were the only claim on that share of the pool's reserves. With the claim gone, the SOL and tokens stay in the pool and keep serving trades, but nobody can ever withdraw that share.

Can burned liquidity ever be removed from a Solana pool?

No, not the share that was burned. Withdrawing from a Raydium AMM v4 or CPMM pool requires handing LP tokens back to the pool program, and burned tokens no longer exist. There is no admin key or recovery process. Liquidity added later by other providers is a separate matter: they hold their own LP tokens and can withdraw their own share whenever they like.

Is locked liquidity as safe as burned liquidity?

It can be for the duration of the lock, but it adds two things to check. The first is the unlock date, since a 30-day lock only postpones the question. The second is the locker itself: you are trusting that program's code and any admin powers it has. A burn depends only on the SPL Token program and never expires, which is why it is the simpler signal.

How do I check if liquidity is burned on Solscan?

Find the pool's LP mint address, which is not the pool address and not the token's mint. Open it on Solscan and check the current supply and the holders list: after a full burn, supply is at or near zero and the creator's wallet is gone from the holders. Then open the burn transaction and confirm it contains a Burn or BurnChecked instruction on that LP mint.

Why can't Raydium CLMM or Meteora DLMM liquidity be burned?

Because those pools do not issue fungible LP tokens. A Raydium CLMM or Orca Whirlpool position is represented by an NFT, and a Meteora DLMM position is a program account tied to the owner's wallet. There is no LP supply to reduce, so a burned percentage cannot be calculated. Destroying a position NFT can strand the funds without giving buyers a verifiable lock; use the protocol's own lock feature instead.

Should a token launcher burn or lock LP tokens?

Burn if credibility matters most and you accept never recovering the paired SOL. Lock if you expect to manage liquidity over time, for example migrating to a different pool, and are willing to explain the locker and the unlock date to buyers. A partial burn is also possible. Whichever you choose, treat the paired assets as spent, and publish the transaction so buyers can verify it.