Page Comparison

Summary

...

13 Aug 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

...

• 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-08-04 Indy …
    • Discussion items:
      • Plans for next Indy Node release
      • Contributions needed on Indy Node
      • Preparations/pre-work for the Indy Interop-athon (highlighted in next call)
  • Indy Node
    • Pending release:  as soon as possible (date TBD) 
    • 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
      • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
      • aries-credx - https://github.com/sovrin-foundation/aries-credx-framework-rs
      • Aries Secure Storage initiatives
  • 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-08-12-A Aries Working Group Call (AMER morning)
      • Test Harness, Aries Protocol Test Suite (Stephen Curran)
        • Creating an Aries Interoperability Lab
      • Aries Toolbox - Services, VC with consent  (Robert Mitwicki)
    • WG B:  2020-08-12-B Aries Working Group Call (US afternoon)
      • Goals with Governance (Sam Curren )
        • Increase User Trust on Accept Screens: https://hackmd.io/pIc1Qo60TD-fXa7ht7rGlw
        • RFC 519: Goal Codes: https://github.com/hyperledger/aries-rfcs/pull/519
        • Goal with Governance: https://hackmd.io/8C4LojQPTfuJJ1PK-c0hng
  • 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)
    • 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)

...

• Trust Over IP Foundation
  • Main site:  https://trustoverip.org/ 
  • Wiki:  https://wiki.trustoverip.org/display/HOME/Trust+Over+IP+Foundation 
  • Steering Committee:  https://wiki.trustoverip.org/display/HOME/Steering+Committee+Meeting+Page
  • 12 Aug 2020 - Steering Committee Meeting:  
    • Recording:  https://zoom.us/rec/share/1ItPFrHN-HlOX4mdy0z4ZZIEIZT1X6a8g3IZ8_sPmhm7tdhYEbxb99jTQDx25xFp
  • ToIP Working Groups:
    • Communications Committee
      • https://wiki.trustoverip.org/display/HOME/Communications+Committee 
      • Confluence wiki organization, development, templates, and training
      • V2 of our ToIP stack diagram
      • V2 of our Introducing the Trust over IP Foundation white paper
    • Governance Stack
      • WG:  https://wiki.trustoverip.org/display/HOME/Governance+Stack+Working+Group
        • Creating new task forces to study governance architecture and process & roles 
      • 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 
      • WG:  https://wiki.trustoverip.org/display/HOME/2020-08-10+Weekly+Meeting  
        • Education Meeting 
          • Aries DID Ledger Architecture: Scheduled for 14-Sep-2020; See Slack Channel and Mailing List for details.
            • Stephen Curran will discuss Interop across Indy networks: two day event, details are available here: https://bit.ly/indyinterop20
              
              • proof should be verifiable across Indy networks in a single transaction
              • Aries agent should be able to resolve all objects (does not work today)
          • BAF and DDNR presentation plans are underway; Lock for announcements  forthcoming on lack Channel and Mailing List.
      • 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
      • WG:  https://wiki.trustoverip.org/display/HOME/UFWG+Meeting+Page
    • Ecosystem Foundry
      • WG:  https://wiki.trustoverip.org/display/HOME/Ecosystem+Foundry+Working+Group 
      • 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
      • WG:  https://wiki.trustoverip.org/display/HOME/Decentralized+Semantics+Working+Group 
      • 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 
      • WG:  https://wiki.trustoverip.org/pages/viewpage.action?pageId=65700
      • Develop a glossary of shared concepts and terminology  

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

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

    • Indy development opportunities

  • Steward Council

    • Nicky Hickman gave an update on the metrics document

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

    • Prometheus metrics

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

      • Open pull request: Image Modifiedhttps://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

...

Call Recording