Rick Byers

If we were to pursue a wallet-provided nonce, what would that look like in the API shape in practice? We can't share the nonce with the site until the user...

+1 to better understanding the threat models. I've written a threat model for the Chrome API that I can probably produce a public version of, but it can assume little...

Discussed on the call now that this can probably be closed based on conversations at IIW, but will wait for confirmation from @tlodderstedt.

As now stated in our [explainer](https://github.com/WICG/digital-identities/blob/main/explainer.md#what), I think it's important that we find a solution which doesn't block the rapidly evolving identity ecosystem (especially EUDI) on browser updates. Maybe our...

From Chrome's perspective, we consider it part of our contract with users that the browser facilitates transparency and control over the user's sharing of personal information. I can't speak for...

@tlodderstedt thank you, I'm thrilled to hear that! I'm quite excited for the potential of an OID4VC profile using the browser API, and am glad to hear that you and...

@tlodderstedt thank you. Yes that is my expectation on market adoption as well (hence "preparing an alternative which can live alongside the use of custom-schemes" in my suggested goal statement)....

Makes sense. Even if the new API supports web wallets out of the gate, I'm sure we're going to see inconsistent uptake of the new api from wallets of all...

Thank you Kristina and sorry for my delay in responding. @hober has been telling us WebKit feels the same way and filed #16. The specific use cases we had in...

Chatting more with @samuelgoto about this, we see how FedCM is really complicating the debate here. In the interest of helping us all converge to a v1 we're all happy...