Skip to content
PANTHER

How to Verify a Solana Token Burn: Supply, Proof and Authority

Check the mint, successful burn instruction, decimals and supply baseline. A worked example shows how burn percentages differ—and why a real burn is no price guarantee.

By Panther@0xPnthr

6 min read

Panther Knowledge conceptual illustration: a circular disc removed from a silver ledger plate, with restrained Solana purple and green edges. PROVE THE BURN.
Illustration: Panther Knowledge

Key points

  • A real token burn reduces mint supply. A transfer or LP burn proves something different.
  • Verify success, the matching mint, burn instruction and decimals; state the supply denominator behind every percentage.
  • Reconcile new minting with burns and check current mint authority. Neither a burn nor revoked authority guarantees price or liquidity.

A Solana token burn is a measurable change to a mint’s supply. A flame emoji, a wallet screenshot and a transfer to a dramatic-looking address are different kinds of evidence.

The useful question is simple: which units were destroyed, in which successful transaction, and against which starting supply? This guide shows how to answer it without connecting a wallet or trusting a project’s percentage.

It covers ordinary fungible tokens on Solana ($SOL is the network’s native asset), not a claim about any particular project. The worked numbers below are hypothetical; no transaction, wallet attribution or live test is presented as real.

What counts as a Solana token burn?

Solana’s Burn Tokens documentation defines a burn as a decrease in both a token account’s balance and the associated mint’s total supply by the same amount. For ordinary tokens, look for the Token Program’s Burn or BurnChecked operation. BurnChecked also checks the expected decimal precision.

A token transfer changes balances between accounts for the same mint. It does not reduce that mint’s supply. Even if a destination is believed to be inaccessible, a transfer alone is not evidence of a protocol-level supply reduction. Proving that nobody controls an address is a separate claim.

Burning the project token and burning a liquidity receipt also answer different questions. For LP tokens or position NFTs, use Panther’s liquidity lock and burn guide. Destroying a project’s tokens does not establish that its trading liquidity is locked.

Step 1: match the full mint address

Start with the token’s complete mint address, not its name, ticker or logo. Compare the issuer’s published address with the address on the trading pair and explorer. Panther’s contract-address verification guide explains that identity check across chains.

Open the mint on Solscan and record its address, owner program and decimals. Solscan’s own token-page guide identifies these fields and the authority and extension information. Labels and layouts can change; match the underlying address before following any burn link.

A wallet address may contain many token accounts. A token account holds units of a particular mint; the mint defines the token itself. A link to an owner’s portfolio is therefore weaker evidence than the exact transaction signature and matching mint.

Step 2: inspect the successful transaction

Ask for the transaction signature. Open it on the correct network, normally mainnet for a publicly traded token. Record the slot or timestamp and confirm that execution succeeded. An attempted burn inside a failed transaction is not a completed burn.

Expand the instruction list, including inner instructions when another program made the token-program call. Solana’s RPC transaction structures distinguish instructions, inner instructions, errors and pre/post token balances. A transfer summary or an app’s custom “burn” label is not enough by itself.

For the relevant burn operation, identify:

  • The actual Token Program operation and the program executing it.
  • The mint being reduced, directly or through the source token account’s mint.
  • The source token account and raw amount.
  • The decimals needed to interpret that amount.

Do not count a second token’s burn just because it appears in the same transaction. A transaction can contain multiple instructions and unrelated assets. For Token-2022 assets, inspect the applicable extensions and program rules; an unfamiliar operation needs more checking, not an automatic scam verdict.

Step 3: convert raw units before calculating a percentage

For a standard fixed-decimal token, displayed token units equal raw units divided by 10 raised to the decimals value. Solana’s getTokenSupply reference returns the raw amount and decimals, alongside display fields.

Hypothetical worked example—no real token or transaction:

Item Value
Token precision 6 decimals
Raw amount in first burn 125,000,000,000,000
Tokens destroyed in first burn 125,000,000
Starting supply assumed for the example 1,000,000,000
Supply after first burn, with no other changes 875,000,000
Tokens destroyed in a second burn 75,000,000
Supply after both burns, with no other changes 800,000,000

The first calculation is 125,000,000,000,000 ÷ 1,000,000 = 125,000,000 tokens. Treating the raw integer as a token count would exaggerate the amount by a factor of one million.

Across both burns, 200 million of the example’s original billion tokens were destroyed: 20% of original supply. The second burn alone is 7.5% of original supply, but approximately 8.57% of the 875 million supply immediately before it. Both percentages can be correct; the denominator must be named.

For tokens with display-altering extensions, do not assume a UI-scaled figure is the raw mint amount divided by decimals alone. Solana documents token extensions, including Scaled UI Amount. Keep the raw-unit calculation and any display conversion separate.

Step 4: reconcile burns with current supply

Record the mint’s current supply and when it was observed. The getTokenSupply method provides a current snapshot; it does not, by itself, prove what the supply was before an earlier burn. Prefer consistent finalized observations when comparing records.

The accounting relationship is:

Closing supply = opening supply + newly minted tokens − burned tokens.

This is supply accounting, not a price model. If the example had also minted 50 million tokens during the period, its closing supply would be 850 million. Gross burns would still total 200 million, while the net reduction from the opening billion would be 150 million, or 15%.

Do not infer “all-time burned” from launch supply minus today’s supply unless the launch baseline is verified and intervening minting is accounted for. If older transactions cannot be retrieved or decoded, describe the verified period or subset instead of calling it a complete history. Deduplicate transaction signatures and count each burn instruction once.

Also distinguish mint supply from circulating supply or tradable float. Vesting, treasury holdings and liquidity arrangements can change what is economically available without changing the mint’s raw supply.

Step 5: check whether more tokens can be minted

Solana’s Mint Tokens documentation explains that minting increases supply and requires the mint authority. A verified burn tells you what happened to existing units; it does not establish whether new units can be created later.

Inspect the current mint authority. Solana’s Set Authority reference says setting the selected authority role to None permanently removes that role. Transferring authority to another address is different from revoking it. A program-controlled authority also needs investigation rather than being treated as absent.

Keep the conclusion precise: mint authority removed is one specific permission check. It does not prove that freeze controls, Token-2022 extensions, concentrated holdings or removable liquidity are harmless. For historical claims, today’s authority state does not establish when revocation occurred; inspect the authority-change transaction too.

What a burn announcement can honestly prove

A useful evidence package contains the full mint, successful transaction links, burn amounts, decimals, observation times, a stated percentage baseline and the current authority status. It should separate gross destruction from net supply change.

“Tokens worth $150,000 burned” needs a valuation timestamp and price source. Multiplying 75 million tokens by a quoted $0.002 gives a $150,000 mark-to-market estimate in our hypothetical example. It does not prove anyone spent that cash buying the tokens, that the block could have been sold for that amount, or that holders gained that value.

A buyback is another claim: show the purchases and the subsequent burn separately. A treasury burn can be real without being a market buyback. Neither establishes future demand or guarantees a higher price. Panther’s market-cap and liquidity guide explains why a quoted price is not cash available to every holder.

Sources and verification

Reviewed November 7, 2026 against the linked Solana protocol/RPC documentation and Solscan’s explorer documentation. The tables and arithmetic are educational examples, not observed chain activity. No wallet connection, transaction submission or paid service is required to read public explorer records. This guide does not endorse a token or a burn service. Cover: conceptual illustration.

Sources

  1. 01Burn Tokens · Solanasolana.com/docs/tokens/basics/burn-tokens
  2. 02Transfer Tokens · Solanasolana.com/docs/tokens/basics/transfer-tokens
  3. 03getTokenSupply RPC reference · Solanasolana.com/docs/rpc/http/gettokensupply
  4. 04Solana RPC JSON Structures · Solanasolana.com/docs/rpc/json-structures
  5. 05Mint Tokens · Solanasolana.com/docs/tokens/basics/mint-tokens
  6. 06Set Authority · Solanasolana.com/docs/tokens/basics/set-authority
  7. 07Token Extensions · Solanasolana.com/docs/tokens/extensions
  8. 08Exploring Token Details page · Solscaninfo.solscan.io/exploring-token-details-page/

Responses

Links, wallet addresses and contact details are not allowed.

0/1000

No responses yet. Start the conversation.

Panther Journal — The intelligence brief

Stay ahead of the story.

Free. New investigations delivered when published. Unsubscribe anytime.

Launching something?

Work directly with Panther.

Start a project

More from the library