...
Excerpt |
---|
Planned Topics:
|
Recordings from the call:
- Full Meeting: 20220419 ACA-Pug Community Call Recording.mp4
- Extracted segments:
- Chat
08:08:48 From Peter Altmann - DIGG : I hope I can introduce myself here. I am Peter Altmann from the Swedish Agency for Digital Government. I work in the EU commission on the technical specifications for the proposed EU Digital Identity Wallet. I also work with some public sector actors in Sweden where I have used ACA-Py to develop some proof of concepts. Nice to be here!
08:17:25 From Victor Martinez : DIDCOMMv2 provides a negotiation compatibility https://identity.foundation/didcomm-messaging/spec/#negotiating-compatibility
08:19:17 From Artur Philipp : But does this offer the Option to negotiate the envolope (V1 vs V2)? A Client which only supports V1, is then probably not able to negotiate, Right?
08:19:
55 From Andrew Whitehead : A client that only supports V1 probably can't decode a V2 envelope at all
08:22:09 From Victor Martinez : Maybe something to take into account, SICPA has started a project to introduce DIDCOMM v2 in Aries JS.
08:22:40 From Victor Martinez : Some comments regarding SICPA implementation :
08:22:52 From Victor Martinez : If underlying primitives computing performance is a concern:
Dependency tree:
Didcomm -> Authlib -> cryptographyCryptography relies on foreign function interfaces (FFI):
for OpenSSL: https://github.com/pyca/cryptography/tree/main/src/_cffi_src/openssl
For rust code (x509 implementation): https://github.com/pyca/cryptography/tree/main/src/rust/src
Conclusion: low-level, performance-critical code is implemented in C or Rust.08:27:11 From Andrew Whitehead : Askar also contains Rust implementations of the primitives
08:29:43 From Peter Strobel : Oh that's interesting, I wasn't aware a v2 connection could be established without an Out Of Band invitation!
08:38:54 From Daniel Bluhm : I'll see if I can follow up with Sam on why the V3 was required and report back on the acapy channel on Discord
08:44:37 From Stephen Curran : Peter Strobel — that can be done in DIDComm V1 as well. “Implicit invitations” are when a party has a DIDComm service entry in their public DID. Another party can use that without an OOB.
08:46:03 From Andrew Whitehead : Not sure if it does make sense to automatically upgrade a V1 connection to V2 without rotating the DID, because the cryptography used is different
08:47:26 From Andrew Whitehead : Downgrading V2 to V1 is a worse proposition
Hakan Yildiz: Introduction to adding DIDCommV2 and Credential Exchange v3 support to ACA-Py - 20220405 ACA-Pug - Planning DIDCommV2 in ACA-Py.mp4
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
...
- Proposal/Discussion: Adding support for DIDComm V2/WACI to ACA-Py – led by Hakan Yildiz
- Homework – Please review this proposal and think about the issues raisedVideo from last ACA-Pug about this topic: 20220405 ACA-Pug - Planning DIDCommV2 in ACA-Py.mp4
- Getting to release 0.7.4 – what is needed after RC0
...