...
- Timo Glastra (Animo Solutions) <timo@animo.id>
- Simon Henriksen (Hyphen) <simon@hyphen.id>
- Alberto 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
- not necessarily needed to support in-between versions of Node.JS (odd numbers)
- 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
- DIDComm v2
...