Guides and answers for the Burn Bot.
A mint is the unique address of a token.
These are the most common issues during L1/L2 and how to fix them quickly.
| Stage | Purpose | Needs signature? | Needs tokens in burn wallet? | Typical failures | Fix |
These levels show how strongly a burn/proof is technically verified.
L2 simulates a burn. If the burn wallet has zero tokens for the mint, the simulation cannot proceed.
This guide shows how to test burn notifications using @burneventinfoBot.
A test push sends a simple message to your project's Info Bot channel. Use it to confirm that notifications work.
An L3 burn can reduce supply, but not every L3 burn is an official project burn.
Last updated: December 2025
These settings are required for burns/dryruns to work reliably.
The bot needs a Solana RPC endpoint to read data and send burns. This guide explains when the default shared RPC is enough and when a paid RPC makes sense.
Never enter seed phrases or private keys on any website or form.
| Role | Purpose | Must Sign? | Must Hold Tokens? |
On Solana, every real burn is a signed transaction. The question is which wallet signs it.
Solana supports token burns, but it does not provide a single standard for reporting supply changes. This bot bridges that gap.