2023-11-14 Aries Cloud Agent - Python Users Group Community Meeting

Owned by Stephen Curran
Last updated: Dec 15, 2023

Summary:

Topics:

  • Status: 0.11.0 Release
  • Status: AnonCreds RS Branch into Main
  • Status: Load Generator
  • Status: AnonCreds in W3C Format
  • Demo: The Traction Sandbox – a new utility for playing with ACA-Py, AnonCreds
  • PRs and Issues - status update
  • 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


Announcements

Agenda

  • Release 0.11.0 status
  • Status: Moving AnonCreds RS Branch into Main
    • Created branch, manually pulling across code net new and integration – all unit tests passing
    • Endpoints hooked up – new /anoncreds endpoints – not the existing endpoints
    • New wallet type "--wallet-type askar-anoncreds"
  • Status: Load Generator – moving along – migrating to Askar for the load agent
  • Status: AnonCreds in W3C VC Format
  • Demo: Traction Sandbox – a new utility for the ACA-Py community
  • Update on Please Ack "~please_ack":
    • One party can request an Ack  on any message – either to be returned on receipt, or on outcome of the message.
    • Other party MAY send an extra Ack  message.
    • Tricky to implement:
      • Generic ACA-Py on receipt  is not as easy as it could be.  Possible, but requires some rework.
        • Is the message a generic Ack or an adopted Ack
      • on outcome  definitely requires per protocol updates at least, plus logic for determining when the outcome of a message is known.
      • Isn't required on many messages, as once the message outcome is determined, a message is immediately generated and sent. What help is sending another message in parallel?
      • Where it is most likely to be useful – at the end of a protocol when there is no other message – making it useful may mean altering the protocol.
        • Issue Credential – should it be sent when the protocol "completes" or after the controller/business process decides to keep the credential.
        • Present Proof – should it be sent when the credential is cryptographically verified, or when the controller/business process decides the credential satisfies the business need?
          • If ACA-Py deletes the protocol state object automatically when the controller is sent the verification result, how can the protocol be kept for an optional "Ack"?
        • Basic Message – could (in theory) be used to enable "received" and "read" notifications of basic messages, but the "read" notification would extend the protocol lifetime from when the controller received the message, to when an event happened inside the controller. Tricky!
      • Requesting ~please_ack :
        • The configuration or the admin API would have to be updated to add the ability for the controller to say, "Hey, I want a ~please_ack added in these places..."
        • How do applications (wallets, etc.) want to use the ~please_ack feature?
  • Other PRs Ready for Review and Issues to Discuss

Upcoming Meeting Topics:

  • Discussion Topics:
    • Update on ACA-Py Container Scanning
    • Multi-architecture containers
      • Issue with BBS+ package – doesn't support ARM containers – need an update to their CI
      • Solution: A third container published that includes BBS+ package, but is single architecture
      • Others are Askar
  • The DSR team has started looking into supporting the "please-ack" protocol. A draft PoA will likely be ready for review on the next call,  

Future Topics

Action items