Zoom Link: https://zoom.us/j/99220079317?pwd=OHk0U05ITnBkSmZ0aXlIQzFDYWg3UT09
Summary
| Excerpt |
|---|
|
Recording of Call:
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
...
- Update on the Indy Ubuntu 20.04 Upgrade – Done?
- Root cause and solution to the "mixed node" problem: Indy Node issue 1769
- Discussion of the short and long term handling of the issue.
- Using a domain name (e.g. "sovrin.org") as the name segment of a `did:indy` identifier, per this GitHub Issue
Upgrade Notes
- 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:
...