What is a liquidity lock — and what it does not protect you from

A liquidity lock deposits a pool's LP tokens into a contract that will not release them until a set date. It stops one thing: the creator withdrawing the paired asset and leaving holders with nothing to sell into. It does not stop a creator dumping their own tokens, a mint authority, a sell tax, or the lock expiring.

Those four exceptions are why this page exists. A lock badge is one of the most over-read signals in memecoin trading, and the gap between what it proves and what people take it to prove is where a lot of money goes.

What is actually being locked

When someone creates a pool, they deposit two assets — the new token and a paired asset such as SOL, ETH or a stablecoin — and the automated market maker issues them a claim on that deposit. On a Uniswap v2-style pool that claim is a fungible LP token. On Uniswap v3 and v4 it is a position NFT. On Solana's Raydium-style pools it is an SPL LP token. Whatever its form, it is the key to the pool: whoever holds it can withdraw the underlying assets in proportion.

A lock takes that key and puts it in a contract with a timestamp. Until the timestamp passes, the withdrawal function reverts for everybody, including the person who deposited it. After it passes, the original owner can claim it back and do whatever they like.

That is the entire mechanism. It is not custody of the token supply, not a guarantee about the token's code, and not any kind of audit. It is a time lock on one specific withdrawal right. If you are unclear on what the pool itself is doing, how memecoin liquidity pools actually work covers the underlying mechanics.

Locking versus burning

There are two ways to remove a creator's ability to pull liquidity, and they are not the same commitment.

Burning sends the LP tokens to an address nobody controls — 0x000000000000000000000000000000000000dEaD or the zero address on EVM chains, the standard incinerator address on Solana. It is permanent and requires no trust in any third party. It is also irreversible in ways that occasionally hurt: burned v3 and v4 positions can leave nobody able to manage or migrate liquidity if the pool later needs to move, and any fees accruing to that position may become unclaimable depending on how the burn was done.

Locking uses a third-party contract with an unlock date. It is reversible by design, which is the point — a project that intends to migrate liquidity to a new pool or a new chain needs to be able to. The cost is that you are now trusting the locker's contract as well as the creator, and you have an expiry date to track.

Neither is strictly safer. LP burning vs LP locking works through the specific scenarios where each is the better choice, including why a burn on a concentrated-liquidity position is not the clean commitment it looks like.

How to verify a lock yourself

Do not accept a lock as verified because a website says so. The check takes a couple of minutes.

Start by finding the pool address for the pair you intend to trade, from the DEX interface or from a screener. Then identify the LP claim that pool issues — the LP token contract on a v2-style pool, or the position NFT and its token ID on v3 and v4.

Then look at who holds it, on the chain's explorer. You are looking for one of three answers. If it sits at a burn address, the liquidity is permanently unwithdrawable. If it sits in a locker contract, open that contract and read the unlock timestamp for this specific position — a locker holding thousands of positions tells you nothing until you find yours. If it sits in an ordinary wallet, the liquidity can be removed right now, whatever the project's marketing says.

Four details people skip, all of which change the answer:

What proportion is locked. A creator can lock 10% of the LP and hold the rest. The lock is real, the protection is not. Compare the locked amount against the pool's total supply of LP claims, not against a number in an announcement.

The unlock date, in your calendar. A 30-day lock on a token you plan to hold for three months is a scheduled event, not a safeguard.

Whether the position is in range. On concentrated-liquidity pools, a locked position can be set to a price range the market has already left, in which case it contributes no depth at all while still displaying as locked liquidity. Check the range, not just the lock.

Who can claim accrued fees. Most lockers separate the principal from the trading fees a position earns, and let the depositor claim the fees while the principal stays locked. That is normal and usually disclosed, but it means a locked position is still generating income for someone, and you should know for whom.

What a lock length actually signals

Honestly: less than people think, and it is worth being precise about what it does signal.

Lock duration is a costless commitment for anyone who never intended to pull liquidity in the first place. A creator who plans to sell their own allocation loses nothing by locking the LP for ten years, because the LP was never their exit route. That is the asymmetry: long locks are cheap for both honest and dishonest creators, which limits how much information the number carries.

What it does tell you is something about intent to persist. A lock shorter than the project's own stated roadmap is a genuine inconsistency worth asking about. A lock that expires in days, on a token being marketed as a long-term community project, is a contradiction between what someone is saying and what they have committed to on-chain, and that contradiction is the actual signal — not the number itself.

The most useful reading of lock length is comparative and unglamorous: it tells you whether the creator has done the minimum that every other launch does, and nothing more.

Venue-enforced locks are stronger than voluntary ones

The most reliable locks in 2026 are the ones the creator never had a choice about, because the launchpad enforces them at deployment.

Pools.trade, launched by Uniswap Labs on 5 August 2026, deploys every token into a standard Uniswap v4 pool with permanently locked, creator-unremovable liquidity; its 0.25% LP fee autocompounds back into that position rather than being paid out. hood.fun runs a bonding curve and then auto-migrates into a locked Uniswap v3 pool. pump.fun migrates the full LP atomically to PumpSwap at its graduation threshold. Pons.family has no bonding curve and no migration at all — fixed supply, pool live from block one, buys and sells against the same pool forever, so there is no migration step to fail or front-run.

The practical consequence is that on some venues, "can the creator pull the liquidity" is answerable from the venue alone. Ask that question before you start reading contracts — it is often the cheapest check available. What Pools.trade is and how its two launch modes differ covers the mechanism in full.

Venue enforcement removes the trust in the individual creator. It does not remove trust in the venue: Noxa's tokens were fine while Noxa itself halted launches on 11 July 2026 and went dark two days later.

What a lock does not protect you from

This is the section the rest of the article exists for.

A creator selling their own token allocation. This is the big one. If a deployer holds 15% of supply and sells it into the pool, every holder eats the impact, the lock is untouched, and no rule has been broken. The pool keeps functioning exactly as designed while the price falls through it. Locked liquidity actually guarantees the sell has somewhere to land. Read the holder distribution separately.

A mint authority. If new supply can still be created, the pool's depth is irrelevant. Someone mints, sells into your locked liquidity, and the lock does nothing but hold the door open. On Solana this is a two-field check — see mint authority and freeze authority on Solana; on EVM chains it is an owner-callable mint function in the source.

A honeypot or a sell tax. A lock says the pool will remain funded. It says nothing about whether your transfer to that pool will succeed. A transfer restriction, a blacklist, a freeze authority or a sell tax raised to 99% after you buy all leave the locked liquidity untouched and you unable to reach it. What a honeypot token is and how detection actually works covers the variants.

Expiry. Locks end. A token that was locked when you bought it may not be locked when you check next month, and nothing notifies you.

The token going to zero on its own. Most memecoins lose most of their value without anyone doing anything malicious. A lock has no bearing on that outcome, which is the most likely one.

What this doesn't tell you

Every check described here is a snapshot of on-chain state at the moment you look. Positions get transferred, lockers get migrated, ranges drift out of the market and unlock dates arrive. Re-check before a second buy rather than trusting your first answer, and treat any lock badge — including the one on this site — as a claim about one variable, dated to when it was read.

There is also no lock quality standard. "Locked liquidity" is a description of a transaction, not a certification, and the strength of any given lock depends on the locker's contract, the proportion locked, the term, and the position's range. Two tokens can both display as locked and offer completely different protection. The full workflow around this check is in how to spot a memecoin rug pull before you buy.

Frequently asked questions

Does locked liquidity mean a token cannot rug?

No. It means one specific rug — the creator withdrawing the pool's paired asset — is off the table until the lock expires. The creator can still sell their own allocation, mint new supply if that authority exists, or change a sell tax. Those are all rugs by any practical definition.

How long should liquidity be locked for?

There is no correct number, and duration is a cheap signal because a creator who never intended to pull liquidity loses nothing by locking it for years. What is worth checking is consistency: a lock that expires well before the project's own stated plans is a contradiction worth asking about.

Is burning liquidity better than locking it?

Burning is a stronger commitment because it is irreversible and involves no third-party contract. That is also its weakness — a burned position can never be migrated or managed, and on concentrated-liquidity pools that can strand liquidity in an unusable range. Neither is universally safer.

How do I check a liquidity lock myself?

Find the pool address, identify the LP token or position NFT it issues, and check who holds it on the chain's explorer. A burn address means permanent. A locker contract means you need to read the unlock timestamp for that specific position. A personal wallet means the liquidity is removable now.

Can a locked liquidity position still earn fees for the creator?

Usually, yes. Most lockers hold the principal but let the depositor claim accrued trading fees. That is standard and normally disclosed, but it means a locked position is still producing income for someone, so read the locker's terms rather than assuming the position is fully dormant.

---

Lock the liquidity, then say what the lock does not cover

If you are launching, this is the one commitment a buyer can verify without taking your word for anything. Team Finance liquidity locking — built by TrustSwap, which also builds Meme Central — holds LP tokens for a fixed term on Ethereum, Robinhood Chain, Polygon, Base and BNB, and the lock surfaces as a verified badge on your token's page in the Meme Central launch feed. It works for a token from any launchpad, including after launch. It will not stop you selling your own allocation, it does not touch your mint authority, and it ends on the date you set — so publish that date rather than letting buyers discover it. How to lock liquidity covers the process step by step.

---

Nothing here is financial, legal or tax advice. Memecoins are extremely high-risk: most lose most of their value, and the majority of tokens launched never reach a decentralised exchange at all. Never spend money you cannot afford to lose entirely. Meme Central does not recommend any specific token. Data described as Meme Central's own reflects tokens indexed by Meme Central and is not whole-market data.