Burn LP Tokens or Lock Them?
Burning LP tokens destroys them permanently, so the liquidity they represent can never be withdrawn by anyone. Locking LP tokens places them in an on-chain vault until a set unlock date, after which the creator can withdraw.
Burning is stronger proof. Locking is more flexible. The right choice depends on whether you will ever need to move, migrate or rebalance that liquidity again, because burning removes that option forever.
Lock LP Tokens on StakePoint
Raydium · Meteora · Orca · PumpSwap · Token-2022
What Burning LP Tokens Actually Does
An LP token is a receipt for a share of a liquidity pool. Burn the receipt and nobody can ever redeem the underlying liquidity, which stays in the pool permanently backing the market.
Two consequences follow, and projects regularly overlook the second one.
First, the liquidity can never be pulled. That is the intended effect and it is absolute.
Second, the liquidity can never be recovered by you either. If your token later migrates to another DEX, if the pool design changes, if the fee tier turns out wrong, or if you need to consolidate two pools into one, the burned share is unreachable. It is not paused, it is gone.
What Locking LP Tokens Does
Locking places the LP tokens in a Program Derived Address vault controlled by on-chain program logic rather than by a person. On StakePoint the vault has no admin keys and no cancel instruction, so nothing releases before the unlock date under any circumstance.
At the unlock date the LP tokens return to the wallet that created the lock. Until then they behave, for every practical purpose, like burned liquidity.
The difference is entirely about what happens after the date you chose.
Burn vs Lock, Side by Side
| Burn LP | Lock LP | |
|---|---|---|
| Reversible | Never | On the unlock date only |
| Liquidity can be pulled | No | No, until the unlock date |
| Can migrate DEX later | No | Yes, after unlock |
| Can rebalance or consolidate pools | No | Yes, after unlock |
| Signal strength to holders | Strongest possible | Strong, proportional to duration |
| Publishes a future date | No | Yes |
| Suits a fixed, final pool | Yes | Yes |
| Suits a project still evolving | No | Yes |
| On-chain verification | Burn transaction and supply | Public lock record and vault |
When Burning Makes Sense
Burning is the right call when the pool is final and the project is simple.
- The token is a fixed supply community token with no roadmap that touches liquidity
- The pool is on a DEX you will never leave
- The fee tier and pool configuration are already correct
- You want the strongest possible signal and you accept there is no reversal
Memecoins and launchpad graduates with no treasury operations often burn for exactly this reason. There is nothing to manage later, so removing the option costs nothing.
When Locking Makes Sense
Locking is the right call when the project has a roadmap that might touch liquidity.
- You may migrate from one DEX to another as your volume grows
- You run multiple pools and may consolidate them
- Your token uses Token-2022 extensions and your pool setup may need adjusting
- You want to seed a farm or a staking pool with the LP position later
- You want to prove commitment with a defined duration rather than an irreversible action
Locking for a long duration and renewing is functionally close to burning, with the difference that you retain a path to move if the market structure around your token changes. Plenty of projects run this way indefinitely and never unlock.
The Case for Doing Both
Splitting the position is the option most projects miss. Burn a portion to establish a permanent liquidity floor, then lock the remainder for a long duration.
The burned portion guarantees a base level of liquidity that can never leave the pool. The locked portion keeps a working share available for a future migration or consolidation. Holders see both on-chain, and the combination reads as considered rather than performative.
A common split is to burn the founding liquidity and lock every later addition.
Risks Projects Underestimate When Burning
DEX migration. If liquidity moves from one DEX to another, burned LP on the original pool stays behind permanently. This catches launchpad projects that later want deeper liquidity elsewhere.
Wrong fee tier. Burning locks in the fee configuration of the pool as well as the liquidity. A fee tier that suits launch volume may not suit mature volume.
Fragmented pools. Burning across several small pools permanently fragments your liquidity. It cannot be consolidated afterwards.
Nothing left to farm. LP positions can be staked in farms to reward liquidity providers. Burned LP cannot. If LP farming is anywhere on your roadmap, burn only what you can afford to remove from that plan.
How Holders Verify Either Option
Burned LP is verified from the burn transaction and the reduced LP token supply on Solana Explorer. Locked LP is verified from the public lock record.
Every lock created on StakePoint is publicly verifiable at stakepoint.app/locks with no wallet connection and no login. Anyone can search by token address or wallet address and see the locked amount and the unlock date, and confirm the vault directly on Solana Explorer.
Whichever route you take, publish the transaction or lock link in your documentation and pinned channels. Proof that nobody can find does no work for you.
How to Lock LP Tokens on StakePoint
StakePoint supports LP locking across Raydium AMM v4 and CPMM, Meteora DAMM v1 and v2, Orca, and PumpSwap, which is the broadest DEX coverage available on Solana in 2026. Token-2022 LP tokens, including those with transfer taxes, are handled natively.
Go to stakepoint.app/locks and connect the wallet holding your LP tokens
Select your LP token
Enter the amount and choose the unlock date
Confirm the transaction
The lock is created in two transactions and is publicly verifiable the moment it confirms.
If you decide to burn instead, StakePoint has a free on-chain token burn tool for SPL and Token-2022 tokens.
Lock Your Liquidity
Non-custodial · PDA-secured · No admin keys
Frequently Asked Questions
Is burning LP tokens safer than locking them?
Burning removes the possibility of a liquidity pull permanently, which is the strongest guarantee available. Locking removes it until the unlock date. Burning is stronger proof, but it also removes your ability to migrate or rebalance that liquidity forever.
Can burned LP tokens be recovered?
No. Burning is irreversible. The liquidity stays in the pool permanently and nobody, including the project team, can withdraw it.
What happens to locked LP tokens at the unlock date?
They become claimable by the wallet that created the lock. Nothing moves automatically. Many projects relock at that point rather than withdrawing.
Can I lock LP tokens and burn them later?
Yes. Locking first keeps the decision open. Once the lock expires you can burn the LP tokens if the pool configuration has proven correct, which is why locking first suits projects that are still evolving.
Does StakePoint support PumpSwap and Meteora LP locking?
Yes. StakePoint supports Raydium AMM v4 and CPMM, Meteora DAMM v1 and v2, Orca, and PumpSwap LP tokens, with full Token-2022 support on both token and LP locks.
How do investors check whether liquidity is burned or locked?
Burned liquidity is confirmed from the burn transaction and LP supply on Solana Explorer. Locked liquidity is confirmed from a public lock record showing the amount and unlock date, searchable at stakepoint.app/locks without logging in.
How much liquidity should be burned or locked?
Projects that want the strongest signal secure the entire founding position. A common structure is to burn the founding liquidity and lock later additions, which keeps a working share available without weakening the floor.
*Lock LP tokens: StakePoint LP Locker. Raydium, Meteora, Orca and PumpSwap supported, non-custodial and publicly verifiable.*
*Lock team and dev allocations: StakePoint Token Locker. SPL and Token-2022, PDA-secured.*
*Related reading: How to Verify Token and LP Locks on Solana and What Is Locked Liquidity.*