2024-05-08 Aries Working Group Call

2024-05-08 Aries Working Group Call

Summary:

  • The new VC-DI Attachment Format for issuing credentials

  • Unqualified DIDs checkin

Zoom: https://zoom.us/j/93803916577?pwd=UWdLSTJ2b0kvZTRyc1hZTUdQQ3ZFZz09

Recording: 

Date

May 8, 2024 (7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)



move



Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

move



Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Attendees

  • @Sam Curren  (Indicio) <sam@indicio.tech>

  • @Stephen Curran  (BC Gov/Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

  • @James Ebert (Instnt) <james@instnt.org>

Welcome / Introductions

Announcements



Release Status and Work Updates

Discussion Topics

  • The vc-di attachment – RFC 809, proposed changes in PR 828

    • Timo/Patrick

  • Unqualified DIDs 

    • https://hyperledger.github.io/aries-rfcs/latest/features/0793-unqualfied-dids-transition/

    • Update Dates?

      • Target Date for code update: 2024-05-01

      • Target Date for deployment update: 2024-07-02

      • Sam to update the RFC with a PR

    • did:indy handling

      • unqualified anoncreds objects being rejected

      • did:indy changes the unique identifier within the DID. both the old method and the new method should work.

      • Credo is using did:indy only, cannot resolve unqualified asset identifiers.

      • Rushed work to address within AnonCreds RS ( ? ) and ACA-Py. 

      • quicker fix in Credo, longer fix in everything.

  • DIDComm v2 adoption

    • ACA-Py progress shared last week

    • Any other updates?

    • Credo has the beginnings of DIDComm v2, but does need some attention.

  • Open Discussion

    • JSON-LD creds impl within ACA-Py no longer working with Credo 0.5.0

      • Sphereon library using for Presentation Exchange objects is not expecting quite the same things, additional fields.

      • Daniel working through and testing, will report / create issues on the appropriate repos.

    • OOB Invitation / DID Exchange CCU

    • Indy - defining a DIDComm protocol for fetching VDR content.

      • send batch requests - essentially DID URLs and get them back.

      • under design now 

    • Protocol RFC

Other Business

Future Topics

Action items

Call Recording: