How to Announce a Token Burn (With Proof)

A burn is one of the few things a token team can do that anyone can verify. Tokens sent to an address nobody controls, or destroyed by the contract, cannot come back, and the chain records exactly when and how many. That is what makes a burn worth announcing, and also why an announcement without proof falls flat.

People who have been around crypto for a while have seen burns that were not quite burns:

• Tokens moved to a wallet the team still controls, announced as “burned”.
• A round number in the post that does not match any transaction.
• A percentage of the circulating supply passed off as a percentage of the total.
• The same burn announced twice, once as it happened and again in a monthly total.

A transaction link answers all four before anyone has to ask. It also turns a one-off post into a habit people can follow: every burn, same format, same proof.

Not every contract burns by sending tokens to a dead address. Some destroy them, so the total supply goes down instead. In that case show the supply before and after, with the transaction between them.

• A one-off burn. The team sends a set amount to a burn address. Prove it with the one transaction and the sender, so people can see it came from the wallet you say it did.
• A buyback and burn loop. A contract or the team buys tokens with funds from somewhere, then burns them. Show the money going in, the buy and the burn, each as its own transaction.
• A burn on every trade. The token’s contract burns a share of a tax automatically. Tokens launched on Torch can set part of their buy tax to buyback and burn, done by Torch’s contract on every buy. There are too many transactions to list, so show the running total at the burn address and how it is calculated.
• A burn funded by revenue. A share of what a product earns buys and burns the token on a schedule. Show each scheduled burn with its transaction, and the rule it follows.

Our own token uses two of these, and our Proof of Burn page shows how they can sit side by side. It reads Robinhood Chain when the page loads: the total held at the burn address, the weekly burns from 30% of crypto payments listed one by one with their transactions, and the rest, mostly burned by Torch’s contract on every buy. Nothing on it is typed in by us. The $LOUD page explains the rules behind it.

The film at the top of this post was made for Proof Hunters, a crypto project with an hourly buyback and burn on Robinhood Chain. The brief was to announce a $1,000 deposit into the burn loop and show exactly how it turns into burned tokens, receipts included.

It works because every scene is something you can check:

• The deposit goes into an open buyback contract on Robinhood Chain, and the film says plainly that funds sent there cannot be withdrawn.
• The loop is one pipeline: every hour the contract buys with part of its balance, within a floor and a cap, then calls burn(). Anyone can trigger a due buy.
• The receipts close the film: the deposit, the buy and the transfer to 0x…dEaD, each as a row with its own Verify link.
• The ending is the point: “Don’t trust. Verify.”, with the project’s burn page.

It also looks like Proof Hunters, with pixel fire and a chiptune score in the project’s own style, so the proof reads as part of the brand rather than a spreadsheet.

For X or Telegram, short and checkable. Replace the brackets with the figures from the explorer:

Leave out “bullish”, “supply shock” and anything else that predicts the price. The figures make the case on their own, and readers trust them more without the commentary.

• Rounding up. If the explorer shows a figure just under a round number, post that figure, not the round one.
• Mixing up locked and burned. Locked tokens come back on the unlock date; burned ones never do. Call each by its name.
• Using the wrong supply. Say whether a share is of the total supply or of what circulates, and use the same one every time.
• Counting a burn twice. Weekly posts and a monthly total should both point at the same transactions.
• Linking a screenshot instead of the chain. A picture of a transaction is not proof; a link to the explorer is.

A weekly burn is the easiest post-launch news to keep up, which makes it a good first habit. loudscene has three ways to film it:

• Burn report and Burn with proof templates: the burned share counting up, or each burn transaction as a row with its hash and block, then a verify-on-the-explorer ending. Browse them in the crypto pack.
• The weekly burn report in Crypto Pro: connect your token on Robinhood Chain, Ethereum, Base or Arbitrum, and every week we read each transfer to 0x0, 0x…dEaD or your own burn addresses and draft a film from those numbers alone. No AI writes the figures.
• The loudscene Agent picks up the burn report as news and sends the draft to your team to approve.

Burns are one part of a month of posts; see our plan for the first 30 days after launch. Buyers look at burns too, which is why they top our anti-rug checklist.