2020-08-18 Indy Contributors Call

Summary

Planned:

  • Update on Indy Node release
  • Preparations/pre-work for the Indy Interop-athon

The call recording is available here: 20200818 Indy Contributors Call Recording

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 http://www.linuxfoundation.org/antitrust-policy. 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.

Introductions

Attendees

  • @name (Employer) <email>
  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  • Richard Esplin (Evernym) <richard.esplin@evernym.com>
  • Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Related Calls and Announcements

Release Status and Work Updates

Meeting Topics

  • Preparation for the initial topics at the Indy Interop-athon - Indy Interop-athon - Making "Network of Networks" Real
    • Topics planned for the Interop-athon - Presentation
      • Creating an did:indy DID Method Specification, including namespacing mechanism
      • Method for finding network metadata (genesis file, governance information)
      • Indy and KERI: Ready for Prime Time?
      • Indy support for DID Docs (Kyle Den Hartog's document discussed at a recent Indy Contributors call).
      • Updating Indy SDK to store and use objects with network references
      • Updating Indy VDR and Aries Storage to use objects with network references
      • Defining the backlog
      • Getting the work done
  • Indicio's networks.
  • Demo of the new Indy Monitoring board setup for the Sovrin network.

Future Calls

Next call:

Future:

Action items