Daniel Bluhm

I think this concept would need to be revisited at some point in the future but from the perspective of DIDComm v2 support for different crypto suites. I think this...

Interesting; the discussion on the linked issue had some unexpected commentary. I think the opposition to using paths is unfounded, to put it bluntly. As mentioned, they're virtually unused at...

@mkempa I'm finding this change a bit confusing. The added method is `get_verification_key_for_did` but the value actually returned is a `DIDInfo` rather than a representation of a verkey. This strikes...

@PatStLouis is going to a take another look at this

@PatStLouis is this superseded by having the keys in the wallet identifiable by kid/verification method id?

I'll take a quick look and see if I can reproduce the issue -- what branch/version of ACA-Py do you have checked out?

With those inputs, the issue is reproducible. I'll dig around some more. It's been a minute since I looked at credential proposals in issue credential v2.

``` curl -X POST http://localhost:11001/issue-credential-2.0/send-proposal \ -H "Content-Type: application/json" -d '{ "comment": "I want this", "connection_id": "fb5793a9-a1ce-43ac-a549-71ff700d4b94", "credential_preview": { "@type": "issue-credential/2.0/credential-preview", "attributes": [ { "mime-type": "plain/text", "name": "name", "value": "Bob"...

The set of flags you specified probably caused the exchange to complete automatically: ``` ... --auto-respond-credential-proposal \ --auto-respond-credential-offer \ --auto-respond-credential-request \ --auto-store-credential ``` You should see the credential on the...

@swcurran that did:key looks like a BLS key. I found recently that in order to fulfill the `is_holder` constraint with BBS+ credentials, the subject ID must be a BLS key...