Asset policy
Reference page for DALP asset policy compliance configuration, module categories, configuration scope, and the pages to use when reviewing per-asset rules.
An asset policy is the configured set of compliance modules and parameters that the platform evaluates for one regulated EVM asset. The policy decides which ordinary token operations can execute: minting, transfers, and burns.
Review the full model in How DALP applies per-asset compliance rules. Use this reference to find the right module page when you review a concrete asset.
What belongs in an asset policy
The platform stores policy choices per asset. A deployed compliance module can be reused across assets, but each asset keeps its own selected module list and parameter values. Changing one asset's policy does not affect another asset's policy.
| Policy area | What it controls | Start here |
|---|---|---|
| Geographic eligibility | Countries that may or may not hold the asset. | Country restrictions |
| Identity eligibility | Claim expressions, identity allow lists, identity block lists, and address block lists. | Identity verification, identity lists, and address block list |
| Supply and holder limits | Caps on supply or investor count. | Supply and investor limits |
| Transfer workflow | Prior approval requirements and holding-period checks before transfer execution. | Transfer approval and TimeLock |
| Collateral and backing | Collateral checks and supply-cap controls for backed assets. | Supply cap and collateral |
Runtime rule
For ordinary regulated operations, the platform reads the asset's active policy and evaluates the selected modules before the token state change. If a required module rejects the operation, the operation reverts and the token balance does not change. Stateful modules update their counters, approval usage, or holding-period records only after a successful operation.
Lost-wallet recovery differs from an ordinary transfer. The platform checks the identity registry's lost-wallet relationship and replacement wallet, then applies a forced balance update through recovery-specific controls. Review recovery controls separately from ordinary transfer policy.
Configuration review checklist
Before you move an asset policy into production, verify these facts for the specific asset:
- The token uses the intended identity registry and trusted issuer records.
- Every active module has a clear justification in the asset's jurisdiction, instrument type, and operating model.
- Module parameters match the schema for that module, including country-code format, identity or wallet address type, claim-expression shape, and numeric limit units.
- You have tested stateful modules across the lifecycle they track, including minting, transfers, burns, and any recovery-side state migration that applies to the asset.
- Governance roles covering install, disable, enable, uninstall, and reconfigure limit access to the intended operators.
- Operational approvals outside the smart contract transaction exist for policy changes that require maker-checker review.
Related pages
Compliance module index
Choose the DALP compliance module that matches each asset policy rule, including identity, geography, supply, approvals, collateral, and holding-period controls.
Country Restrictions
Choose CountryAllowList or CountryBlockList to permit or exclude token recipients by ISO 3166-1 country code, covering MiCA jurisdiction selection, OFAC sanctions screening, and similar regulatory requirements.