• Evolving Indy usage to support DIDDocs

The call recording is available here: 20200721 Indy Contributors Call

Remember the Hyperledger Code of Conduct

Anti-Trust Policy

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.



Related Calls and Announcements

  • Identity Implementer Working Group call (Wiki Page) - every 2nd Thursday 

Release Status and Work Updates

  • Indy Node
    • Timing TBD:
      • Replacing Indy Crypto with Ursa(Kiva)
        • Test are running as I type...
      • ? More "rich schema" objects
      • ? Ubuntu 20.04 (Kiva) - other dependencies - Jira Issue
  • Indy SDK
    • Timing TBD:
      • Indy VDR into LibIndy
      • Indy Credx into LibIndy
  • Indy/Aries Shared Libraries

Meeting Topics

  • Kyle Den Hartog Recent discussion on the did:sov method and adding DIDDoc support to indy-node
  • Stephen Curran Continuing the discussion about Indy network interoperability.  How do we accomplish this use case:
    • "Enabling a prover to seamlessly create a proof that involves credentials rooted in different Indy networks, and for a verifier to verify such a proof"

Future Calls

Next call:


Action items