You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
There are a few issues that I have ran to while trying to use the proof predicate.
Returning empty credentials. The function ListCredentialsForProofRequestAsync returns an empty list when request_predicates is included in the proof request JSON. I have worked around this by converting it into requesting_attribute to get the needed credentials id before converting it back to request_predicates later.
Error: "A value being processed is not valid.". When creating the proof presentation. From what I know the value should be in the correct format, both are int which now I'm not sure why it is happening. Did anyone manage to successfully create a proof predicate with hyperledger dotnet?
For reference: this is the JSON used to request predicate
There are a few issues that I have ran to while trying to use the proof predicate.
Returning empty credentials. The function ListCredentialsForProofRequestAsync returns an empty list when request_predicates is included in the proof request JSON. I have worked around this by converting it into requesting_attribute to get the needed credentials id before converting it back to request_predicates later.
Error: "A value being processed is not valid.". When creating the proof presentation. From what I know the value should be in the correct format, both are int which now I'm not sure why it is happening. Did anyone manage to successfully create a proof predicate with hyperledger dotnet?
For reference: this is the JSON used to request predicate
@"{
""name"":""Proof Request"",
""version"":""1.0"",
""nonce"":""1234567890"",
""requested_predicates"":{
""dob"" : {
""name"": ""age"",
""p_type"": ""<="",
""p_value"": 18,
}
},
""non_revoked"":{
""to"": 2147483647
}
}";
Thank you in advanced!
The text was updated successfully, but these errors were encountered: