SettleMint

Business documentation

Choose the right DALP business guide for evaluation, market context, use-case routing, compliance posture, market data infrastructure, terminology, and legal notices before an architecture review.

The business guides help executives, programme owners, and evaluators decide whether DALP fits a regulated digital asset programme. Use them to see what DALP covers, where your organisation still makes operating decisions, and which guide to read before an architecture or procurement review.

Start with the question in front of you. Use the executive overview for the platform model, market context for institutional requirements, use cases for asset-class routing, compliance posture for controls, market data for pricing integrity, the glossary for terminology, and the legal pages for terms and privacy notices.

Rendering diagram...

DALP provides platform capabilities, lifecycle controls, supported asset templates, compliance enforcement, market data primitives, and the operating split described in this section. Your organisation decides the business case, jurisdiction, custody policy, issuer mandate, regulator engagement, distribution approach, and operating model that sit around those capabilities.

These guides describe supported DALP behaviour and shared terminology. They do not create legal opinions, custody arrangements, SLA terms, regulator approvals, bridge operations, or non-EVM deployment support. Treat those items as organisation-specific decisions unless a detail page states a DALP behaviour explicitly.

What DALP covers

DALP gives a regulated digital asset programme one EVM-based platform for asset issuance, identity and compliance enforcement, custody-routed signing, settlement coordination, lifecycle servicing, market data, and indexed operating records. The business guides describe that model in buyer language so an evaluator can test fit before reading the architecture or integration documentation.

AreaDALP definesYour organisation defines
Platform modelLifecycle controls, asset templates, compliance enforcement, custody-routed signing, evidenceBusiness case, target operating model, jurisdictional scope, and risk appetite
Asset programmeSupported asset classes, instrument templates, servicing actions, and lifecycle statesIssuer mandates, distribution channels, investor base, and commercial terms
Compliance postureIdentity registry, claims, transfer controls, audit-log emission, and enforcement evidenceRegulator engagement, legal opinions, jurisdictional approvals, and policy ownership
ExclusionsDocumented platform behaviour and shared terminology onlyCustody arrangements, SLA commitments, bridge operations, and non-EVM deployment decisions

Pick the right path

If you need to...Start hereThen read
Evaluate DALP for a new programmeExecutive overviewDALP solution model and Platform capabilities
Understand institutional requirementsWhat institutions requireDigital asset lifecycle platform
Match an asset class to a DALP templateUse casesThe corporate bonds, equities, funds, stablecoins, real estate, precious metals, deposits, and structured products pages
Review the compliance and security postureCompliance and securitySecurity overview for the layered control model
Decide how market data is sourced and usedMarket data infrastructureFeeds overview for the integration view
Align reviewers on shared terminologyGlossaryArchitecture overview for the technical mapping
Review legal terms before procurementTerms of servicePrivacy policy

Evaluation model

DALP exposes four business-facing layers:

  • The platform capabilities describe what the system does after the first token is created: issuance, holder controls, servicing, settlement, evidence, and integration surfaces.
  • The use case library matches each supported asset class to instrument templates, lifecycle controls, and external operating responsibilities. Use the page to confirm whether a target asset fits the existing model before scoping integration work.
  • The compliance and market data sections explain the control model: identity, claims, transfer enforcement, market data primitives, and pricing integrity for valuation.
  • The glossary and legal sections give reviewers shared language and the procurement-ready terms before an architecture review.

Most evaluations combine all four layers. Read the executive overview first, then use the asset programme and compliance pages to test the operating model. Move to architecture documentation when reviewers need deployment detail, and to developer documentation when integration work begins.

Start here

Market context

Asset use cases

Compliance and trust

Reference

On this page