Versions Compared

Old Version 3

changes.mady.by.user Richard Esplin

Saved on

compared with

New Version Current

changes.mady.by.user Richard Esplin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

Excerpt

Expected topics

  • Release updates
  • Moving the PostgreSQL wallet out of experimental
  • Proposal to improve performance of the Indy SDK CI test pipeline
  • Proposal to support Fully Qualified DIDs

...

  • Name (organization) <email>
  • Richard Esplin (Evernym) <richard.esplin@evernym.com>
  • John Jordan (Province of British Columbia)
  • Ian Costanzo (Anon Solutions)
  • Cam Parra  (Kiva) <camilop@kiva.org>
  • Alexander Shcherbakov (Evernym) <alexander.shcherbakov@evernym.com>
  • Ken Ebert (Sovrin Foundation) <ken@sovrin.org>

Announcements

  • Hyperledger voting is about to happen. Make sure you have received an invitation to hyperledger-contributors mailing list to get voting instructions.

Summary of Prior Call

Release Status

  • Indy Node
    • August: 1.9.2
      • Bug fix release
      • Important bug fix for ledger corruption INDY-2211
    • September: 1.10.0
      • PBFT view change
  • Indy SDK
    • August: 1.11.1
      • Finish Authors vs Endorsers
      • Finish proof of possession of payment address
      • Platform Updates: Ubuntu 18.04
    • September: 1.12.0
      • Fully qualified DIDs
        • Dependent on DIDDoc support? (Daniel's document and David Huseby's work)
      • Platform Platfrom Updates: MacOS, CentOS
    • Future
      • GitLab migration alongside Jenkins (Foundation)?
      • Aries / Indy split
      • Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
  •  Ursa
    •  Working on release of 0.2.0
      • ZKP  / ZKLang improvements
      • Debian packages
      • Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
      • Refactor multi-signature BLS in addition to aggregated signature
  •  Aries
    • Agent from Indy Catalyst migrated to aries-cloudagent-python (BC.gov)
    • Initial code migration from Indy SDK repositories
  • Indy Catalyst
    • Migrated?

...

Other Business

  • Name change: Indy Maintainers call → Indy Developers call
    • Approved
  • Sovrin specific upgrade script for Indy Node 1.9.2 due to auth_rules bug (INDY-2211)
  • Replace Amazon Linux with CentOS in the build pipeline
    • Adding CentOS increases the build pipeline by another 30 minutes.
    • Approved. Need to be clear about this change in the release notes.
  • Improving the performance of the Indy SDK CI pipeline: 
    Jira
    serverHyperledger JIRA
    serverId6326cb0b-65b2-38fd-a82c-67a89277103b
    keyIS-1345
  • https://github.com/hyperledger/indy-post-install-automation is superseded by indy-qa-automation, so it was archived.
  • Improving the performance of the Indy SDK CI pipeline: 
    Jira
    serverHyperledger JIRA
    serverId6326cb0b-65b2-38fd-a82c-67a89277103b
    keyIS-1345
  • Proposal for Fully Qualified DIDs
    • IS-451
    • IS-1358
    • Breaking change in order to go faster and avoid duplicated code?
  • What should be done in Indy SDK next: 
    • Aries architecture (Ken's proposal)
    • Evernym: OSX support and architecture investigation
    • BC.gov:
      • New Ursa features?
        • Proving that a link secret has been seen before, 
        • Repudiability as an option for proving
        • New predicates
        • Anononcreds 2.0
      • Architecture investigation
  • PostgreSQL wallet to graduate from "experimental" status?
    • BC.gov and Kiva are using the plugin
    • Need an update on the open issues.
    • Need testing to be part of the automated CI / CD pipeline: publish to repo.sovrin.org
      • Sergey will look to see if there are any concerns with repo.sovrin.org
    • Need to define the release process: who fixes issues and when does PostgreSQL reliability prevent releases?
  • Need an apt-get artifact of Ursa that can be used by Indy Plenum and Indy SDK
  • Progress on Fully Qualified DIDs: IS-1358, IS-1359

Future Calls

  • fuzzing libindy https://github.com/AxelNennker/indy-sdk/tree/fuzzing/
    `cargo +nightly fuzz run fuzz_target_1 -- -only_ascii=1`
    Worried about the lots of unsafe code in libindy
    ```
    ignisvulpis@namenlos:~/development/hyperledger/indy-sdk/libindy$ find src -name \*\.rs -exec fgrep unsafe {} \; | wc -l
    61
    ```
  • New pack / unpack requires disclosure of recipient
    • Cannot hide the receiver of the message like we could with msg_pack
    • Allows having multiple recipients of the same message
    • Should list the drawback in the Aries-RFC? Is there an alternative way that preserves the capability to selectively disclose the recipient?
    • From Kyle Den Hartog
      msg_pack presents problems when dealing with an agent that maintains more than one relationship. For example, if I receive a message, I don't know which key in my agent I should be using to decrypt the message. We can get sender anonymity or receiver anonymity, but I don't believe it's possible to get both and still determine who the message is for.
    • Pack/unpack only exposes the Verkey of the recipients. It does not do forward secrecy.
  • Ursa and AMCL:  Discussed in the Ursa call (August 21), but no decision yet.
  • Architecture questions for Indy SDK:
  • PostgreSQL wallet to graduate from "experimental" status?
  • Partially completed refactoring of the Request format: INDY-1375 and IS-567
  • Maintainership requirements for Indy Node and Indy SDK
  • How to handle old pull requests that failed DCO Checks? Close?
  • How to handle pull requests for IOS / Swift wrappers? Close and encourage the move to Aries?
  • How to handle pull requests for LibVCX? Deprecate?
  • Close PR https://github.com/hyperledger/indy-sdk/pull/1048 as something that will be replaced by the advanced schema work?
  • HIPE pull requests: https://github.com/hyperledger/indy-hipe/pulls

...

  •  Nathan (Daniel)
    • Set up alternate meeting hosts to record
  •  HIPE #138, Issue #144 (Ken and Brent)
    • Create a PR for changing status to ACCEPTED
    • Check for an Aries RFC
  •  Rename Indy Maintainers → Indy Developers in the calendar invitation (Richard)

Call Recording

View file
namezoom_0.mp4
height250