Key flows
Index of the seven most important system flows in DALP, covering platform operations and asset lifecycle capabilities with links to detailed walkthroughs.
Purpose: Provide a navigable index of the key platform and capability flows. Doc type: Reference (flow index). What you will find here:
- Platform flows that every transaction passes through
- Capability flows for specific asset lifecycle operations
- For each flow: trigger, outcome, and key components involved
Related: Architecture map | System context | Flows section | Components
Platform flows
These flows represent core platform operations. Every asset lifecycle action depends on one or more of them.
| Flow | Trigger | Outcome | Key components |
|---|---|---|---|
| Signing flow | Any state-changing operation (transfer, mint, redeem) | Transaction signed by custody provider and confirmed on-chain | Execution Engine, Transaction Signer, Key Guardian, Custody Provider (DFNS/Fireblocks), Chain Gateway, SMART Protocol compliance engine |
| Asset issuance | Issuer creates a new tokenized instrument | Asset contract deployed with compliance rules, identity requirements, and optional features configured | Asset Console/API, Execution Engine, Factory Registry, System layer, SMART Protocol |
| Compliance transfer | Token holder initiates a transfer | Transfer completes if both on-chain compliance and custodian policies pass; reverts otherwise | SMART Protocol compliance engine, Identity Registry, Compliance Modules, Custody Provider policy engine |
Capability flows
These flows represent specific asset lifecycle capabilities that issuers configure per instrument.
| Flow | Trigger | Outcome | Key components |
|---|---|---|---|
| DAIO offering | Issuer creates a Digital Asset Initial Offering | Verified investors participate atomically — settlement currency exchanged for digital assets with optional lock-up | DAIO Module, Compliance Layer, Settlement Engine, Custody Accounts |
| Airdrop distribution | Issuer initiates token distribution to a set of recipients | Tokens distributed to eligible addresses according to the configured strategy | Airdrop Addon, Compliance Layer, Identity Registry |
| Treasury distribution | Scheduled interval or lifecycle event (coupon date, maturity) | Settlement currency distributed from asset treasury to eligible investors proportional to holdings | Asset Treasury, Payment Features (Yield/Coupon/Redemption), Compliance Layer |
| XvP settlement | Counterparties agree to exchange assets | Atomic delivery-versus-payment across two asset legs — both complete or neither does | XvP Addon, Compliance Layer (both legs), Settlement Engine |
How to read a flow page
Each flow page in the Flows section follows a consistent structure:
- Overview -- what the flow does and why it matters
- Sequence diagram -- step-by-step visual with numbered steps
- Step breakdown -- detailed explanation of each step
- Failure handling -- what happens when a step fails
- Related resources -- links to component, security, and API documentation
Flow dependencies
All capability flows depend on the signing flow for on-chain execution and on the compliance transfer logic for transfer validation. The dependency structure:
- Signing flow -- used by every flow that changes on-chain state
- Compliance transfer -- used by every flow that moves tokens between addresses
- Asset issuance -- prerequisite for all capability flows (an asset must exist first)
- DAIO, Airdrop, Treasury, XvP -- independent of each other; each can be configured separately on an asset
Next steps
- Flows section for full walkthroughs of each flow
- Components to understand the components referenced above
- Security for how authentication and compliance enforcement work across these flows