Locking liquidity on Solana

What you are actually locking

The mechanism is simpler than the vocabulary suggests. When you deposit tokens and SOL into a pool, you receive LP tokens representing your share of it. Those LP tokens are the claim ticket: holding them lets you withdraw the underlying liquidity at any time.

Locking means putting that claim ticket somewhere you cannot reach for a defined period. Burning means destroying it outright. In both cases the pool is untouched and continues to function normally. What changes is whether the position can be removed, and by whom.

That distinction is why the phrase "locked liquidity" is slightly misleading. The liquidity is not locked; the ability to take it back is.

What it proves

Exactly one thing, and it is worth stating precisely: the person who created the pool cannot withdraw its liquidity for the duration of the lock.

That single guarantee eliminates the most feared failure mode in this category, where a pool is drained and holders are left with tokens they cannot sell into anything. It is a real and meaningful protection, and it is the reason the check has become standard.

It also has a second effect that is more subtle and arguably more valuable. A team that has locked its position has removed its own cheapest exit, which is a costly signal in the economic sense. It says something about intent that a statement of intent cannot.

What it does not prove

Almost everything else, and treating the lock as a general safety certificate is how people get caught.

• It does not stop selling. Anyone holding tokens can still sell into the pool, including the team, and heavy selling collapses the price with the liquidity fully locked.
• It does not disable mint authority. If new supply can be created, locked liquidity does not protect you from it.
• It does not disable freeze authority. A separate permission with separate consequences, covered in the sell failure guide.
• It does not guarantee depth. A tiny position locked forever is still a tiny position.
• It does not prevent abandonment. The pool stays, the project can still stop.

The useful mental model is that locking removes one specific exit while leaving the others open. It belongs on a checklist rather than at the end of one.

Lock or burn?

Burning is the stronger signal and the more expensive commitment, because it forfeits both the position and any fees it would have earned. Locking keeps the door open, which matters if you may need to migrate liquidity to a different venue later. Neither is universally correct; what matters is that the choice is deliberate and stated.

Choosing a duration

The principle is that the lock has to outlast the window in which pulling liquidity would be tempting or profitable. That window is longer than most first-time launchers assume.

Very short locks are worse than no lock at all in one specific way: they publish a date. A position unlocking in two weeks tells every holder exactly when to be gone, and sophisticated ones will act several days before that. You have converted an open-ended situation into a countdown, and the countdown does the damage.

Longer terms are read as more credible for the obvious reason, and the credibility is roughly proportional to how much of the token's plausible lifetime the lock covers. Whatever you choose, announce the expiry rather than only the fact of locking, because buyers will find the date anyway and finding it themselves reads worse than being told.

A second consideration on duration is what happens at the end of it. An unlock is an event whether you intend it to be or not, and it will be noticed. Teams that plan for this decide in advance what happens on that date and say so early: extend the lock, burn the position, or migrate to a deeper pool with the same commitments. Teams that do not plan for it arrive at the date with no announcement prepared, which reads as the worst of the three options even when nothing is wrong. The date is known to everyone from the moment you lock, so the only variable you control is whether you are ready for it.

How buyers actually verify it

Announcements are not evidence, and experienced buyers check rather than read. The check is straightforward: find where the LP tokens went.

If they sit in a burn address, the position is unrecoverable and that is the strongest possible state. If they sit in a locking contract, the terms including expiry are generally readable on-chain. If they sit in an ordinary wallet, nothing is locked no matter what has been posted, and this is the case that actually catches people out.

Because this check is quick and public, the practical advice for a team is to make it easy: publish the transaction and the address, so that anyone doing thirty seconds of diligence lands on evidence rather than on ambiguity. The launch failure guide covers how much of week one is decided by exactly these small friction points.

One further nuance about verification is worth knowing because it is where announcements and reality most often diverge. Locking a position and locking all of it are different things. A team can lock a portion of its LP tokens, publish that transaction honestly, and retain the ability to withdraw the rest, and nothing about the announcement would be false. Anyone checking properly compares the locked amount against the total supply of LP tokens for that pool rather than confirming that a lock exists. If you are on the team, publishing both numbers pre-empts the question entirely; if you are evaluating someone else's token, it is the second thing to check after finding the lock at all.

Where it sits in launch order

Locking is a step in a sequence rather than a milestone on its own, and doing it out of order wastes its signalling value.

Seed the pool with enough depth that a realistic buy does not move the price several percent, because locking a thin pool locks a thin pool. Disable mint and freeze authority if they are not needed, since a locked pool alongside live mint authority is an odd combination that invites questions. Then lock, publish the evidence, and only after all of that spend anything on attention. Bringing visitors to a token whose foundation is still unfinished converts interest into a decision to pass, which is the most expensive kind of traffic there is. The exact SOL cost of that last step is visible in the console on the home page before anything runs.