SMART Protocol architecture moved
Find the current DALP SMART Protocol architecture page for ERC-3643 asset contracts, identity checks, compliance modules, and transfer validation.
The SMART Protocol architecture guide now lives in the asset contract component catalogue. Start with SMART Protocol integration (ERC-3643) when you need the ERC-3643 model for regulated transfers.
That guide explains how DALP asset contracts check recipient identity, evaluate compliance modules, run token-feature hooks, and update token state after the transfer is permitted.
Architecture map
The canonical page places the asset token at the enforcement point. It then follows the checks that decide whether a regulated transfer can change token state.
Where to go
The overview URL remains as a compatibility entry point for old bookmarks and search results.
The asset-contract page gives the full mental model before you continue to the concept, security, flow, and feature pages listed below.
Related architecture pages
| If you need to understand | Read this page |
|---|---|
| How ERC-3643 maps to DALP asset contracts | SMART Protocol integration (ERC-3643) |
| The ERC-3643 standard concepts used by DALP | ERC-3643 compliance standard |
| Identity claims, claim topics, and trusted issuers | Claims and identity model |
| The checks that run before regulated transfers | Compliance Transfer Flow |
| Runtime token features attached to assets | Token Features |
| How asset contracts are deployed and upgraded | Deployment Architecture |