Infrastructure overview
The infrastructure layer coordinates the execution services that preserve DALP workflows, prepare EVM transactions, route signing, submit chain operations, index events, route RPC traffic, and provide trusted feed data behind the platform interfaces.
DALP infrastructure services turn accepted platform requests into EVM operations. The layer handles signing, transaction submission, and event indexing, then exposes the result to the Console and Platform API. Infrastructure owns the technical execution path after DALP has selected the asset, compliance route, signer route, and chain context for the participant.
Use this page to determine which service owns each part of the execution path and where that responsibility stops. For task steps, use the linked component and flow pages. Start with the service that owns the step you are investigating.
Scope
Read this section to build the mental model for DALP infrastructure before you inspect the component references. The page covers four review paths.
- Workflow continuity from accepted platform request to terminal outcome.
- Signer and custody routing without turning DALP into the custody provider.
- EVM connectivity, transaction submission, event indexing, and read-model freshness.
- External feed values as configured workflow inputs.
It does not document business approval rules, legal commitments, custody-provider controls, RPC-provider service levels, or non-EVM networks.
Execution path at a glance
The request path has two review boundaries. Platform services check whether an operation is valid given the asset, the participant, the policy rules, and the chain context. Infrastructure services carry out the EVM execution work and report the result back to platform read models.
Each step can involve different deployment providers. The infrastructure layer keeps the DALP responsibility boundary clear. Operators choose their own custody, RPC, feed-source, and observability providers.
How the services fit together
The infrastructure layer is the execution backbone between DALP's business-facing platform and the EVM networks it operates on. A user request becomes a managed workflow. The platform validates the business context. Infrastructure services then preserve progress, prepare the chain operation, and request signatures through the configured custody path. They submit the transaction and update application read models after chain events are indexed.
The separation gives each group a focused review scope. If you work on product or compliance, focus on the Console, Platform API, identity model, asset rules, and workflows. If you work on technology or operations, review signing, EVM connectivity, retry behavior, read-model freshness, and deployment-specific providers.
Decision path for reviewers
Start with the operation you need to explain, then open the detail page for the service that owns it.
| Review question | Read next | What the page defines |
|---|---|---|
| How does DALP keep a multi-step operation alive? | Workflow Engine | Workflow orchestration, retry handling, failure recovery, and how lifecycle operations continue across infrastructure steps. |
| How are transactions prepared and sent? | Contract Runtime, then Transaction Signer | ABI encoding, contract calls, state queries, gas handling, nonce coordination, and how transactions are signed and broadcast. |
| Where are signing keys controlled? | Key Management, plus Advanced accounts when smart accounts are in scope | Local, custody-provider, HSM-backed, and ERC-4337 signing paths. Covers which component controls key material and smart-account execution. |
| How does DALP reach EVM networks? | Broadcast and EVM RPC Node | RPC routing, upstream configuration, failover, direct JSON-RPC access, transaction submission, state queries, and supported EVM connectivity patterns. |
| How do chain events become application state? | Ledger Index | Event ingestion, event-to-domain translation, historical blockchain state, and queryable read models for applications and integrations. |
| How are external prices and values supplied? | Feeds system | Price and foreign-exchange feed types, subject scopes, feed resolution, and where feed values enter DALP workflows. |
The detail pages are the public reference set for the overview above. Component names remain visible because those names are the stable documentation entry points. The surrounding tables describe public responsibilities instead of exposing deployment-specific internals.
Review sequence
Read the page in this order when you need a fast architecture review:
- Use the execution path diagram to place the operation.
- Use the decision table to choose the component reference.
- Use the ownership table to separate DALP behavior from operator and provider responsibilities.
- Use the related pages for detailed flows or component contracts.
Operating model
Operators configure and monitor infrastructure services. End users and integrations do not call infrastructure components directly. They use the Console, Platform API, CLI, SDK, or documented integration endpoints.
That split keeps the user-facing workflow stable. As an operator, you can change custody backends, RPC providers, deployment topology, feed sources, and observability wiring without disrupting the interfaces users see.
Ownership and limits
| Area | DALP infrastructure covers | Operator or provider owns | Not covered |
|---|---|---|---|
| Workflow execution | Coordinating infrastructure steps, retrying supported operations, and preserving progress. | Deployment sizing, operational runbooks, monitoring response, and incident escalation. | Business approval rules, legal sign-off, or asset-policy decisions. |
| Signing and custody | Preparing signing requests and routing them through the configured signer path. | Custody-provider configuration, HSM operation, key ceremonies, access policies, and contractual custody commitments. | A blanket custody guarantee or replacement for the selected custody provider's controls. |
| EVM connectivity | Routing contract calls and transaction submission through configured EVM access, including reads, retries, and failover. | RPC provider selection, private-network access, endpoint credentials, throughput planning, and network availability commitments. | Non-EVM networks, bridge guarantees, settlement finality promises, or RPC-provider SLAs. |
| Indexed state and feed data | Turning supported chain events into read models and resolving configured feed values. | Feed-source contracts, data-vendor controls, source freshness monitoring, and deployment-specific reconciliation procedures. | Legal valuation, market-data licensing commitments, or external source accuracy promises. |
Component responsibilities
| Responsibility | Infrastructure services involved | What client reviewers should understand |
|---|---|---|
| Workflow continuity | Workflow Engine, Transaction Signer | Multi-step lifecycle requests continue across infrastructure steps without exposing raw execution details to users. |
| Signing and custody | Key Management, Transaction Signer, Advanced accounts | Signing routes can use local signing, custody providers, HSM-backed signing, or ERC-4337 execution paths. |
| EVM network access | Contract Runtime, Broadcast, EVM RPC Node | Contract calls, transaction submission, and RPC routing (including failover and chain reads) are handled below the platform interfaces. |
| Queryable state and external values | Ledger Index, Feeds system | Chain events become application read models, while feed data remains an operator-controlled input for workflows that need trusted external values. |
What stays outside this layer
Infrastructure services do not replace the platform's identity, compliance, asset, or policy model. The services execute the operation after the platform has selected the asset, participant, compliance path, signer route, and chain context.
Infrastructure services also do not make legal, custody, RPC-provider, or availability promises by themselves. Those commitments depend on the selected deployment architecture, custody backend, network providers, monitoring setup, and contractual operating model.
Related architecture pages
- Component catalog for the full platform inventory.
- Platform layer for the interfaces that call into infrastructure services.
- Key flows for cross-service operation sequences.
System Factory
How DALP creates a system for an organisation, keeps assets scoped to that system, and uses the token factory registry to isolate multi-tenant reads.
Workflow Engine
How the Workflow Engine turns accepted asset lifecycle requests into durable, observable work that survives signer delays, approval queues, and EVM confirmation latency.