This page lists the 9 errors in the contract error reference with a code from DALP-9300 to DALP-9399. Match the error's id, or its dalpCode on a contract error or a failed deployment step, for example DALP-9339, 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-9339 | This document is already anchored under the same issuer and nonce. | An entry is identified by its issuer and the nonce reserved for it, and the registry only ever appends. A repeat of the same pair with the same subject, digest, document type and label means an earlier attempt's write reached the chain even if its response did not. | Read the existing entry back and record it as the anchor. Do not reserve a new nonce; that would write a second entry for one document. | error | No | AlreadyAnchored(bytes32) |
DALP-9340 | The sending wallet holds no claim key on the issuer identity it named. | The registry accepts an entry only from a wallet the issuer identity lists with claim purpose, so an issuer cannot be attested for by a key it never authorized. | Add a claim key for this wallet on the issuer identity, or send from a wallet that already holds one, then retry. | error | No | Sender |
DALP-9341 | The issuer identity is not a trusted issuer for document hashes in this system. | The registry checks the trusted-issuer registry pinned to it when it was created, so a registration made in another system's registry does not authorize an entry here. | Register the issuer identity for the documentHash topic in this system's own trusted-issuer registry, then retry. | error | No | Issuer |
DALP-9342 | This registry holds no entry with that identifier. | An entry identifier is derived from the issuer and the nonce reserved for it, so an identifier the registry does not hold was never anchored here. | Check the identifier and the registry address. Look the document up by its digest if you do not have the entry identifier. | error | No | EntryNotFound(bytes32) |
DALP-9343 | The issuer or the subject identity is the zero address. | An entry records which identity attested to the document and which identity it belongs to, and neither can be the zero address. | Send the issuer identity contract and the subject identity contract, then retry. | error | No | InvalidIdentity() |
DALP-9344 | The document digest is empty. | The digest is the evidence the entry exists to hold, so an all-zero value is rejected rather than recorded on a permanent record. | Send the document's 32-byte manifest digest, then retry. | error | No | InvalidDigest() |
DALP-9345 | The anchor registry was created without a trusted-issuer registry. | The registry pins the trusted-issuer registry it checks when it is created, so it cannot be created without one. | Deploy the anchor registry through the system bootstrap or migration, which supplies the system's own trusted-issuer registry. | error | No | Invalid |
DALP-9346 | The anchor registry for this system has been retired. | A system manager archived the registry's registration. The registry only ever appends, so it stops accepting entries the moment it is retired rather than adding a record nobody can withdraw. | Ask a system manager to re-register the anchor registry on this system, then retry. | error | No | RegistryArchived() |
DALP-9347 | The wallet signing this anchor is no longer an active registration. | The wallet was marked lost during an identity recovery, or it has no registration in the system's identity registry. The registry only ever appends, so it refuses a wallet the identity registry no longer recognises rather than leaving a record nobody can withdraw. | Sign the anchor with the wallet the recovery replaced this one with, or ask an identity manager to register it. | error | No | Sender |
The previous page is DALP-9200 to DALP-9299. The next page is DALP-9500 to DALP-9999.