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

  • Aries Bifold (Aries Bifold User Group Meetings)
  • Aries Call
  • Animo has won eSSIF Lab Grant to build Aries Mobile SDK - 
    • AIP 2.0
    • BBS+, JSON-LD
    • Shared components (Aries Askar, Indy CredX, Indy VDR)

Agenda

  • Record the meeting
  • Hyperledger moved to Discord
  • Hyperledger Fabric (Harsh Multani)
  • License headers (Timo Glastra)
    • Sign-off / PGP signature
  • Shared Components libraries (Berend Sliedrecht)
    • Three packages
      • Shared library for typing and utils method
      • Separate Node and React Native package
    • Having three static libraries increases the bundle size quite a lot
      • Possible to create a single binary to decrease bundle size?
    • React Native packages are focused on React Native
    • TS → C++ → libindyvdr
      • Not using a Swift / Kotlin wrapper
  • Wallet Storage and querying (Mike Richardson)
  • AyanWorks contributions 
    • sidetree protocol for non-indy ledgers
      • still looking into which did methods
    • DIDComm v2
  • Ongoing work
    • Issue Credential V2
    • Present Proof v2
      • Where to locate e2e tests?
        • option: locate in module / protocol directory. Indicate test is e2e test using .e2e.test.ts
        • locating tests in the protocol directory makes it easy to run tests for a specific protocol version
    • Revocation
      • Revocation has been merged into main, tests for holder are passing in AATH with ACA-Py
    • OOB / DIDExchange (routing keys, roles and states, get rid of did doc and verkey) 
    • Shared Components
  • BBS+ work 
  • Open PRs
  • AMA

Meeting Notes

Future topics

  • React Native testing
  • Support for Deno
  • Monorepo dependencies
    • TypeScript types



Meeting recording:

video1885108435.mp4

  File Modified
Multimedia File video1885108435.mp4 Feb 21, 2022 by Timo Glastra