A supply cap is a rule in a token's smart contract that stops minting once the total supply reaches a set maximum. A rate limit caps how much can be minted, transferred, or moved between chains within a period of time, then refills as the period passes. Issuers use both to bound what can happen to a token, even if a key or an integration behaves unexpectedly.
Last updated: November 9, 2026.
What is the difference between a supply cap and a rate limit?
A supply cap is a ceiling on the total. Once the token reaches it, the contract rejects any further mint, no matter who requests it. Some tokens fix the cap at deployment, and others let an authorized role raise or lower it.
A rate limit is a ceiling on speed. It allows activity up to a set amount per window, such as per hour or per day. When the window's allowance is used, further requests fail or wait until capacity returns.
| Control | What it limits | When it blocks | Typical use |
|---|---|---|---|
| Supply cap | Total tokens in existence | A mint would exceed the maximum | A fixed-supply asset or a backed asset limit |
| Mint rate limit | Tokens minted per period | A mint exceeds the period's allowance | Bounding issuance by a minter role |
| Transfer limit | Amount per transfer or per address | A transfer exceeds the set amount | Limiting single movements |
| Cross-chain limit | Amount moved between chains per period | A transfer exceeds the route's allowance | Bounding flows on each chain pathway |
Why would an issuer set these limits?
Limits reduce how much damage a single failure can do. If a minting key is misused, a rate limit bounds how many tokens can be created before someone notices. A supply cap keeps the total from growing past what the issuer intends, for example the amount of reserves backing the token.
Limits also make supply easier to explain. Holders and auditors can read the maximum and the per-period allowance from the contract when it exposes them.
How do limits work on a token that spans several chains?
Each deployment enforces its own rules, so a cap or limit on one chain does not automatically apply on another. A token that moves between chains also needs its total supply to stay consistent. With LayerZero's OFT standard, a transfer burns tokens on the source chain and mints the same amount on the destination, or an OFT Adapter locks them on the home chain, so the total supply across chains stays the same. The unified token supply explainer covers this model.
An OFT can be deployed with an optional rate limiter that caps how much can leave a chain toward another chain over a time window. A transfer above the limit reverts on the source chain.
Questions we get asked
Can a supply cap be changed after deployment?
It depends on the contract. Some caps are fixed in code. Others can be updated by an authorized role, which means the cap is only as firm as the controls on that role.
Does a rate limit stop normal users?
It depends on how the limit is set. A limit above expected activity mainly affects unusual spikes, and a transfer above the remaining allowance reverts and can be retried once the window refills.
Is a rate limit the same as a pause?
No. A pause stops the activity it covers until it is lifted, while a rate limit lets activity continue up to a set amount.
Set limits that match the asset
To discuss supply and transfer controls for an asset across chains, request a custom briefing.