Torsten Lodderstedt

> cnf claim in the payload of the Wallet Instance Attestation binds the holder public key in the JWS That seems to me a pretty constrained concept. What is the...

It is not the wallet instance issuing the id token, it is the holder. The attestation answers the question whether the wallet can be trusted to securely manage the keys...

@danielfett Shall we drop the combined approach?

the spec now has text for client / wallet attestation and - SD-JWT VCs: web-based key resolution and x.509 - wallet attestation: web-based key resolution - verifier attestation: web-based key...

@danielfett @paulbastian What do you think?

According to the feedback we got so far on the concept, I think SNA is the way to go. I see value in the proposal @tplooker made to always use...

@peppelinux This issue is about the question what the identifier of an issuer is in a VC. Since we are leaning towards using a HTTPS URL, that would work for...

@peppelinux I have to admit I don't fully understand your arguments. This issue is about the value of the `iss` value in the credential. A HTTPS URL works fine with...

I don't see a reason for having a relationship between sub and the pop key. I think the sub could just be set to the wallet provider name/ id.

yep