# Burn

{% hint style="info" %}
This feature is only available to **Pro** users.
{% endhint %}

## Overview

The **Burn Page** provides an in-depth view of a project’s token burn activity. It captures every confirmed burn event and aggregates total value, supply offset, and underlying rationale, giving a clear picture of how deflationary mechanics operate across different projects.

<figure><img src="/files/1gOfZLOWqWxBzGMMPO4L" alt=""><figcaption></figcaption></figure>

## Accessing Burn Page

You can access the **Burn Page** by selecting any token from the **Burn Screener** or directly from its project profile.

Each Burn Page includes a **summary panel**, a **historical chart**, and a **burn event table**.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAiV8rQPRMYfCyYrQgX5Q%2Fuploads%2F2Cawe2EbENBS2erKjRLE%2Faccessing-burn.mp4?alt=media&token=e42ae9ea-7658-4dac-aeaa-b2f658be0531>" %}

## Using Burn

On the left you’ll see an overview summary of the burn information

* **Total Burn (USD)**: Total value of tokens burned across all burn events, denominated in USD.
* **Total Burn (Token)**: Total number of tokens permanently removed from supply.
* **Supply Offset**: The percentage of circulating (or released) supply offset by cumulative burns.
* **Burn Type**: Classification of the burn mechanism type and methodology.
* **Burn Reasons**: The primary rationale or purpose behind burn events.

The **Burn Chart** visualizes cumulative burns over time, overlayed with token price and burn value in USD.

You can toggle between **7D**, **1M**, **1Y**, or **All Time** views, and switch between **absolute** and **percentage** scaling for supply offset comparisons.

Hovering over the chart displays precise values for each date and cumulative totals. Below the chart, you’ll find a detailed table of all the latest 10 burn events.

Each row includes:

* **Date**: Timestamp of the burn event.
* **Burn Value (USD)**: USD value of tokens burned.
* **Burn Amount (Token)**: Quantity of tokens removed.
* **Burn Type**: Mechanism classification.
* **Burn Reason**: Context for the burn.
* **Source / Transaction**: Link to the originating on-chain transaction or record.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAiV8rQPRMYfCyYrQgX5Q%2Fuploads%2FbVJjWlVwwxREWlQRzlG1%2Fusing-burn.mp4?alt=media&token=2105f0df-c871-445c-af79-14a32fb3eaf3>" %}

## Burn Types

| **Type**             | **Description**                                                                                                                                                                                                 |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Programmatic**     | Burns that occur automatically according to protocol rules, such as fee burns, validator penalties, or on-chain logic. These are predictable and repeatable mechanisms embedded in the system’s design.         |
| **Non-Programmatic** | Burns executed manually or through discretionary decisions by the team, foundation, or community. Typically one-off or periodic, often based on governance votes, treasury decisions, or strategic adjustments. |

## Burn Reasons

| **Reason**           | **Description**                                                                                                                                            |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Governance**       | Burns decided through community or on-chain governance, such as proposals to reduce supply or allocate treasury funds to burn.                             |
| **Protocol Design**  | Burns that are an inherent part of how the protocol operates. For example, automatic burning of transaction fees or gas fees.                              |
| **Project Decision** | Burns initiated by the project’s core team or foundation, often as part of treasury management, tokenomics realignment, or discretionary supply reduction. |

## Why It Matters

Burns directly impact token scarcity and supply dynamics.

By tracking both **cumulative burn totals** and **burn rate trends**, you can assess whether a project’s deflationary design is structural, sustained, or symbolic.

This page helps investors and analysts understand:

* How much supply has been permanently removed.
* Whether burns are automatic or discretionary.
* How burns relate to price action and network activity.

## Where To Next?

* Compare across projects using the [Buyback Comparison](/features/buyback/buyback-comparison.md) page or [Burn Screener](/features/burn/burn-screener.md)


---

# Agent Instructions: 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:

```
GET https://docs.unlocks.app/features/token-page/burn.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.