How to lock liquidity — and why buyers check

The Editor·9 min read·Updated 31 Aug 2026

How to lock liquidity step by step: what LP tokens are, choosing a term, how a buyer verifies the lock on-chain, and the two things it cannot protect.

Locking liquidity means sending the LP tokens from your pool to a time-locked contract you cannot withdraw from until a set date. You create the pool, receive LP tokens, approve them to a locker, choose a term, and lock. The result is a public, on-chain commitment that you cannot pull the pool. It does not stop you selling your own tokens.

What you are actually locking

When you add a token and a base asset — ETH, SOL, BNB, USDC — to an automated market maker, the pool issues you LP tokens. They are a receipt. Holding them entitles you to withdraw your share of whatever is in the pool at the time, and burning or transferring them transfers that claim.

This is the single most important thing to understand about a rug pull. The classic hard rug is not exotic: the creator holds the LP tokens, redeems them, takes the ETH or SOL out of the pool, and the token is left trading against nothing. Every buy that funded the pool becomes the creator's exit liquidity in one transaction. The mechanism is trivial and that is exactly why it is so common. If the concept of a pool is new to you, how memecoin liquidity pools actually work is the prerequisite.

A lock removes the creator's ability to do that for a defined period. You transfer the LP tokens into a locker contract with an unlock timestamp. Until that timestamp passes, nobody — including you — can move them.

Two things follow. First, the lock is only as good as the locker contract, so use one with a track record rather than something a Telegram contact deployed last week. Second, the lock is public: anyone can read the locker contract and see the amount, the token pair and the unlock date. That verifiability is the entire point. A promise on a website is a promise; a lock is a state change on a public ledger.

How to lock liquidity, step by step

  1. Create the pool first. Locking is a post-pool action. Add your token and your base asset to the DEX — Uniswap, PancakeSwap, Aerodrome, Raydium, whatever your chain uses — and confirm the LP tokens arrive in your wallet. Check the balance before you go further.
  2. Decide how much to lock. Locking 100% of the LP supply is the only version that means anything. If you lock 60% and keep 40%, you can still withdraw 40% of the pool, and a competent buyer will read the locker contract, see the partial amount, and treat the announcement as misleading. Partial locks are worse than no lock, because they invite a claim you cannot back.
  3. Choose a term. More on this below. Pick a date before you open the interface, not while you are staring at it.
  4. Approve the LP token to the locker. Standard ERC-20 approval on EVM chains. Approve only the amount you are locking rather than an unlimited allowance.
  5. Execute the lock. You will sign a transaction that transfers the LP tokens into the locker with your chosen unlock timestamp. Read the timestamp in the transaction before you sign — this is irreversible until it expires.
  6. Save the transaction hash and the locker page URL. You will be asked for it. Repeatedly.
  7. Publish it. Put the link in your pinned post, your site, your token profile. An unpublished lock protects buyers who look hard and nobody else.
  8. Set a reminder for the unlock date. Not for yourself — for the fact that your holders will notice it approaching. See below.

On Solana the shape is the same but the primitives differ: LP positions are pool-specific, some venues issue an LP mint you can lock and others use position NFTs. Confirm what your pool actually issues before assuming a locker supports it.

Choosing a lock term

There is no correct number, but there are clearly wrong ones.

A 30-day lock is close to worthless as a signal. It reads as a compliance gesture, and experienced buyers treat a short lock as a countdown rather than a commitment. If your term is a month, do not expect credit for it.

Six months to a year is the range where a lock starts changing how a token is read. It is long enough that the creator cannot treat the unlock as an exit plan and short enough to be a realistic commitment for a small project.

Multi-year or effectively permanent locks are a stronger signal and they cost you flexibility. If you ever need to migrate liquidity to a new pool version, change fee tiers, or move to a different DEX, you cannot. That is a real trade-off and it is worth thinking about before you pick a five-year term to look serious.

The alternative to locking is burning the LP tokens — sending them to an address nobody controls, which is permanent and unrecoverable. Burning is the stronger commitment and the more inflexible one. LP burning versus LP locking works through which suits which kind of project.

What a buyer sees when they verify it

Assume they will check, because the good ones do, and design the lock for that inspection.

A buyer verifying your lock reads the locker contract, not your announcement. They will look at four things: which token pair is locked (it must be your pool's LP token, not some other pair with a similar name), what fraction of the LP supply is locked, when it unlocks, and who the beneficiary is — the address that receives the LP tokens at expiry.

The failure modes are all in that list. A lock on the wrong pair. A lock covering a fraction of the LP supply while the announcement implies all of it. An unlock date three weeks out. A beneficiary address that is not the address holders have been told is the project's. Each of those is a common way a lock is presented as safety while providing very little.

Safety scanners and token pages surface locks automatically, and on Meme Central a verified lock shows as a badge on the token's page in the live launch feed. That badge is the thing a buyer sees before they read anything you wrote.

The two things a lock does not protect against

This is where most guides stop, and where the honest ones start.

A lock does not touch the creator's own token holdings. If you kept 15% of supply in a wallet, that 15% is entirely unaffected by locking the pool. You can sell all of it into the liquidity you just made unwithdrawable, and the price collapses, and the lock is still perfectly intact the whole time. This is a soft rug, and in 2026 it is far more common than the hard version precisely because the hard version has become easy to detect. Locked liquidity plus a large unlocked dev bag is a specific, recognisable risk shape — dev wallet tracking after a launch covers how buyers watch for it, and vesting your own allocation is the answer if you want to close the gap.

A lock expires. On the unlock date the LP tokens return to the beneficiary address and everything the lock prevented becomes possible again. Holders can read the expiry date as easily as they read the lock, and a token approaching an unlock with no announced plan tends to see selling into it. Decide well in advance whether you will extend, burn, or let it lapse, and say so publicly before anyone has to ask.

A lock also does not make the contract safe. A token can have locked liquidity and a mint function, a transfer tax, a blacklist, or a honeypot sell path. Those are contract properties and the lock says nothing about any of them. What a liquidity lock is and what it does not protect you from takes the buyer's side of the same argument.

Where locking fits in a launch

If you launched on a bonding-curve launchpad, you may have nothing to lock — the venue holds the funds and migrates liquidity itself, and some venues lock or burn it automatically as part of that migration. Check what yours actually does rather than assuming, because "liquidity is locked" and "liquidity is permanently unremovable by the creator" are different claims and both get made loosely.

If you deployed your own token and seeded your own pool, locking is the first thing to do after the pool exists and before you tell anyone the token is live. Announcing a launch and then locking looks like a response to pressure. Locking and then announcing looks like a plan. The rest of the sequence is in the token launch checklist.

Frequently asked questions

How long should I lock liquidity for?

Six months to a year is where a lock starts to function as a real signal. Thirty days reads as a countdown rather than a commitment. Multi-year locks are stronger but cost you the ability to migrate pools or change fee tiers, so choose the term against how likely you are to need that flexibility.

Can I unlock liquidity early?

No. That is the point of the mechanism — the locker contract enforces the timestamp and there is no early-withdrawal path for you or anyone else. If a locker advertises an early-unlock option, it is not providing the guarantee buyers think they are reading, and they will find out.

Does locking liquidity make my token safe?

No. It removes one specific attack — the creator draining the pool — and nothing else. Your own token allocation is untouched by the lock and can still be sold at any time. The contract can still have a mint function, a transfer tax or a broken sell path. A lock is one verifiable commitment among several, not a certificate.

Should I burn my LP tokens instead of locking them?

Burning is permanent and unrecoverable, which makes it the stronger signal and the more rigid choice. If you might ever need to migrate to a new pool version or a different DEX, burning forecloses that entirely. Locking with a long term gets most of the trust benefit while leaving an eventual decision open.

How does a buyer check whether liquidity is locked?

They read the locker contract or a scanner that surfaces it, and they check four things: the token pair, the fraction of LP supply locked, the unlock date and the beneficiary address. Any of those can undermine an announcement that sounded convincing, which is why publishing the transaction hash directly is better than describing the lock in words.


Lock your liquidity before you ask anyone to trust it

A liquidity lock is the one on-chain commitment a buyer can verify without trusting you. Team Finance — built by TrustSwap, which also builds Meme Central — locks LP tokens for a fixed term on Ethereum, Robinhood Chain, Polygon, Base and BNB, and the lock shows as a verified badge on your token's page in the Meme Central feed. It does not stop you selling your own allocation, and it expires on the date you set, so it is a commitment with an end rather than a guarantee.


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.

Not financial advice. Memecoins are extremely high risk.

·Community RulesMeme Central aggregates public launchpad data.