Page History

...

Timezone: America afternoon / APAC morning

...

• Name (Organization) <email>
• Richard Esplin(Evernym) <richard.esplin@evernym.com>

Related Calls and Announcements

...

• Indy Node
  • January:
    • Bugfix-release for edge cases in consensus protocol 
    • Additional rich schemas objects: schema object (Sovrin Foundation)
      • Just posted Indy HIPE
        https://github.com/hyperledger/indy-hipe/pull/149
      • Aries RFC
        https://github.com/hyperledger/aries-rfcs/pull/281
      • PR of schema object in progress for December
      • Making progress on other RFCs for objects and one that shows how all the objects fit together.
      • Next: encoding object, then mapping object
  • Future
    • Replacing Indy Crypto with Ursa (Kiva)
      • Debian packages for Ursa-0.3.0 are uploaded to repo.sovrin.org
    • Ubuntu 18.04 (Kiva)
      • Need to check additional dependencies: 

        Jira
        server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key INDY-2196

    • Anoncreds 2.0 (Sovrin Foundation)
• Indy SDK
  • January:
    • Bugfixes 1.14.2
  •  Future
    • Deprecating some docs (IS-1425: Getting Started Guides) and wrappers (IS-1423: Python and DotNet)
    • Deprecate  additional wrappers (IS-1424) and LibVCX (IS-1416)
    • GitLab migration alongside Jenkins (Foundation)?
    • Warnings from rust cargo clippy (Mike and Axel), epic: IS-1401
• Indy Catalyst
  • https://github.com/bcgov/indy-catalyst
  • Migrating to Hyperledger Aries: plan is to moving to aries-verified-credential-registry
    
    • Needs more documentation
• New design for revocation / Anoncreds 2.0 (Mike)
  • Need a plan for changes to Indy Node
    • Design: https://github.com/hyperledger/ursa-docs/tree/master/specs/anoncreds2
    • HIPE for overall changes, then a design PR for the changes specific to the different repos.
      https://github.com/hyperledger/indy-node/tree/master/design
    • BC.gov will implement the existing revocation capability in ACA-Py for use in constrained cases, starting with extracting anoncreds from libindy into indy-aries-anoncreds
  • Comparison of Anoncreds 1.0 and 2.0: https://docs.google.com/presentation/d/18aqk5q1sqRI_UhOEuXWAS46-Oltsu_HNk_JtKfDVBGc/edit#slide=id.g790163706e_0_0
• Aries Shared Libraries
  • indy-aries-vdr (Andrew Whitehead) https://github.com/andrewwhitehead/indy-ledger-client
    • Rust API is almost completed
    • No FFI
    • HTTP proxy
  • Next is indy-aries-anoncreds with anoncreds 1 (ready to add anoncreds 2)

Main Business

Future Calls

• Move afternoon call to once in four weeks?
  • Should just cancel, and focus on the AMER / EUR calls.
• Keith: Requirements questions: INDY-2305: Add IP address range for outbound TCP connections from validator nodes
  • Changes the way nodes are represented in the Pool Ledger
  • Next step: provide guidance to Keith on where the change should be made.
  • Should probably also change the Sovrin Steward Technical Guidelines to reduce the uptime requirements (uptime should be based on the pool, not individual validator nodes)
• Andrew:
  • Next steps on VDR
    • VDR Design Doc
    • FFI
    • Unit tests
    • Functional tests
    • Integrate into existing LibIndy
    • Migrate repo to Hyperledger
      • First commit should point to previous history in indy-sdk
• Aries-KMS
  • Would like a volunteer to move the wallet crate so we have a starting point
•  indy-aries-anoncreds
  • Mike has started. Repo for aries cred exchange framework.
    https://github.com/sovrin-foundation/aries-credx-framework-rs
  • Microsoft might be taking a different approach to ZKP revocation
    https://eprint.iacr.org/2019/550.pdf
• Aries-Shared-Util
  • Need a place for Rich Schemas functions
  • Lift-and-shift would be Indy specific, but refactoring for Aries could take a long time
  • Overlap with Mike's aries-core-rs?
    https://github.com/sovrin-foundation/aries-core-rs
• Rich Schemas
• Mike: IS-1222 blocked by Ursa CI / CD
• Agenda for next call: work session.

Future Calls

• Requirements questions:
  • IS-1099: anoncreds.prover_get_credentials_for_proof_req should return per-credential timestamp
    • Should we allow duplicate credentials from the same issuer?

...