2020-07-30 Identity WG Implementers Call

Summary

Connection Info

The call takes place over Zoom here https://zoom.us/j/244779296 

Date

30 Jul 2020 4PM UTC, 9AM PDT, 10AM MDT, 12AM EDT

Welcome/Introductions

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct

All activities should be conducted in accordance with the Antitrust Policy found here.

Attendees

• Name (Organization) <email>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>
• Matt Raffel (Kiva) <mattr@kiva.org>
• Anshu Jain (private)<Anshu.Jain.OBA@said.oxford.edu>
• John Callahan (Veridium) <jcallahan@veridiumid.com>
• Daniel Bachenheimer (Accenture) <daniel.bachenheimer@accenture.com>
• Sam Curren (Indicio) <sam@indicio.tech>
• Kyle Den Hartog (Mattr) <kyle.denhartog@mattr.global>

Announcements

• Indy Interoperathon Conference (Stephen Curran)

  • Enabling resolution protocols to operate across different Indy networks

  • Virtual event in September
  • Info & Registration
• Sovrin Technical Governance Board – seeking nominees

Working Group Reports and Release Plans

• Main Identity WG
  • Meeting notes
  • Ayanworks presented their SSI solution for Covid-19 / health credentials
  • https://github.com/p2418-6-identity/community/tree/master/VerifiableVaccinations
  • Discussion about "open standards" vs. "open source"

• Hyperledger Indy
  • Code Management Updates
    • Migrate Jira to Github issues
    • Moving from Jenkins to GitHub actions
    • Revocation 2.0 
  • Contributors Meeting
    • Revocation 2.0 (target:  available Summer 2020)
    • 2020-07-07 Indy Contributors Call
  • Indy Node
    • Replacing Indy Crypto with Ursa .
    • Discussed "rich schema" objects
    • Planning for Ubuntu 20.04 - other dependencies - Jira Issue
  • Indy SDK
    
    • Indy VDR into LibIndy
    • Indy Credx into LibIndy
  • Indy/Aries Shared Libraries
    • Aries Shared:
      • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
      • indy-credx - https://github.com/andrewwhitehead/indy-credx
        • To be moved to BC Gov and then to Hyperledger
      • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
        • Shared features across indy-vdr and indy-credx
        • To be moved to Hyperledger
      • aries-credx
        • https://github.com/sovrin-foundation/aries-credx-framework-rs
          • 6 most common attribute encodings (but not anoncreds 1 attribute encoding)
        • Can make a non-revocable credential and create proofs.
      • Aries Secure Storage initiatives:
        • Andrew is making progress on this. Covered on Aries WG call. Recording available on this page.
        • Key management
        • Demo planned for this week's ACA-Pug call.
  • Indy Semantics WG
    • ODCA pilots underway
    • The agenda, video, notes, etc. from the HL Indy Semantics WG call: 

• Hyperledger Aries
  • Aries Working Group meetings:
    • Meeting Agenda & Notes:  Aries Working Group
    • WG A:  2020-07-15-A Aries Working Group Call (AMER morning)
      • Work updates
      • Digital Wallet in IoT - - Robert Mitwicki
        • IoT platform use case
        • Values which brings SSI for IoT platforms
      • SSI in IoT Whitepaper - work update - Michael Shea 
      • Other businesses
      • 
        

        • 
          

    • 2020-07-29-B Aries Working Group Call (US afternoon)

      • GoalCode RFC
      • ActionMenu RFC
      • did:key support
  • Aries Protocol Test Suite - https://github.com/hyperledger/aries-protocol-test-suite
    
  • Aries Agent Test Harness - https://github.com/bcgov/aries-agent-test-harness
  • Aries Agents (Cloud Agent Python, Static Agent)
    • Aries Cloud Agent Python - ACA-Py User Group (ACA-Pug) Bi-weekly meetings
      • Release 0.5.1                   
      • Revocation based on anoncreds 1.0 has been merged into master and will be in the next release.
    • Static Agent Python - Release 0.7.1 - Patch to accept base64url encoded values with or without padding
    • Toolbox - Various improvements including Transaction Author Agreement support for Indy ledgers requiring it
  • Tools
    • Aries Protocol Test Suite
    • Aries Toolbox
  • Aries Shared Libraries (agent storage, vdr, utils)
    • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
      • Verifiable Data Registry (VDR; ledger) 
      • Remaining work: Design doc
      • As an Aries interface becomes standardized, will add that API layer
    • indy-credx / aries-credx
      • Rust layer that wraps Anoncreds (1.0 currently) 
      • https://github.com/sovrin-foundation/aries-credx-framework-rs
      • https://github.com/andrewwhitehead/indy-credx
      • Ran a branch of ACAPy with Aries Credx instead of LibIndy
    • Aries-Shared-Util
      • Pack / Unpack
      • Not started yet
    • Aries-KMS
      • Mike's presentation in Aries WG A
      • Mike and Cam's aries-core-rs → aries-kms-mayaguez
        https://github.com/sovrin-foundation/aries-kms-rs
      • Indy wallet crate might move to start another aries-kms implementation → aries-kms-vostok
  • Aries Language Frameworks and SDKs (Go, Java, JavaScript, .NET, Ruby, Python)

• Hyperledger Ursa
  • Meeting Agendas and Notes  
  • Presentations
  • Discussed:  
    • Enhanced Privacy ID from Bilinear Paring (https://eprint.iacr.org/2009/095.pdf)  
    • WASM Pr for BBS+ signatures
    • Non-revocation range tree RFC
    • Cryptographic accumulators

• Trust Over IP Foundation
  • Main site:  https://trustoverip.org/ 
  • Wiki:  https://wiki.trustoverip.org/display/HOME/Trust+Over+IP+Foundation 
  • 15 July 2020 - All Member Meeting:  
    • 
  • ToIP Working Groups:
    • Governance Stack
      • ToIP Standards Specification (TSS) - defines overall governance framework model, intended to become an industry standard.  May be implemented by multiple TIPs
      • Layer One Utility Governance Framework Templates (based on Sovrin)
    • Technical Stack 
      • ToIP Interoperability Profile (TIP) - a specific combination of technology layers for a full ToIP stack (e.g., Layer 1: Indy, Layer 2: Aries, Layer 3: Aries, etc.)
      • Layers - technical description & scope, required functionality, interfaces to other layers, certification testing standards
    • Utility Foundry
      • Focus on Layer One (e.g., Indy ledger) utility projects
    • Ecosystem Foundry
      • Focus on Layer Four governance frameworks (Human Trust layer)
      • Covid-19 Credentials Initiative (https://wiki.trustoverip.org/display/HOME/CCI+GF+Task+Force) 
        • Create a governance framework, establish governance authority, and define methodology for health passports & credentials 
    • Decentralized Semantics
      • Define specs and best practices for the data capture processes and semantic standards
      • Data capture architecture of immutable schema bases and interoperable overlays
    • Concepts and Terminology 
      • Develop a glossary of shared concepts and terminology  

• Sovrin Foundation
  • Technical Governance Board (TGB)
    • Seeking nominees
    • Smoothing developer onboarding
      • Curated getting started experience

      • How-To approach to using or making code changes in the project

    • Indy-performance status update 

      • Node-monitor is being developed that will take validator-info data and use it to build dashboards

  • Steward Council

    • Nicky Hickman gave an update on the metrics document

      • https://docs.google.com/document/d/1fjX_YIYHa6ok6zlohScvU13qACU0q6HzF18Jb10qtBU/edit - Connect to preview

    • Prometheus metrics

      • https://github.com/bcgov/indy-node-monitor/issues/5 - Connect to preview

      • Open pull request: https://github.com/bcgov/indy-node-monitor/pull/6 - Connect to preview

    • Discussion of legal issues
      • GDPR:  https://sovrin.org/gdpr-position-paper
      • Tombstones

        • Tombstones are transactions that mask data on a ledger without altering previously written data to the ledger. Essentially, a ‘GDPR’ request requires that personal data be removed from a ledger, however, data can’t be removed from immutable ledgers while still maintaining the integrity of the ledger. To compensate for this dilemma, ‘tombstones’ can be written to ledger nodes, such that when read requests for ‘retracted’ ledger blocks are made, the node returns a tombstone (blocked request) instead.

        • It’s up to individual nodes to add a tombstone or not. IOW, a node in Germany may return a tombstone on a retracted block. However, another node in Canada may return the original data. This is another dilemma…

        • Individual nodes can tombstone data: https://jira.hyperledger.org/browse/INDY-2082

  • Network is healthy with near 100% uptime

• DIF DIDComm Working Group
  • WG Rolling Agenda 
  • What are the possibilities for didcomm.org?
  • Discussion of DIDCOmm Errors (https://hackmd.io/NgbwTRg1RfKAQJ6QRUizKg)

  • PR/Issues:

    • Essential Protocols #81

    • Message Authorization Section #69

  • DID Relationships and Connections

    • https://hackmd.io/3TWLuQsYQ4-oJwnRNBYGFA

• DIF Interoperability Group
  • https://identity.foundation/interop/ 
  • Participation does not require DIF membership 
  • DIF Interop WG Charter Draft 

• W3C Standard
  • Verifiable Credentials Working Group
  • DID Working Group
    • DID Working Group Face-to-Face this week. Expect freeze to standard in May.

• Other?

Open Discussion

• Mattr Presentation – Kyle Den Hartog
  • Supporting compliant DID Documents without changes to Indy Node or Indy Plenum
  • Target:  proposing a new set of conventions to make it possible for the universal resolver sovrin driver and indy-vdr-proxy library (and other resolver implementations) to produce a did-core compliant DID document without needing to update the transaction structures that are submitted to the Indy ledger.
     
  • 0

Future Topics

• Trust over IP (www.trustoverip.org) 

Call Recording

zoom_0.mp4audio_only.m4a