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
As discussed in w3c-ccg/vc-api#111, it seems that verifying a presentation in vc-http-api is supposed to include verifying embedded verifiable credentials rather than expecting the client to verify them separately. DIDKit should probably be updated to follow this behavior in its API.
The text was updated successfully, but these errors were encountered:
I believe the consensus is that verifying VCs as well is default behavior turned off with a flag-- I have already heard examples of both being floated among users of the API!
As discussed in w3c-ccg/vc-api#111, it seems that verifying a presentation in
vc-http-api
is supposed to include verifying embedded verifiable credentials rather than expecting the client to verify them separately. DIDKit should probably be updated to follow this behavior in its API.The text was updated successfully, but these errors were encountered: