Versions Compared

Key

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

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.

...

  • Timo Glastra  (Animo Solutions) <timo@animo.id>
  • Simon Henriksen (Hyphen) <simon@hyphen.id>
  • Alberto Antonio Leon (Instnt, Inc.) <alberto@instnt.org>
  • Ariel Gentile (2060.io) <gentilester@gmail.com>
  • James Ebert (Indicio) <james.ebert@indicio.tech>
  • Alexander Shenshin (DSR Corporation) <alexander.shenshin@dsr-corporation.com>
  • Artem Ivanov
  • Aziz Karabashov
  • Berend Sliedrecht
  • Clecio Varjao
  • Esteban Velasquez
  • Gary de Beer
  • Kurt Milam
  • Lance Byrd
  • Mike Richardson
  • Mücahit KARSON
  • Renata Toktar
  • Rodolfo Miranda
  • Ry Jones
  • Saroj Basnet.
  • shehan pingamage

Resources

...

...

  • Record the meeting
  • new time for the meeting
  • github runners limitations
  • ??GitHub runners limitations
    • not necessarily needed to support in-between versions of Node.JS (odd numbers)
      • reduces ci resource usage
  • indy-vdr proxy
  • Continue the conversation about “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

Recording

https://youtu.be/94RafocD_9c

GMT20230323-130609_RecordingnewChat.txt

Future topics

Future Topics:

...