Asset Contracts
DALPAsset is the recommended contract type for all new tokenization projects. Configure token features and compliance modules per instrument. Specialized types remain supported for existing deployments.
In development: DALPAsset and token features are behind a feature flag and under active development. Interfaces and behavior may change before general availability.
Purpose: Define DALP asset contract types, the recommended approach for new projects, and per-instrument legacy-equivalent presets.
- Doc type: Reference
- What you'll find here:
- DALPAsset — recommended configurable contract type
- Legacy-equivalent presets — feature and compliance starting points per instrument
- Legacy types — when and why specialized contract types still exist
- Unified role-based access control
- Deployment architecture
- Related:
DALPAsset: recommended for all new projects
DALPAsset is the recommended contract type for all new tokenization projects. It extends SMART Protocol (ERC-3643) with runtime-configurable token features and compliance modules — no redeployment needed to evolve.
See DALPAsset for the full architecture: how configuration works, change impact, and relationship to legacy types.
Legacy-equivalent presets at a glance
| Preset | Token features to attach | Compliance modules |
|---|---|---|
| Bond | Fixed Treasury Yield, Maturity Redemption, Historical Balances | Capped |
| Equity | Voting Power, Historical Balances | Per jurisdiction |
| Fund | AUM Fee, Voting Power, Historical Balances | Per jurisdiction |
| StableCoin | Historical Balances | Collateral |
| Deposit | Historical Balances | Per jurisdiction |
| RealEstate | Historical Balances | Capped |
| PreciousMetal | Historical Balances | Per jurisdiction |
See Legacy-Equivalent Presets for the full configuration spec — token features, compliance modules, parameters, and legacy equivalents per instrument.
When to choose
- DALPAsset — runtime flexibility: attach and reconfigure token features post-deployment. Recommended for all new projects. See DALPAsset for details and Legacy-Equivalent Presets for configuration guidance.
- Legacy specialized type — compile-time immutability: features embedded at deployment cannot change. Choose when compliance or legal frameworks require post-issuance immutability guarantees. See Legacy Types for the full decision checklist.
Common foundation
Every asset type — DALPAsset and specialized — shares the same SMART Protocol foundation:
- ERC-3643 compliance — on-chain transfer enforcement via compliance modules
- ERC-20 compatibility — standard wallet, DEX, and tooling support
- OnchainID integration — identity registry for KYC/AML claims
- ERC-2771 meta-transactions — gasless operations via trusted forwarders
- ERC-165 introspection — external systems query supported capabilities
- Unified RBAC — seven per-asset roles with separation of duties (see RBAC)
Further reading
- DALPAsset — recommended configurable contract type
- Legacy-Equivalent Presets — pre-built configurations per instrument type
- Legacy Types — compile-time types, decision checklists, coexistence guidance
- RBAC — per-asset role model and separation-of-duties invariants
- Deployment Architecture — factory pattern, invariants, failure modes
- Token Features — runtime-pluggable feature catalog
- Compliance Modules — transfer and supply rule engine
Feeds system
The Feeds system provides reliable, system-guaranteed price and foreign exchange data for digital assets through a centralized directory with multiple feed types and subject scopes.
SMART Protocol integration (ERC-3643)
How DALP integrates the SMART Protocol (ERC-3643) as its on-chain compliance foundation — responsibility boundaries, multi-asset model, and where enforcement details are documented.