2023-09-28 Aries Framework JS Meeting notes

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

• Ariel Gentile - 2060.io (a@2060.io)
• Timo Glastra - Animo Solutions (timo@animo.id)
• Karim Stekelenburg - Animo Solutions (karim@animo.id)
• Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>

Resources

• Hyperledger Discord: https://discord.gg/hyperledger (#aries-javascript and #aries-bifold)
• Aries JavaScript Docs: https://aries.js.org/
• Repositories:
  • Aries Framework JavaScript: https://github.com/hyperledger/aries-framework-javascript
  • Aries Framework JavaScript Extension: https://github.com/hyperledger/aries-framework-javascript-ext
  • Aries Mobile Agent React Native: https://github.com/hyperledger/aries-mobile-agent-react-native

Status updates

• Aries Bifold (Aries Bifold User Group Meetings)
• Aries Call 2023-09-27 Aries Working Group Call
  • Unqualified DIDs
  • Credential Protocols
  • AFJ OWF Proposal

• Aries Interop Profile 3.0 continues to be discussed https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQ

Agenda

• Record the meeting
• Moving to OWF
• Separating the storage layer
  • Storing messages? All state should be derived from message exchange
    • User chooses whether to store the messages, but user needs to provide the current state of the protocol
  • Goal from Timo: More control over the database entities, how state is persisted. 
  • Built in storage useful in a lot of cases as well
  • Discuss next time: current storage model
• DIDComm v2
  • Discover Features V2 over DIDComm V2: https://github.com/hyperledger/aries-framework-javascript/pull/1576
  • Basic Messages V2:  https://github.com/hyperledger/aries-framework-javascript/pull/1546
  • Credentials protocols V3: https://github.com/hyperledger/aries-framework-javascript/pull/1560
  • Missing:
    • DID Rotation
    • Mediation / Pickup
• 0.5.0 release
  • https://github.com/hyperledger/aries-framework-javascript/discussions/1525
    
    • https://github.com/hyperledger/aries-framework-javascript/pull/1427
    • Drop node 16 support
  • Releasing new wrapper versions (for dropping support for Node 16)
    • https://github.com/hyperledger/aries-askar/pull/179
    • Need to update Indy VDR React Native wrapper: https://github.com/hyperledger/indy-vdr/issues/216
    • Need to create AnonCreds version update PR
    • Mark the indy-sdk as deprecated
  • DIDComm V2 moved to 0.6.x
  • Message repository updates?
    • Does not support filtering by key/id
• Keeping http socket open, when using implicit invitations
  • delay the closing of the http session?
  • Have a interface to override session closing handling? If not registered it will auto close if no response internally. Otherwise you get control over it
    • could be solved using middleware?
    • https://github.com/hyperledger/aries-framework-javascript/issues/97
    • feels a bit hacky? Requires you to implement custom logic, but there's probably more people that need to solve this issue → accepting request based on implicit invitation from an agent without an endpoint
  • Add option to auto accept requests to implicit invitations for certain dids?
    • DidRecord.metadata.allowImplicitInvitations = true
    • config: { autoAcceptImplicitInvitationsForDids: ["did:web:mediator.animo.id"] }
• Support ~timing decorator natively in AFJ

Meeting Notes

• Moving to OWF - meeting notes from this week's Aries WG
  
  • https://github.com/hyperledger/aries-framework-javascript/discussions/1586
  • Org migrations should be done with a transfer of the repo
    • maintains links & commit history
    • Move is far better than a fork.
  • Should discuss which components would be moved simultaneously
    • Probably at least Bifold and Askar
  • What to do with the RFCs?
  • Interoperability: are .Net and Go implementations still interoperable with the latest RFCs and interop suite?
    • .Net already moved to OWF
  • OWF policy: maintainers are in charge of the repositories and decisions (same as in Hyperledger)
  • AJF would probably be the most mature wallet framework, so OWF would have an incentive to promote and market it

Recording / Slides

Future topics

Future Topics:

• It would be good to discuss OCA implementation in AFJ and in Aries Bifold and where should be a boundary between the two in this feature.
• Extracting parts of AFJ into generic libraries
• Cheqd integration (Daev Mithran )
• AFJ Interop tests not running