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 5 Next »

Summary:

Planned

  • Work updates
  • Plan for future meetings
  • IOT best practices

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

  • IIW April 28-30
  • Mttr's proposal for a different approach to ZKPs

Related Calls

  • Previous Aries Working Group calls
  • DIF DIDComm WG Call: Rolling Agenda.
  • Identity Implementors Working Group call
    • Main place to get project updates, release status, and announcements.

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:
    • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
      • Nearing release 1.0(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
        • CD not there
        • No design doc, but crate docs
      • As an Aries interface becomes standardized, will add that API layer
        • Do we hold off on setting the version until this is in place.  Maybe 0.8
      • GitHub actions runs unit tests and basic integration tests
      • VON Network browser moved to Indy-VDR instead of LibIndy (no wallet needed because it is stateless)
        • Andrew working a refactor in a PR
    • indy-credx - https://github.com/andrewwhitehead/indy-credx
      • ACA-Py branch created that can do credential exchange with indy-credx
      • Next up: adding revocation 2.0 support
      • Integrating upgraded PyO3 library
    • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
      • Shared features across indy-vdr and indy-credx
      • pack/unpack on Ursa (not libsodium)
      • home for revocation support?  Or at least shared set membership proof handling?
    • aries-credx
    • Aries Secure Storage initiatives:
  • Aries-CloudAgent-Python (bc.gov)
    • Release 0.5.0 is on PyPi.
    • Revocation support added and tested with Streetcred and esatus Mobile Agents; major/minor version handling
  • Aries-Framework-Go (Troy) #aries-go
  • 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)
  • Aries-MobileAgent-Xamarin
  • 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.

RFC Progress

Other Business

Future of this meeting

  • We recognize as a community that each of us needs to adapt to current global events: improving the upstream open source libraries is likely to be slower.
    • No apology is needed if people take longer to respond to things.
    • Richard's role changed, so we need a change in host.
    • Fewer meetings and more async collaboration?

IOT best practices by Robert Mitwicki (cc Adam Burdett , Lohan Spies )

Future Topics

Action items

  •  

Call Recording

  File Modified




  • No labels