Supported Networks
Reference for blockchain networks supported by the DALP platform, covering EVM-compatible Layer 1 mainnets, Layer 2 rollups, testnets, and private consortium networks with their configuration differences.
Purpose
Reference for blockchain networks that DALP supports, their configuration requirements, and compatibility constraints.
- Doc type: Reference
- What you'll find here:
- EVM compatibility requirements
- Supported network categories (L1, L2, testnet, private)
- Network-specific configuration differences
- Private network deployment considerations
- Related:
- EVM RPC Node — blockchain access point
- Chain Gateway — multi-node connectivity
- Deployment Topology — environment architecture
Compatibility requirement
DALP operates on any blockchain that implements the Ethereum JSON-RPC specification. No application changes are required when switching networks. Configuration handles consensus differences, gas models, and confirmation requirements.
Network categories
Layer 1 mainnets
| Network | Gas model | Block time | Notes |
|---|---|---|---|
| Ethereum | EIP-1559 (base + priority fee) | ~12 seconds | Primary target, full feature support |
| Polygon PoS | EIP-1559 variant | ~2 seconds | Lower gas costs, faster finality |
| Avalanche C-Chain | EIP-1559 | ~2 seconds | Sub-second finality with 3-block confirmation |
| BNB Smart Chain | Legacy gas pricing | ~3 seconds | Higher throughput, centralized validator set |
Layer 2 rollups
| Network | Type | Settlement | Notes |
|---|---|---|---|
| Arbitrum One | Optimistic rollup | Ethereum L1 | 7-day challenge period for withdrawals |
| Optimism | Optimistic rollup | Ethereum L1 | Bedrock architecture |
| Base | Optimistic rollup | Ethereum L1 | Coinbase-incubated, OP Stack |
| zkSync Era | ZK rollup | Ethereum L1 | Validity proofs, different gas accounting |
| Polygon zkEVM | ZK rollup | Ethereum L1 | EVM-equivalent ZK proofs |
Testnets
| Network | Corresponds to | Faucet availability |
|---|---|---|
| Sepolia | Ethereum mainnet | Public faucets |
| Amoy | Polygon PoS | Public faucets |
| Fuji | Avalanche C-Chain | Public faucets |
Private / consortium networks
DALP supports private EVM deployments:
- Hyperledger Besu — Enterprise Ethereum with IBFT 2.0 or QBFT consensus
- Go-Ethereum (Geth) — private PoA (Clique) or PoS configurations
- SettleMint networks — Managed private networks with genesis-allocated DALP contracts (predeployed infrastructure, deployment starts at Phase 2)
Network-specific configuration
| Parameter | What varies | Impact |
|---|---|---|
| Block confirmation count | 1 (private) to 12+ (Ethereum mainnet) | Finality confidence before indexing |
| Gas price strategy | Legacy, EIP-1559, or custom | Transaction cost estimation |
| RPC batch limits | Varies by provider | Indexer chunk size and concurrency |
| Chain ID | Unique per network | Multi-chain identity registry |
Configuration is environment-variable driven. No code changes required for network switching.
Multi-chain considerations
DALP supports simultaneous operation across multiple chains. Key architectural implications:
- Identity isolation: Each chain has its own identity registry. An investor's OnchainID is chain-specific.
- Compliance isolation: Compliance module configurations are per-chain, per-token.
- Indexer per chain: One
ChainIndexerRestate Virtual Object per chain ID. - Custody per chain: Fireblocks and DFNS support multi-chain asset wallets through the same vault/wallet.
See also
- EVM RPC Node for blockchain connectivity
- Chain Gateway for multi-node failover
- Deployment Topology for environment architecture
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.
Overview
Overview of DALP's security architecture covering authentication, authorization, identity and compliance, on-chain compliance modules, and wallet verification as layered defenses for digital asset operations.