New projects often tout "LP locked" or "LP burned," making you think funds are safe and cannot be withdrawn. The core difference: Locking means "temporarily held, returned upon expiration," while Burning means "permanently discarded, never retrievable." From the perspective of preventing sudden withdrawal, burning is more thorough and harder to reverse than locking.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Here are 3 steps to understand these two mechanisms and verify project security.
Step 1: First understand what LP tokens are and why they enable "liquidity withdrawal"
LP tokens are the receipts you receive after providing liquidity on a DEX (decentralized exchange). They represent your ownership share of the funds in the liquidity pool. The holder of these tokens has the right to redeem a proportional share of both assets in the pool.
In other words, whoever holds the project's LP tokens can withdraw the corresponding proportion of liquidity from the pool at any time. A "rug pull" – where the project team suddenly drains the pool – relies precisely on this authority from owning LP tokens.
Therefore, the core factor in assessing a project's safety is: Does the address controlling the LP tokens have the power to move them?
Step 2: Deconstruct "Liquidity Locking" – a time-bound promise
What to do: Understand that locking means depositing LP tokens into a "third-party locking contract" with a set unlock time.
How it works:
The project team transfers LP tokens into the locking contract. Until the lock period ends, no one can withdraw them (including the team itself).
After expiry, the LP tokens are returned to the project's designated wallet (the beneficiary). At that point, if the team hasn't yet disappeared, they can lock again; if they want to run, they can withdraw all liquidity immediately.
Locking does not equal 100% security. Its limitations are clear:
No protection after the lock period expires: Common lock periods range from 6 months to 1 year. If the lock period is extremely short (e.g., 1 week), it's nearly the same as no lock.
May only lock a portion of liquidity: Claiming "LP locked" might mean only 20% is locked, while the remaining 80% of LP tokens are still held by the team. They can withdraw that 80% anytime, with the same effect.
Possible emergency unlock backdoor: Some locking contracts have an "emergency withdrawal" function that allows an admin to forcibly retrieve LP tokens even during the lock period.
When you've done this: You understand that locking is "handing control over to time," and you know to verify the lock duration, the proportion locked, and whether there's any permission to unlock early.
Step 3: Deconstruct "LP Burning" – an irreversible permanent renunciation
What to do: Understand that burning means sending LP tokens to a "black hole address" (an address no one controls). Once done, this operation is irreversible.
How it works:
A black hole address is an address without a private key; tokens sent there can theoretically never be retrieved.
After burning, the project team completely renounces ownership of that portion of liquidity. Since they can't retrieve it themselves, they can't "withdraw" it either.
Burning is "harder to suddenly withdraw" than locking:
No expiration date: There's no risk of the team withdrawing after a deadline – it's permanent.
No going back: After locking expires, the team can choose to re-lock, but after burning there is no choice; the funds are permanently locked in the pool.
But burning also has limitations:
Probably only a tiny portion was burned: Just like with locking, the team might have burned only a very small share of LP tokens, keeping the majority in their own hands.
Fees could become unclaimable: In some AMM mechanisms, burning LP tokens may also make the trading fees generated by that share unclaimable. While this doesn't affect security, it's a capital efficiency issue.
Comparison Summary of the Two Mechanisms
| Comparison Dimension | Liquidity Locking | LP Burning |
|---|---|---|
| Core action | Deposit LP tokens into a timelocked contract; can be retrieved after expiry. | Send LP tokens to a black hole address; keys are permanently lost. |
| Can it be withdrawn? | Not during the lock period, but possible after expiry. | Never, because the ownership certificate has been destroyed. |
| Risk points | After expiry, the team can withdraw; lock may be short, locked amount small; possible early-unlock backdoor. | Only a tiny fraction of liquidity was burned; after burning, market-making strategies cannot be adjusted flexibly. |
| Which is harder to suddenly withdraw? | Hard during the lock period, but risk returns upon expiry. | Harder – because ownership of that liquidity is permanently renounced. |
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
How to verify operations correctly?
Next time you see a new project claiming "LP locked" or "LP burned," don't just rely on the wording. Go on-chain and verify using the checklist below:
Verify the ratio locked/burned: What percentage of total LP tokens has the project actually locked or burned? Locking only 5% is not much different from doing nothing.
Verify the locking platform: Are they using a mainstream, verifiable locking service (like Uniswap's official locker or a well-known third-party locker)? An opaque locking link is likely fake.
Verify the lock duration: If they claim "locking," when is the unlock date? Over 6 months is basically acceptable; anything under 1 month is essentially no lock at all.
Verify contract permissions: Check whether the project contract retains advanced permissions such as "minting," "changing tax," or "blacklisting." Even if LP tokens are safe, these permissions can still drive the token price to zero.
Screenshot the results of these four checks. If the project only mentions "locking" in promotional materials but provides no verifiable on-chain link, or the link points to an obscure, unheard-of platform, treat it as a high-risk signal directly.
