Kristina

@deshmukhrajvardhan looks like the content is good to go and can be merged but there are so many conflicts, it might be easier to do a new PR to the...

replaced by #464

looks like this is out of scope of opendi4vp. closing it as a reporter

please do a PR for your suggested updated text. I thnk it makes sense.

> In addition to this, I would open a conversation about how a wallet is supposed to provide its public keys to the verifier for the signature validation, when the...

on 1., given that in unsigned requests, `the Wallet will use the Verifier's origin as asserted by the user agent to determine the Verifier's effective Client Identifier.`, I think there...

i think this has been superseded by the recent changes in DC API. closing in a week unless objections

Here is a sequence diagram that is envisioned in QES use-case 

what if browser API is not used in which case returning deeplink feels like a natural option? i think these implementers are looking into using vanilla openid4vp. and for browser...

discussed during the WG call: - we need to clearly define how error codes currently defined in https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#section-6.4 are returned in the openid4vp response over the browser API. Current assumption...