• Update on June releases.
  • Planned releases for July and August.
  • Discussed call mechanics.
  • Discussed documentation improvements.
  • Discussed improvements to how transactions are endorsed.

Timezone: US morning and Europe afternoon

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 (organization) <email>
  • Sam Curren (Sovrin Foundation) <>
  • Richard Esplin (Evernym) <>
  • Samuel Smith (Sovrin Foundation)
  • Tomislav Markovski (Streetcred)


  • Indy SDK call being cancelled

Summary of Prior Call

Release Status

  • Indy Node
    • Early July: 1.9.0 Pluggable Request Handlers
      • CI / CD problems left us broken for days. Release is likely to be next week.
    • July: 1.9.1
      • Bug fix release
      • Still trying for late July
    • August: 1.9.2
      • Bug fix release
    • September: 1.10.0
      • PBFT view change
  • Indy SDK
    • Early July: Indy SDK 1.10.0
      • Flexible Credential Attribute Tagging (
      • Bugfixes
      • CI / CD problems left us broken for days. Release is likely to be late this week.
    • Late July:
      • GitLab migration alongside Jenkins (Foundation)?
        • Linux should be ready, maybe Windows.
        • Need a plan for mobile devices.
        • Could run it right after the release.
      • LibVCX without agency (Evernym)
    • August
      • Platform Updates (Evernym?)
      • Aries / Indy split
      • Anoncreds 2.0 (Sovrin Foundation,
  •  Ursa
    • June: 0.1.2
      • Exposing the existing functionality over a C-API for the Aroha team.
      • Not tagged in GitHub
    • July: 0.2.0
      • Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
      • Multi-signature BLS instead of aggregated signature
  •  Aries
    • Agent from Indy Catalyst migrated to aries-cloudagent-python (
    • Initial code migration from SDK repositories
  • Indy Catalyst
    • Migration from BC repos this week.

Work Updates

  • Documentation improvements: Michael B and Stephen C
    • Start with new developer path through Aries.
    • Need to review and prune out-of-date documentation (Alice / Faber treatment of pairwise DIDs is a key pain point)
    • Michael is working on Indy Agent walkthrough using C#
  • SDK 2.0 architecture / Indy-Aries split (Sergey)
  • Payment decorator (Sergey)
    • Tomislav has some feedback that should be incorporated
  • GitLab migration (Mike and Steve G)
    • Evaluated Circle CI, but it doesn't support Windows
    • Blocking various platform updates and CI / CD improvements
  • Warnings from rust cargo clippy (Mike)
    • IS-1270 through IS-1274
    • Will look at again in July
  • New design for revocation / Anoncreds 2.0 (Mike)

Other Business

  • Call mechanics:
    • Merge this call with the Indy SDK working group calls
    • Timing: move afternoon call later to pick up more of Asia
      • No change at this point
    • Frequency of the call: move to every week alternating timezones
      • No change at this point
    • Will begin recording the call
  • Documentation improvements: (a conversation for the US / Europe group, already had it with US / Asia)
    • Where to document changes? HIPEs/Repo Docs/Jira Tickets
    • PR's should link back to Jira tickets / GitHub issues
      • Goal is for each PR to link to somewhere that includes additional context / underlying motivation
      • Exclude RFC and HIPE repos
      • Need to revisit Hyperledger's policy on GitHub issues
    • Rocket Chat questions should be pushed to Stack Overflow
  • Recording transaction endorsers and INDY-1999
    • Unable to render Jira issues macro, execution error.

Next Week

Action items

Call Recording