Locked vs Burned Liquidity

In a fungible liquidity model such as Uniswap v2, providers receive LP tokens representing proportional ownership of pool reserves. Whoever controls those LP tokens can generally redeem the corresponding share. Locking liquidity usually means transferring LP tokens to a time lock contract. Burning generally means transferring them to an inaccessible address or otherwise destroying the redeemable ownership token.

Concentrated liquidity changes the object. A Uniswap v3 position is represented by a nonfungible position with a range, fee tier, and accrued fees. A service must custody or restrict that position token, not a fungible LP balance. If an interface says liquidity is locked without identifying the exact pool version and position identifier, the label is too vague to verify.

A typical locker records the deposited LP asset, beneficiary, amount, and unlock timestamp. Until that timestamp, withdrawal should fail under the contract's rules. At expiration, the beneficiary can usually retrieve the ownership claim and then remove liquidity from the AMM. Some lockers allow extension, ownership transfer, fee collection, or migration. Those permissions must be read from the specific implementation rather than assumed from the word locked.

Suppose a pool has 10,000 LP tokens outstanding and a team locks 8,000 for twelve months. The headline locked share is 80 percent at that moment. The remaining 20 percent is not restricted by that lock. New liquidity deposits can change total LP supply, and locks in a different pool do not protect this pool. The percentage, denominator, beneficiary, and expiry all need a timestamp.

If the same 8,000 LP tokens are sent to a recognized irrecoverable address, the associated pool share is commonly described as burned. Unlike a time lock, it has no intended unlock date or beneficiary withdrawal. The assets remain in the AMM and continue participating in its curve, but the burned ownership claim cannot normally be presented to redeem them.

Verification still requires care. An address described socially as a burn address may be controlled, a token contract could contain unusual recovery behavior, or the displayed transfer might involve a negligible pool while another pool remains removable. On some protocols, permanently inaccessible ownership does not prevent fees or protocol controls from affecting reserves. Burned does not mean that every aspect of the market is immutable.

Restricting an LP position can reduce one specific risk: the holder abruptly redeeming that restricted share of pool assets. It does not prevent minting additional project tokens, blocking sellers, changing taxes, pausing transfers, exploiting upgrade authority, draining an unlocked pool, or selling a concentrated token allocation into the pool. GoPlus token and locker data can help locate some of these signals, but automated findings require onchain confirmation.

A concentrated position can also be locked yet out of range. It may count toward a headline value while supplying no active depth at the current price. A locked quote asset can still lose its peg, and the project token side can fall in market value. Smart contract vulnerabilities in the AMM, locker, token, bridge, or approval path remain possible. A lock is a narrow custody fact, not a broad certification.

Start with the canonical token and pool addresses. Identify the pool type, total LP supply or position identifier, current owner, locker contract, amount, beneficiary, unlock time, and any privileged functions. Calculate the restricted percentage using current onchain supply. Search for other material pools and check whether deployers or related wallets control separate liquidity. Review the underlying token's mint, blacklist, pause, proxy, and transfer fee behavior.

Locker interfaces and security APIs are discovery tools, not final evidence. Contracts can be upgraded, timestamps can be displayed in different time zones, chains can reorganize, and labels can lag current state. CoinGecko or CoinMarketCap market pages may list liquidity venues but do not prove lock status. Report the exact transaction, chain, block, contract, and expiration rather than repeating an unqualified locked or burned badge.