Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt

Topics:

  • Presentation/Demo about AnonCreds in W3C VCDM format
  • Status ACA-Py 0.12.0rc1
  • Status AnonCreds RS
  • Status did:peer and AFJ Interop – where we are
  • Upgrading an ACA-Py deployment to AnonCreds RS
  • Status: ACA-Py 1.00 Checklist
  • Open Discussion

...

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

...

  • Presentation/Demo about AnonCreds in W3C VCDM format – Whats Cookin'
  • Status Updates:
    • AnonCreds RS in ACA-Py
      • Endorser progress – PRs 2715, 2720, 2782 all merged. Left?Done!
      • AnonCreds RS Update process - Issue #2808
        • Key concern – multi-tenant handling around enabling tenants to independently update when they are ready.
        • Handling is detailed in the issue.
        • Biggest change – enabling the use of Askar and Askar AnonCreds wallet types at the same time
          • credx and anoncreds-rs libraries both loaded.
          • All endpoints (old and new) available
    • did:peer and AFJ Interop
      • AATH – tests implemented for did:peer:1, 2, 4
      • PR 2748 with fixes for Credo/ACA-Py for did:peer:4
        • 1.0 and 1.1 support for 0023 DiD Exchange
      • Want to get Credo working for AATH – upgrade to backchannel controller for DID Exchange and OOB, restart the agent with new settings for everything
        • Sheldon is looking at this – starting with devcontainers so that a local environment is not needed.
        • Pick the devcontainer when you start the project – good pattern for the use of devcontainers on our repos
    • DID Rotation – PR #2816Akiff Manji
      • Getting close – applying updates from feedback on the PR
      • Two more endpoints – creating the DID Peer 2, 4
      • Concern generally about DID Peer creation related to the DIDComm service – did-communication  vs. DIDCommMessaging  - making sure that if you use one or the other, the related data must be consistent.
        • ACA-Py should be using did-communication only -- the related data should be a string -- not JSON. -- verify this.
    • Status of DRPC – working, adjustment to the protocol to support a problem report.
  • Status of ACA-Py 0.12.0rc2 - ready to go?
    • What PRs are needed for it?
  • Status of ACA-Py 1.0.0 Release:
  • Other PRs Ready for Review and Issues to Discuss

...