Architecture documentation
Choose the right DALP architecture guide for the platform map, design principles, concepts, components, flows, integrations, data availability, operability, and self-hosting decisions.
The architecture guides are for solution leads, architects, and review teams scoping DALP for a regulated digital asset deployment. Solution leads use them to map the platform onto a target operating model. Architects use them to inspect components, flows, and integration seams. Reviewers use them to confirm who operates what, how recovery is planned, and where evidence is available before approval.
Choose the guide family that matches the architecture question on the table. Start with the architecture map for the overall layout, principles for design choices, concepts for the model, components for the layer catalog, flows for end-to-end paths, integrations for external systems, data availability for read-side consistency, operability for production posture, and self-hosting for cluster deployment.
DALP provides the platform layers, contract architecture, supported integration seams, indexed read models, operability posture, and self-hosting reference for this section.
Your organisation sets the target operating model, deployment topology choices, integration vendor selection, recovery targets, network policy, and governance around DALP.
These guides cover the current platform architecture. They do not commit to legal opinions, custody arrangements, SLA terms, non-EVM deployment support, or vendor selections.
Treat those as organisation-specific decisions unless a detail page states the DALP behaviour explicitly.
What DALP covers
DALP architecture separates user surfaces, execution services, asset contracts, indexed reads, and integration seams so a reviewer can find which layer owns each decision. The guides explain the layers, their interfaces, the flows that connect them, and the operating posture a self-hosted deployment inherits.
| Area | DALP defines | Your organisation defines |
|---|---|---|
| Platform layers | Console, Platform API, Transaction Lifecycle Engine, SMART Protocol contracts, Ledger Index | Network policy, exposed routes, tenancy choices, and operator access |
| Flows | Signing, issuance, compliance transfer, feed update, offerings, distributions, XvP settlement | Approval chains, custody policy, settlement counterparties, and operating procedures |
| Integrations | Documented seams for custody, compliance, networks, market data, storage, and observability | Vendor selection, contractual terms, provider configuration, and integration ownership |
| Operability | Telemetry, PostgreSQL persistence, workflow durability, failure-mode behaviour | Recovery targets, HA pattern selection, backup retention, and on-call coverage |
| Exclusions | Documented platform behaviour and supported deployment surfaces | Legal opinions, SLA commitments, custody arrangements, bridge operations, and non-EVM deployment decisions |
Pick the right path
| If you need to... | Start here | Then read |
|---|---|---|
| Read the architecture end to end | Architecture overview | System context, then follow the Overview pages in order down to Data domains |
| Look up a fact for an RFP or review | Architecture one-pager | Capability docs matrix to find the page that answers a named capability |
| Review architecture principles and scope | Architecture overview | Principles and scope and Quality attributes |
| Build the mental model for the platform | Concepts: tokenization modeling | Claims and identity and Asset policy |
| Inspect a specific component layer | Component catalog | The platform, infrastructure, asset contracts, token features, and capabilities pages |
| Walk a flow from request to settlement | Flows overview | Signing flow, Asset issuance, Compliance transfer |
| Decide an integration surface | Integration overview | Custody providers and Compliance providers |
| Reason about read-side consistency | Data availability overview | Ledger Index |
| Plan production operability | Operability overview | Observability, Database, Failure modes, Backup and recovery |
| Deploy on Kubernetes or OpenShift | Self-hosting overview | Prerequisites, Installation process, High availability |
Architecture model
DALP exposes four architecture-facing layers:
- The platform layer is where operators and integrations enter the system through the Console, the Platform API, and the System Factory.
- The infrastructure layer coordinates execution services that preserve workflows, prepare EVM transactions, route signing, submit chain operations, and index events.
- The asset contracts layer enforces token rules on EVM networks through SMART Protocol contracts, identity, claims, and compliance modules.
- The capabilities and token features layers add focused workflows around the asset for distribution, settlement, treasury, market data, governance, and yield.
Most production reviews touch all four. Use the start-here pages for the evaluator overview, then route to the layer or flow the conversation needs. Cross-link to Developer guides for integration work and Compliance and security for control evidence.
Start here
Architecture map
Navigate the architecture documentation by platform layer and reader goal.
Architecture one-pager
Reference: the buyer-safe DALP platform map on one page for RFP, security, and integration lookups.
Capability docs matrix
Reference: find the documentation page that answers a named capability during a review.
Asset tokenization architecture
See how DALP structures institutional asset tokenization end to end.
System context
Identify external actors, operating scopes, trust relationships, and contract layers.
Lifecycle after issuance
Read the operating model for managing an issued DALP asset.
Key flows
Index the main DALP system flows from signing to settlement.
Glossary
Reference definitions for DALP terminology across SMART Protocol, OnchainID, and execution.
Architecture overview
Overview
Read the DALP architecture overview for solution leads and reviewers.
Principles and scope
Inspect the architecture choices DALP makes and the decisions that remain with the client.
Quality attributes
Review security, reliability, operability, data consistency, performance, and evidence posture.
Deployment topology
See runtime zones, network paths, EVM access, custody dependencies, and recovery points.
Data domains
Map which records are on-chain, off-chain, indexed, and who owns each governance decision.
Concepts
Account abstraction model
Review the operator controls for advanced accounts, smart-account routing, and gas sponsorship.
UserOperations
See how UserOperations move through smart wallets, bundlers, and the EntryPoint.
Bundlers
Read how DALP uses bundler-compatible discovery behind the platform execution path.
Paymasters and gas sponsorship
Sponsor eligible account abstraction transactions without changing identity or asset policy.
Claims and identity
Connect participant wallets, OnchainID claims, trusted issuers, and compliance expressions.
Asset policy
Combine identity, compliance modules, lifecycle hooks, and governance into per-asset policy.
Tokenization modeling
Turn an asset class and template into token metadata, features, and compliance rules.
Components
Component catalog
Find the component layer that owns an architecture decision or evidence trail.
Platform layer
Review the Console, Platform API, and System Factory entry surfaces.
Infrastructure layer
Inspect execution services that prepare EVM transactions, route signing, and index events.
Asset contracts
Read the SMART Protocol contract layer that enforces token rules on EVM networks.
Token features
Attach fees, governance, lifecycle, yield, permit, and conversion behaviour to assets.
Capabilities
Add focused add-on workflows for distribution, settlement, treasury, sales, and feeds.
Flows
Flows overview
See how a business request becomes a controlled platform operation.
Signing flow
Walk an EVM transaction from request through compliance simulation, custody signing, and broadcast.
Asset issuance
Follow asset deployment from instrument configuration to first operations.
Compliance transfer
Step through identity, module, and policy checks before a token transfer executes.
Feeds update flow
See how issuer-signed feed updates reach the platform and contracts that use them.
Treasury distribution
See how treasury distributions move from configuration to investor wallets.
XvP settlement
Coordinate multi-party asset exchanges through local or HTLC settlement.
Integrations
Integration overview
Review supported integration surfaces and operator-configurable seams.
Custody providers
Connect DFNS, Fireblocks, Luna HSM, browser wallets, and provider approval policy.
Compliance providers
Onboard identity, business, AML, and wallet-monitoring providers as on-chain claims.
Supported networks
Configure built-in viem chains and custom EVM networks with RPC and finality controls.
Data availability
Data availability overview
Understand how EVM events become queryable platform state and where reads can lag.
Ledger Index
Inspect how checkpoints, finality, reorg handling, and reindexing affect indexed reads.
Operability
Operability overview
Map telemetry, PostgreSQL persistence, durability, HA handoffs, and failure behaviour.
Observability
Run the observability stack with metrics, logs, traces, and Grafana dashboards.
Database
Configure PostgreSQL connection control, TLS, pooling, and health checks.
Failure modes
Review degradation and recovery behaviour when dependencies are unavailable.
Self-hosting
Self-hosting overview
Deploy DALP in your own Kubernetes or OpenShift infrastructure.
Prerequisites
Check the infrastructure, service, network, and credential requirements.
Installation process
Walk through SettleMint-managed installation phases for self-hosted deployments.
OpenShift installation
Deploy DALP on OpenShift with restricted SCCs, Routes, and CSI-backed storage.
High availability
Choose an HA and disaster recovery pattern with documented recovery metrics.