Summary:
Topics:
- Release Planning:
- 0.12.1
- PR Merges for pending 1.0.0
- Adding Support in ACA-Py for DIDComm v2
- Open Discussion
Zoom Link: https://zoom.us/j/98856745538?pwd=VkJROWRxeW43d3hOdnJLemwrS0JKUT09
Call Time: 8:00 Pacific / 17:00 Central Europe
Recordings From the Call:
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
Welcome, Introductions and Announcements
Attendees
- Daniel Bluhm (Indicio PBC) <daniel@indicio.tech>
- Wade Barnes (Neoteric Technologies Inc / BC Gov) <wade@neoterictech.ca>
- Emiliano Suñé (Quartech / BC Gov) <emiliano.sune@quartech.com>
Documentation:
- ACA-Py documentation: https://aca-py.org
Agenda
- Status of ACA-Py 0.12.1
- Release 0.12.1rc1 available – any issues found?
- Potential issue – the "holder_did" / "entropy" issue – Issue 2923
- Limited to the AnonCreds in W3C VCDM Format code?
- Anything else to add?
- Once 0.12.1 is out – ready for 1.0.0rc4?
- Include the tenant authorization changes?
- Wait for the drop Indy SDK to be ready to merge?
- AnonCreds RS PRs – finally!
- Main Topic: Adding DIDComm v2 Support to ACA-Py – Daniel Bluhm Frostyfrog
- Uses DMP: https://github.com/Indicio-tech/didcomm-messaging-python
- https://github.com/frostyfrog/didcomm-v2-test-util
- https://github.com/Indicio-tech/aries-cloudagent-python/tree/feat/didcommv2-proof-of-concept
- Diff: https://github.com/hyperledger/aries-cloudagent-python/compare/main...Indicio-tech:aries-cloudagent-python:feat/didcommv2-proof-of-concept
- ED25519 2020 Verification of JSON-LD Signatures
- Can issue the credentials
- When trying to verify – looking for the old style (2018) format – needs to be update
- Verification is failing because decoding the public key incorrectly – wrong key, looking for base58 key, should be looking for multi-base.
- Daniel Bluhm does real time debugging and identifies the problem. Cool!
- Decoding is likely in ACA-Py
- VCDM 2.0 – need to add support for that.
- Be able to receive/process 2.0 and 1.1
- Flag at issue time to send 1.1 or 2.0?
- Discussion for tomorrow at Aries Working Group call to discuss the new vc-di attachment format.
- How to manage the transition from the current JSON-LD vs using the VC-DI attachment format?
- How to retain backwards compatibility?
- How to use the new VC-DI attachments.
- Importance – using ACA-Py with VC-API – see this issue: https://github.com/w3c-ccg/vc-api/pull/382
- Open Discussion
Upcoming Meeting Topics:
Future Topics
- Formal test plan
- We go through a process of release candidates but we often still end up discovering bugs after releases are out
- Daniel to create an issue to start a discussion