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

Compare with Current View Page History

« Previous Version 2 Next »

Summary:

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

Date

(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                   

Welcome / Introductions

Announcements

Release Status and Work Updates

Discussion Topics

  • did:keri lite - Rodolfo
  • 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
    • did:peer:2
      • Contains endpoint info
      • will exist in DIDComm v2
      • will require deterministic construction on both sides

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
  • OIDC Credential Exchange in Aries - Mike Richardson
  • decorator for redirection after proofs. - existing?

Action items

Call Recording


  • No labels