Token Supply Cap

Overview

How it works and why it matters

A supply cap specifies an intended upper bound on the total amount of a token. Some contracts enforce a fixed maximum in code, while others allow governance or privileged administrators to change the number. When an asset exists across bridges or multiple contracts, the meaning of global supply requires careful accounting for locked originals and minted representations. A published maximum is not proof of present circulating supply, market liquidity, or immutable scarcity.

Technical context

The cap may be immutable, governance-adjustable, chain-specific, or defined across multiple networks.

It differs from current total supply, circulating supply, and a mint cap assigned to one issuance path.

Operationally, analysis should inspect contract code, upgradeability, privileged roles, bridges, wrapped representations, burns, re-mint rules, migrations, and whether the published cap uses base or display units.

Practical checks

Separate the contract’s `totalSupply` value from unlocked and circulating supply reported by exchanges. If wrapped assets circulate on another chain, identify whether the underlying units are locked and whether the representation is counted separately. Review who can change the cap and whether an upgrade can replace the implementation.

Related concepts

Token Mint Cap; Token Burn Cap; Token Emission Schedule

Further reading

• docs.openzeppelin.com documentation