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

This taxonomy is used across the following Tokenomist features:

Burn Pane — View a single token’s burn activity, including summary metrics, historical chart, and event-level details.
Burn Screener — Scan all tracked projects with burn activity, sorted by value, recency, and supply impact.
Compare Burn — Compare burn scale and mechanisms across multiple projects side by side.

​Overview

​Burn Types

​Burn Reasons

​Access Features

Overview

Burn Types

Burn Reasons

Access Features