Closed PJUllrich closed 5 years ago
Not feasible since the wrapper functions need the Maps as input parameters.
I'd say we want this, but we actually need to refactor the wrapper to support both datatypes, currently the proving supports only Strings for a reason I forgot. So I'll reopen this and mark this as "wrapper"
The function
createCredential
inIssuer
has aMap<String, Object>
as second parameter. The functionfulfillProofRequest
inProver
has aMap<String, String>
as parameter.In the
Main
function, this causes me some issue with handing in the attributes intofulfillProofRequest
that I've used previously to create the Claim. Do you think that these two should maybe be made equal to e.g.Map<String, Object>
?