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)
- Warren Gallagher (AffinitiQuest)<warren@affinitiquest.io>
- Karim Stekelenburg - Animo Solutions <karim@animo.id>
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
...
- Aries Bifold (Aries Bifold User Group Meetings)
- Integrating AFJ 0.4.0, lot of updates to follow (e.g. react native update)
- OCA package
- Aries Call 2023-02-08 Aries Working Group Call
- Discussion on Agents vs Wallets
- We have a phone, but the phones have a "Phone" app (in case of iOS)
- Purpose of a phone has expanded greatly, it is now a computer
- Too puristic on the naming
- Scalable Mediation - DocketSock
- Socket server separate from mediator agent
- Aries Interop Profile 3.0 continues to be discussed https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQ
...
- Record the meeting
- DIDComm v2 discussion
- DIDComm v2 crypto implemented using Aries Askar, Indy SDK not supported
- Wallet takes resolved DIDDocument for now (will be reworked as planned API refactor)
- No support for sessions, queue, or priority yet
- Supported protocols: OOB create invitation, trust ping send/receive
- Specify DIDComm version when creating an invitation
- did:peer:2 for p2p connections
- how do we want to handle connections?
- connection can be useful, but it can also be useful to be able to send a message to another connection
- are we conflating a contact with a connection?
- what if we receive a message from a did we've never seen before?
- configuration to allow/disallow certain messages? → simple default behaviour
- create dynamic connection?
- allow application layer to decide whether the message is accepted, or discard the message → more complex custom behaviour
- don't want junk in your connection list
- DIDComm v2 protocols for issuance / etc..
- issue: need to resolve our own did to send message
- Can it be used with AFGO mediator?
- Need to support mediator protocols as client as well: https://didcomm.org/mediator-coordination/2.0/
- Open Wallet Foundation
- Wallet API discussion continued
- Documentation and getting started – continued
- Revocation PR, other open issues/PRs
...
- 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.
- Extracting parts of AFJ into generic libraries
- Cheqd integration (Daev Mithran )
- AFJ Interop tests not running