Token Burn Cap

Overview

How it works and why it matters

A burn cap limits how many token units can be permanently removed under a specified rule. That might mean a maximum per transaction, over a 24-hour window, or during one authorized buyback program. The underlying token contract needs to define what counts as burned, how the cap resets, and whether privileged upgrades can alter enforcement. Simply sending tokens to a publicly inaccessible-looking address is not necessarily equivalent to using the contract’s recognized burn function.

Technical context

The cap limits how quickly or how far supply can be reduced.

It is distinct from a supply cap, which constrains issuance, and from a burn mechanism that defines how destruction occurs.

Operationally, the rule should specify the measured period, eligible burn sources, whether failed burns count, governance authority, reset timing, and treatment of tokens sent to inaccessible addresses outside the formal burn function.

Practical checks

Verify whether the burn is enforced by contract logic or by an administrator’s process. Check failed transactions, decimal scaling and whether burns free up minting headroom. A burn from an issuer-controlled address is different from destroying tokens held by an unrelated user without their permission.

Related concepts

Token Supply Cap; Token Mint Cap; Token Emission Schedule

Further reading

• docs.openzeppelin.com documentation