Skip to content
Verification Claim class – unverified Security

“Liquidity Is Locked”: Checking the Lock Contract Instead of the Logo

The claim class: a token team states that liquidity provider tokens for its trading pair are locked for a stated period, preventing the team from withdrawing the underlying liquidity before that date.

“Liquidity Is Locked”: Checking the Lock Contract Instead of the Logo
RECEIPTS Claim class – unverified
The claim
The claim class: a token team states that liquidity provider tokens for its trading pair are locked for a stated period, preventing the team from withdrawing the underlying liquidity before that date.

Claim class: a pattern of statements, not one attributed, dated quote.

The receipt

Receipt to pull The receipt is the lock contract itself: the specific address holding the liquidity provider tokens, the unlock timestamp or block encoded in that contract, and confirmation that the locked tokens are in fact the liquidity provider tokens for the pair in question, rather than some unrelated token sent to a lock service for appearances. No single receipt is linked: this piece explains how to check this kind of claim and does not grade one specific claim.

What it doesn't prove

A genuine, verified lock only covers the specific liquidity provider tokens actually sent to it, for the specific pair and amount locked. It does not prevent the team from adding a new, unlocked pool elsewhere, does not cover liquidity provider tokens minted after the lock was set up, and does not by itself say anything about the token's other risks, such as an active mint function or a renounced-ownership claim that turns out not to hold.

Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker.

A padlock icon next to a trading pair is meant to reassure traders that the project cannot simply pull its liquidity and disappear. That reassurance is only worth anything if the actual lock contract, and the unlock date inside it, say what the badge claims they say.

The Claim

The claim class: a token team states that liquidity provider tokens for its trading pair are locked for a stated period, preventing the team from withdrawing the underlying liquidity before that date.

The Receipt

The receipt is the lock contract itself: the specific address holding the liquidity provider tokens, the unlock timestamp or block encoded in that contract, and confirmation that the locked tokens are in fact the liquidity provider tokens for the pair in question, rather than some unrelated token sent to a lock service for appearances.

Third-party lock services exist specifically to make this checkable: a team sends liquidity provider tokens to the service’s contract, which enforces the unlock date in code rather than on trust. The receipt is the lock service’s own page for that specific lock, or a direct read of the lock contract’s stored unlock time, not the team’s own description of having “locked liquidity somewhere.”

What It Doesn’t Prove

A genuine, verified lock only covers the specific liquidity provider tokens actually sent to it, for the specific pair and amount locked. It does not prevent the team from adding a new, unlocked pool elsewhere, does not cover liquidity provider tokens minted after the lock was set up, and does not by itself say anything about the token’s other risks, such as an active mint function or a renounced-ownership claim that turns out not to hold.

How to Check It Yourself

  1. Find the specific lock transaction or lock-service page the team points to, not just a stated claim that liquidity is locked somewhere.
  2. Confirm the locked asset is actually the liquidity provider token for the specific trading pair in question, by checking the token address against the pair’s own liquidity pool address.
  3. Read the unlock timestamp or block number directly from the lock contract rather than from a marketing graphic.
  4. Check what percentage of total liquidity provider tokens for that pool are actually held in the lock, since a partial lock can coexist with a much larger unlocked position.
  5. Check whether the lock is permanent (burned, sent to the null address) or time-limited, since these are different strengths of claim.
  6. If using a third-party lock service, check that service’s own reputation and contract code, since the lock is only as strong as the service enforcing it.

A Worked Example

A new token’s trading pair carries a locked liquidity badge linking to a lock-service page. The page shows a real lock contract holding liquidity provider tokens with an unlock date months away, but reading the pool’s total liquidity provider token supply shows the locked portion covers only a small slice of the pool, with the much larger remainder held in an ordinary, unlocked wallet. The lock is genuine; the badge’s implication that the pool itself is locked is not.

What Supported, Contradicted, and No Receipt Look Like

Supported: The lock contract or service page confirms the actual liquidity provider tokens for the stated pair are held in a lock contract, with an unlock date matching the claim, and the locked amount represents a meaningful share of total pool liquidity.

Contradicted: The locked asset is not actually the pair’s liquidity provider token, the unlock date encoded in the contract is sooner than claimed, or only a small fraction of total liquidity provider tokens are locked while the marketing implies the whole pool is covered.

No receipt: No specific lock contract or service page is identified anywhere, only a general statement that liquidity is locked; there is nothing on-chain to point to.

Red Flags

  • A lock badge or logo is shown with no link to the specific lock transaction or contract behind it.
  • The locked token address, when checked, does not match the actual liquidity provider token for the pair being promoted.
  • Only a small share of total pool liquidity is locked while marketing describes liquidity generally as locked.
  • The unlock date is unusually short, letting the team regain control of liquidity on a timeline that defeats the purpose of locking it.
  • The lock service itself is unfamiliar, unverified, or has no track record that can be checked.

A Practical Complication to Expect

Liquidity locking services themselves differ in what they actually guarantee: some are simple time-lock contracts with no other function, while others allow the original depositor to extend, modify, or in some configurations even partially withdraw before the stated date under specific conditions coded into the lock contract itself. Reading only the unlock date without checking whether the lock contract permits any kind of early action can overstate the strength of the guarantee. It is also worth checking whether a given lock service has a track record of enforcing its locks as advertised across other projects, since the service itself, not just the individual lock, is part of what a reader is ultimately trusting when relying on this kind of claim.

Why It Matters

Liquidity locks exist to answer one specific, exploitable risk, a team pulling all liquidity and leaving traders holding an untradeable token, and they answer it well only when the lock is real, matches the actual pool, and covers a meaningful share of it. A badge with no underlying contract answers nothing.

Keep checking: How to Read a Hack Post-Mortem Without Taking It on Trust; The Ronin Bridge Theft: Checking the North Korea Attribution Against the FBI and OFAC Records.

FAQ

Does a liquidity lock protect against the token’s own smart-contract risks?

No. It only restricts withdrawal of the pooled liquidity itself; it says nothing about mint functions, ownership, or other contract-level risks, which need to be checked separately.

What happens when the lock expires?

Control over the liquidity provider tokens reverts to whoever locked them, who can then withdraw the underlying liquidity. A lock delays this risk to a known date; it does not remove it permanently unless the tokens were burned instead of time-locked.

Is a burned liquidity provider token stronger than a time-locked one?

Generally yes, since burning removes the ability to ever withdraw that liquidity, while a time lock only delays it until the stated date, after which the original risk returns.

Can a team create a new, unlocked pool while an old one stays locked?

Yes, and this is a known way the spirit of a liquidity lock can be defeated even while the original lock claim remains technically true; check whether trading has migrated to a different, unlocked pool.

Is a lock set up through a well-known, widely used lock service inherently more trustworthy than a custom one a project built itself?

An established, widely used lock service has typically been reviewed and tested across many other projects’ locks already, which gives it a track record a brand-new, custom-built lock contract does not have; that said, an established service is still a piece of software that could contain its own bugs, so the lock contract’s own code, where verified, is worth a quick look even when using a reputable provider, rather than assuming reputation alone guarantees the lock will behave exactly as described.

Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker; we describe how a claim like this can be checked, never whether to buy, sell, or hold anything on the back of it.

Sources

This piece links no outside source: it explains a class of claim and the public records you would check, rather than grading one specific statement. When a specific claim is checked, every source link is listed here with its status.

About the author

The Crypto Online Editorial Team

A collective byline for a claim-verification desk. Every piece is human-edited and checked against a primary record; AI assistance is disclosed in our editorial guidelines.

All work by the team → Methodology Corrections

Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.