LP Lock Check

Identify a Base token's main liquidity pool and classify LP custody via read-only calls.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill lp-lock-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: LP Lock Check
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/lp-lock-check
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill lp-lock-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve a token's main liquidity pool on Base and classify whether its LP is burned/locked or removable (rug-pull risk). Keyless — no explorer key needed.

Core Features & Use Cases

  • Locate the main pool for a given token on Base and identify the dominant counterparty.
  • Distinguish between V2 fungible LP tokens and V3/V4 non-fungible liquidity; classify custody risk.
  • Provide a clear verdict (LOCKED, PARTIAL, UNLOCKED, UNKNOWN, INCONCLUSIVE) and optional notifications and logs for risk assessment.

Quick Start

Supply a Base token address to run LP Lock Check and obtain a custody verdict.

Frequently Asked Questions about LP Lock Check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a Base token liquidity pool is locked to prevent rug pulls?

To check Base token liquidity pool custody and prevent rug pulls, supply the token address to evaluate whether its LP is burned, locked, or removable, returning a verdict of LOCKED, PARTIAL, UNLOCKED, UNKNOWN, or INCONCLUSIVE.

What is the best way to detect removable LP tokens for Base blockchain tokens?

Detecting removable LP tokens for Base blockchain tokens involves identifying the main V2 fungible liquidity pool via read-only eth_call and eth_getLogs to classify whether the LP ownership poses rug-pull custody risk.

Does LP Lock Check work with V3 or V4 non-fungible liquidity pools on Base?

LP Lock Check does not analyze V3 or V4 non-fungible liquidity pools on Base, returning an UNKNOWN custody verdict for these scenarios while specifically classifying V2 fungible liquidity pools.

Do I need an explorer key or private key to analyze Base liquidity pool custody?

No explorer key or private key is needed to analyze Base liquidity pool custody, as the evaluation uses keyless read-only eth_call and eth_getLogs methods to determine pool, balance, and ownership without executing transactions.

How does liquidity pool custody classification identify rug-pull risk for Base tokens?

Liquidity pool custody classification identifies rug-pull risk by resolving a Base token's main pool, determining the dominant counterparty, and verifying if the LP tokens are burned or locked versus removable by the owner.

Why does my Base token liquidity check return an INCONCLUSIVE custody verdict?

A Base token liquidity check returns an INCONCLUSIVE custody verdict when the read-only evaluation cannot definitively classify the V2 fungible LP ownership state or locate the main pool balance for risk assessment.