2023-03-06 AnonCreds v2.0 Working Group Meeting

Summary

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

	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>

Steve McCown (Anonyome Labs) <smccown@anonyome.com>

AnonCreds Specification: https://hyperledger.github.io/anoncreds-spec/
AnonCreds Methods Registry: https://hyperledger.github.io/anoncreds-methods-registry
AnonCreds Rust Open Source Code: https://github.com/hyperledger/anoncreds-rs
- Ledger Agnostic AnonCreds Project Page: https://github.com/orgs/hyperledger/projects/16
Goals of the Working Group:
- The goal of AnonCreds v2.0 is to retain and extend the privacy-preserving features of AnonCreds v1.0, while improving capabilities, performance, extensibility, and security

Mike Lodder will lead a discussion on the Data Models he is proposing for AnonCreds v2.0
- Data Models HackMD document: https://hackmd.io/ZlsnLoclSveePJOZljgMfA
Notes from Meeting:
- Side topic: BARE – another binary data format comparable to CBOR
- Data Models introduced:
  - Claim Schema
  - Claim Validators
  - Claim Data
  - Credential Schema
  - Credential Definition
  - Revocation Registry
Next Week – one of these topics:
- Collect some examples and continue this discussion:
  - Applying the data structures to a real use case or two
    - Take an existing AnonCreds Schema (maybe this) and Credential Definition (maybe this) and define what it would be using Mike's proposed data models.
      - Where would the data models exist, such as on ledger, in the AnonCreds specification?
  - What concrete uses other than link-secret is there for blinded data in a credential?
- Continue on with Mike's data models to presentation.