LP Burned and Mint Revoked: What Those Two Phrases Actually Protect You From

Read the bio of any Solana meme coin and you will find the same two phrases: LP burned and mint revoked. They get deployed the way a restaurant displays a hygiene certificate, as proof that somebody responsible has been through the place.

Both describe real, permanent, verifiable things. Neither means what most people reading them assume. One of them, on a pump.fun token, was not a decision anybody made at all.

This is the mechanism behind those phrases: what each one destroys, what it cannot touch, and how to check both yourself without trusting a website. $CATE is the worked example throughout, because its numbers are public and because a specific fact about it makes the limits of “LP burned” unusually easy to see. Everything here applies to any Solana token.

What the two phrases actually mean

A Solana token is not a smart contract in the Ethereum sense. It is an account holding a small, fixed set of fields, and a few of those fields are addresses that grant powers. Revoking means writing null into one of them, permanently. There is no undo, because there is nobody left with the standing to undo it.

The mint authority is the field that controls supply. Whoever holds it can create new tokens from nothing and sell them into whatever buying pressure exists. As Helius documents it, the mint authority “controls the issuance of new tokens.” Null means the current supply is the permanent maximum.

The liquidity pool is a different kind of thing entirely, and this is where the confusion starts. Buying a token means swapping against a pool that holds both the token and SOL. Whoever deposited into that pool holds LP tokens, which are receipts. Hand the receipts back and you get the contents. Burning them means sending them to an address with no private key, so the receipts still exist but nobody can ever present them. The contents become unclaimable.

There is a third authority almost no safety checklist mentions, and its absence is arguably worth as much as the other two.

That third row deserves a moment. If the update authority is live, somebody can rename a token and swap its logo while you hold it. A wallet that showed one thing yesterday shows another today, and it is the same asset. It is a favourite trick for making a dying token look like a new launch. On $CATE it is null, which means the name, the symbol and the artwork are as frozen as the supply.

Mint revoked is usually not a decision anybody made

Here is the part that changes how you should read the phrase. On a token launched through pump.fun, revoked mint authority is not a virtue the creator chose. It is the default the launchpad applies before the creator gets a say.

Helius states it plainly: with a launchpad like pump.fun “the mint authority configuration is handled for you, and in both cases, it is set to null.” The same is true of the freeze authority, and revoking the update authority “is the default for all new Pump.fun tokens.” All three of the fields in that table are set to null by the platform on creation, for every token it has ever produced, including the outright scams.

So “mint revoked” on a pump.fun token carries roughly the information content of a car advertised as having seatbelts. True, worth having, and not a distinguishing feature. Millions of tokens can claim it. Most of them are worth nothing.

This matters practically, not just semantically. If you treat those three phrases as a filter, you have built a filter that passes almost everything on the platform. The check is still worth running, because tokens launched outside a launchpad genuinely do vary and some of them keep the mint authority live. But finding the expected answer should move your opinion very little, and finding the unexpected answer should end the conversation.

LP burned describes one pool, on one day

This is the misunderstanding worth the price of admission, and it is not a subtle technicality. It is the difference between what people think the phrase promises and what it can possibly cover.

When a pump.fun token graduates from the bonding curve, its liquidity moves into a PumpSwap pool and the LP tokens for that pool are destroyed automatically. Pump.fun’s own documentation says the liquidity pool tokens “are locked and burned,” that “liquidity cannot be removed manually,” and that “the only way to withdraw liquidity is through trading.” That is a genuine, meaningful protection, and it is what “LP burned” refers to on essentially every graduated token.

Note the singular. That pool. One pool, created once, at launch.

Nothing stops anyone from creating more pools for the same token afterwards. Not the creator, not the community, not you, not a stranger who has never spoken to any of them. Pool creation on the Solana DEXs where these pools live needs nobody’s approval, which is the entire point of a permissionless exchange. Those later pools have their own liquidity and their own owners, and those owners can withdraw whenever they like.

$CATE makes the gap unusually easy to measure, because there are 75 pools trading it, and the burned one is no longer where most of the liquidity lives.

Anyone can open a new pool, and strangers do

Once you know to look, the pool list stops reading like infrastructure and starts reading like weather. Of the 75 pools trading $CATE on 9 August 2026, 24 held at least a thousand dollars and only nine held at least ten thousand. The rest are dust, some of it a few dollars.

The largest pool that is not the burned one was created about ten and a half hours after launch and held $564,847. Several others appeared a week or more later. And some are not CATE against SOL or a stablecoin at all: there are pools pairing it against other meme coins, which are almost certainly the work of people with no connection to the project, made for reasons that are their own business.

The newest pool at the time of writing had existed for less than two hours.

None of this is sinister. It is what a permissionless market looks like when a token is actively traded, and the alternative would be worse. But it does mean one specific thing: “LP burned” is a fact about the launch pool, not a description of the token’s total liquidity. A token can be entirely honest about having burned its LP and still have most of its depth sitting in pools that a handful of people could pull tomorrow.

Burned, locked, and the difference that matters

The related phrase you will see is “liquidity locked,” and the two are not synonyms.

Locked means the LP tokens are held in a contract that will release them at a future date. The lock is a promise with an expiry, and you should always ask when it expires and who receives them when it does. A twelve month lock on a meme coin whose median life is measured in days is theatre, but at least it is checkable theatre.

Burned means there is no expiry and no recipient, because the receipts are gone. It is the stronger of the two by a wide margin, and the trade-off is that it is equally final in the other direction: liquidity that is burned can never be moved, migrated, upgraded, or recovered if something about the pool turns out to be broken. You are trading the possibility of repair for the impossibility of theft. For a meme coin that is almost always the right trade, and it is worth knowing that a trade is being made.

There is a subtler point in pump.fun’s phrasing, and it is easy to skim past. If the only way to withdraw liquidity is through trading, then liquidity leaves a burned pool the same way it arrived: one sale at a time. Burning stops the pool being removed in a single transaction. It does not stop it draining steadily as people sell, and a burned pool that has been sold into for months is a shallow burned pool.

How to check both yourself in two minutes

Everything above is verifiable without an account, an API key, or anybody’s permission. This is the part worth learning, because it transfers to every token you will ever look at.

For the authorities, ask a Solana RPC node for the mint account and read three fields. One request, no tooling beyond curl:

curl https://api.mainnet-beta.solana.com -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"getAccountInfo","params":["MINT_ADDRESS_HERE",{"encoding":"jsonParsed"}]}'

In the response, mintAuthority and freezeAuthority should both be null. The update authority sits in a different place depending on the token’s age: on a newer Token-2022 mint like this one it is updateAuthority inside the token metadata extension, and on an older token it lives in a separate metadata account that explorers usually label with a Mutable flag, where false is what you want. If you prefer a browser, Solscan collapses all of it into an Authority row in the profile summary, and shows N/A when there is nothing left to hold. Any address where you expected nothing is a reason to stop and work out who holds it before you buy.

For the LP burn, the trick is that you do not need to find the burn transaction. You compare two numbers that come from two different places and see whether they agree.

An AMM pool account records how many LP tokens it believes it has issued. The token program separately records how many of those LP tokens still exist. Withdrawing liquidity through the pool reduces both figures together. Burning the receipts directly reduces only the second one. So the gap between them is the burn, and you can read it off without interpreting anybody’s announcement.

Note what that arithmetic also shows: the burn is 99.65%, not 100%. A residual claim on roughly 21 SOL of the pool remains withdrawable by whoever holds the surviving receipts. It is a rounding error rather than a risk, and it is the sort of detail that gets flattened into “100% burned” everywhere else. Precision is cheap here, so there is no reason to round in the project’s favour.

The failure case is just as readable. If the two figures agree, nothing has been burned, and every receipt is sitting in somebody’s wallet waiting to be presented. If they agree on a pool whose bio advertises burned liquidity, you have found a straightforward lie, and you found it in one request without asking anyone a question. That asymmetry is the reason to learn the check rather than the conclusion: the same two numbers that confirm an honest claim expose a dishonest one, and they are equally cheap to read either way.

What neither guarantee protects you from

Both phrases close specific attacks. Between them they make it impossible to dilute you, freeze you, rename the asset, or remove the launch pool in a single transaction. That is a genuinely short list of things ruled out, and it is worth being precise about everything that remains open, because the remainder is where the losses actually come from.

That last row is the one that costs people money. Copying a token’s name, ticker, artwork and bio takes an hour, and the copy launches through the same launchpad, which sets the same three fields to null automatically. A scam clone can display “LP burned, mint revoked” with complete honesty. The phrases travel with the counterfeit.

The part that has nothing to do with the chain

One more limit, and it has become newly relevant for $CATE. On-chain guarantees describe the asset. They say nothing about where you keep it.

As of August 2026 the token also trades on a few smaller centralised exchanges alongside the Solana pools. Buy there and the exchange holds the token while you hold a balance in an account. Revoked authorities and burned liquidity are still true of the asset, and they no longer describe your position, because your position is a claim on a company. Withdrawals can be halted, accounts can be frozen, and thin markets get delisted. None of those risks exist in a wallet whose keys you hold, and none of them are visible on chain.

It is the same category of mistake as reading “mint revoked” as “safe”: a true statement about one layer, quietly applied to a different one.

So what should you conclude

That the two phrases are worth checking, worth very little as a recommendation, and worth understanding precisely.

Read them as a floor. Mint revoked means the supply cannot be inflated, and on a launchpad token it was automatic. LP burned means the launch pool cannot be withdrawn, and it says nothing about the other pools, the depth of the burned one, or where you choose to custody the token. Absent either one, walk away. Present, and you have learned that the most obvious ways of being robbed are closed off, which thousands of worthless tokens can also claim.

The useful habit is not memorising the phrases. It is the two minutes of checking: three fields from an RPC call, and two numbers that should disagree by almost exactly the amount somebody claims was burned. Once you can do that, no bio has to be taken on trust again.

$CATE’s live figures, including holder distribution and the current state of the pools, are on the stats page, refreshed hourly from chain. The wider set of structural checks is in the five checks that actually matter.