How to Lock Liquidity on a Solana Token

“Liquidity locked” is the claim every new token makes and the one buyers most often get wrong. What a lock actually is on-chain, the three ways to do it, the order that matters — and how a buyer tells a real lock from a marketing line.

September 15, 2026 · ~8 min · For token creators

When you add liquidity to a Solana pool, the DEX hands you back LP tokens — receipts that let whoever holds them withdraw the underlying SOL and tokens whenever they want. A liquidity lock moves those receipts somewhere you cannot touch them for a defined period: a time-locked program, a dead address, or the DEX’s own lock position. That is the whole mechanism. There is no liquidity-lock flag on the token itself — the lock lives wherever the LP tokens went, which is exactly why buyers verify it on-chain rather than reading it off your website.

Lock, burn, or DEX position lock — the three real options

Burning is the cleanest promise a meme launch can make — no maturity date, no contract risk, nothing to take back. A time-lock suits projects that will legitimately need to migrate pools or deepen liquidity later, but it always asks buyers to trust a contract and a calendar where a burn asks them to trust nobody. Choose burn unless you can name the reason you need the LP back.

The order that matters

1. Create and seed the pool — pair the token against SOL (or a stable) and fund the position.
2. Receive the LP tokens into the deployer wallet — they land there automatically.
3. Lock or burn them immediately, in the same launch sequence — before you post the contract address anywhere.
4. Announce with the proof: the lock transaction or burn signature, the locker program address, and the unlock date if there is one.

The ordering mistake is announcing before the lock lands. “Liquidity locked” posted while the LP tokens still sit in your wallet is a lie buyers can watch you tell — the pool is pullable for every minute between the claim and the transaction. Lock first, then talk about it.

How buyers actually verify it

A real lock is a public on-chain fact, and that is what makes it worth doing: a buyer needs no trust in you at all. Their read, in order:

1. Where the LP tokens sit. In a known locker program, a dead address, or a DEX lock position — verifiable from the pool’s LP mint and the locker’s account. “Locked” with no locker address or burn signature to point to means nothing.
2. How much is inside. The amount locked over the pool’s total LP supply — the coverage percentage. Anything short of ~100% leaves a wallet holding withdrawable receipts.
3. For how long. The unlock timestamp, if there is one. A 7-day lock on a token marketed for months just schedules the pull.
4. Who the beneficiary is. When the lock matures, the LP returns to the beneficiary address. A lock paying out to a fresh deployer-side wallet is decoration.

None of this requires trusting the project’s claims — scanners and block explorers surface it from the chain directly, which is why sophisticated buyers go quiet when a team cannot produce the lock transaction on request.

The patterns that fake it

The phantom locker. Marketing says locked, but no locker program, burn signature, or DEX lock position exists — the LP sits in the deployer wallet. The most common rug setup of all, and the easiest to catch: ask where the lock lives.

The fake locker. A “lock” program the deployer controls — technically a contract, functionally their own wallet with extra steps. The locker must be a program buyers recognize and can read; a custom one-off program proves nothing.

The partial lock. Some LP locked for show, the rest held to pull later. Coverage percentage is the only number that matters.

The unlocked second position. LP locked on one position while the deployer seeds a second, unlocked position on the same pool — the lock is real and the rug still works. Scanners total LP held outside lockers across all positions.

The short cliff. A lock measured in days on a token marketed in months — the pull is scheduled, not prevented.

A lock answers one question

Locked liquidity settles exactly one thing: the pool cannot be pulled right now. It says nothing about a live mint or freeze authority, a dev wallet holding half the supply, or sell pressure draining the pool legitimately. The tokens that read clean clear the lock and the authority flags and the distribution — buyers’ scanners read all three on the same page, and a perfect lock beside red flags elsewhere is a detail, not a rescue.