• Catch up on Indy Interop-athon
  • Getting started on a new release
  • Getting started on a CI/CD migration
  • Getting started on the did:indy Method

The call recording is available here: 20200915 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.



  • @name (Employer) <email>
  • Stephen Curran (Cloud Compass Computing Inc.) <>
  • Kevin Griffin (Scoir, Inc) <>
  • Steve McCown (Anonyome Labs) <>
  • Lynn Bendixsen ( <>
  • Wade Barnes <>
  • Ajay Jadhav (AyanWorks) <>
  • Mikaela Tarkocheva  (Scoir, Inc) <>

Related Calls and Announcements

  • IIW coming soon - October

Release Status and Work Updates

Meeting Topics

  • Catch up on Indy Interop-athon - Presentation
  • Getting started on a new release of indy-node
    • Schedule a meeting - to review the release contents.
    • This Thursday at 6AM Pacific, 3PM CET to discuss.  We'll use this Zoom room, Richard to invite interested parties.
  • Getting started on a CI/CD migration
  • Getting started on the did:indy Method
  • Discussion
    • Why did the Sovrin node hard requirements get bumped to where they are today?
      • Factors: 
        • Primarily based on load testing, including load testing the Sovrin token and in particular, a token launch event.
          • This would trigger a spike in usage plus an ongoing higher load, plus a gradual load increase as payment events rise.
        • Also based on the load expected from revocation (gradual climb).
      • Any Indy Network must set the node hardware spec.
      • indy-node-monitor validator info includes usage information (CPU, disk space) and should be used for trending to predict when to increase resources
        • Clarity required on what the resources measure – e.g. overall load/disk usage on the server vs. indy-node load/disk usage.

Future Calls

Next call:


Action items