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.
Purpose: Define the integration boundary between DALP and the SMART Protocol — what each layer owns, how multiple assets are organized, and where to find enforcement details.
- Doc type: Explanation
- What you'll find here:
- What SMART Protocol provides to DALP
- Responsibility boundaries (DALP vs SMART)
- Multi-asset organization model
- Pointers to DALPAsset, token features, and compliance enforcement
- Related:
What is SMART Protocol?
SMART (SettleMint Adaptable Regulated Token) Protocol is an ERC-3643 implementation that DALP uses as its on-chain compliance foundation. ERC-3643 defines a specification for security tokens where transfers are only permitted when a compliance engine — consisting of one or more modular rules — approves them.
SMART provides three layers that DALP builds on:
| Layer | What it provides |
|---|---|
| Token | ERC-20 compatible contracts with compliance hooks and modular extensions |
| Compliance | Orchestration engine that evaluates configurable rule sets before each transfer |
| Identity | On-chain identity management via OnchainID (ERC-734/735), storing KYC/AML claims |
DALP extends these layers with access control, proxy architecture, infrastructure integration, runtime token features, and system-seeded compliance templates.
Responsibility boundaries
| Concern | DALP responsibility | SMART responsibility | Where documented |
|---|---|---|---|
| Token lifecycle | Factory deployment, proxy upgrades, role assignment | ERC-20 token logic, compliance hook invocation | Deployment Architecture |
| Compliance rules | System-seeded templates, module configuration per instrument | Rule evaluation engine, module interface | Compliance Modules |
| Identity verification | Claim issuance workflow, trusted issuer management | Identity registry, claim storage (OnchainID) | Identity & Compliance |
| Token features | Runtime-pluggable features (fees, yield, governance) | Extension hook points (SMARTConfigurable) | Token Features |
| Access control | Seven per-asset roles, multi-tenant authority model | Role-checking hooks | RBAC |
| Transfer enforcement | Policy design (which modules, which parameters) | On-chain enforcement (revert if non-compliant) | Compliance Transfer Flow |
| Multi-asset organization | Instrument profiles, shared identity registries | Separate-contract-per-instrument model | Legacy Types |
Organizing multiple assets
ERC-3643 uses a separate contract per instrument model. Each financial instrument — a bond tranche, equity share class, or fund unit — is deployed as its own token contract with independent compliance configuration and lifecycle.
This provides:
- Lifecycle isolation — one bond can mature while related equity continues trading
- Compliance independence — each instrument has its own module configuration and investor restrictions
- Upgrade independence — upgrade one instrument without risk to others
- Clear accounting — each token has its own
totalSupply, holder list, and transaction history
Related assets are linked through on-chain references (when behavior depends on another asset) or identity claims (when assets share an issuer or program for reporting).
ERC-3643 was chosen over ERC-1400 for its modular compliance engine, on-chain identity integration via OnchainID, and active ecosystem support.
DALP's recommended approach
DALPAsset is the recommended contract type for all new deployments. It extends SMART Protocol with the SMARTConfigurable extension, allowing any combination of token features to be attached at runtime — after deployment.
- DALPAsset — full architecture and configuration model
- Legacy Types — compile-time types and when they still apply
- Legacy-Equivalent Presets — pre-built configurations per instrument type
Where to read next
- How identity enforcement works — Identity & Compliance
- What each compliance rule does — Compliance Modules
- Transfer enforcement step-by-step — Compliance Transfer Flow
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.
DALPAsset
Recommended configurable asset contract. Attach token-features and compliance modules per instrument; evolve configuration post-deploy under governance controls.