Token supply limit
Configure the DALP token-supply-limit (capped) compliance module so total supply cannot exceed a fixed maximum.
The token-supply-limit compliance module (also called the capped module) enforces a fixed maximum total supply for an asset. DALP rejects any mint that would push the asset's total supply above the configured cap.
Use the cap when the operating model requires a fixed share count, a fixed cap on issuance for a private placement, or a hard ceiling on outstanding supply for a stablecoin reserve management posture. The cap does not adjust automatically when supply burns; if the operating model needs supply to track an evolving reserve, use Supply cap and collateral instead.
For the architecture reference, see Supply and investor limits.
Prerequisites
- The asset already exists (configure during creation) or you have the Asset administrator role on the deployed asset.
- The maximum supply value is signed off by your operating team and matches the regulatory or corporate-action approval.
Configure during asset creation
In the Asset Designer compliance step, pick the token-supply-limit module. Enter the maximum supply value in the asset's decimal units (the Designer converts to base units before deployment).
For instruments with an immutable share count (real-estate fractional ownership, fixed-supply equity issues), set the cap to match the corporate-approved share count. The cap value is restricted-mutable; updates run through the governance-update path.
Configure on an existing asset
From the asset detail workspace, open the compliance tab and update the cap. The platform queues an on-chain transaction. The new cap takes effect after confirmation.
Operating considerations
- The cap is checked against current total supply at the moment of the mint. The platform queues mints in nonce order; concurrent mint attempts share the same cap and the second mint fails if the first consumed the remaining capacity.
- Burning units does not change the cap. After burn, the next mint can re-fill capacity up to the cap value.
- The cap is restricted-mutable. Reducing the cap below the current supply is rejected; the operating team must burn supply first if the goal is to reduce the ceiling.
- The supply-limit module does not enforce collateral or any external dependency. For collateral-gated minting, use Supply cap and collateral.
What stays external
The decision on what the cap should be, the regulatory or corporate-action approval that sets it, and the audit trail justifying any cap update stay with your operating team.
Troubleshooting
| What you see | What to check |
|---|---|
| Mint blocked by cap | Confirm the requested mint plus current supply does not exceed the configured cap. |
| Cap update transaction rejected | The platform rejects cap reductions below current supply. Burn supply first or pick a higher target value. |
| Need collateral-driven cap | Use Supply cap and collateral instead; that module ties the cap to an attestation. |
Read next
- Compliance overview
- Supply and investor limits architecture
- Supply cap and collateral for collateral-attested supply caps.
Address block-list
Configure the DALP address block-list module so an asset rejects specific wallet addresses regardless of registered identity status.
Investor count limit
Configure the DALP investor-count compliance module so an asset cannot exceed a configured maximum number of unique holder identities.