Asset Issuance
Step-by-step flow for issuing a new digital asset on the DALP platform, from infrastructure deployment through identity setup, compliance configuration, and initial token operations.
Purpose
Step-by-step reference for the complete asset issuance workflow, from platform infrastructure through first token operations.
- Doc type: Reference (flow)
- What you'll find here:
- Multi-phase deployment sequence
- Transaction dependencies between phases
- Role requirements at each stage
- First-operations validation
- Related:
- Asset Contracts — token types and configurations
- Signing Flow — transaction signing sequence
- Authorization — role assignments
Deployment phases
Asset issuance spans 7 phases. Phases 1-3 execute once per platform deployment. Phases 4-7 repeat for each new instrument.
Phase details
Phase 1: Infrastructure deployment
Deploys all implementation contracts and the system factory. On SettleMint networks with genesis allocations, implementation contracts are predeployed — execution begins at Phase 2.
| Step | Transaction | Sender |
|---|---|---|
| 1 | Deploy 43 implementation contracts (system, token, addon, compliance) | Deployer |
| 2 | Deploy DALPSystemFactory with all implementation addresses | Deployer |
Output: System factory address
Phase 2: System bootstrap
Creates the platform system instance and registers all factories.
| Step | Transaction | Role required |
|---|---|---|
| 1 | createSystem() on SystemFactory | Deployer |
| 2 | bootstrap() on System proxy | Deployer |
| 3 | Register token factories (Bond, Deposit, Equity, Fund, StableCoin) | Deployer |
| 4 | Register addon factories (yield schedule, XvP, airdrops, vault) | Deployer |
Output: System proxy, access manager, identity registry, compliance contract, all factory registries
Phase 3: Identity & compliance setup
Configures the identity verification system and global compliance rules.
| Step | Transaction | Role required |
|---|---|---|
| 1 | Grant identity manager role | System admin |
| 2 | Create identities for actors | Each actor |
| 3 | Register identities in registry | Identity manager |
| 4 | Add trusted claim issuer(s) | Claim policy manager |
| 5 | Issue KYC/AML claims to identities | Actors (signed by issuer) |
| 6 | Add global compliance modules (country block, address block) | Compliance manager |
Phase 4: Asset creation (per instrument)
Creates a new token through the appropriate factory.
| Step | Transaction | Role required |
|---|---|---|
| 1 | Call create<AssetType>() on the asset factory | Token manager |
| 2 | Token factory deploys proxy, creates identity, registers in identity registry | Automatic |
| 3 | Add asset metadata claims (classification, ISIN) | Token contract |
Output: Token proxy address, token identity, per-token access manager
Phase 5: Role assignment (per instrument)
Assigns per-token roles to operators.
| Step | Transaction | Role required |
|---|---|---|
| 1 | Grant supply management role | Token admin |
| 2 | Grant emergency role | Token admin |
| 3 | Grant governance role (if features needed) | Token admin |
Phase 6: Feature attachment (per instrument)
Optionally attaches runtime features via addon factories.
| Step | Transaction | Role required |
|---|---|---|
| 1 | Deploy feature proxy via addon factory (e.g., yield schedule) | Governance |
| 2 | Attach addon to token contract | Token admin |
| 3 | Configure per-token compliance modules | Compliance manager |
Phase 7: Initial operations
Validates the token with first operations.
| Step | Transaction | Role required |
|---|---|---|
| 1 | Mint tokens to initial holders | Supply management |
| 2 | Transfer between verified holders | Token holders |
| 3 | Verify compliance enforcement (blocked transfers fail) | — |
Key dependencies
- Identity registration (Phase 3) must complete before any token operations
- Global compliance modules (Phase 3) apply to all tokens automatically
- Per-token compliance modules (Phase 6) are additive to global modules
- All transactions execute through the Signing Flow
See also
- Signing Flow for how each transaction is signed
- Deployment Architecture for factory deployment patterns
- Authorization for role definitions
Signing Flow
End-to-end transaction signing sequence in DALP, from on-chain compliance validation through the unified signer interface to MPC custody providers (DFNS and Fireblocks), including custodian policy evaluation and blockchain broadcast.
Compliance Transfer
Step-by-step sequence for how DALP validates token transfers through the compliance engine, from identity resolution through sequential module evaluation to post-transfer state updates.