This page lists the 5 errors in the contract error reference whose code is a name, not a number. Match the error's id, or its dalpCode on a contract error or a failed deployment step, for example DALP-WORKFLOW-FAILED, to the DALP Code column, then read Retryable and Suggested Fix. The contract error reference explains each column, including Severity, and the DALP error index lists the page for every code range.
DALP Code | Message | Why | Suggested Fix | Severity | Retryable | Solidity Error |
|---|---|---|---|---|---|---|
DALP-CHAIN-EMPTY-REVERT | The blockchain rejected this transaction with no reason code. | The transaction reverted without revert data, so DALP cannot name the check that failed. This happens when a contract calls an address with no contract code, or when an inner call runs out of gas. | Check that the system is fully deployed on this network and that the request targets the right contract. Share the requestId from the error with your administrator. | error | No | EmptyRevert() |
DALP-EXT-TOKEN-NO-CODE | No contract exists at {{tokenAddress}} on this network. | The external token registry checks that the address provided for registration contains deployed bytecode. The address {{tokenAddress}} has no bytecode on this network, so the registry blocks registration before any interface detection can proceed. | Verify the address is correct, that you are connected to the right network, and that the token contract exists at that address before retrying. | error | No | Token |
DALP-TOKEN-DUPLICATE | Your organization already has an asset named {{name}} with symbol {{symbol}} and {{decimals}} decimals. | The token factory derives each asset's on-chain address from its name, symbol, and decimals, then rejects any deployment whose address already exists. This organization already deployed an asset with that exact combination, so the factory cannot create a second one at the same address. | Change the name, symbol, or number of decimals to a combination your organization does not already use, then create the asset again. | error | No | DALPAssetAlreadyExists() |
DALP-WORKFLOW-FAILED | The deployment workflow failed before it could finish. | The deployment workflow stopped before it finished. Either a contract reverted with data the platform could not decode, or the failure matched no known type. | Retry the deployment. If the problem persists, share the correlation id with your administrator. | error | Yes | WorkflowFailed() |
DALP-WORKFLOW-RPC-UNAVAILABLE | The blockchain RPC endpoint is temporarily unreachable and the deployment did not complete. | The deployment workflow could not complete a call to the blockchain node or a platform service. The cause is an HTTP error, a timeout, a socket error or a nonce conflict. | Check that the network's RPC endpoint is reachable and its node is healthy, then retry the deployment. If it keeps failing, share data.correlationId and the requestId from the error with your administrator. | error | Yes | RpcUnavailable() |
The previous page is DALP-9500 to DALP-9999.
Was this page helpful?
