2023-03-16 Aries Framework JS Meeting notes

Owned by Timo Glastra
Last updated: Mar 16, 2023 by Alexander Shenshin
3 min read

Meeting recording


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

Resources

Status updates

Agenda

  • Record the meeting
  • timezones / meeting time
  • Update on AFJ 0.4.0
    • Bifold e2e flow working now
    • requirement for android API 30+ (Android 11+) is only for indy-vdr
      • Bifold currently supports Android SDK 21+ (Android 5+) 
      • could use indy-vdr-proxy as an alternative (Ariel Gentile will give demo next week)
        • need to trust proxy
      • As of January 6th, 2023, Android Studio recommends targeting Android 7 (API 24) for 94.4% device coverage. Android 5 (API 21) gives 99.3% coverage
      • https://hackmd.io/@blueberi/Bk50yEyJh
    • AFJ 0.4.0
      • Bug fixing, last releases, finishing touches
      • migration scripts (mostly done)
  • Update on cheqd integration
    • Ask Daev to give a demo
  • DIF presentation exchange format
    • Timo Glastra will update with latest changes, look at what's missing
    • Mike Richardson demo of the presentation exchange flow (in 1/2 weeks)
  • prioritisation for 0.5.0
    • DIDComm v2
      • now that indy-sdk is gone, other libraries have DIDComm v2 support, main objective of AIP 3
      • Askar as backend for DIDComm v2? SICPA has implemented using didcomm v2 wasm library
      • support both libraries
    • Need to work on a new wallet api
      • focused on indy-sdk
      • still uses parameters for indy-sdk
      • way we are creating / opening the wallet is inherited from indy-sdk
    • Improving interfaces for message repository
      • fully support pickup v2 and v3 protocols
      • be a mediator without in memory message repository
    • Refactor basic message / trust ping to align with new way of doing things (support multiple versions of the protocol)
    • End user wallet perspective
      • key rotation
      • changing mediator
      • initialization, efficient way to check if the wallet key is valid

Meeting Notes

  • ...

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.