Crypto 101 · Research papers
Token Issuance and Mint Authority: Rigid Supply vs. Flexible Supply
Abstract
On a proof-of-work base layer, new units come only from the block subsidy defined in consensus code. On a proof-of-stake smart-contract network a token is created by a program that can include an authority allowed to mint more. This flexibility enables useful financial products but shifts trust from protocol rules to whoever holds the authority. We describe both models and give a checklist for verifying supply.
Keywords: mint authority, freeze authority, SPL token, ERC-20, fixed supply, tokenomics
1. Two ways supply comes into existence
On a proof-of-work chain, new units appear as the block subsidy. There is no account that can decide to issue more; the rule is part of the consensus code, and every full node rejects blocks that break it [1, 2]. Changing the schedule requires a network-wide fork, which is why its supply feels rigid.
On a smart-contract network, a token is a record created by a program. On Solana, a mint account records the token's supply and can name a mint authority, the account authorised to create new units, and a freeze authority, the account authorised to freeze token accounts so tokens cannot be transferred. Both are optional, and if no mint authority is present the mint has a fixed supply [3]. On Ethereum, the ERC-20 standard defines the interface for balances and transfers but not a supply policy; whether more can be minted depends on the contract [4].
2. Consequences
Table 1. Supply mechanics by network type.
| Question | Proof-of-work base layer | Token on a smart-contract network |
|---|---|---|
| Who can create new units? | Miners, only through the block subsidy the rules allow | The mint authority or contract logic, if any |
| How do you verify the supply policy? | Read consensus code; supply follows from it | Inspect the mint: authority present or none; read the contract |
| Can supply change later? | Only by a network-wide fork | Yes if an authority or upgradeable contract exists |
| Can balances be frozen? | Not by protocol design | Yes if a freeze authority or contract logic exists |
| Main risk | Ossified policy that may not fit future needs | Trust in whoever controls the authority |
3. Flexibility is a feature for finance
The flexibility is not a flaw, and it is why proof-of-stake networks host most token issuance [5, 6]. A stablecoin needs to mint when reserves are deposited and burn when they are redeemed; a wrapped asset needs the same. A token with a fixed supply cannot do either. So the useful question is not whether an authority exists but what constrains it: a proof of reserves, an audit trail, revocation after a sale, or a multi-party control structure.
4. A checklist for any token
- Is there a mint authority? If it is none, supply is fixed; if it exists, who controls it and what limits it?
- Is there a freeze authority, and who holds it?
- Is the token program upgradeable, and by whom?
- How is supply distributed, and how concentrated are the largest holders?
- Are there scheduled unlocks that will add to tradeable supply?
- If the token claims to be backed by another asset, where can the backing be verified?
5. Reading the two together
The asymmetry explains the roles in this series. Proof-of-work chains encode a schedule that changes only by network-wide fork [1], while a smart-contract token follows whatever its program permits [4]. Rigid issuance is valuable for an asset whose main claim is scarcity; flexible issuance is valuable for instruments that must track deposits, loans or reserves. The conservation principle links them: a flexible token that claims to represent a rigid asset should be constrained so that its supply never exceeds the backing.
References
- Bitcoin Core developers (2009). GetBlockSubsidy (src/validation.cpp). Bitcoin Core source code: the consensus rule for the block subsidy (50 coins, halved every nSubsidyHalvingInterval blocks). https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp
- Dogecoin Core developers (2013). GetDogecoinBlockSubsidy (src/dogecoin.cpp). Dogecoin Core source code: a constant 10,000 DOGE per block once the chain passes 6 halving intervals (block 600,000). https://github.com/dogecoin/dogecoin/blob/master/src/dogecoin.cpp
- Solana Foundation (2024). Tokens on Solana. Solana documentation: mint accounts, mint authority, freeze authority; with no mint authority the mint has a fixed supply. https://solana.com/docs/core/tokens
- Vogelsteller, F., & Buterin, V. (2015). EIP-20: Token Standard. Ethereum Improvement Proposal defining the ERC-20 fungible token interface. https://eips.ethereum.org/EIPS/eip-20
- ethereum.org (2022). Proof-of-stake (PoS). Ethereum developer documentation for the proof-of-stake consensus mechanism. https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/
- Yakovenko, A. (2017). Solana: A new architecture for a high performance blockchain. Whitepaper introducing Proof of History. https://solana.com/solana-whitepaper.pdf
Common questions
What is a mint authority?
On Solana, the account authorised to create new units of a token, increasing its supply. If no mint authority is present the mint has a fixed supply.
Can a mint authority be removed?
Yes. Solana authorities are optional and can be set to none, after which no further tokens can be minted.
General education, not financial, tax or legal advice. Figures are schematic. Protocol parameters are cited to primary sources and can change; verify against the linked source before relying on them.