FAQ

Guides and answers for the Burn Bot.

Newbie Guide: Mint, Wallets & Burns (Solana)

A mint is the unique address of a token.

Common L1/L2 errors and fixes

These are the most common issues during L1/L2 and how to fix them quickly.

L1, L2, L3: What each stage checks

| Stage | Purpose | Needs signature? | Needs tokens in burn wallet? | Typical failures | Fix |

Trust Levels: L1 / L2 / L3

These levels show how strongly a burn/proof is technically verified.

Why L2 fails when the burn wallet is empty

L2 simulates a burn. If the burn wallet has zero tokens for the mint, the simulation cannot proceed.

How to configure the Notification Bot

This guide shows how to test burn notifications using @burneventinfoBot.

How to run a test push

A test push sends a simple message to your project's Info Bot channel. Use it to confirm that notifications work.

Official vs Custom Burn

An L3 burn can reduce supply, but not every L3 burn is an official project burn.

Privacy Policy - Burn Event Bot

Last updated: December 2025

Project setup checklist

These settings are required for burns/dryruns to work reliably.

RPC providers: do I need a paid endpoint?

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.

Security: You should never enter seeds/private keys

Never enter seed phrases or private keys on any website or form.

Wallet Roles in the Bot (Owner / Burn / Treasury)

| Role | Purpose | Must Sign? | Must Hold Tokens? |

When do I need my wallet for the burn?

On Solana, every real burn is a signed transaction. The question is which wallet signs it.

Why a Burn Bot?

Solana supports token burns, but it does not provide a single standard for reporting supply changes. This bot bridges that gap.