2024-08-12 AnonCreds Working Group Meeting

This specification creating group operates under the Linux Foundation Community Specification License v1.0.

cifi	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

cifi	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

• @Stephen Curran (BC Gov / Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

• AnonCreds v1.0:

  • The v1.0 specification is published here: https://hyperledger.github.io/anoncreds-spec/

  • The Working Group uses this GitHub repository to manage the specification: https://github.com/hyperledger/anoncreds-spec

  • The AnonCreds Methods Registry: https://hyperledger.github.io/anoncreds-methods-registry

  • The v1.0 implementation in Rust is here: https://github.com/hyperledger/anoncreds-rs

  • The v1.0 implementation is dependent on this Rust CL Signatures implementation: https://github.com/hyperledger/anoncreds-clsignatures-rs

• AnonCreds v2.0

  • The initial framework for the v2.0 specification repository is here: https://github.com/hyperledger/anoncreds-spec-v2

  • The v2.0 implementation in Rust is here: https://github.com/hyperledger/anoncreds-v2-rs

  • Underlying AnonCreds v2.0 are cryptographic libraries in Hyperledger Labs Agora

• Welcome and Introductions

• Announcements:

• Any updates to the Agenda?

• Proposal from Dfinity / Google / Jan Camenisch for using ZKPs with Hardware Keys

  • Follows:

    • Feedback from Cryptographers on the European ARF

      • GitHub Issue: https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/issues/66

      • Paper: https://github.com/user-attachments/files/15904122/cryptographers-feedback.pdf 

      • Proposal: EUDI_Follow_up-2.pdf

    • ECDSA proposal – early days. Start of an academic paper. – EUDI___Generic_ZK___ECDSA_Proposal.pdf. The work is based on Ligaro (Ames, Ishai, Hazay, Venkitasubramaniam).

      • Must go through all the rigour, and then through standardization.

      • Digital Bazaar objects because it lacks a pseudonymous identifier for the credential – same complaint it had about AnonCreds back in the day.

      • Push for BBS to be reviewed by Cryptographers.

• Status updates from current work:

  • Revocation Manager for ALLOSAUR Project – Hyperledger Mentorship project being executed by @VictorH2208Project plan

  • BBS Signatures

  • Audit Updates from Mike Lodder: 

    • blsful - audit complete and published in Agora

    • Audit complete: Genaro to be contributed

    • Audit Complete: verifiable-secret-sharing – some changes, and some ripple affects, such as to Genaro.

• AnonCreds Project Charter:

  • Stems from the recent "intent to form" announcement from the Linux Foundation and Hyperledger Foundation about LF Decentralized Trust.

  • Proposed Charter: https://docs.google.com/document/d/1UiUv2H_xOHxV_rXfTSlsPu2TdQjgxNlVhU67RtqbMlM/edit?usp=sharing

  • Plan:

    • Create an "anoncreds" repo, similar to this Aries repo.

    • Put into it a "TSC.md" file that lists the TSC members and processes – same as this TSC.md in Aries.

    • Put into it a "MAINTAINERS.md" that points to the Hyperledger "access-control.yaml" file and processes of Maintainers – same as this MAINTAINERS.md in Aries.

    • Put a "MAINTAINERS.md" (like this one) file in all repos that points to the "access-control.yaml" file and to the AnonCreds repo MAINTAINERS.md ^^^^^^

    • Update the charter to match roughly what is in the Aries Charter

• PQ Efforts for Revocation

  • PQ equivalent to ALLOSAUR – fast, scalable, unlimited.

  • Research – very fast set membership for both lattice and elliptic curves (need not be pairing friendly).

    • Tweak to bullet proofs.

    • As high as: 2^38 memberships – pre-allocated – but can be a smaller set.

    • Less than 1 sec. to make proof, less than 1 sec. to verify.

• Open Discussion