2023-02-22 Aries Working Group Call

Summary:

• did:keri lite
• LegacyPeer vs Transition to did:peer:1 or did:peer:2?

Date

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

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

Attendees                   

• Sam Curren(Indicio) <sam@indicio.tech>
• Warren Gallagher (AffinitiQuest.io) <warren@affinitiquest.io>
• Simon Henriksen (Hyphen) <simon@hyphenapp.xyz>
• Rodolfo Miranda (RootsID)<rodolfo.miranda@rootsid.com>
• Michael Richardson (NorthernBlock) <mike.richardson@northernblock.io>
• Alexandra Walker (Indicio) <alex.walker@indicio.tech>
• Timo Glastra (Animo) <timo@animo.id>
• Stephen Curran  (BC Gov / Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

Welcome / Introductions

Announcements

• AnonCreds v2.0 Working Group's first meeting was held Monday – Meetings Page: Meetings: AnonCreds v2.0 Working Group
  • Meetings will be every 2nd Monday at 10:00 Pacific / 19:00 Central Europe starting this week (next meeting March 6)
  • Summary of discussion on Monday 2023-02-20 AnonCreds v2.0 Working Group Meeting, and slides
• Aries Meeting at OWF – recording to be posted here: https://github.com/openwallet-foundation/architecture-task-force/wiki/2023-02-20-Meeting-Minutes

Release Status and Work Updates

• Aries Agent Test Harness (https://aries-interop.info)
• Aries Shared Components - Indy SDK replacements
  • Shared Rust Library/CredX (AnonCreds) https://github.com/hyperledger/indy-shared-rs
  • Indy Verifiable Date Registry - Ledger Interface https://github.com/hyperledger/indy-vdr
  • Aries Askar secure storage - https://github.com/bcgov/aries-askar
  • AnonCreds Rust - https://github.com/hyperledger/anoncreds-rs
• Frameworks:
  • Aries-CloudAgent-Python (https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings)
  • Aries-Framework-JavaScript (https://github.com/hyperledger/aries-framework-javascript, Meetings: Framework JS Meetings)
    • Version 0.3.2 released - https://www.youtube.com/watch?v=PGgUPPwa63g
    • PR from SICPA for DIDComm v2 on AFJ need help:
      • https://github.com/hyperledger/aries-framework-javascript/issues/1038
      • https://github.com/hyperledger/aries-framework-javascript/pull/1096
  • Aries-Framework-Go (Troy) #aries-go (https://github.com/hyperledger/aries-framework-go, Meetings: aries-framework-go) 
  • Aries VCX (https://github.com/hyperledger/aries-vcx)
  • Aries-Framework-DotNet (https://github.com/hyperledger/aries-framework-dotnet)
  • Picos as Aries agents (https://github.com/Picolab/aries-cloudagent-pico)
    • Phil Windley has students working on a DIDComm v2 version of ACA-Pico
• Mobile:
  • Aries Mobile Agent React Native, aka Aries Bifold (https://github.com/hyperledger/aries-mobile-agent-react-native, Meetings: Aries Bifold User Group Meetings)
    • Bifold Summit Happening now – Bifold Summit 2023
    • BCGov has realeased an Aries Bifold version, rebranded w/ BC blue/theme/etc (BC wallet)
  • Aries-MobileAgent-Xamarin aka Aries MAX (https://github.com/hyperledger/aries-mobileagent-xamarin)
• aries-mediator-service – a DIDComm Mediator in a Box
  • working on Pickup support
• aries-endorser-server – an Indy Endorser in a Box (in development)
• Aries-Toolbox
• Aries-SDK-Java
• Ursa (https://www.hyperledger.org/use/hyperledger-ursa, https://github.com/hyperledger/ursa)

Discussion Topics

• OWF Presentation
• did:keri lite - Rodolfo
  • Has support for 'short-version' and 'long-version'
  • Currently has a dependence on larger keri libraries
  • Currently has a dependency on the larger did:keri method spec
• LegacyPeer DID Method vs did:peer:1 or did:peer"2
  • LegacyPeer DID Method
    • https://github.com/hyperledger/aries-rfcs/pull/768
    • Community Coordinated Update?
    • Phase 1 - Everybody can read, defaults remain using old - April?
    • Phase 2 - Everybody switches default to fully qualified DIDs - June?
    • Phase 3 - Support for Old may be removed. - Sept?
  • did:peer:1
    • Supported in AFJ
    • lacks test vectors to verify serialization/normalization
  • did:peer:2
    • Contains endpoint info (large)
    • will exist in DIDComm v2
    • will require deterministic construction on both sides
• Timo: translating to existing DID makes the most sense.
  • requirements: translate by both sides of connection
  • recommends did:peer:2
  • skip legacy peer (also stephen, james agrees)

Other Business

Future Topics

• Thomas - Nessus DIDComm 0.23.2 First Release
  • Wallet abstraction for AcaPy + Nessus native
  • Camel Http Endpoint for Nessus agent
  • Support for RFC0434 Out-of-Band Invitation V1 & V2
  • Support for RFC0023 Did Exchange V1
  • Support for RFC0048 Trust Ping V1 & V2
  • Support for RFC0095 Basic Message V1 & V2
  • CLI to work with supported protocols and model

• Issue Credential v2.1 learning
• State-of-union of Aries projects
• decorator for redirection after proofs. - existing?

Action items

Call Recording