LP Locking

LP locking is the practice of time-locking a liquidity pool position so that whoever created it cannot withdraw the funds before a preset date. The deployer deposits their LP tokens, or the NFT representing a concentrated liquidity position, into a locker contract that rejects withdrawals until the unlock timestamp passes. Because the lock lives onchain, anyone can verify it before buying the token.

The point is rug pull prevention. In an unlocked pool, a token creator can pull the paired reserves at any moment, leaving holders with a token that cannot be sold. Locking removes that exit: while the lock is active, the liquidity stays in the pool and the market keeps functioning. This is why credible launches advertise their lock terms and why some launchpads enforce locking automatically. A launchpad that enforces locking removes the decision from the creator entirely, because the lock is written into the launch transaction and pool liquidity stays in place for years.

A lock is necessary but not sufficient. Check what exactly is locked (all of the liquidity or only a fraction), how long the lock runs, and whether the locker contract has admin functions that could release funds early. A lock also does nothing about other risks: a team holding a large share of the token supply can still sell into the pool, and a malicious token contract can block transfers no matter where the liquidity sits.

Treat LP locking as one verifiable layer of protection rather than a guarantee that a token is safe, and always confirm the lock onchain instead of trusting screenshots.