Errors
The algorithms described in this specification can raise the specific errors listed below. Additional error types defined in the Errors section of DID Resolution v1 DID-RESOLUTION may also be raised.
These errors are assumed to be fatal and all did:btcr2 operations must abort when one of these errors are raised.
Each error below declares the DID Resolution error type that it refines, as the Errors section of DID Resolution v1 DID-RESOLUTION allows. A binding can use the declaration to decide how to convey the error. In the HTTP(S) binding, a resolver SHOULD send the HTTP status code of the error type that the error refines.
A resolver that cannot reach a service it uses, such as a Bitcoin RPC service or a CAS service, SHOULD raise INTERNAL_ERROR. It MUST NOT raise NOT_FOUND or MISSING_UPDATE_DATA for data that it could not look for because the service was unreachable.
INVALID_DID_UPDATE
An error was found in a BTCR2 Update, or when creating or applying one.
Refines INVALID_DID_DOCUMENT.
INVALID_SIGNAL_DATA
The data for a Beacon Signal does not agree with its Signal Bytes. Example: an SMT Proof that does not verify against the SMT root in the Beacon Signal.
Refines INVALID_OPTIONS.
LATE_PUBLISHING
An error was found when processing the full history of BTCR2 Updates announced by all relevant Beacon Signals. See Late Publishing.
Refines INVALID_DID_DOCUMENT.
MISSING_UPDATE_DATA
Data that is necessary to find what a Beacon Signal announces for the DID is not in the Sidecar Data and not in CAS. This data includes BTCR2 Updates, CAS Announcements, and SMT Proofs.
Refines INVALID_OPTIONS.