Paul Bastian

This has been down similarly to ARMs 64 bit architecture already: https://github.com/protocolbuffers/protobuf/issues/3844

I think the title hints that this is for debugging and better understanding of the data. We had the range idea and didn't find an easy way

While Idexmix/Anoncreds offer great privacy features they lack: - final standardization - acknowledgment by regulators - cryptographic agility - potential to move to PQC algorithms - support for hardware-backed keys...

> > While Idexmix/Anoncreds offer great privacy features they lack: > > > > * final standardization > > * acknowledgment by regulators > > * cryptographic agility > >...

I just came through the same thought process. Have a look here: https://github.com/multiformats/unsigned-varint https://lists.w3.org/Archives/Public/public-credentials/2021Mar/0042.html

Yes, I agree as well, it's pretty unintuitive and makes it hard to read the codec as the values in the csv are stored as "real" ints and not varints....

Yes, since writing the did:indy spec the `publicKeyBase58` is already deprecated again :)

As I read it, Authorization Request in OpenID4VP does not mandate `client_metadata` or `client_metadata_uri`, which are actually used to communicate the data. Therefore the rules are meant to be: You...

Why should I do an HTTP call if the absence of kid can tell me that I shouldn't?

HAIP does not define the trust mechanism in general, and so the wallet attestation trust is not an exception to this. As you have written, JWT VC Issuer Metadata is...