HANNISOL
Sign in
Token Security7 min read·Apr 25, 2026

Liquidity Locks Explained: Why They Matter and When They Don't

"Liquidity is locked" has become one of the most frequently cited trust signals in the Solana token community. You'll see it in Telegram groups, whitepaper summaries, and project announcements as a near-universal marker of legitimacy. Teams know buyers want to see it. So teams provide it. The proble

H
Hannisol Team

The signal everyone looks for — and misunderstands

"Liquidity is locked" has become one of the most frequently cited trust signals in the Solana token community. You'll see it in Telegram groups, whitepaper summaries, and project announcements as a near-universal marker of legitimacy. Teams know buyers want to see it. So teams provide it. The problem is that not all liquidity locks are equal, and the community's over-reliance on this single signal — without examining its specifics — has made it a tool for false reassurance as much as genuine security.

Understanding what a liquidity lock actually does technically, what the meaningful details are (duration, percentage, platform), and what it cannot protect against is essential for using it as an effective due diligence tool rather than a checkbox that provides unwarranted confidence.


What a liquidity lock is

When a project creates a liquidity pool on Raydium, Orca, or another Solana DEX, the deposited assets (typically some amount of SOL plus the project token) are represented by LP (Liquidity Provider) tokens. These LP tokens are proof of ownership of the underlying pool position — whoever holds the LP tokens can burn them to withdraw the corresponding assets from the pool.

A liquidity lock means that the LP tokens have been deposited into a time-locked contract that prevents them from being withdrawn until a specified future date. During the lock period, neither the project team nor anyone else can remove those LP tokens from the contract, and therefore cannot drain the underlying liquidity.

Without a lock, the project team can remove all liquidity in a single transaction at any time — this is the mechanic of a classic DEX rugpull. With a lock, the team is technically prevented from executing this attack until the lock expires.


Lock duration: the most critical variable

A liquidity lock's protective value scales directly with its duration. Here is how to think about different timeframes:

Lock durationEffective protectionInterpretation
Under 7 daysNoneEssentially meaningless — enough time for a pump-and-dump to complete before expiry
7 – 30 daysMinimalProvides some short-term reassurance but insufficient for any meaningful investment
1 – 6 monthsModerateShows some commitment; team has a defined responsibility period; still finite
6 – 12 monthsGoodCredible signal of intent to build; meaningful deterrent against quick abandonment
12+ months or permanent burnStrongMaximum commitment signal; "permanent" burn (sending LP tokens to a dead wallet) is the gold standard

The most important question about any lock is: when does it expire? If a project locked liquidity for 30 days three weeks ago, the lock expires in one week. At expiration, the team's ability to rugpull is fully restored.


Lock percentage: the detail most buyers skip

The lock covers only the LP tokens that were submitted to the locking contract. If a project created a liquidity pool with 100 LP tokens and only locked 10 of them, 90% of the liquidity can still be withdrawn at any time. Locking 10% of liquidity while 90% remains freely accessible provides almost no meaningful protection.

What to check: the total LP token supply for the relevant pool, the amount submitted to the locking contract, and the implied percentage. This requires going to the pool on Raydium or Orca, finding the total LP token supply, then checking the lock contract on your locking platform of choice to confirm the locked amount.

For a lock to be credible, at least 90% of total LP tokens should be locked. Anything below 50% is a signal that the team retains substantial ability to drain liquidity despite their "locked" claims.


Lock platform: where the lock actually lives

Not all liquidity locks are created equal — the security of a lock depends entirely on the trustworthiness of the smart contract holding it. For Solana, recognized locking platforms include:

  • Streamflow Finance: the most widely used on Solana; provides a public dashboard showing all active locks verifiable by anyone
  • Raydium's native lock: built directly into Raydium's pool creation interface; integrated with their UI
  • Vaultx: another Solana-native locking protocol with public verification

What is not a lock:

  • A screenshot of a transaction the team says is a lock
  • Verbal commitment from the team to "never remove liquidity"
  • LP tokens held in the team's own wallet (no time restriction; can be moved at will)
  • LP tokens in a multisig that the team controls (only secure if multisig signers are genuinely independent)

Verify every lock claim independently on the platform where it was executed. RugCheck.xyz automatically checks Streamflow locks for any token you analyze.


What liquidity locks cannot protect against

Even a perfectly executed long-term full liquidity lock does not protect you against every form of token attack:

Mint inflation: A token with active mint authority can be diluted by creating new supply and selling it into the market, regardless of whether liquidity is locked. The lock prevents the team from pulling the pool assets — it does not prevent them from flooding the market with new tokens.

Freeze-based attacks: Active freeze authority enables holder account locking regardless of liquidity lock status. If your wallet is frozen, the fact that liquidity is locked in a 12-month contract doesn't help you — you can't access that liquidity because your sell transactions will fail.

Coordinated dump from insider holdings: If the team controls 60% of token supply outside the liquidity pool, they can dump those holdings into the locked liquidity, extracting SOL from the pool without ever touching the LP tokens. The lock prevents LP withdrawal; it does not prevent token selling.

This is why Hannisol evaluates liquidity lock status as one factor among eight, rather than treating it as a near-sufficient signal of safety. A locked liquidity pool is a positive signal that should be combined with confirmation that mint authority and freeze authority are both revoked, and that holder concentration is reasonable. Check the complete picture for any token at Hannisol.

Ready to apply this to a real token?

Run any Solana mint address through Hannisol's 8-dimension risk engine — free, no signup required.

Analyze a token on Hannisol →

Related articles

Profile
Notification
FavoritesFavorites
History