Content Comparison

Summary:

...

01 Nov 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                 

...

• Aries marketing update - Helen Garneau Alex Metcalf  
  • Logo concepts are on Discord for an informal vote
  • Join our marketing working group meeting, last Tuesday of every month: Aries Marketing Working Group
• Aries Akrida - https://github.com/Indicio-tech/aries-akrida
  • Load Testing Framework
  • Supports testing Issuance and Verifications
  • Migrate to Hyperledger?
  • Continues work from https://github.com/hyperledger/aries-mediator-service/tree/main/load-testing
  • AATH Backchannels https://github.com/hyperledger/aries-agent-test-harness/tree/main/aries-backchannels
• Unqualified DIDs
  • DID Rotation
    • https://github.com/hyperledger/aries-rfcs/pull/794
    • Implementation Updates?
  • did:peer:4
    • https://identity.foundation/peer-did-method-spec/index.html#method-4-short-form-and-long-form
    • Browser Resolver Demo
  • DID Exchange with no DID Document / Signature
    • https://github.com/hyperledger/aries-rfcs/pull/795
    • Version Bump for DID Exchange included
  • Community Coordinated Update
    • https://github.com/hyperledger/aries-rfcs/pull/793
    • Dates?
      • Implementation Completion
        • ACA-Py end of December is reasonable
        • AFJ? did:peer:2 tweak, did rotation, did:peer:4
        • VCX? 
        • Bifold (inherits AFJ, but also may need minor associated UI work)
      • 'Understand New' Deployment
        • 4-6 weeks?
      • 'Default to New' Deployment
        • Begins immediately after 'Understand New' Deployment
        • 4-6 weeks
  • Aries Agent Test Harness update for testing support
• Why Move to DIDComm v2?
  • Aligns with demos, tools, and presentations

    • Example/demo using DIDComm V2 & did:peer:2 (there are plans to move this to did:peer:4 instead)

    • DIDComm Book
  • Adopts handshakeless interactions (no anticipating of going back)
  • Eliminates criticism of protocol choice - DIDComm v2 was not created within the HL Aries project.
  • Cleans up historical issues with Aries.
  • Aligns with expanded DIDComm adoption
    • Example: Veramo
• Please Ack question – is a ~please_ack (OUTCOME) 
• Open Tasks
  • LTS Policy
    • Fabric starting point: (https://hyperledger.github.io/fabric-rfcs/text/0005-lts-release-strategy.html)
• Open Discussion

...