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.
...
- Timo Glastra <timo@animo.id>
- Philippe Foucault (Gouvernement du Québec) <philippe.foucault@mcn.gouv.qc.ca>
Status updates
- Aries Bifold (Aries Bifold User Group Meetings)
- Aries Call
- Hyperledger moved to Discord
- Replaces rocket.chat
- https://discord.gg/N84Eg4z3
...
- Record the meeting
- Non-Indy ledger support finding the correct approach (Sai Ranjit Tummalapalli)
- OOB/DID-exchange
- 0.2.0 release of AFJ
- Target release date march 15th. Can we make it? What are the bottlenecks?
- Target date to have everything merged by March 15th
- https://github.com/hyperledger/aries-framework-javascript/discussions/622
- Done:
- In Review:
- Add support for 0453: Issue Credential v2
- Add support for RFC 0183 Revocation Notification Protocol
- Support only v2?
- ACA-Py has not implemented v1 according to the RFC
- The AFJ PR conforms to the ACA-Py implementation, not the RFC
- In Progress:
- Add support for RFC 0023: DID Exchange
- Add support for RFC 0434: Out-of-Band
- Current changes are mainly about refactoring
- Update the old connection invitation to the new OOB invitation
- Add support for 0454: Present Proof v2
- Implementation is complete
- v1 tests are complete
- Working on v2 tests
- Adopt RFC 0592: Indy Attachment Format
- Issuer side done as part of Issue Credential v2 PR
- Verifier side will be done as part of Present Proof v2 PR
- Need strategy for handling breaking changes in storage records
- Logic in place to import/export wallets for NodeJS, React Native WIP
- Logic in place to apply the needed upgrades
- Will need some time to add migration scripts for the breaking changes introduced after the respective PRs are merged
- Let Timo Glastrawhich fields have changed.
- Unable to accept credential offer as of 0.2.0-alpha.20
- Storing revocation status in CredentialRecord
- Fabric Support (Harsh Multani)
- Ongoing work
- Issue Credential V2
- Present Proof v2
- Revocation
- OOB / DIDExchange (routing keys, roles and states, get rid of did doc and verkey)
- Shared Components
- Open PRs
- AMA
...