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
The DALP component catalog is the project home for architecture readers. It routes each question to the layer that owns the relevant platform entry point, execution path, token rule, extension, capability workflow, or external handoff.
Use this page when you know the workflow or review question, but not which architecture page to read first. Choose the component layer that controls the decision or evidence you need. Then follow the linked detail page for the focused explanation.
The catalog is organized by review path:
- Platform surfaces show where operators and integrations enter DALP.
- Infrastructure services show how workflows execute, sign, connect to EVM networks, index chain activity, and resolve feed inputs.
- Asset contracts show the token model and on-chain controls.
- Token features show extensions attached to each asset.
- Capabilities show addon workflows around distribution, settlement, treasury control, sales, and signed market data.
How to read the component model
Read the model as a routing map, not a reference page or deployment runbook. Each layer points to the detail page that explains its responsibilities, boundaries, and linked component pages.
For example:
- To review 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, use 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 capability workflows listed here.
Operators, issuers, custody providers, RPC providers, feed sources, payment providers, and market venues own the off-platform policies, provider configurations, operating procedures, and legal obligations named in the external-scope column.
A regulated workflow usually crosses several layers. 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.
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, roles, and 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, account abstraction, and issuer-signed feeds. |
| How does smart-account execution change the transaction path? | Account abstraction model | Explains UserOperations, EntryPoint routing, bundlers, paymasters, and why identity and compliance controls stay separate. |
| 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, maturity redemption, 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
User-facing interfaces that operators and integrators interact with directly.
| 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
Backend services that power workflow execution, signing, chain connectivity, indexing, and external value inputs.
| 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. |
| Account abstraction | ERC-4337 smart-account execution paths when account abstraction is configured. |
Asset contracts
The foundational contract primitive, DALPAsset, and 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 that add fees, governance, lifecycle, approvals, history, conversion, and yield to DALPAsset tokens.
| Component | Responsibility |
|---|---|
| Token Features | Runtime-pluggable features for DALPAsset: fees, voting power, historical balances, permit approvals, maturity redemption, conversion, and yield. |
Capabilities
Optional system addons that extend asset workflows without changing the base asset contract.
| 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 follow asset issuance, settlement, identity, and operational sequences across components.
- Integration architecture to review provider responsibilities and external system handoffs.
- Security architecture to review trust boundaries and control mapping.
- Deployment topology to review runtime zones and network responsibilities.
Tokenization modeling
A concepts guide to how DALP turns an asset class and instrument template into token metadata, token features, compliance rules, and an issued asset.
Overview
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.