TrustDex › Guides › Liquidity locks
Liquidity locks — what they prove, and what they don't
"Liquidity locked" is one of the most quoted safety badges in token trading — and one of the most misread. A lock closes exactly one door, for exactly as long as the timer says, and nothing more.
Every trading pool on a DEX has an escape hatch: whoever supplied the liquidity can take it back out. A liquidity lock exists to bolt that hatch shut for a while. It's a real, verifiable commitment — but it's a narrow one, and scammers have learned to dress up weak locks as strong ones. This guide walks through what locking actually does mechanically, the games played with duration and percentages, how locks compare with burning LP outright, and how to read a lock line in a risk scan without being fooled by the word alone.
Look up a token's lock status
Drop in a Solana or EVM contract address to see how its liquidity is held.
What a lock actually is: custody on a timer
When someone deposits tokens into an AMM pool, the pool hands back LP tokens — transferable receipts that entitle the holder to withdraw a share of everything in the pool. Owning the LP tokens is owning the exit. Locking liquidity means transferring those receipts into a third-party contract (a "locker") that refuses to release them before a chosen date. The deployer keeps future ownership but loses present control: until the timer runs out, they physically cannot redeem the LP tokens and drain the pool.
That's the entire mechanism. Nothing about the token itself changes — no authority is renounced, no supply is touched. The lock is a constraint on one specific set of receipts, held by one specific contract, until one specific timestamp. Each of those three details can be weak on its own, which is why "locked" as a bare adjective tells you almost nothing.
Duration and percentage games: how a weak lock wears a strong badge
The cheapest way to wear the locked badge is to lock briefly. A team can park its LP tokens for thirty days, harvest the credibility while attention and volume peak, and then withdraw everything the moment the cliff passes — often on a quiet weekend, long after screenshots of the lock stopped circulating. From the buyer's side the token was "locked" right up until it wasn't.
So the question is never whether liquidity is locked but until when. A lock that outlives any plausible trading horizon — a year or more — is a meaningfully different commitment from one measured in weeks. Some lockers also support extending a lock but never shortening it; a team that keeps rolling the date forward is showing ongoing intent, while a short fixed cliff sitting a few days away should be read as a scheduled unlock event, not a safety feature. If you hold through an unlock date, you're trusting the team's restraint, because the mechanical guarantee is gone.
Locks apply to whatever quantity of LP tokens was deposited — not automatically to all of them. A team can lock six of every ten LP tokens, advertise the lock, and keep the other four liquid in a wallet. Those unlocked receipts can be redeemed at any moment, and pulling 40% of a pool is plenty to crater a thin market while technically leaving the "locked liquidity" untouched.
Reading a partial lock takes one extra division: what share of the pool's total LP supply actually sits inside the locker? Anything well short of the full amount leaves a working escape hatch, and the smaller the pool, the more damage the free remainder can do. A high percentage locked for a long period is the combination that actually forecloses the withdrawal rug; a fraction locked for a month is theater with a receipt.
Rule of thumb: a lock's strength is the product of three numbers — the fraction of LP inside it, the time left on the clock, and the credibility of the contract holding it. If any factor is near zero, the whole product is near zero.
Who's holding the keys? Locker credibility varies
A locker is just a contract, and contracts differ. Established locking services have audited, widely reused code, public dashboards, and no function that lets anyone — including their own operators — release deposits early. At the other end sit obscure or self-deployed "lockers" that are effectively the team's own contract wearing a costume: an owner-only withdraw function, an upgrade path, or an emergency escape clause means the lock is a promise, not a mechanism. There have also been incidents where genuine third-party lockers were themselves exploited, taking every project's deposits with them.
You don't need to audit bytecode to apply the lesson. Check whether the lock lives at a recognizable, battle-tested service, and be suspicious of a lock at an address nobody has heard of. An unverifiable locker deserves the same trust as no locker at all.
Locked vs burned LP
The alternative to locking is destroying the receipts entirely — sending LP tokens to a burn address so no one can ever redeem them. The two approaches solve the same problem with different trade-offs:
| Question | Locked LP | Burned LP |
|---|---|---|
| Can the pool be pulled? | After expiry, yes | Never |
| Anything to monitor? | Unlock date, locker contract | Nothing ongoing |
| Third party to trust? | The locker service | None |
| Team can recover funds later? | Yes — sometimes legitimately needed | No, ever |
| Fee earnings on the position | Usually claimable by the team | Forfeited with the receipts |
Neither is universally "better." A project with real long-term plans may reasonably prefer a long lock, keeping the option to migrate liquidity to a new pool or DEX someday. For a throwaway meme launch, though, burning answers the question permanently, and permanence is worth a lot when the team is anonymous. Our companion guide on LP tokens and burned liquidity goes deeper on verifying a burn.
The doors a lock leaves open
Here's the limit that gets people hurt: a lock constrains the pool, not the token. It cannot stop a deployer with live mint authority from printing fresh supply and selling it into that very same locked pool. It cannot stop insiders who hold a third of the supply from dumping it. It cannot prevent honeypot-style transfer restrictions, a migration to a new unlocked pool that drains attention from the old one, or a plain abandonment where the chart bleeds out with the liquidity sitting safely — and pointlessly — locked. The anatomy of a rug pull guide catalogs these routes; liquidity withdrawal is only one of them.
This is why a locked badge on an otherwise ugly token changes little. Concentrated holders, unrenounced authorities, or a suspicious launch pattern all operate through doors a locker never touches.
Reading the lock line in a scan
When a risk scan reports on liquidity, translate the output into the three questions this guide keeps returning to. How much of the pool's LP supply is committed — all of it, or a fraction? Committed how — burned forever, or locked to a date, and if a date, how far away? And held where — a known locker with a track record, or an address that could be anything? A scan that shows burned LP or a near-total, long-dated lock at a reputable service has closed the withdrawal door convincingly. Anything mushier means the door is ajar, whatever the marketing says. Then keep reading the rest of the report, because as the previous section showed, this is one field among several that have to be clean together. The full walkthrough lives in how to read a token risk scan.
Check the whole picture, not just the lock
One scan covers liquidity status, authorities, and holder concentration together.
Frequently asked
What does it mean when a token's liquidity is locked?
The team has deposited its LP tokens — the receipts that allow withdrawing the pooled funds — into a locker contract that will not release them until a set date. While the lock holds, the team cannot pull the pool. It says nothing about minting, dumping held supply, or what happens after the unlock date.
Is a token with locked liquidity safe to buy?
Safer against one specific attack, not safe in general. A lock only prevents the LP-withdrawal rug. The team can still sell a large token allocation into the pool, and if mint authority is live they can print supply. Treat a lock as one closed door in a house with several.
What happens when a liquidity lock expires?
The LP tokens become withdrawable by whoever deposited them, immediately and without any further announcement. Many pulls happen quietly at or shortly after expiry, which is why the unlock date matters as much as the word "locked" itself.
Is burned LP better than locked LP?
Burning is stronger on permanence: the withdrawal claim is destroyed forever, with no expiry to track and no custodian to trust. Locking is reversible by design, which suits projects that legitimately need their liquidity back later. For an anonymous meme token, burned LP removes more doubt than a short lock does.
Can a liquidity lock be faked?
The claim can be. Teams have pointed at the wrong pool, locked a trivial fraction of LP while keeping the rest, or used obscure locker contracts with owner backdoors. Verify which pool is covered, what percentage of LP sits in the locker, the unlock date, and whether the locker itself is a known audited contract.