...
- Ariel Gentile - 2060.io (a@2060.io)
- Timo Glastra - Animo Solutions (timo@animo.id)
- Karim Stekelenburg - Animo Solutions (karim@animo.id)
- Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>
- Artem Ivanov (DSR Corporation) <artem.ivanov@dsr-corporation.com>
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
- Moving to OWF
- Interest on moving Bifold as well and Askar. ACA-Py not yet but probably in a future
- Repositories to move:
- Aries JS Docs
- Aries Framework JS
- Aries Framework JS Extensions
- Pre-IIW F2F OWF event: https://www.eventbrite.com/e/openwallet-pre-iiw-developers-face-to-face-tickets-722252636077
- 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
- Splitting DIDComm in packages like:
- @afj/didcomm-base
- @afj/didcomm-credentials
- @afj/didcomm-proofs
- @afj/didcomm-mediation
- Storing messages? All state should be derived from message exchange
- DIDComm v2
- Discover Features V2 over DIDComm V2: https://github.com/hyperledger/aries-framework-javascript/pull/1576
- Basic Messages V2: https://github.com/hyperledger/aries-framework-javascript/pull/1546
- Credentials protocols V3: https://github.com/hyperledger/aries-framework-javascript/pull/1560
- Missing:
- DID Rotation
- Mediation / Pickup
- 0.4.2 release
- Add fix for https://github.com/hyperledger/aries-framework-javascript/issues/1587
- Fix in implicit invitations: https://github.com/hyperledger/aries-framework-javascript/pull/1592
- 0.5.0 release
- https://github.com/hyperledger/aries-framework-javascript/discussions/1525
- https://github.com/hyperledger/aries-framework-javascript/pull/1427
- Drop node 16 support
- Releasing new wrapper versions (for dropping support for Node 16)
- https://github.com/hyperledger/aries-askar/pull/179
- Need to update Indy VDR React Native wrapperProblem releasing Indy VDR wrapper. Hopefully fixed by: https://github.com/hyperledger/indy-vdr/issues/216
- Need to create AnonCreds version update PR
- Mark the indy-sdk as deprecated
- pull/222
- DIDComm V2 moved to 0.6.x
- Message repository updates?
- Does not support filtering by key/id
- delay the closing of the http session?
- Have a interface to override session closing handling? If not registered it will auto close if no response internally. Otherwise you get control over it
- could be solved using middleware?
- https://github.com/hyperledger/aries-framework-javascript/issues/97
- feels a bit hacky? Requires you to implement custom logic, but there's probably more people that need to solve this issue → accepting request based on implicit invitation from an agent without an endpoint
- DidRecord.metadata.allowImplicitInvitations = true
- config: { autoAcceptImplicitInvitationsForDids: ["did:web:mediator.animo.id"] }
- https://github.com/hyperledger/aries-framework-javascript/discussions/1525
Meeting Notes
- Moving to OWF - meeting notes from this week's Aries WG
- https://github.com/hyperledger/aries-framework-javascript/discussions/1586
- Org migrations should be done with a transfer of the repo
- maintains links & commit history
- Move is far better than a fork.
- Should discuss which components would be moved simultaneously
- Probably at least Bifold and Askar
- What to do with the RFCs?
- Interoperability: are .Net and Go implementations still interoperable with the latest RFCs and interop suite?
- .Net already moved to OWF
- OWF policy: maintainers are in charge of the repositories and decisions (same as in Hyperledger)
- AJF would probably be the most mature wallet framework, so OWF would have an incentive to promote and market it
...