Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

Agenda

  • Record the meeting
  • DIDComm v2
  • 0.45.1 released0 releaseOpenID4VCI, SIOP, OpenID4VP support
    • Project proposal:
      Widget Connector
      urlhttps://docs.google.com/document/d/1fja1pQvB6UJcJR7d00HaEDTk-WMUFS9SZNkle-jm2BE/edit#heading=h.ro1tvbkzavyy
    • Make AFJ compatible with ARF / EU Standards
      • mDL
      • OID4VC
      • SD-JWT
      • Secure enclave integration with Askar
      • AnonCreds over OpenID4VC
    • Get experimental SIOPv2 / OpenID4VP integrated based on implementation in Paradym WalletNeed to extract the openid4vc-client from here: discussions/1525
    • Discussion: https://github.com/
    DIDComm v2
  • Keeping http socket open, when using implicit invitations0.5.0 release
    • Separating the storage layer
    • Support ~timing decorator natively in AFJ
    • 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

    Meeting Notes



    Recording / Slides

    ...