How to Lock Liquidity for a Token Launch: A Practical LP Lock Guide

To lock liquidity for a token launch, you deposit the receipt for your DEX liquidity position — the LP tokens on a constant-product pool, or the position NFT on a concentrated liquidity pool — into a contract that will not release it until a set date or condition. Once it is there, nobody, including your own team, can withdraw the pool before the unlock. That is the whole point: a liquidity lock turns "we promise not to pull the pool" into something anyone can verify on-chain.

Doing it is technically simple. Doing it well is not. The decisions that matter are what kind of lock to use, how much of the position to lock, for how long, and how to keep enough flexibility to manage liquidity after launch. Get those wrong and you either fail the checks buyers run in the first minutes of trading, or you lock yourself out of your own market.

Why Liquidity Locks Matter to Buyers

When a new token pool goes live, the single fastest way for a dishonest deployer to take money is to remove liquidity: withdraw the paired asset (ETH, USDC, SOL) and leave buyers holding a token with no market. This is the classic rug pull, and it is the reason token scanners, trading terminals and experienced traders check liquidity status before they buy anything.

A lock answers one question for them: can the people who created this pool take it away tomorrow? If the answer is "yes, a single wallet holds the LP position and it is not locked," many buyers simply skip the token. Some trading tools surface this as a warning label right next to the chart.

For a legitimate project this is a credibility problem, not a security one. You were never going to pull the pool, but you have to prove it to people who have no reason to trust you yet. Locking is the cheapest proof available.

Step 1: Understand What You Are Actually Locking

The thing that represents ownership of a DEX position differs by pool design, and it changes how the lock works.

Pool type	What represents the position	What you lock	Practical note
Constant-product AMM (Uniswap v2-style and forks)	Fungible LP tokens	LP tokens, fully or partially	You can lock a portion and keep the rest liquid
Concentrated liquidity AMM (Uniswap v3-style)	A non-fungible position NFT per range	The NFT for each position	All-or-nothing per position; a locked range cannot be adjusted
Order-book or hook-based designs	Varies by protocol	Depends on the protocol	Check whether mainstream lockers support it at all

The concentrated liquidity case deserves attention. A locked v3 position keeps its price range for the life of the lock. If the market moves outside that range, the position stops providing liquidity, and you cannot move it until the lock ends. Some locker services let you collect trading fees from a locked position, but most do not let you change the range. We cover the range decisions themselves in our guide to concentrated liquidity mistakes at launch.

Step 2: Choose the Type of Commitment

There are four common ways to commit liquidity. They are not equally good for every project.

Time lock in a third-party locker. The most common choice. You deposit LP tokens or the position NFT into a well-known locker contract with an unlock date. Scanners and terminals recognise the major lockers and read the lock automatically, which is the main advantage. The trade-offs: you depend on that contract's security, and some lockers charge a fee, either flat or as a percentage of the locked position. Check current terms yourself before committing.

Time lock in your own contract. You deploy a simple timelock that holds the position. This avoids third-party fees and dependency but has a real cost: scanners may not recognise it, so buyers see "unlocked" until someone reads your contract. If you go this way, verify the source code, keep it minimal, and publish the address prominently.

Burning the LP position. Sending LP tokens to a dead address makes the liquidity permanent. It is the strongest possible signal and the least flexible. You can never migrate that liquidity to a new pool, a new DEX version or a new chain, and you can never recover the paired asset for anything else. Burning suits some community and fair-launch tokens. For a project that expects to grow, list on centralised exchanges and work with market makers, it is usually a mistake.

Multisig custody with a published policy. Some teams hold the position in a multisig and publish a policy for what it can and cannot be used for. This is honest and flexible but weaker as a signal, because policies can be broken. It works better as a complement to a lock than as a substitute, for example a locked core position plus a smaller multisig-held position for active management.

Which should you pick?

Community or memecoin launch with no CEX plans: a long third-party lock, or a burn if the community expects it.
Venture-backed project planning CEX listings: a third-party time lock on the core position, with a documented reserve for active management.
Project with heavy technical scrutiny and its own security team: a custom timelock can work, but pair it with clear public documentation.

Step 3: Decide How Much to Lock

You do not have to lock everything, and locking everything is not always wise.

The useful split is between core liquidity, the base depth that guarantees there will always be a market, and working liquidity, which you or your market maker adjust as the market develops. Lock the core. Keep working liquidity in a multisig with a clear purpose.

Be transparent about the split. A buyer who sees that a large share of the pool is locked and the remainder sits in a disclosed treasury multisig has a clear picture. A buyer who discovers an undisclosed unlocked position later will assume the worst.

How large the core should be depends on the trades you expect to absorb. Our sizing method in how much liquidity a token needs at launch applies directly: define the trade size you want to serve without excessive slippage, then make sure the locked portion alone can serve it.

Step 4: Choose the Lock Duration

There is no standard duration, but a few principles hold.

Longer than the riskiest period. The first weeks after launch, and the dates of major token unlocks, are when trust is most fragile. A lock that expires just before a large investor unlock sends exactly the wrong signal.
Aligned with your vesting. If team tokens vest over a long schedule, a liquidity lock that ends far earlier looks inconsistent. Match the story your token vesting schedule already tells.
Extendable, not just renewable. Many lockers let you extend a lock before it expires. Plan to do so publicly, ahead of time. Watchers notice unlock dates, and an approaching expiry with no announcement creates avoidable fear.
Not so long that it traps you. If you expect to migrate to a new pool version, change the pair, or move the bulk of trading to a CEX, a multi-year lock on a single range can become dead weight. Lock in tranches with staggered expiries if you are unsure.

Step 5: Execute the Lock Cleanly

The mechanics are straightforward but sequence matters, because the window between adding liquidity and locking it is when buyers are watching.

Prepare in advance. Decide the locker, duration and amount before launch day. Test the full flow on a testnet or with a tiny position.
Add liquidity from the wallet that will lock. Ideally a multisig. Avoid transferring LP tokens between wallets after creation; it muddies the on-chain trail.
Lock immediately. The gap between pool creation and the lock should be minutes, not hours. Some teams lock in the same session as adding liquidity.
Verify the lock on-chain. Confirm the locker contract holds the position, the unlock date is correct, and the withdrawal address is the one you expect.
Publish it. Post the lock transaction, locker link, amount and unlock date in your docs, announcement channels and token listing profiles.

Step 6: Know What Buyers and Scanners Check

A lock is only useful if it passes the checks people actually run. Expect them to look at:

Percentage of LP locked or burned. Reported by most scanners as a single number.
Unlock date. A lock expiring soon is treated almost like no lock.
Who can withdraw. If the beneficiary is a single externally owned wallet, that is noted.
Other admin powers. A locked pool means little if the owner can still mint unlimited supply, change taxes or blacklist sellers. Liquidity locks are read alongside contract permissions, which is why audits matter as much as locks — see our guide to smart contract audits before launch.
Holder concentration. A locked pool next to a single wallet holding a large share of supply still worries buyers, because that wallet can drain the pool by selling.

That last point is often missed. Locking liquidity stops one kind of rug, not every way a market can collapse.

Common Liquidity Lock Mistakes

Locking a concentrated position with a narrow range. It looks impressive at launch and becomes useless once price leaves the range.
Burning liquidity, then needing it. Teams that later want CEX listings or a market maker often wish they had kept the paired capital.
Using an obscure locker. If scanners cannot read it, buyers see an unlocked pool.
Letting a lock expire quietly. Extend early, announce it, and avoid the rumour cycle.
Treating the lock as the whole trust story. Admin keys, supply controls and treasury disclosure matter just as much.

Liquidity Lock Checklist

Locked Liquidity Is a Floor, Not a Market

A locked pool guarantees that liquidity exists. It does not guarantee that the market is deep enough, that spreads stay tight across venues, or that price reflects real demand rather than a few large orders. That work happens on top of the lock: active liquidity management on DEXs, order books on centralised exchanges, and coordination between them.

That is the part Fibonacci Capital focuses on with token teams, from planning the launch pool through to market making once trading starts. If you are designing your launch liquidity and want a second opinion on the structure, talk to our pre-TGE team.