Liquidity Locks and Burns: Verifying Them Before You Trust a Launch

Liquidity Locks and Burns are among the most quoted safety claims in new token launches, and among the least verified. A project can claim its liquidity is locked while the lock is short, partial, or held by a contract the team still controls. On Tuesday 3 November 2026, with total crypto market capitalization around $2.67 trillion and the Binance story in the news, with the FBI attributing the roughly $6.3 billion 29 October theft to North Korea's TraderTraitor group, trust in unverified claims was in short supply. This guide gives the on-chain checks that separate real locks and burns from marketing.

What Locks and Burns Actually Mean

When liquidity is added to a decentralized exchange pool, the provider receives liquidity provider tokens, known as LP tokens, representing a claim on that pool. Locking liquidity means sending those LP tokens to a lock contract that releases them only after a set date. Burning liquidity means sending LP tokens to an address nobody controls, usually the zero address, so they can never be retrieved. Both arrangements prevent the team from suddenly withdrawing the pool, but they differ: a lock eventually expires, while a burn is permanent.

Neither arrangement guarantees a token's price or the project's honesty. Locked liquidity can still lose value if the token price falls, and a project with burned liquidity can still fail, abandon development, or carry dangerous contract functions. Locks and burns protect against one specific abuse, the sudden removal of liquidity, and they should be weighed alongside supply checks, contract review, and team track record. A verified lock is a positive signal, not a complete safety verdict. The glossary defines LP tokens, locks, and burns.

Verifying a Liquidity Lock

Verification starts on a block explorer. Find the lock contract, confirm it holds the LP tokens for the correct pool, and read the amount locked and the unlock date. Compare the locked amount with the total LP tokens issued: locking 10% of LP tokens while the team holds the other 90% offers little protection. Check who can extend, cancel, or modify the lock, because a lock the team can revoke early is not a lock at all. Reputable locking services publish these details publicly, but always confirm them on-chain rather than trusting a screenshot.

Duration matters as much as existence. A lock expiring days after launch protects holders only briefly, while a lock of a year or more signals longer commitment, though even long locks eventually end. Note the unlock date in your calendar and reassess the position before it arrives, since liquidity removal becomes possible again at expiry. Also check whether new liquidity added later is locked too; an initial lock does not cover LP tokens minted afterward. For a wider view of safer venues, see the best crypto arbitrage scanners page.

Verifying a Burn

A burn claim is verified by finding the burn transaction on-chain: LP tokens sent to an unspendable address, most commonly the zero address, in the amount claimed. Check that the tokens burned correspond to the real pool, not a different or fake pool, and that the amount is a meaningful share of total LP tokens. Partial burns are common and legitimate, but they should be described honestly: burning 20% of LP tokens while retaining 80% is not the same as burning the liquidity. If the project claims a full burn, the numbers must show it.

Be careful with lookalike burn claims. Some projects send tokens, not LP tokens, to a burn address and describe it as burning the liquidity, which is a different and weaker claim. Others burn LP tokens for a pool that holds little value while the main trading pool remains unlocked. Always identify exactly which asset was burned, which pool it relates to, and what share of that pool's LP tokens it represents. If any link in that chain is unclear, treat the claim as unverified.

A Pre-Buy Verification Routine

Combine the checks into a short routine before buying any launch that leans on lock or burn claims. Confirm the pool address, find the LP token holders, verify the lock contract or burn transaction, record the amount and expiry date, and check whether the team retains unlocked LP tokens. Cross-check the project's statements against the on-chain record, and search for independent confirmation. If the lock cannot be found, the amounts do not match, or the team controls the lock contract, walk away: a launch that misstates its liquidity safety is unlikely to be trustworthy elsewhere.

AI Help: Muse AI

Muse AI is Meta's personal AI assistant. It can explain a concept from this article in simple words, for example the difference between locking LP tokens and burning them, and help you draft a verification checklist to reuse before a launch.

Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code. Disclosure: LTGSWD is the author's Muse invite code. Muse AI is not a trading tool and does not give financial advice.