2024-03-11 AnonCreds Working Group Meeting -- CANCELLED

Summary

Time: 7:00 Pacific / 16:00 Central Europe
Call Link: https://zoom.us/j/97954159540?pwd=WWk3WmQ3MVh1SXBYZGVreGl0QllGdz09

Recording: 

Notices: 

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

Meeting Attendees

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

Related Specifications and Repositories:

• 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

Meeting Preliminaries:

• Welcome and Introductions
• Announcements:
  • Workshop Wed. April 24th: Zero Knowledge Proofs and ZK Programming in Blockchain Application Development
  • IIW – April 16-18, 2024
• Any updates to the Agenda?

Agenda

• AnonCreds in W3C VCDM Format - Status/Updates
  • Test Vectors Repo: https://github.com/TimoGlastra/anoncreds-w3c-test-vectors
  • Credo / Bifold Progress:
    • PR is merged into Credo, 0.5.0 Alpha is available
    • Working on the Bifold – update agent to 0.5.0
  • ACA-Py Progress:
    • Progress and work on it.  Difficulty in getting tests to run.
    • ACA-Pug meeting tomorrow for a demo.
• Data organization in the AnonCreds v2 Presentation flow – presentation
  • For ZKPs in a presentation, make the "claim" item a complex data structure, with one or more ZKPs listed with type and value.
    • Consider how best to handle multiple of the same type – e.g. multiple memberships on the same claim
    • TBD: The exact data format for each type (predicate, range proof, membership, etc.)
  • Revocation to be "automatic" based on whether or not the issuer decides to issue a revocable or non-revocable credential.
    • TBD: the flow of that during issuance
    • TBD: What about the W3C VCDM concept of "credentialStatus" and the possiblity of multiple status types on a credential.
  • Link secret to be likewise automatic – in the schema, in the credential, and always disclosed in a presentation.
  • To Do: formalize the list.
• Pluggable Signatures in AnonCreds v2 – PR submitted/merged – commits pushed to get the PR accepted.
• AnonCreds Hyperledger Mentorship Program ideas – suggestion of ideas:
  • A "revocation manager" implementation that can receive sharded requests and send back responses.
  • BBS+ Implementation.
  • Rust coding to work on AnonCreds objects so that they can be published/spec'd.
  • Rust coding to do Post Quantum signatures -- a plugin to the existing library.
  • Other ideas?
• Open Discussion

To Dos:

Action items

• Links to be referenced in the spec and used where needed:
  
  • From Will Abramson : https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.186.5994&rep=rep1&type=pdf
  • From Will Abramson : https://github.com/hyperledger/indy-hipe/blob/c761c583b1e01c1e9d3ceda2b03b35336fdc8cc1/text/anoncreds-protocol/README.md