Component catalog
Use the DALP component catalog to find the platform surface, infrastructure service, asset contract layer, token feature, or capability that owns an architecture decision, integration handoff, control, or evidence trail.
Overview
Each layer owns a distinct set of responsibilities. Platform surfaces control entry and access policy. Infrastructure services run workflows and sign transactions. Asset contracts, token features, and capabilities govern what the asset can do. Use this catalog when you know the workflow or area of interest but not which architecture page to read first.
Pick the section that controls the decision or evidence you need, then follow the linked detail page for its focused explanation. You can also start from the component inventory below if you already know the component name.
The catalog is organized by layer:
- Platform surfaces show where operators and integrators enter DALP.
- Infrastructure services show how workflows run, sign transactions, connect to EVM networks, index chain activity, and resolve feed inputs.
- Asset contracts show the on-chain rules the asset enforces.
- Token features show extensions that attach to individual tokens.
- Capabilities show addon workflows for distribution, settlement, treasury control, token sales, and signed market data.
How to read the component model
Read the model as a routing map, not a deployment runbook. Each entry points to the detail page that covers its responsibilities and boundaries, with links to related component pages.
For example:
- To see who can start an asset lifecycle workflow, use the platform layer.
- To trace how a submitted workflow becomes signed EVM transactions and indexed state, use the infrastructure layer.
- To check what rules the token enforces on-chain, start with asset contracts and token features.
- To understand an addon such as XvP settlement or issuer-signed scalar feeds, use capabilities.
The model is layered for review. DALP owns the platform surfaces, infrastructure services, contract model, token-feature attach points, and the capability workflows listed here.
Operators, issuers, custody providers, RPC nodes, feed sources, payment networks, and market venues own the off-platform policies, configurations, operating procedures, and legal obligations named in the external-scope column.
A regulated workflow usually crosses several areas. Issuing or transferring an asset may start in the Console or Platform API, pass through authorization and durable execution, request custody signing, call SMART Protocol contracts, apply token features, and emit events for audit and read models. When you need to diagnose or extend a workflow, this catalog tells you which component to open first.
Choose the right detail page
| Review question | Start with | Why |
|---|---|---|
| How do operators or external systems enter DALP? | Platform layer | Explains the Console, Platform API, and System Factory as the request entry surfaces. |
| Which backend services execute and observe a workflow? | Infrastructure layer | Covers durable execution, signing, contract calls, indexing, EVM connectivity, and feed inputs. |
| Which on-chain token model enforces asset rules? | Asset contracts | Covers DALPAsset, ERC-3643 integration, instrument configuration, and role-based administration. Also covers legacy specialised types. |
| How do wallets, OnchainID contracts, claim topics, and trusted issuers fit together? | Claims and identity | Explains the identity model used by asset contracts, compliance modules, advanced accounts, and issuer-signed feeds. |
| How does smart-account execution change the transaction path? | Advanced accounts concept | Explains UserOperations, EntryPoint routing, and bundler/paymaster flow. Covers why identity and compliance controls stay separate from execution. |
| Which per-asset extension adds fees, yield, maturity, voting, or history? | Token features | Maps runtime-pluggable extensions that attach to DALPAsset tokens. |
| Which addon owns a workflow outside the base token contract? | Capabilities | Maps airdrop, vault, XvP settlement, token sale, and issuer-signed scalar feed workflows. |
Component layers
| Layer | What DALP covers | Owner and external scope | Detail page |
|---|---|---|---|
| Platform | User and integration entry through the Console, Platform API, and System Factory. | DALP owns the entry surfaces and shared backend controls. Operators own user access policy, external callers, and operating decisions. | Platform layer |
| Infrastructure | Workflow execution, transaction preparation, signing routes, contract runtime, chain indexing, RPC access, and feed resolution. | DALP owns the orchestration and integration points. Operators and providers own custody policy, RPC selection, feed-source contracts, response procedures, and deployment sizing. | Infrastructure layer |
| Asset contracts | EVM asset tokens, compliance hooks, identity links, factory deployment, token roles, and on-chain events. | DALP owns the contract model and documented role behavior. Issuers own legal instrument terms, custody policy, and investor onboarding outside DALP. | Asset contracts |
| Token features | Asset-level extensions for fees, voting power, historical balances, permit approvals, and maturity redemption. Includes conversion and yield. | DALP owns the feature contracts and attach points. Issuers own economic terms, tax treatment, accounting treatment, and external valuation evidence. | Token features |
| Capabilities | Optional addons for distribution, treasury control, settlement, token sales, and signed market data. | DALP owns the documented addon workflows. Operators and providers own venue operations, payment rails, legal settlement process, and provider procedures. | Capabilities |
Component inventory
Platform
Operators and integrators enter DALP through the Console, the Platform API, and the System Factory. Each entry point enforces access policy and scoping. Use this section when you need to understand who can initiate a request and how DALP scopes it.
| Component | Responsibility |
|---|---|
| Console | Web interface for asset lifecycle management, compliance workflows, portfolio views, and distribution management. |
| Platform API | OpenAPI-documented programmatic access to platform operations. |
| System Factory | Organisation system creation and token factory scoping for asset isolation. |
Infrastructure
These backend services power execution and signing. They also handle chain connectivity, indexing, and external value inputs. Each service has a defined boundary: DALP owns the integration point; operators and providers own custody policy, RPC selection, and feed-source contracts.
| Component | Responsibility |
|---|---|
| Workflow Engine | Reliable workflow orchestration with persistent state and exactly-once semantics. |
| Key Management | Secure cryptographic key storage with HSM and cloud KMS integration. |
| Transaction Signer | Transaction preparation, gas estimation, nonce management, and signing. |
| Contract Runtime | Smart contract interaction, ABI encoding, and call routing. |
| Ledger Index | Blockchain event processing, data translation, and queryable state projection. |
| Broadcast | Multi-network connectivity with failover and load balancing. |
| EVM RPC Node | Blockchain network access for transaction submission and state queries. |
| Feeds System | Trusted market data feeds for pricing, NAV calculations, and reference data. |
| Advanced accounts | ERC-4337 smart-account execution paths when advanced accounts is configured. |
Asset contracts
DALPAsset is the foundational contract primitive. This section also covers specialised legacy types for existing deployments.
| Component | Responsibility |
|---|---|
| Asset Contracts | DALPAsset, ERC-3643 integration, legacy-equivalent presets, specialised token types, deployment architecture, and role-based administration. |
Token features
Runtime-pluggable extensions attach to DALPAsset tokens. They add fees, governance, and lifecycle controls. Each extension also exposes approvals, balance history, conversion paths, and yield. Issuers own the economic terms. DALP owns the feature contracts and attach points.
| Component | Responsibility |
|---|---|
| Token Features | Runtime-pluggable features for DALPAsset: fees, voting power, historical balances, permit approvals, and maturity redemption. Covers conversion and yield. |
Capabilities
Optional system addons extend asset processing without changing the base asset contract. Operators and providers own venue operations, payment rails, and the legal procedures that govern settlement. DALP owns the documented addon workflows.
| Component | Responsibility |
|---|---|
| XvP Settlement | Atomic cross-party settlement with delivery-versus-payment mechanics. |
| Issuer-Signed Scalar Feed | Issuer-signed scalar values for market data and reference-value workflows. |
Read next
- Architecture overview for the principles and quality attributes behind the component model.
- Key flows to trace how asset issuance, settlement, and identity work across components.
- Integration architecture for provider responsibilities and external system handoffs.
- Security architecture for trust boundaries and control mapping.
- Deployment topology for runtime zones and network responsibilities.
Tokenization modeling
How DALP composes a deployable digital asset from an instrument template, metadata, token features, and compliance rules without requiring a new contract for every business case.
Platform layer - Console, API, and system creation surfaces
The platform layer is where operators, integrators, and administrators enter DALP. It explains how the Console, Platform API, and System Factory route requests through shared authentication, authorization, wallet verification, and audit controls.