Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Summary:

  • Work updates
  • Transferable reputation via VC (Mike Richardson - EuroLedger)

    • Topic to discuss:

      - Proxy Issuer Wallet: is this a bit too much of a centralised data store?
      - Website Authentication, use of Trinsic connection Ids, or DIDs for user passcode?
      - Lack of revocation notifications: is this a problem?
      - Synchronizing upstream and downstream platforms (ie issuer and verifier) where credentials change
      - Wallet management: are we in danger of "credential proliferation"?
  • Optional: Wallets - do we need certification and who can do it? Robert Mitwicki
  • Other businesses

Note: This call is Recorded. Recordings posted at the bottom of the page.

Date

(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Attendees                                                                                                                                                            

Welcome / Introductions

Announcements

Related Calls

Release Status and Work Updates

  • Aries Protocol Test Suite
    • One agent under test
    • Issue, credential, and proof tests are merged.
  • Aries Agent Test Harness
  • Aries Shared:
    • Aries Shared:
      • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
        • Nearing release 0.6(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
          • CI - GitHub actions runs unit tests and basic integration tests
          • CD not there
          • No design doc, but crate docs
          • Rich Schema merged and behind a feature flag
          • Refactoring PR not merged - cleanup, internal simplification, crate docs
      • indy-credx - https://github.com/bcgov/indy-credx
        • Experimental ACA-Py branch created that can do credential exchange with indy-credx
      • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
        • Shared features across indy-vdr and indy-credx
        • pack/unpack on Ursa (not libsodium)
      • aries-credx
      • Aries Secure Storage initiatives:
  • Aries-CloudAgent-Python (bc.gov)
    • Release 0.5.1 is on PyPi.
    • Revocation support added and tested with Streetcred and esatus Mobile Agents; major/minor version handling
  • Aries-Framework-Go (Troy) #aries-go
    • Implementing the Out-Of-Band protocol
    • Implementing issue-credential and present-proof protocols
    • Edge agent in work based aries-framework-go using WASM with support for DIDs, VCs and DIDComm support being added
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
    • Release last week for Aries compatibility with ACApy and LibVCX (RFC 0094)
  • Aries-StaticAgent-Python
  • Aries-Toolbox
  • Aries-SDK-Java
  • Aries-Framework-JavaScript
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
    • Some work has been done to support the W3C Verifiable Credentials Data Model specification
  • Aries-MobileAgent-Xamarin (Aries MAX)
  • Ursa
    • 0.4.0 scheduled for late March
      • Improved hash to curve algorithm
      • Updates to AMCL wrapper
    • To replace libsodium, need to have a replacement for the anoncrypt / authcrypt sealed box for pack / unpack.
      • Can be done in Ursa with two steps, but might add as a single function call.

Agenda:

RFC Progress

Other Business

Future Topics

Action items

  •  

Call Recording

  File Modified




  • No labels