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.
...
- Aries Interop Profile 3.0 continues to be discussed https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQAnonCredsUrsa replacement with anoncreds-clsignatures-rs https://github.com/hyperledger/anoncreds-rs/pull/226A few changes in the API (tails file not required anymore for issuing/revoking credentials
Agenda
- Record the meeting
- DIDComm v2
- Supporting multiple versions of DIDComm WIP by Ariel Gentile
- 0.45.1 released0 release
- https://github.com/hyperledger/aries-framework-javascript/blob/main/CHANGELOG.md
- Project proposal:
Widget Connector url https://docs.google.com/document/d/1fja1pQvB6UJcJR7d00HaEDTk-WMUFS9SZNkle-jm2BE/edit#heading=h.ro1tvbkzavyy - Make AFJ compatible with ARF / EU Standards
- mDL
- OID4VC
- SD-JWT
- Secure enclave integration with Askar
- AnonCreds over OpenID4VC
- Get experimental SIOPv2 / OpenID4VP integrated based on implementation in Paradym WalletNeed to extract the openid4vc-client from here: discussions/1525
- Discussion: https://github.com/
- https://github.com/animo/paradym-wallet/tree/main/packages/openid4vc-client
- However this is dependant on a custom packed version of the oid4vc library from sphereon, based on this draft PR
- discussions/1539 Basic Message V2 protocol:
- pull/1427
- Drop node 16 support
- Releasing new wrapper versions (for dropping support for Node 16)framework-javascript1546Credential v3 protocols
- 179
- Need to update Indy VDR React Native wrapper: https://github.com/hyperledger/
- It is possible to merge without breaking changes?
- How to make protocols support both DIDComm V1 and V2 (e.g. Discover Features V2, Basic Messages V2)
- do we want to make it explicit or automatic?
- e.g. see migration script: https://github.com/decentralized-identity/didcomm-book/blob/main/docs/migratorscript.md
- Get it released in 0.5.0 with mediation
- Goal: move over to DIDComm v2 as soon as possible
- Need to create AnonCreds version update PR
- Mark the indy-sdk as deprecated
- DIDComm V2 moved to 0.6.x
- Message repository updates?
- Does not support filtering by key/id
- Keeping http socket open, when using implicit invitations0.5.0 release
- Separating the storage layer
- 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/
- 97
- Create a 0.4.1 first. To not introduce Breaking Changes, merge first:
- https://github.com/hyperledger/aries-framework-javascript/pull/1427
- https://github.com/hyperledger/aries-framework-javascript/pull/1542 (need a change to not break public field)
- Drop node 16 support
- Merge DIDComm V2 stufffeels 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
- Add option to auto accept requests to implicit invitations for certain dids?
- DidRecord.metadata.allowImplicitInvitations = true
- config: { autoAcceptImplicitInvitationsForDids: ["did:web:mediator.animo.id"] }
- Support ~timing decorator natively in AFJ
- 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
- Storing messages? All state should be derived from message exchange
Meeting Notes
Recording / Slides
...