Promote from testnet to mainnet
Move a validated DALP environment from a test EVM network to a production EVM network without treating testnet chain state as production state.
What changes when you promote from testnet to mainnet? You move the validated DALP deployment configuration and operating checks to a production EVM network. You do not move testnet transactions, balances, issued assets, identity registry state, or indexed chain history into mainnet.
What is the smallest safe step? Start by comparing the testnet environment against the target production network configuration: chain identity, RPC endpoints, DALP contract addresses, finality settings, custody policy, compliance setup, and monitoring thresholds.
What does production require? Production needs its own configured EVM network, deployed DALP contracts, issuer and operator permissions, compliance configuration, custody signing policy, indexer state, and monitoring for that network.
Before you promote
Use testnet to validate the workflow shape before you submit production transactions. Confirm that your team can create the asset, configure compliance modules, approve the required operations, sign transactions through the configured custody provider, observe transaction status, and reconcile the resulting indexed data.
Promotion is an environment deployment and configuration activity. Treat the production network as a separate chain with its own contract addresses and chain state.
Promotion checklist
| Area | Check before mainnet |
|---|---|
| Network | The target mainnet or production EVM network is enabled with the correct chain ID, RPC endpoints, block explorer, batching limits, and finality settings. |
| Contracts | The production environment points to the DALP contracts deployed for that network. Testnet contract addresses are not reused on mainnet. |
| Permissions | Issuer, operator, compliance, and system roles are granted in the production environment. |
| Custody | The custody provider signs for the production network and applies the production wallet policy. |
| Compliance | Token-level compliance modules and identity requirements are configured for the production token, not copied as completed testnet state. |
| Indexing | The indexer starts from the production network's deployment and tracks production blocks, transactions, and events. |
| Monitoring | Blockchain monitoring uses production-safe finality and stale-block settings for the target network. |
Run the production deployment
- Configure the production EVM network with the target chain, RPC transport, block explorer, contract addresses, and finality settings.
- Deploy or attach the DALP contracts that belong to that production network.
- Configure production roles, custody policy, compliance modules, and market data dependencies.
- Run the same user-facing workflow you validated on testnet, but submit it as a new production transaction on the mainnet network.
- Track the production transaction status and wait for the configured confirmation policy before treating the operation as complete.
- Confirm the production indexer and operational views show the expected production events.
What does not carry over
The testnet validation run proves that the workflow works. It does not create production chain state.
Do not assume these objects automatically move from testnet to mainnet:
- token contracts or issued assets
- token balances or holder history
- identity registry entries and trusted issuer claims
- compliance module state
- transaction hashes, confirmations, or event history
- indexer checkpoints or indexed testnet records
If you need DALP to track an already deployed production token that was created outside the active DALP factories, use the external token registration flow for an address on the active production EVM network.