José Pumahuanca (QC)

Hi, I'm facing a similar problem. Any news on this issue's progress?

@TimoGlastra Given that there is no `anonCredsUnqualifiedRevocationRegistryId` tag in the CredentialRecord as @barnabef pointed out, as a workaround I added this tag (`anonCredsUnqualifiedRevocationRegistryId`) to the `processCredential ` method in AnonCredsCredentialFormatService.ts...

@TimoGlastra 1.- I found out that when ACA-Py (version 1.2 , wallet-type=**askar-anoncreds**, and using unqualified DID) issues a credential to Credo (0.5.13) and Credo accept the credential (there are 2...

Hi, Maybe my case could provide more clues... I'm just trying to establish a connection using DIDexchange 1.1 between ACA-Py (_responder_) and Credo (_requester_). So, my flow: 1.- ACA-Py create...

If you refer to the `"kid": "did:key:z6MkoFQVs9kP3n6MXk1en5aNw4vazHECLEZjvNvAydNZ11i4"` in the **_response_** and the key from the **_invitation_**, after resolving the did:peer:4, `"publicKeyMultibase": "z6MkoFQVs9kP3n6MXk1en5aNw4vazHECLEZjvNvAydNZ11i4"`, the answer is Yes.

@PatStLouis I think I didn't explain myself well. I was not talking about resolving a did:indy but the generation of the IDENTIFIER using the spec [Indy Did Method](https://hyperledger.github.io/indy-did-method/) . AFAIK...