Open filip26 opened 6 months ago
@filip26 good cases. I think you found an error in my server side checks. I was rejecting the case with nothing selected but forgot that there could be mandatory reveal information.
I've gotten some requests to update the spec test vectors with something a bit more relevant than fictional windsurfing races. Also the longer test cases from @aljones15 helped me find a bug in my primitives so I'm going to try to come up with something more relevant for the spec and something longer and a bit more realistic for adding here. Ideas are welcome.
@filip26 I'm not aware of a normative statement for empty mandatoryPointers and selectiveDisclosure in the spec, but this is a good idea.
Hi, please consider testing corner cases when pointers are empty/null. The tests could show real maturity/stability of an implementation.
Issuer.sign - empty/null mandatory pointers An implementation should return a base proof with no mandatory/always disclosed/ data.
Holder.derive - base proof from 1. + empty/null selective pointers An implementation should fail, as there is nothing to disclose. @Wind4Greg please can you confirm? Thank you!
Holder.derive - base having mandatory pointers + empty/null selective pointers An implementation should return a derived proof disclosing only mandatory data.