> For the complete documentation index, see [llms.txt](https://docs.chestfi.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chestfi.cash/tools/burn.md). # Burn Permanently remove tokens from circulation by sending them to an address nobody controls. * **Path:** Web App → **Burn** * **Status:** Live * **Fee:** Gas only ### How it works ChestFi sends your tokens to the **dead address**: ``` 0x000000000000000000000000000000000000dEaD ``` This is a well-known burn address. No private key exists for it, so anything sent there can never move again. The tokens still exist on-chain but are permanently out of circulation — which is exactly what makes the burn verifiable: anyone can look up the dead address's balance of your token and see precisely how much has been destroyed. * Tokens are sent to a dead address (`0x...dEaD`) * This permanently removes them from circulation * **The action cannot be undone** * You pay gas fees for the transaction ### Burning tokens 1. Go to **Burn** in the sidebar. 2. Paste the **Token Address** you want to burn. The Summary panel updates to reflect it. 3. Enter the **Amount to Burn**, in token units. 4. Approve the token spend, then confirm the burn. The **Burn Tokens** button stays disabled until both fields are valid and a wallet is connected. ### ⚠️ Warning > Burning tokens is permanent and irreversible. The tokens will be sent to a dead address and cannot be recovered. There is no undo, no admin recovery, and no support process. Triple-check the token address and the amount before confirming. Burning `10000000` when you meant `1000000` destroys nine million tokens you will never see again. ### What burning does and doesn't do **It does:** * Reduce circulating supply, permanently and verifiably. * Create a transparent on-chain record you can point to. **It does not:** * Automatically raise the price. Burning changes supply, not demand. Removing tokens that were never going to be sold changes nothing about the market. Burning your own idle treasury is a supply cut on paper; a buyback-and-burn funded by real revenue is a supply cut backed by real buying pressure. These are not the same event, and markets tend to price them differently. * Change the `totalSupply()` figure reported by a standard ERC-20 contract. The tokens leave circulation, but `totalSupply` still counts them unless the contract implements a true `burn()` that decrements it. Explorers usually show "circulating supply" net of the dead address, but be precise in your communications about which number you're quoting. ### Practical tips * **Do a test burn first.** Burn 1 token, confirm it shows up at the dead address on Blockscout, then do the real amount. * **Announce with a transaction hash.** A burn without a link is a claim; a burn with a tx hash is evidence. * **Consider locking instead.** If the goal is a credible commitment rather than permanent destruction, a long-dated Token Locker entry achieves the same trust signal while keeping optionality. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.chestfi.cash/tools/burn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.