Date
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.
Attendees
Status updates
- Issue credential protocol
- Issue credential merged
- Still needed:
- Start with credential proposal
- advanced threading
- validation of protocol state
- validate credential preview against actual credential
- Present proof protocol
- First PR for presentation request message opened
- AFJ ↔ React Native
- https://github.com/TimoGlastra/aries-mobile-agent-javascript
- Errors thrown by rn-indy-sdk do not match errors thrown by indy-sdk for NodeJS (https://github.com/AbsaOSS/rn-indy-sdk/issues/21)
- Started work on `@types/indy-sdk`
- DefinitelyType will be updated instantly, adding to indy-sdk repo limits us to their release cycle
- I hope this would also allow us to reuse the types for rn-indy-sdk
- https://github.com/TimoGlastra/DefinitelyTyped/tree/%40types/indy-sdk/types/indy-sdk
Agenda
- Record the meeting
- Show how to run various kind of framework tests
- Reiterate toJSON approach
- Inconsistencies between connection and issue credential implementations
- Auto accept credentials (+connections)
- More granular config? (Like ACA-Py with auto-accept-request / auto-accept-response)
- Currently when you accept the credential request, you accept the whole credential. No option to control every step of the protocol.
- How will this work with auto-accept credentials? https://github.com/hyperledger/aries-framework-javascript/issues/116
- Decide on logger library to use
- Create custom logger interface so library is abstracted away?
- https://github.com/hyperledger/aries-framework-javascript/issues/77
- Use new https://didcomm.org prefix for agent message types
- Reiterate possible approaches for `@types/indy-sdk`
Meeting Notes
Future topics
- State machines