How to Verify a Liquidity Lock Before Trusting It

Liquidity locks are mechanisms intended to prevent token creators or others from withdrawing the liquidity pool tokens and thereby 'rug pulling' investors. These locks typically involve transferring liquidity pool tokens to a smart contract or address that restricts access for a set period or indefinitely.

On Ethereum and other EVM-compatible chains, liquidity providers receive LP tokens representing their share of the pool. Locking liquidity involves locking these LP tokens in a contract or multisig that prevents their transfer or withdrawal.

On Solana, liquidity is managed differently, with token authorities controlling minting and freezing permissions. A liquidity lock may involve revoking or transferring these authorities to a null or inaccessible address, but this is distinct from locking LP tokens on EVM chains.

While liquidity locks can reduce certain risks, they do not guarantee complete safety. Other permissions, such as minting new tokens or changing trading rules, can still pose risks even if liquidity is locked.

• Liquidity locks restrict access to liquidity pool tokens to prevent rug pulls.
• EVM chains use LP tokens; locking involves restricting their transfer.
• Solana uses token authorities; revoking these is a form of liquidity lock.
• Liquidity locks do not eliminate all risks; other permissions matter.

To verify a liquidity lock on an EVM chain, start by identifying the liquidity pool token contract associated with the token's trading pair. This token represents the liquidity provider's share.

Next, check where the LP tokens are held. If they are in a known lock contract or a multisig with a time lock, this suggests liquidity is locked. Some platforms provide verified lock contracts with public interfaces.

You can also review the token contract for functions that allow liquidity removal or transfer of LP tokens. If such functions are accessible by the owner or other privileged accounts, liquidity may not be fully locked.

Be aware that some liquidity locks are temporary or have conditions. Confirm the lock duration and any conditions for unlocking.

Remember that liquidity concentrated in certain price ranges (as in Uniswap v3) means that liquidity is active only within those ranges, which affects trading depth and price impact, but does not affect the lock status itself.

• Identify the LP token contract for the token pair.
• Check the LP tokens' holding address and verify if it is a lock contract.
• Review token contract for permissions to remove liquidity.
• Confirm lock duration and conditions.
• Understand that concentrated liquidity affects trading but not lock status.

Solana tokens do not use LP tokens in the same way as EVM chains. Instead, token authorities control minting and freezing capabilities, which influence liquidity and token supply.

To verify a liquidity lock on Solana, examine the token mint's authorities. If the mint authority and freeze authority are set to None (revoked), this indicates that no one can mint new tokens or freeze accounts, which is a strong indicator of locked liquidity.

Use blockchain explorers or tools like Rug.Tools to fetch the mint account data and check the authority fields. A burn address is not equivalent to revoking authority; only setting the authority to None fully revokes control.

Be cautious that other permissions or associated contracts may still have control over trading rules or token behavior. A liquidity lock on Solana is not a guarantee of safety by itself.

• Check the mint authority and freeze authority on Solana tokens.
• Authorities set to None indicate revoked permissions and locked liquidity.
• Use explorers or tools to inspect mint account data.
• Burn addresses are not the same as revoking authority.
• Other permissions may still pose risks despite liquidity lock.

A liquidity lock prevents immediate withdrawal of liquidity pool tokens but does not prevent other risks. For example, token creators may retain minting rights, allowing them to create new tokens and dilute value.

Tokens may have upgradeable contracts or admin roles that can change trading rules, impose fees, or blacklist addresses, which liquidity locks do not affect.

Liquidity locks also do not prevent 'soft rug pulls' where liquidity remains but is manipulated to reduce token value.

Scanners and tools can detect some permissions and locks but cannot guarantee safety or detect all risks. Always combine liquidity lock verification with broader token research.

Wallet connections or shared addresses do not prove common ownership or control; avoid assumptions based solely on wallet clustering.

• Liquidity locks do not prevent minting or contract upgrades.
• Admin roles can change token behavior despite liquidity locks.
• Soft rug pulls are possible even with locked liquidity.
• Scanners have coverage limits; manual checks are essential.
• Wallet connections do not prove shared control.

Suppose you discover a new token on an EVM chain and want to verify its liquidity lock. First, identify the token's liquidity pool on a decentralized exchange like Uniswap or PancakeSwap.

Find the LP token contract address and check where the LP tokens are held. If they are in a known lock contract with a verified lock period of six months, this suggests the liquidity is locked for that duration.

Next, review the token contract for owner privileges. If the owner can still mint new tokens or change fees, the liquidity lock alone does not guarantee safety.

Finally, check for any upgradeable contract proxies or admin roles that could affect token behavior. If these exist, consider the risks accordingly.

This exercise shows that verifying liquidity locks involves multiple steps and cannot rely on a single indicator.

• Identify liquidity pool and LP token contract.
• Check LP token holding address and lock status.
• Review token contract for minting and admin privileges.
• Check for upgradeable contracts or admin roles.
• Assess risks beyond the liquidity lock.

Use this checklist as a practical guide when verifying liquidity locks:

1. Identify the liquidity pool and LP token contract (EVM) or token mint authorities (Solana).

2. Verify LP tokens are held in a recognized lock contract or multisig with a defined lock period (EVM).

3. Confirm mint and freeze authorities are revoked (set to None) on Solana tokens.

4. Review token contract for minting, pausing, upgrading, or fee-setting permissions.

5. Check for upgradeable proxies or admin roles that can alter contract behavior.

6. Understand the nature of liquidity: uniform vs concentrated liquidity affects trading but not lock status.

7. Use trusted tools like Rug.Tools for initial analysis but perform manual verification.

8. Avoid assuming wallet connections imply shared control or safety.

Following this checklist helps you gather evidence and understand the limitations of liquidity locks before trusting a token.

• Identify liquidity pool and LP token or mint authorities.
• Verify LP tokens held in lock contract or revoked authorities.
• Review token contract permissions for minting and upgrades.
• Check for upgradeable proxies and admin roles.
• Understand liquidity types and their impact.
• Use Rug.Tools and manual checks.
• Avoid assumptions from wallet connections.