<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/06/2022 11:06, Torsten
Lodderstedt wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2AD285E5-881B-4F25-97EC-C6FD4AED8CB1@lodderstedt.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Am 10.06.2022 um 11:56 schrieb David Chadwick
<<a href="mailto:d.w.chadwick@verifiablecredentials.info"
class="moz-txt-link-freetext" moz-do-not-send="true">d.w.chadwick@verifiablecredentials.info</a>>:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div class="">
<p class=""><br class="">
</p>
<div class="moz-cite-prefix">On 10/06/2022 10:43, Torsten
Lodderstedt wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:2FF99EC7-11D7-44B9-8022-A454AC7C395D@lodderstedt.net"
class=""> read it and I think the public key id in the
cert is a correlation handle. <br class="">
</blockquote>
<p class="">Not if the key is transient and is different
everytime (which is what I said)</p>
<div class=""><br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
That would mean the wallet would need to obtain an authorisation
credential from a central authority for every transaction. You
think that will scale?<br class="">
</div>
</blockquote>
<p>OIDC seems to scale pretty well. So does OCSP.</p>
<p>However, sharing the same key pair between thousands of
smartphone wallets would also protect the user's privacy.</p>
<p>Kind regards</p>
<p>David<br>
</p>
<blockquote type="cite"
cite="mid:2AD285E5-881B-4F25-97EC-C6FD4AED8CB1@lodderstedt.net">
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class="">Kind regards</p>
<p class="">David<br class="">
</p>
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote>
</body>
</html>