Coin Forge Hub / Knowledge library · Research · 2 min read
Supply has several definitions
A token contract’s totalSupply field reports a quantity according to its implementation. Circulating supply is usually a data-provider classification about which units count as available to the market. Maximum supply is a claimed or enforced upper limit. These values answer different questions and should not be substituted casually.
A burn may reduce a contract’s recorded supply, or a project may describe tokens sent to an inaccessible address as economically removed. Those mechanisms are not identical. Read the implementation and provider methodology before comparing figures from different dashboards.
A hypothetical allocation ledger
Consider a token with 100 million issued units: 40 million publicly distributed, 30 million held by a treasury, and 30 million subject to a vesting contract. One provider might exclude both restricted allocations from circulation. Another might classify some treasury units differently. The disagreement can be methodological rather than fraudulent arithmetic.
Suppose 5 million vested units become transferable next month. That changes availability even if no new units are minted. Alternatively, a mint function could increase total supply while all new units remain locked. Issuance and unlocking affect different parts of the supply story.
A useful worksheet starts with allocation addresses and vesting rules, then reconciles them with onchain balances at a specified block. Record which addresses are excluded and why. Do not assume that a public label such as “team” establishes the precise legal or technical restrictions on those holdings.
Authority can change the future
Inspect who can mint, alter caps, upgrade implementation code, or modify vesting. A cap in an implementation may not be permanent if an administrator can replace that implementation. Economic promises should be evaluated together with the authority capable of changing them.
Rebasing tokens and shares representing underlying assets need special treatment. A changing unit balance may reflect a designed accounting adjustment rather than a discretionary issuance event. Compare the token’s unit model with the underlying claim before calculating dilution from a single balance chart.
Cross-chain representations add another reconciliation problem. Tokens locked on one network and represented on another should not automatically be counted twice as separate economic supply. Trace backing and minting paths, and distinguish canonical issuance from bridged representations and unrelated tokens sharing a symbol.
Supply review checklist
- Identify chain, contract, unit scale, and snapshot block.
- Separate issued, circulating, vested, locked, and maximum quantities.
- Reconcile major allocations with address balances and enforceable restrictions.
- Identify mint, burn, rebase, and upgrade authorities.
- Document treatment of treasury holdings and cross-chain representations.
Repeat the worksheet when significant contract or governance changes occur. A one-time supply snapshot cannot establish a permanent issuance policy, especially when permissions or token accounting can change independently of the website’s tokenomics diagram.
Frequently asked questions
Does a burn guarantee a higher price?
No. Price also depends on demand, liquidity, expectations, and the scale and meaning of the burn. Arithmetic supply reduction alone does not determine market outcomes.
Is a maximum-supply statement enough?
No. Determine whether the limit is enforced, who can change relevant code, and which network representations the statement covers.