How to Verify a Lock or Burn on PulseChain

On most chains you check whether liquidity is locked. On PulseChain you check two things, because most liquidity here isn't locked at all — it's burned. Both are verifiable on the public explorer without trusting the project.

Why should you verify a lock or a burn yourself instead of trusting the claim?

Because a lock or a burn is a transaction that either exists on-chain or does not, and a project's claim about one costs nothing to make. If a team cannot point you to the transaction, the correct assumption is that there is no transaction. That matters here in particular: PulseChain resolves roughly 53 new pairs a day into about 19 to 25 genuinely new tokens, and most new pools hold under $3,000 (as of August 2026). Most of what you are looking at is minutes old and has no reputation to lean on. The explorer is the history.

How do you verify a lock or a burn on PulseChain?

You verify a lock or a burn on PulseChain by finding the token's PulseX pair on scan.pulsechain.com, looking at who holds the LP tokens for that pair, and identifying whether that holder is a burn address, a locker contract, or an ordinary wallet. Those three outcomes mean three different things. The process:

1. Find the token's liquidity pair. A token's liquidity lives in a pair contract, usually on PulseX, which holds about 79% of chain TVL at $94.61M (as of August 2026). The token's explorer page or any screener listing identifies the pair.
2. Look at who holds the pair's LP tokens. The pair contract issues LP tokens representing claims on the pooled assets. The holder list for those LP tokens is the entire question: whoever holds them can withdraw the liquidity, and nobody else can.
3. Check whether the LP tokens went to a burn address. A burn address is not a wallet — it is an address whose private key cannot exist, so tokens sent there can never move again. Explorers label the well-known ones, and the LP supply will show as held by that labelled address rather than by any person.
4. Check whether the LP tokens are held by a locker contract instead. A lock leaves LP tokens in a contract that holds them until a set unlock date, so the supply sits at a contract address with a public lock record naming the token, the amount and the unlock date.
5. Read the transaction that put them there. A burn or a lock is a single transfer with a timestamp. Confirm it moved the LP tokens you care about, and how much of the LP supply it covered — a burn or lock of part of the supply leaves the rest withdrawable.
6. Check the team's token allocation separately. Liquidity is one balance sheet; the team's own tokens are another. Find where the largest non-pool holders sit and whether those balances are in a locking or vesting contract or in an ordinary wallet.

What does a burned LP look like on-chain?

A burned LP looks like the pair's LP tokens sitting permanently at an address that cannot spend them, with a transfer transaction showing when they arrived and no outgoing transfers afterwards — ever. This is the normal outcome on PulseChain, not the exception. pump.tires, the dominant launch pipeline, states in its own documentation that “When coins launch on PulseX, the liquidity provider (LP) tokens are automatically burned, permanently locking the liquidity.” Graduation happens at 200M PLS of bid liquidity, roughly $2,860 at prices as of August 2026, and the burn is part of graduation rather than a team decision afterwards.

What you are confirming, then, is whether this token actually went through that pipeline and whether the burn covered the whole LP supply. A burn is irreversible, which makes it stronger than a lock and also means nobody — including the team — can ever migrate or top up that position. Burned versus locked liquidity is worth understanding before you judge a project either way.

What does a locked LP look like instead, and how do you tell the difference?

A locked LP looks like the pair's LP tokens held by a locker contract with a published unlock date, and the difference from a burn is that a lock has a future — an address that will one day be able to move those tokens. Read that distinction rather than treating both as a green light. With a burn, the question “what happens at unlock” has no answer because there is no unlock. With a lock, that question is the whole risk: who owns the lock, when does it expire, and what percentage of the LP supply does it cover.

Locks are the relevant mechanism for manual PulseX positions created outside a launch pipeline, where the LP tokens land in the deployer's wallet and stay there — here's what locking a PulseX LP position involves. If you find a genuine lock, the unlock date and the covered percentage are the two numbers that matter. A lock covering 40% of the pool, or expiring in three weeks, is not the assurance the announcement implied.

What does a renounced contract actually tell you?

A renounced contract tells you that certain owner-only functions can no longer be called — nothing more. It is a checkable fact — renouncement is a transaction, and pump.tires launches are renounced as part of their model. What it does not tell you is whether the token's code was safe to begin with. Renouncement freezes the contract as written, including any behaviour already coded into it: a punitive transfer rule, a hidden fee path or an unusual supply mechanism does not become safer when ownership is renounced — it becomes permanent. Treat renouncement as one line item, not a verdict. It removes the risk of the owner changing the rules later, and says nothing about liquidity, the team's holdings, or whether the rules were acceptable in the first place.

Does burned liquidity mean the team can't dump?

No — burned liquidity says nothing at all about the team's own token allocation, and this is the single most common misreading on PulseChain. Burning LP removes one specific risk: nobody can withdraw the pooled assets and leave holders with an empty market. It does not touch the tokens the team holds in wallets. A project can have permanently burned liquidity and a team wallet holding a large share of supply that can be sold into that same pool at any moment.

This is the gap the burn creates and nobody closes. Teams graduating from a launch pipeline find their liquidity already handled and their own allocation unsecured — which is what a team token lock is for. As a buyer: after confirming the burn, look at the largest holders that are not the pool. If a meaningful share of supply sits in an ordinary wallet with no lock or vesting record behind it, you have found the actual risk, and it is not the liquidity.

What are the red flags when verifying a PulseChain lock or burn?

The red flags are a claim with no transaction behind it, LP that moved shortly before a lock announcement, and a team allocation sitting in an ordinary wallet. Taking those in turn: a claim with no verifiable transaction — if a team cannot point to a hash, or points to one that does not do what they say it does, stop there. LP that moved just before a lock announcement — a position partially withdrawn and then locked is a locked remainder, not a locked pool, so compare the LP supply before that transaction and after. A team allocation in an ordinary wallet — the risk that survives every burn, every lock and every renouncement.

Two smaller ones: partial coverage, where the announcement quotes the locked or burned fraction as though it were the whole supply; and badge-only verification, where a screener icon stands in for the check. Badges are automated inferences drawn from holder data and known-address lists, and on a chain where burns dominate they mislabel more often than on chains where locks do. The holder list is the source.

For project teams: everything above is what your community will check, which is what makes a verifiable lock worth having. Team Finance supports PulseChain at full tier-1 parity — liquidity and team locks at $150, vesting at $100, charged in PLS (verified August 2026). Start with the pillar guide, or go straight to the app.

FAQ

Do I need anything besides the explorer to verify a lock or burn on PulseChain? No. The token's pair contract, the LP token holder list and the transaction that moved those LP tokens are all public on scan.pulsechain.com, and together they answer the question completely.

Is burned liquidity better than locked liquidity? Burned liquidity is more permanent and locked liquidity is more flexible. A burn can never be reversed, so the liquidity can never be pulled and also never migrated; a lock ends on a date you can read in advance.

Does a renounced contract mean the token is safe? No. Renouncement means owner-only functions can no longer be called, which freezes the contract as written — including anything already coded into it. It is one checkable fact, not a verdict on the token.

If liquidity is burned, what is still at risk? The team's own token allocation. Burning LP prevents the pool from being withdrawn; it does nothing about tokens held in wallets, which can be sold into that pool at any time unless they are locked or vesting.

Next steps: burned vs locked liquidity · lock PulseX LP tokens · team token locks · the PulseChain hub