Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Summary:

Topics:

  • Recent Merges / Priorities
  • Enabling OCA in ACA-Py
  • Update on Ledger Agnostic AnonCreds in Aries / ACA-Py
  • Q&A

Recordings from the call: 

  • Full Meeting: 
  • Extracted segments:
  • Relevant Chat Bits:

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Attendees

  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  •  @ Kim Ebert <kim@indicio.tech>
  • Frostyfrog<colton@indicio.tech>

Announcements

Deployments and Work Updates

Agenda

  • Updates on merges and current PRs – priorities
  • Presentation and discussion on enabling OCA for Aries in general and in ACA-Py specifically
    • MRGs and OCA – how to link them
  • Update on last week's discussion and ledger agnostic AnonCreds in Aries/ACA-Py:
    • How to enable object (DID and AnonCreds) resolution to improve ledger agnostic Aries protocols, and in particular, ledger-agnostic AnonCreds
      • Topics:
        • DID Resolution:
          • State of DID Resolution in ACA-Py – local and external resolvers, regex to define if and how to resolve a DID.
            • External resolvers – http and didcomm interfaces available
          • Work happening now on did:peer to make it fit the interface
          • Working happening at SICPA on a DID Registrar based on the DIF Spec - Issue to be added to discuss/track
            • EBSI plugin being created (Ethereum based, DIDs only)
            • Plugins needed for did:sov, did:indy, did:peer, did:key (question) and folks may be interested in adding more
          • Inconsistency in returned DIDDoc – suggests the need for a method in ACA-Py to "smooth out" the handling of DIDDocs - Issue to be added to request
        • AnonCreds Objects Handling
          • Currently tied to Indy – a "baseLedger" class with instances for Indy-SDK (indy-wallet storage only) and Indy VDR (indy-wallet or askar storage).
            • Handles writing as well, with Endorser handling.
          • Likely need to abstract to a similar, pluggable resolution and writing mechanisms - Issue(s) to be created.
            • Given an identifier in an AnonCreds object/context – resolve it.
            • Write AnonCreds objects using plugins to various target VDRs.
          • AFJ starting to talking about an AnonCredsResourceService

Next Meeting

Future Topics

Action items


  • No labels