Liquidity, locked LP and the limits of a token scan
Understand why market capitalization, pool liquidity and LP control answer different questions, and why locked liquidity is not a promise of a safe exit.
RugSignal editorial notes · Published 16 October 2026 · Source-based, not investment advice.
A quoted value is not an exit price
Market capitalization and pool liquidity measure different aspects of a market. A displayed token price is an observation, not an offer to buy your entire balance at that price. Trading changes pool balances and execution prices; fees and market conditions also matter. Compare the available liquidity with the size of the exposure you are considering, rather than relying on a headline valuation.
LP control is one part of the picture
Liquidity providers supply assets to pools and may receive a position or claim associated with that liquidity. Whether that position can be removed depends on the pool design and applicable controls. A lock or burn claim must identify what was locked, for which pool and under what conditions. Do not apply a single pool's evidence to every market for the token.
Locked liquidity cannot remove every risk
Even when removal restrictions are established, tokens held outside the pool can still be sold. Mint permissions, transfer restrictions, concentrated balances and a deteriorating market can remain relevant. A liquidity lock does not prove the team will keep building, and it does not guarantee that demand or price will persist. Unknown lock evidence should stay unknown; a provider's failure to load is not proof of either a lock or developer control.
Worked quote example: units and tolerance
Illustrative arithmetic, not a live quote: for a token with six decimals, 1.5 tokens is 1500000 raw units. Enter that exact integer in Check an exit size. If a provider quotes 1000000 raw USDC units, that is 1 USDC; a minimum of 995000 is 0.995 USDC at 50 basis points (0.5%) tolerance. Route fees may already be incorporated into quoted output: inspect the provider fee fields instead of subtracting them again. Missing network-fee fields remain unknown. The timestamp expires quickly; a route quote is neither a transaction simulation nor a guarantee of execution. Jupiter Swap V2 permits a quote without a signing wallet.
How RugSignal presents liquidity
RugSignal compares reported liquidity with market capitalization where both fields are available and records the observation time. Its threshold is a warning policy, not a forecast. The scanner chooses among reported markets and may lack complete coverage of every venue. Read the provider states, coverage and LP explanation before acting on the category. Historical reports remain immutable; opening them never triggers an automatic scan or AI request. Refresh deliberately when current evidence is needed.
Sources and further reading
- Raydium: liquidity and pool documentation
- RugSignal: deterministic warning method
- Jupiter: Swap V2 quote-only order and fields
Official protocol documentation explains capabilities; it does not certify an individual token. RugSignal-specific statements describe our current implementation.