Locking and burning liquidity solve the same problem differently. A lock holds the pool position until a release date you set, and can be withdrawn after it. A burn hands the position to an address nobody controls, permanently. Choose a lock if the pool may need to move again; choose a burn if it never should.
Lock vs burn liquidity: the decision table
| Dimension | Liquidity lock | LP burn |
|---|---|---|
| What happens to the position | A locker contract holds it until a release timestamp | It goes to the dead address, which has no keys |
| Reversible | Yes, after the release date, by whoever holds withdrawal rights | No |
| What you read to verify | Position, share of pool, owner, release timestamp | Position ownership: the dead address |
| Decision left open | Extend, withdraw, or let it expire | None |
| Trading fees the position earns | Collectable by the owner throughout the term | Abandoned — nobody can ever collect them |
| Cost (as of August 2026) | $150 per liquidity lock through Team Finance, plus gas in ETH | Gas in ETH only |
| What a buyer sees | A date, a share of the pool, a countdown | A permanent state, no date |
What each mechanism actually does
On Robinhood Chain most liquidity sits in Uniswap v3 positions — NFTs rather than fungible LP tokens. That detail shapes both mechanisms.
A liquidity lock moves the position into a locker contract that will not release it before a timestamp fixed at locking. Team Finance locks run on TrustSwap's own contracts, so Locksley reads that state rather than a project's word for it.
An LP burn sends the position to the dead address instead. Nothing releases it, because nobody is left to. The liquidity pool keeps trading; only the right to pull it out is gone.
How you verify each one
A lock is four readings: which position, what share of the pool, who can withdraw, and when. The walkthrough is read a liquidity lock in 60 seconds; locked at birth lists tokens locked at pool creation.
A burn is one reading: who owns the position now. If the answer is the dead address there is no countdown, because there is no future event. LP burned lists tokens whose positions ended up there.
"No lock found" means we found none — not that none exists. Locksley does not yet index every locker.
As of —pending, —pending of new Robinhood Chain launches locked liquidity at creation, per Locksley's contract reads.
Where the trade-off bites
The burn's strength and its cost are the same fact: it cannot be revisited. A pool needing a different fee tier, a new range, or a migration to another venue can do none of it once the position is burned.
And it gives up the income, which is the asymmetry most comparisons miss. A v3 position accrues trading fees only its owner can collect. A lock leaves that income alone — the owner keeps collecting for the whole term. A burn hands the position to an address with no keys, so the fees accrue to nobody. For a pool that trades at any volume this is the larger of the two costs, and the one nobody puts in the table.
The lock's cost is also its strength: it has a date, and a date is a scheduled event anyone watching will see coming — more information than no date, but something to manage rather than forget. What happens when a lock expires covers that day.
Cost separates them too. A burn costs gas. A lock costs $150 per use through Team Finance — our sister product, so take the price as a dated fact — as of August 2026, plus gas in ETH, and buys back the option to change your mind.
Who should choose which
Choose a lock if the pool is one of several, if you are still tuning ranges, or if you want extension as a repeated signal rather than one irreversible act. Lock liquidity on Robinhood Chain for a duration matching your committed roadmap.
Choose a burn if the pool is the pool, the range is settled, and you would rather answer "it is gone" than "here is the date." Fair launches with one position are the common case.
As a buyer, read the mechanism, not the label. A burn tells you the position will not be withdrawn; a lock tells you not before a specific timestamp, and what share of the pool it covers. Neither tells you what the price will do.
Frequently asked questions
Is burning liquidity better than locking it?
Neither is a grade; they answer different questions. A burn is permanent, needs no follow-up, suits a settled single pool — and permanently abandons the trading fees the position earns. A lock is time-bound, reversible after its release date, keeps that income collectable throughout, and suits a project that may migrate, re-range, or add venues. Both are verifiable on-chain, and neither says anything about a token's price, team, or supply.
Can the same liquidity be locked and burned?
Not the same position. A burned position has no owner left to place it in a locker; a locked one is still owned by whoever holds withdrawal rights. A project running several positions can burn one and lock another, so read what share each state covers.
“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.
How to check a liquidity lock in 60 seconds
How to check a liquidity lock on Robinhood Chain in under a minute: read the source contract, the locked share, the owner and the release date.
Read nextWhat happens when a liquidity lock expires
What happens when a liquidity lock expires on Robinhood Chain: nothing automatic — the pool position simply becomes withdrawable by whoever owns it.
See it liveLiquidity locks vs LP burns
A lock holds a pool position until a release date; an LP burn gives it up for good. Both are verifiable on-chain, differently. How to choose and read each.
See it liveHow to lock liquidity, step by step
How to lock liquidity on Robinhood Chain in six steps: find your Uniswap v3 position NFT, set a release date, approve, confirm. Costs, gas and what shows after.
Do itLock liquidity on Robinhood Chain
Lock liquidity on Robinhood Chain through Team Finance: the Uniswap v3 position is held until a timestamp you set. Steps, price, and what a lock proves.
