Page Comparison

Meeting recording

...

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>

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

...

• Record the meeting
• new time for the meeting
• github GitHub runners limitations
  • not necessarily needed to support in-between versions of Node.JS (odd numbers)
    • reduces ci resource usage
• indy-vdr proxy
  • https://github.com/2060-io/aries-javascript-indy-vdr-proxy/tree/main/packages/server
  • https://github.com/hyperledger/indy-did-networks/issues/3
  • https://github.com/hyperledger/indy-did-method/issues/66
• 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

...