> For the complete documentation index, see [llms.txt](https://docs.proxima.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxima.tools/live-settings/burn-supply.md).

# Burn Supply

### **How Burning Works**

1. Select the **percentage of total supply** you want to burn.
2. Proxima burns the tokens **from your Deployer wallet only**.
3. The burn is **instant and irreversible**.
4. A confirmation modal appears, showing the **transaction details**.

<div align="left"><figure><img src="/files/vJLk0HotQB6q8dgn3e4v" alt="" width="563"><figcaption></figcaption></figure></div>

### **Proof of Burn**

After confirming the burn, the modal displays the **transaction hash**.\
You can share this transaction as a **verifiable Proof of Burn** with your community, KOLs, or analysts.

This ensures full transparency and makes it easy to demonstrate that the burn is legitimate and on-chain.

***

### **Notes**

* Burning reduces the circulating supply but does not affect liquidity directly.
* Only tokens currently held by the Deployer wallet can be burned.
* Use burns strategically to reinforce confidence post-launch.

***


---

# 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.proxima.tools/live-settings/burn-supply.md?ask=<question>&goal=<endgoal>
```

`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.