GGlossary · 2 min read

What is an LP burn?

An LP burn sends a liquidity pool position to a dead address, so it can never be withdrawn. What a burn proves, what it doesn't, and how to check one.

300 words · about 2 minutes·Article updated 20 August 2026
Definition

An LP burn sends a token's liquidity position to a dead address nobody holds the keys to, so it can never be withdrawn again. On Robinhood Chain that position is usually a Uniswap v3 NFT, and the transfer is public, permanent and readable by anyone.

Verification is a transfer read, not a trust exercise. Find the liquidity pool position, confirm it now sits at the dead address, and check what share of the pool it represented when it moved. A position still held by the deployer wallet is not burned, whatever an announcement says.

Permanence cuts both ways. Nobody can pull that liquidity, including the team — and nobody can migrate it or top it up either. A burn also says nothing about price, about supply held elsewhere, or about what the token contract lets you do after you buy.

A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.
Where you'll see it on Locksley

Burn state renders in the Liquidity panel on every token page, next to lock state. LP burned lists tokens whose pool position sits at the dead address.

Locks vs LP burns works through the permanence-versus-flexibility trade, and read a liquidity lock in 60 seconds teaches the same reading habit for a liquidity lock.

Frequently asked questions

Is an LP burn the same as a liquidity lock?

No. A burn is one-way: the position goes to an address with no owner and stays there. A lock holds the position until a release timestamp, after which whoever set it can withdraw. Burns trade all future flexibility for permanence; locks keep the option and put a date on it. Both are on-chain facts you can read yourself.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.