Liquidity Lock Legitimacy Checker

WHAT IT DOES

Liquidity Lock Legitimacy Checker reads live on-chain data from any EVM liquidity pool and uses AI to verify whether locked liquidity is legitimate or presents a rug-pull risk. It examines LP token contract data including total supply, token reserves, and pool composition. It scans for lock contracts holding LP tokens, reading unlock timestamps or block numbers, locked amounts, beneficiary addresses, and lock contract ownership. It calculates the percentage of total LP supply that is locked and analyzes whether the lock meets industry standards for safety. It detects multiple locks per pool, staggered expiries, and suspicious beneficiary patterns. The AI generates a plain-language verdict—SAFE, PARTIAL, or UNSAFE—along with specific explanations of lock legitimacy and risk factors before you trade or invest in the token.

HOW TO USE

Paste any EVM liquidity pool address (Uniswap V2 style) into the input field. The tool reads the pool's token reserves, LP token total supply, and identifies the token pair. It then scans transfer event logs to find contracts holding significant LP token amounts that may represent locks. For each lock candidate, it reads the lock contract's locked amount, unlock time, beneficiary, and owner. The AI receives all this data and returns a structured verdict: SAFE (adequately locked with long duration), PARTIAL (some liquidity locked but risk remains), or UNSAFE (inadequate lock, short duration, or suspicious patterns). The AI also provides a plain-language explanation of the specific risks.

CHUNKED LOG SCANNING WITH AUTOMATIC BACKOFF AND LOCK CONTRACT DETECTION

The tool scans transfer event logs of the LP token to identify potential lock contracts—addresses that hold large amounts of LP tokens and are likely lock contracts. Public RPC endpoints enforce varying block range limits per request—some allow 10,000 blocks, others only 2,000, and some reject requests that span more than a few hundred blocks. This tool automatically detects the per-request range limit by probing and adjusts batch sizes accordingly. It walks backwards from the current block in chunks and, if a request fails due to a range limit, it halves the chunk size and retries. If a request fails due to rate limiting, it backs off exponentially and resumes from the last successfully scanned block. The scan is capped to the most recent 200,000 blocks to balance completeness against performance; older locks may be missed, but the most active and relevant locks are still captured. Once lock contracts are identified, the tool queries each lock's interface to extract unlock time, locked amount, and beneficiary, then calculates the locked percentage of total LP supply to assess legitimacy.

WHAT IT CANNOT SEE

This tool cannot detect off-chain claims about lock duration or liquidity amounts that have not been executed on-chain. It cannot verify that locked LP tokens correspond to the actual liquidity pool being traded—if LP tokens are locked for a different pool, the tool cannot distinguish this. It cannot detect lock contracts that are obfuscated or use non-standard interfaces that do not expose locked amount, unlock time, or beneficiary through standard methods. It cannot verify that the lock beneficiary is the legitimate project team; a beneficiary could be a shell address controlled by a scammer. It cannot detect private locks not visible through standard lock contract interfaces or locks performed through custom, unverifiable contracts. It cannot see pending lock creation transactions not yet in the mempool. It cannot verify that a lock contract's source code has been publicly verified on Etherscan or equivalent explorers.

PLEASE NOTE

EVM chains only. This tool reads on-chain data and generates AI explanations—it does NOT sign transactions or execute any on-chain actions. The wallet's own signature prompt remains the final gate for every real action. Always review the exact transaction details in your wallet before approving any signature or investment. The AI assessment is informational only and does not constitute financial or security advice. Always verify lock details independently through official project documentation and block explorers before assuming any token is safe to trade.