Digital Asset Lifecycle Platform documentation

DALP documentation is the map for evaluating and operating regulated digital assets on EVM-compatible networks. It routes business sponsors, architects, operators, developers, and reviewers to the page that answers their current question without forcing them through the whole docs set.

Start with the business and control model, move into architecture when you need responsibility splits, then use the operator and developer guides for the workflows and APIs that run the platform.

What DALP is

The SettleMint Digital Asset Lifecycle Platform is a control plane for regulated tokenised assets on EVM-compatible networks. It gives institutions one platform surface for creating assets, enforcing eligibility, submitting lifecycle actions, coordinating settlement and servicing, and reading operational state.

The docs describe DALP as five cooperating layers:

The core mental model is: request, execution, enforcement, evidence. Operators or integrations start work through DALP. The execution layer controls the long-running transaction path and signing handoff. SMART Protocol contracts enforce configured asset and compliance rules on-chain. The indexer turns emitted events into the state shown in dashboards, API reads, reports, and operational review.

Choose the path for your role

Pick the card that matches the decision you need to make. Each audience root gives you a short first path and links across to the pages another reviewer will need for the same decision.

If the review has multiple readers, use the architecture overview as the shared checkpoint. It defines what DALP controls and what the institution, custody provider, EVM network, compliance provider, and downstream systems still own.

Cross-audience routes

If you have 15 minutes

Use this path when you need a fast view of DALP before a demo, architecture review, or implementation planning session:

1. Read Introduction for the tokenisation and lifecycle model.
2. Read Digital asset lifecycle platform to connect the lifecycle-platform concept to DALP's product layers.
3. Read DALP overview for the platform capabilities and operating evidence DALP exposes.
4. Read Architecture overview for the control plane, state-change path, and responsibility split.
5. Choose one working surface: User guides for console operations or Developer guides for API, CLI, and event integration.

After that path, use the table above to go deeper by reader role rather than reading the docs in page order.

Documentation map

Executive overview

Use the executive overview to understand the business problem, the asset tokenisation model, and the platform capabilities before reading architecture detail.

• Introduction explains asset tokenisation, lifecycle controls, compliance, custody and signing responsibilities, settlement, and operating records.
• DALP overview describes the platform capabilities for issuance, compliance, custody-aware approvals, settlement, servicing, exception handling, and operating evidence.
• Use cases maps DALP to common regulated digital asset scenarios.
• Glossary defines product, tokenisation, compliance, and architecture terms used across the docs.

Architecture

Use the architecture section when you need the bank-grade control review: platform layers, responsibility splits, deployment topology, security model, integration points, operability, data domains, and limits.

• Architecture overview explains the control model, ownership split, state-change path, and explicit limits.
• Architecture map routes reviewers by platform layer, operating concern, and integration question.
• Components describes the major platform components and where each responsibility sits.
• Flows traces key platform operations end to end.
• Integrations covers external systems such as custody providers, compliance providers, EVM network access, and downstream consumers.
• Security covers authentication, authorisation, identity compliance, wallet verification, and related controls.
• Operability covers observability, database architecture, recovery concerns, and production failure modes.

User guides

Use the user guides when an administrator, compliance officer, or operations team needs to run a governed task through the platform console.

• User guides is the operator task index.
• Platform setup starts platform administration.
• Asset creation covers deploying a tokenised asset through the Asset Designer.
• Compliance covers compliance templates, trusted issuers, KYC verification, and collateral configuration.
• Asset servicing covers minting, burning, forced transfers, pauses, and asset administrator changes.
• System addons covers optional platform capabilities such as XvP settlement and yield schedules.

Developer guides

Use the developer guides when you need to automate DALP workflows, call the API, build against generated types, use the CLI, or connect platform events to other systems.

• Developer guides is the technical integration index.
• API integration getting started starts API key and TypeScript client setup.
• API reference provides the OpenAPI specification and type-safe client generation path.
• Token lifecycle covers token creation, minting, transfers, and burns through API workflows.
• Events catalogue covers lifecycle events, webhook delivery, payload privacy, retries, and audit proofs.
• Transaction tracking explains how integrations follow long-running blockchain actions.

Runbooks and resources

Use runbooks for coordinated operating procedures that cross system, chain, and provider responsibilities. Use appendices when you need terminology, deployment prerequisites, or legal notices.

• Runbooks lists high-control operational procedures.
• Rotate provider claim signer key covers compliance provider signer rotation.
• Self-hosting prerequisites covers deployment prerequisites for self-hosted environments.
• Glossary defines recurring terms.
• Privacy policy provides the public privacy notice.

From evaluation to implementation

For a first bank-grade review, read in this order:

1. Introduction to align on asset tokenisation, lifecycle controls, and institutional adoption concerns.
2. Digital asset lifecycle platform to understand the lifecycle-platform model and DALP's five layers.
3. DALP overview to understand the platform capabilities after launch.
4. Architecture overview to review the control plane, ownership responsibilities, state-change path, and limits.
5. Architecture map to choose the next architecture path by review question.
6. User guides or Developer guides to move from evaluation into console operations or API integration.
7. Runbooks and Operability when the review turns to production procedures and failure handling.

This sequence keeps the evaluation grounded: business purpose first, architecture and responsibility splits second, then the detailed operator and developer surfaces that execute the model.