> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tokenomist.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Burn Taxonomy

# Overview

Tokenomist classifies token burn events using two dimensions: **Type** and **Reason**. Burns permanently remove tokens from circulation, directly reducing total supply — but not all burns are created equal. This taxonomy distinguishes between automated, protocol-level burns and discretionary, team-initiated ones, and clarifies the motivation behind each event. Understanding these distinctions helps users assess whether a project's deflationary mechanisms are structural and sustainable or one-off and discretionary.

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

# Access Features

<video src="https://mintcdn.com/daosurv/Mfr1OD2wOl3Tsgel/videos/burntaxonomy-access.mp4?fit=max&auto=format&n=Mfr1OD2wOl3Tsgel&q=85&s=6e5cb82a627a0943c29a431943b11341" controls={true} data-path="videos/burntaxonomy-access.mp4" />

This taxonomy is used across the following Tokenomist features:

* [**Burn Pane**](/burn-pane) — View a single token's burn activity, including summary metrics, historical chart, and event-level details.
* [**Burn Screener**](/burn-screener) — Scan all tracked projects with burn activity, sorted by value, recency, and supply impact.
* [**Compare Burn**](/compare-burn) — Compare burn scale and mechanisms across multiple projects side by side.
