What burning LP tokens does, and what it proves
Burning sends LP tokens to an address whose private key does not exist. The liquidity stays in the pool and keeps backing trades forever; what disappears is anybody's ability to withdraw it. That is why a burn reads as a permanent liquidity lock, and it is irreversible the instant the transaction confirms.
It proves exactly one thing: the share you burned can never be pulled out. It does not prove the pool is safe, that the token has no other risks, or that other LP holders are locked. A buyer checking your claim should compare the burned amount against the pool's total LP supply on BscScan, which takes about a minute.
Burn or lock? The honest comparison
Burning is not the only way to signal that liquidity will stay put, and it is the most expensive one, because it gives up the deposit and all future fees permanently.
| Burn | Time lock | Hold | |
|---|---|---|---|
| Can you get the liquidity back? | Never | After the term ends | Any time |
| Do you keep earning trading fees? | No | Usually yes, released with the LP | Yes |
| Third party required? | No | Yes, a locker contract | No |
| What a buyer has to trust | Only the chain | The locker contract and its term | You |
| Reversible by you? | No | At expiry | Yes |
Burn when you genuinely never intend to reclaim that liquidity. Lock when you might need it back, and be honest in your announcement about which one you did, because the two are routinely conflated and a buyer who discovers the difference later treats it as a lie.
What an LP token represents on PancakeSwap V2
A PancakeSwap V2 pool holds two reserves and prices them by their ratio. When you deposit, the pair contract mints LP tokens to your wallet: a fungible BEP-20 whose balance is your proportional claim on both reserves plus the trading fees that have accrued to them. Nothing records that you specifically deposited; the LP balance is the entire claim, which is why losing it means losing the deposit.
That design is what makes the three operations on this site distinct. Adding liquidity mints LP to you. Removing liquidity burns your LP back into the two underlying assets at current reserves. Burning LP destroys the claim while leaving the reserves in the pool forever. Alchemii routes all three through a verified liquidity manager and never holds your keys, tokens or LP.
| Operation | What happens to your LP | Alchemii fee | Also pay |
|---|---|---|---|
| Create or add liquidity | Minted to your wallet | 0.05 BNB | Both deposits, gas, and a token approval |
| Remove liquidity | Redeemed for the two underlying assets | 0.05 BNB | LP approval if needed, plus gas |
| Burn LP tokens | Destroyed permanently | 0.05 BNB | LP approval if needed, plus gas |
PancakeSwap's own trading fee is charged on swaps against the pool and is separate from every figure above; its fees and routes documentation covers the current split. The pair contracts these tools call are the ones listed in PancakeSwap's V2 deployment reference.
What to publish so the burn is verifiable
A screenshot proves nothing. Four values let anyone reproduce your claim independently, and they all come from the transaction you just signed.
| Publish | Where a reader verifies it |
|---|---|
| The burn transaction hash | BscScan transaction page: a transfer of LP to the dead address |
| The LP amount burned | The transfer amount on that same transaction |
| The pool (pair) address | BscScan token page for the LP token |
| The pool's total LP supply | Same page: burned ÷ total is the share actually locked |
Publishing the total supply alongside the burned amount is the part most launches skip, and it is the part that turns a claim into evidence. LP burn proof: exactly what to share walks through the same checks, and why a burned position still shows liquidity explains the display that confuses people afterwards.
Burning LP tokens on BSC FAQ
What does burning LP tokens actually do?
It sends the LP tokens to an address whose private key does not exist, so the claim they represent on the pool's reserves can never be redeemed. The liquidity itself stays in the pool and keeps backing trades; what disappears is anyone's ability to take it out. That is why a burn is read as a permanent liquidity lock, and it is irreversible from the moment the transaction confirms.
How do I burn LP tokens on BSC?
Connect the wallet holding the LP on BNB Smart Chain mainnet, paste the PancakeSwap V2 pool address, check the symbols and LP balance the form reads back, enter the amount or use 50% or MAX, tick the confirmation that burned LP cannot be recovered, and confirm the transaction. The service fee is 0.05 BNB plus gas. Save the transaction hash, because it is the proof other people will ask for.
Is burning liquidity the same as locking it?
No, and the difference matters to a careful buyer. A burn is permanent and needs no third party: the LP is destroyed and nobody can withdraw. A lock is a contract that holds the LP for a set period and returns it to you when the term ends, so it is reversible by design and depends on the locker contract being trustworthy. Burn when you never intend to reclaim the liquidity; lock when you might.
Does burning LP tokens raise my token's price?
No. Burning LP destroys a claim on the pool's reserves; it does not change the reserves themselves, and price is set entirely by their ratio. Nothing about the chart changes at the moment of the burn. What changes is what a buyer can conclude about your intentions, which is a credibility effect rather than a price one.
Does burning my LP prove the whole pool is locked?
Only for the share you burned. If other wallets hold LP in the same pool, they can still withdraw their share whenever they like. A buyer checking your claim should compare the burned amount against the pool's total LP supply on BscScan rather than taking a single transaction as proof that all liquidity is locked. Publish both numbers if you want the claim to stand up.
Can I recover burned LP tokens?
No. The burn address has no private key, so the tokens sit there permanently and no contract, service or support request can return them. This is why the form requires an explicit acknowledgement before it will build the transaction. Burn only what you are certain you will never need, and test with a small amount first if you are unsure about the flow.
What should I publish after burning liquidity?
The burn transaction hash, the LP amount burned, the pool address and the pool's total LP supply at that time. Those four values let anyone reproduce your claim on BscScan in under a minute. Pair them with the token contract, the supply and the ownership setting, and a reader can verify the whole launch without trusting an announcement.