Overview
Overview of DALP's integration architecture covering custody provider connectivity, supported blockchain networks, and the platform's approach to external system boundaries.
Purpose
This section documents DALP's integration boundaries with external systems, including custody providers and blockchain networks.
- Doc type: Reference
What you'll find here
- Supported custody providers and their integration contracts
- Supported blockchain networks and EVM compatibility requirements
- DALP's integration posture: how external dependencies are abstracted
- Boundary contracts and stability expectations for each integration
Integration posture
DALP isolates external dependencies behind internal abstraction boundaries. The Key Guardian abstracts custody providers. The Chain Gateway abstracts blockchain networks. The Feeds system abstracts market data sources. This design allows providers and networks to change without affecting platform workflows or API contracts.
Each integration has a defined contract surface:
- Inbound contracts specify what DALP expects from the external system (API versions, authentication, response formats)
- Outbound contracts specify what DALP exposes to external systems (webhook payloads, callback URLs, status formats)
- Stability promises define versioning, deprecation windows, and backward compatibility guarantees
Section pages
| Page | Description |
|---|---|
| Custody providers | Supported MPC custody solutions (DFNS, Fireblocks), integration architecture, and policy evaluation |
| Supported networks | EVM-compatible blockchain networks, RPC configuration, and network-specific considerations |
Key design decisions
- Provider-agnostic signing: The unified signer interface accepts signing requests without coupling to a specific custody provider. Adding a new provider requires implementing the signer adapter, not changing platform flows.
- Network abstraction: Blockchain-specific details (gas pricing, finality, block times) are encapsulated in the Chain Gateway. Platform workflows operate against a normalized transaction interface.
- No direct external calls from business logic: All external system interactions route through dedicated gateway components with retry handling, circuit breaking, and observability.
See also
- Key Guardian for custody abstraction internals
- Signing flow for end-to-end custody interaction
- Chain Gateway for network abstraction
- EVM RPC Node for blockchain connectivity
- Feeds system for market data integration
XvP Settlement Flow
How the DALP XvP settlement flow executes atomic multi-party token exchanges -- from settlement creation through approval collection, optional hashlock coordination for cross-chain legs, to all-or-nothing execution.
Custody Providers
Architecture overview of DALP's custody provider integrations covering DFNS and Fireblocks MPC signing, policy engines, configuration requirements, and the unified signer abstraction that makes providers interchangeable.