Investor count limit
Configure the DALP investor-count compliance module so an asset cannot exceed a configured maximum number of unique holder identities.
The investor-count compliance module enforces a maximum number of unique holder identities on an asset. DALP rejects any transfer that would push the holder count above the configured limit. Use the module for private-placement caps (Reg D 99-investor limit, Reg S investor restrictions) or any regulatory rule that bounds the size of the investor base.
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 holder count is approved by your operating team and reflects the regulatory or corporate-action rule.
- Holders have registered OnchainIDs (the module counts unique identities, not unique wallets).
Configure during asset creation
In the Asset Designer compliance step, pick the investor-count module and enter the maximum unique-holder value. For private placements limited to 99 investors, enter 99. For a smaller club deal, enter the approved size.
Configure on an existing asset
From the asset detail workspace, open the compliance tab and update the maximum value. The platform queues an on-chain transaction. The new limit applies forward; the platform does not retroactively block existing holders if the new limit is below the current count, but new transfers to fresh holders are blocked until burn or transfer reduces the count.
Operating considerations
- The count is per unique OnchainID, not per wallet. A holder with multiple wallets under the same identity counts once.
- The count increases when a new identity acquires a non-zero balance and decreases when an identity's balance returns to zero. Forced transfers and burns release count capacity.
- Transfers that move balance between two existing holders do not change the count. Transfers that introduce a new holder are checked against the cap.
- Set the value at the regulatory limit, not below. Manually tracking an off-by-one buffer creates operational risk; the module enforces the value exactly.
What stays external
The choice of cap value (regulatory limit, corporate-action approval, distribution-policy decision) and the audit trail justifying any update stay with your operating team.
Troubleshooting
| What you see | What to check |
|---|---|
| Transfer to a new holder rejected | Confirm the current holder count plus the new holder does not exceed the cap. |
| Holder count appears off | Confirm zero-balance accounts are not in the count. Use the holders tab on the asset detail workspace to inspect the active holder list. |
| Need to raise the limit | Update through the compliance configuration. The transaction is asynchronous; wait for confirmation before treating the new value as active. |
Read next
- Compliance overview
- Supply and investor limits architecture
- Identity allow-list for explicit holder approval alongside the count cap.