See which pool was checked, what is actually locked or burned, and what the provider did not classify.
A lock constrains one observed LP position. It does not certify the token or every pool as safe.
How this calculation works — the formula, its inputs, what it assumes, and what it does not establish.
Inspect provider-observed LP locks, burned LP tokens, unlock dates and coverage for one explicitly identified pool. MoonMath keeps unreported LP supply unclassified and never turns a lock into a token safety guarantee.
A substantiated lock shows that an observed LP token balance or position cannot be withdrawn before its documented unlock time under the observed locker rules. It does not prove that every pool position is locked or that the token contract is safe.
A token can trade in several pools with different LP owners and liquidity models. MoonMath reports the exact pool and distinguishes top-holder coverage from the complete LP population.
Burned fungible LP tokens and time-locked LP tokens are different observations. Concentrated-liquidity NFTs require a position model and are never evaluated with V2 LP-token supply mathematics.
Inspect pool-specific LP locks, burns, expiry dates and unclassified coverage without a safety score. MoonMath labels the data basis for this tool as Observed.
No. The Liquidity Lock & LP Evidence is an educational scenario tool, not financial advice, a recommendation, or a forecast. Provider coverage, liquidity, routing, fees and market conditions can make real outcomes materially different.
No. A lock only constrains the observed LP position until its unlock conditions are met. Contract controls, other pools, holder concentration and market execution remain separate risks.
Not necessarily. Unreported supply remains unclassified unless a source identifies its holder and control.