2022-05-26 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

Status updates

  • Aries Bifold (Aries Bifold User Group Meetings)
  • Aries Call
  • Hyperledger moved to Discord
  • Releases
    • Next release - 0.2.0
      • Issue Credential v2 indy
      • Present Proof v2 indy
      • Out of Band / DID Exchange - no public dids yet
      • Pickup v2
      • Holder/Verifier revocation and revocation notification
    • 0.3.0
      • Issue Credential v2 JSON-LD
      • Present Proof v2 JSON-LD
      • Shared Components?
      • Splitting up the framework

Agenda

  • Record the meeting
  • OOB / DID Exchange / Issue credential v2 fixes
  • JSON-LD Credential support update
  • Message queueing in mobile agents
  • Splitting up the framework
  • AMA

Meeting Notes

  • Aries Agent Test Harness documentation for AFJ
  • Message queueing in mobile agents
    • Context
      • using AFJ in mobile agent in bifold
      • using websockets to pick up messages from mediator
    • Problem: messages are not processed sequentially in order
    • Batch pickup already queues messages and processes in order
    • Websocket transport does not queue messages
    • Issue occurs because the credential offer is sent when the connection is still response, did exchange doesn't have this problem anymore because of required complete message.
    • How do we want to proceed with having ability to configure messages being processed sequentially or in parallel
    • Use sequential processing for pickup v1, v2 and implicit.  (Timo Glastra)

Future topics

  • React Native testing
  • Support for Deno
  • Monorepo dependencies
    • TypeScript types



Meeting recording:

meeting-recording

  File Modified

Text File dummyfile.txt Replaced video attachment for Atlassian cloud migration

Sept 10, 2024 by Anton Baranov