Zoom: https://zoom.us/j/94626752608?pwd=K0t4N3VqRzlscTNYajlxMHNPM08yQT09
...
(6AM Los Angeles, 9AM New York, 2PM London, 3PM CET, 17H Moscow)
| Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.  |
|---|
Attendees
...
Discussion Topics
- Introduction
- Implementations
- Look over and document Veramo DIDComm v2 impl
- Typescript implementation
- Status Updates
- Hakan -
- Backwards compatibility between v1 and v2 Connections using v2? Non-Aries and Aries agent compatibility.Berend Sliedrecht Typescript impl
- No Secret Resolver or DID Resolver
- Heavily influenced by SICPA Rust impl
- DID Document updates and feedback to the SICPA team
- Will have examples
- ACA-py impl
- message structure
- encryption work coming
- add isue_credential and present_proof v3 for DIDComm v2
- didcomm/v2 profile not there yet https://identity.foundation/didcomm-messaging/spec/#defined-profiles
- Raise this in other Aries Working Groups (ACA-PUG)
- Start a draft?
- Exploring, so far we haven't identified an agent that supports the DIDCommV2 related tests
- Hakan and Judith -
- JFF teams
- Flow diagrams https://github.com/aviarytech/jff-didcomm-issuance/issues/2
- Is WACI spec sufficient? https://github.com/hyperledger/aries-rfcsdecentralized-identity/waci-presentation-exchange/blob/main/features/0160-connection-protocol/README.mdIf Aries is mandating connections, how do we reconcile the v2 spec which has no concept of connections?If issuance is tied to connectionsissue_credential/README.md
- https://github.com/sicpa-dlab/didcomm-rust/issues/91
- profiles managed and discovered
- interoperability fail points
...