feat: w3c anoncreds support

[auer-martin]

Summary of Changes

Add support for receiving w3c-anoncreds credentials via the new DataIntegrity attachment format
Add support for rendering dif pex presentation requests using the existing rendering logic
Add support for presenting credentials via PresentationExchange

Related Issues

Please reference here any issue #'s that are relevant to this PR, or simply enter "N/A" if this PR does not relate to any existing issues.

Pull Request Checklist

Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

• All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
• Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
• Updated documentation as needed for changed code and new or modified features;
• Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

Pro Tip 🤓

• Read our contribution guide at least once; it will save you a few review cycles!
• Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

[TimoGlastra]

Great stuff @auer-martin

[TimoGlastra]

Could you add a video demo where an AnonCreds credential is received using Data Integrity and shared using Presentation Exhcange?

[TimoGlastra]

cc @cvarjao @jleach @swcurran

[auer-martin]

Could you add a video demo where an AnonCreds credential is received using Data Integrity and shared using Presentation Exhcange?

https://www.loom.com/share/96e7dc8f407a40b7902b0f9472ead94f

[jleach]

@auer-martin Able to fix the two conflict and well get this merged in?

[auer-martin]

@auer-martin Able to fix the two conflict and well get this merged in?

@jleach done

[wadeking98]

Great work, I have some questions about the index file but other than that it looks great

[wadeking98]

it seems like the change is not backwards compatible to indy credentials. I'm getting the following error whenever I try and get an indy credential:

"name": "CredoError",
"message": "AuJrigKQGRLJajKAebTgWu:4:AuJrigKQGRLJajKAebTgWu:3:CL:209526:default:CL_ACCUM:9fc50d37-b15d-47f2-8ada-75c2249abc44 is not a valid did:indy did",

here is the demo you can use to get some example indy credentials: https://digital.gov.bc.ca/digital-trust/showcase/
Once that issue is resolved I'm happy to merge

[auer-martin]

it seems like the change is not backwards compatible to indy credentials. I'm getting the following error whenever I try and get an indy credential:

"name": "CredoError",
"message": "AuJrigKQGRLJajKAebTgWu:4:AuJrigKQGRLJajKAebTgWu:3:CL:209526:default:CL_ACCUM:9fc50d37-b15d-47f2-8ada-75c2249abc44 is not a valid did:indy did",

here is the demo you can use to get some example indy credentials: https://digital.gov.bc.ca/digital-trust/showcase/ Once that issue is resolved I'm happy to merge

Nice catch! There was an issue in credo-ts that caused this. I updated the PR to use the latest credo alpha, and tested issuing and verifying with the bcgov demo, and it works now. 👍🏻

[TimoGlastra]

@wadeking98 BTW it's OK to be on an alpha version for now. We'll be releasing 0.5.2 soon, and will make a follow up PR then to the stable version

[wadeking98]

okay sounds good, I'll do some testing in a bit and then we'll get this merged!

[wadeking98]

Okay seems to be working well in bifold, I'm still running into an issue when I link it to bc wallet but I think that must be an issue with some configuration on our end. Great work LGTM