Open Wind4Greg opened 2 weeks ago
Recommendation: Add INVALID_PROOF_CONFIGURATION, INVALID_PROOF_DATETIME, PROOF_TRANSFORMATION_ERROR, and MALFORMED_PROOF_ERROR to the VC-DI spec as the first three are are used in multiple cryptosuite specs and I propose that we use the MALFORMED_PROOF_ERROR for many ECDSA-SD errors and BBS errors. See below for details.
The rest of these errors could be grouped under the general category of a MALFORMED_PROOF_ERROR:
u
, indicating that it is a multibase-base64url-no-pad-encoded value, throwing an error ";u
, indicating that it is a multibase-base64url-no-pad-encoded value, throwing an error if it does not."0xd9
, 0x5d
, and 0x01
, throwing an error if it does not."
To unify error handling language across this specification (and if desired other cryptosuite specifications) I'd recommend:
Below I show codes used but not in the DI specification and error conditions without codes. Thoughts/Opinions?
Error Codes Used but Not in DI Spec
Errors without Codes
These seemed to me to need codes and rigorous handling. Line numbers are approximate. Need to assign to existing error codes or come up with new codes.
u
, indicating that it is a multibase-base64url-no-pad-encoded value, throwing an error ";u
, indicating that it is a multibase-base64url-no-pad-encoded value, throwing an error if it does not."0xd9
,0x5d
, and0x01
, throwing an error if it does not."