How to check a liquidity lock in 60 seconds

How to check a liquidity lock on Robinhood Chain in under a minute: read the source contract, the locked share, the owner and the release date.

1,267 words · about 5 minutes·Article updated 20 August 2026
The short answer

Here is how to check a liquidity lock on Robinhood Chain in under a minute: read four fields — which pool position is held, what share of the pool it covers, who holds the right to withdraw, and the exact release timestamp. Every one is on-chain state, and Locksley renders all four on the token page.

The four fields that make up a lock

A liquidity lock is a contract holding a pool position until a set date. On Robinhood Chain that position is usually a Uniswap v3 NFT rather than a fungible LP token balance, which is why a lock here points at a specific position ID instead of a quantity.

Everything you need sits in four fields:

  • Source — which contract holds the position, and whether Locksley reads it directly.
  • Share — how much of the liquidity pool that position represents.
  • Release — the exact timestamp the position becomes withdrawable.
  • Owner — the address that can withdraw once that timestamp passes.

Anything a project says about its lock that isn't one of those four fields is a claim, not a reading.

How to check a liquidity lock, step by step

Open the Liquidity panel on the token page.

Lock state renders inside it, because a lock is metadata about a liquidity number you are already reading. The panel walkthrough is in how to read a token page.

Check the source.

Team Finance locks run on TrustSwap's own contracts, so Locksley reads that state directly rather than taking a project's word for it. Locks held elsewhere show the holding contract we found. A screenshot, a Telegram message, or a receipt image is none of these — it is not a source you can read.

Check the share.

One lock covers 90% of a pool, another covers 4%: both display the same word. The percentage is the whole story. If only part of the pool is locked, the rest can leave at any moment, and the price you get is set by the pool as a whole.

Check the release timestamp.

Read the date, not the phrase "locked". A lock releasing in three days and a lock releasing in three years are the same fact with completely different consequences. Locksley shows the countdown next to the date.

Check the owner and the tail.

One address holds the right to withdraw at release. Note whether that address is the same deployer wallet that created the token, and note what happens next: expiring locks lists positions approaching release across the chain.

That is the read. Sixty seconds, four fields, no interpretation required.

What a lock read does not tell you

This is the part most explainers skip, and it is why the read is worth doing properly rather than treating a badge as a verdict.

A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.

A lock says nothing about what the position is currently made of, and on this chain that is the omission that costs people money. A v3 position holds two assets inside a price range, and every trade swaps some of one for the other. As a token's price falls, sellers take the quote asset out and leave the project's own token behind — while the lock sits untouched. A pool can be locked for two more years and hold almost none of the asset a seller is paid from. Both are true at once: the lock is as strong as it was, and the thing it holds has changed shape. Locksley draws each locked position's range against the current price for this reason.

A lock also says nothing about supply. Liquidity being held does not stop minting, does not stop a large holder selling into the pool, and does not stop transfer restrictions in the token contract. Those are separate checks, covered in the 7-point token check.

A burn is a different mechanism: the position goes to an address nobody controls, permanently, where a lock is temporary by design. Both are verifiable — a lock by its release timestamp, a burn at the dead address.

When the panel shows no lock

"No lock found" means we found none — not that none exists. Locksley does not yet index every locker.

So treat an empty lock panel as an unanswered question rather than an answer. It may mean liquidity is unlocked. It may mean the position is held somewhere we do not yet read. The useful move is to check the pool directly on the explorer, or to ask the project which contract holds the position and at what release timestamp — a project that locked liquidity can answer that in one line.

As of pending, pending of new Robinhood Chain launches locked liquidity at creation, per Locksley's contract reads. Locked at birth lists the tokens whose liquidity was locked at the moment their pool was created.

Locking liquidity on your own token

If you are on the other side of this read — a project rather than a buyer — the mechanics are the same in reverse. Team Finance is our sister product, so take this with the disclosure: it locks the Uniswap v3 position directly. If you have not launched yet, the free route comes first — locking inside a MintPlus launch waives the standard lock fee, so mint, pool and lock cost only gas. Outside that flow a lock costs $150 per liquidity lock as of August 2026, plus gas in ETH. You can lock liquidity on Robinhood Chain the lock renders on your token page once the transaction confirms. Pick the release date deliberately, because the far end of the timeline is a public event: what happens when a lock expires covers what release does and does not change.

Frequently asked questions

How do I verify a liquidity lock myself?

Read the on-chain state rather than the announcement. Find the contract holding the pool position, the position ID, the share of the pool it covers, and the release timestamp — all public on Robinhood Chain. Locksley renders those fields on each token page. For Team Finance locks, the holding contracts are TrustSwap's own, so the state is read directly.

Does a locked pool mean the price cannot crash?

No. A lock controls one thing only: whether the pool position can be withdrawn before its release date. Price is set by trading against the pool, and trading continues throughout the lock. A token with fully locked liquidity can fall to near zero while the lock is still active, and locked pools do fall.

What percentage of liquidity should be locked?

There is no threshold that makes a number meaningful on its own. What matters is the arithmetic: an unlocked share can leave the pool at any time, so a lock covering 40% of a pool leaves the other 60% mobile. Read the locked share against the total pool size and the release date together, since a large share locked for one week behaves differently from a small share locked for two years.

What happens to the lock when the release date arrives?

Nothing automatic. At the release timestamp the position becomes withdrawable by its owner, and it stays in the pool until that owner acts. No transaction fires on its own and holders receive no notification from the chain. The full mechanics, including how to see expiries before they arrive, are covered in what happens when a lock expires.

“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.