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
- Timo Glastra <timo@animo.id>
- Philippe Foucault (Gouvernement du Québec) <philippe.foucault@mcn.gouv.qc.ca>
- Jason Leach <jason.leach@fullboar.ca>
- James Ebert <james.ebert@indicio.tech>
Status updates
- Aries Bifold (Aries Bifold User Group Meetings)
- Aries Call
- Hyperledger moved to Discord
- Replaces rocket.chat
- https://discord.gg/N84Eg4z3
Agenda
- Record the meeting
- Merging OOB / DIDExchange
- What's left? Who wants to help?
- Refactoring on `did:key`
- How to convert numalgo 2 did document to did
- Waiting on https://github.com/hyperledger/aries-rfcs/issues/728 to be resolved
- If we change the algorithm, previous dids don't match anymore
- Public api
- passing id instead of record
- add methods to manage oob records
- DIDExchange record state and Connection record state
- Handshake reuse
- James Ebert has done some work on handshake reuse, will create PR against oob branch
- What's left? Who wants to help?
- iOS Simulator issues (Akiff Manji)
- Question Answer Protocol (James Ebert)
- AMA
- How to handle the growing size of dependencies
- Selectively add dependencies (more lean core)?
- Slim agent by default.
- No credential formats supported by default
- Should be added using JSON-LD / Indy plugins
- No storage implementation
- should be added using Askar or Indy SDK
- Can help with multi-platform deployments
- Worry about having a gazillion afj packages
- JSON-LD vs Indy
- BBS vs Ed25519
- Shared components vs Indy SDK
- Selectively add dependencies (more lean core)?
Meeting Notes
Future topics
- DIDComm v2 support
- React Native testing
- Support for Deno
- Monorepo dependencies
- TypeScript types
Meeting recording: