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

...

• Name (Organization) <email>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Announcements

• Indyoperathon Conference Interop-athon (Stephen Curran)

• Enabling resolution protocols to operate across different Indy networks

Virtual event in September
• The Indy Interop-athon is a two-day virtual event to define the work needed in Indy and Aries to make "network of networks" a reality for Indy DID Utility instances.
• Homepage & registration:  Indy Interop-athon - Making "Network of Networks" Real
• Sovrin Technical Governance Board – seeking nominees

...

• 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-08-04 Indy …
    • Discussion items:
      • Plans for next Indy Node release
      • Contributions needed on Indy Node
      • Preparations/pre-work for the Indy Interop-athon
  • 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-credxaries-credx - https://github.com/sovrin-foundation/aries-credx-framework-rs6 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-0708-1512-A Aries Working Group Call (AMER morning)
      • Human Colossus Foundation 
      • https://humancolossus.foundation/technology
      Working demo: https://argo.colossi.networkTest Harness, Aries Protocol Test Suite (Stephen Curran)
      • Creating an Aries Interoperability Lab
      • Aries Toolbox - Services, VC with consent  (Robert Mitwicki)
    • WG B:  2020-0708-1512-B Aries Working Group Call (US afternoon)
      • Aries Storage - Andrew Whitehead
      • OOB Reuse
      • Credential Issue Replacement_ID
  • 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)

...

• 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 -performance status update 

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

      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

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

  • PR/Issues:

    • Essential Protocols #81

    • Message Authorization Section #69

  • DID Relationships and Connections

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

...

• KERI Presentation – Sam Smith
  • KERI paper
  • KERI webinar

Future Topics

• Trust over IP (www.trustoverip.org) 

...