...

Recording of Call: 20220830 Indy Contributors Call Recording.mp4

...

Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>

Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>

Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

Char Howland (Indicio PBC) <char@indicio.tech>

Related Calls and Announcements

...

• Update on the Indy Ubuntu 20.04 Upgrade – Done?
  • New release candidate – dev build is available, further updates are needed found from 16.04 release, needs to be tagged for RC
    • Add in recent updates to Indy
    • Review commit differences between main and 20.04 branches.
  • Sovrin Build – might be this week – should be copy/paste, although the pipelines take a long time to run (but 1/2 the time of the Jenkins pipelines!!!)
• Root cause and solution to the "mixed node" problem: Indy Node issue 1769
  • Discussion of the short and long term handling of the issue.
  • Option 1: Just use the new "compat_set" merging from now on.
  • Option 2: Add a config transaction with a transaction number and use "compat_set" for earlier transactions, "sort" for ones after
  • Option 3: Versioning of transactions
  • Option 4: Option 1  for now, and revisit after we are live
• Using a domain name (e.g. "sovrin.org") as the name segment of a `did:indy` identifier, per this GitHub Issue

  Upgrade Notes

  • • Make it optional – the challenge for some will be in retaining a long lasting domain name
    • How to keep the two versions (domain hosted, one in did-indy-networks repo) of the genesis file in sync?
      • Idea – GHA that compares the two files and if they differ, creates a Pull Request to update the one in GitHub repo to match the one on the domain name.
      • Pull request must be reviewed and merged by the editors according to the governance – ensures there is a human step in the process
  • Action item: work on did-indy-networks
    • Include a static web generator so that we can publish a human friendly version of the information.
    • Include the governance guidance for the repo — who can merge and when?
  • Odd pipeline behaviour – test export jobs failing – perhaps a missing/wrong token?  Fail showing because of export fail but the tests are passing.
    • exports being used so that debugging can occur when tests fail.
    • Could we disable for PRs, but allow for internal builds.
  • Need to update the Indy read-the-docs documents
    • Project needed to provide updated docs
    • Would like to be on GH-Pages
    • Need to redirect from read-the-docs when the transition occurs
  • Update on CI/CD Update and Ubuntu Upgrade 
  • The root cause of the "Mixed Node" issue has been found – and it's not a mixed node issue.
    • Christian Bormann has been investigating and looks like he's figured it.
    • Issue: The merging of the RevRegEntry arrays into the RevReg was implemented in the past without a specified ordering. Such a merge is implemented differently between Python 3.5 and later, such that the merged array is in a different order in the 20.04 code, and so causes the root hash to be different between implementations. The result of the root hash differences is a 20.04 node as it stands today cannot join consensus.
    • Remaining ptions to address the issue that were discussed:
      • DONE: Write a version of the Python 3.5. merge routine (C code) in Python to get the same order as previously.
      • Discussion: How to deploy the new routine and how/when to replace with a the code supplemented with a ".sort" to always produce an ordered list.
    • Actions:

  Future Calls

  • GDPR and the right to be forgotten – mitigations and approaches.

  ...