2023-08-21 AnonCreds v2.0 Working Group Meeting

Summary

AnonCreds v1.0 Spec PRs – Cryptographic Elements
Open Discussion

Recording of Call:

Notices:

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.

Meeting Attendees

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

Related Repositories:

Mike Lodder's proposed Data Models: https://hackmd.io/ZlsnLoclSveePJOZljgMfA
AnonCreds v2.0 Specification Repository: https://github.com/hyperledger/anoncreds-spec-v2/
AnonCreds v1.0 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

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.

Meeting Preliminaries:

Welcome and Introductions
Announcements:
Updates to the Agenda?
- Patrik: Revocation lists in Anoncreds spec
  - revocation lists in relation to indy "from, to" intervals
  - Anoncreds registry specification for indy
  - Anoncreds 2.0 revocation

Agenda

PRs from AnonCreds v1.0 Spec.
Open Discussion

Future Calls

Collect some use case specific examples and continue the discussions:
- 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?

To Dos:

Schema Claim Type:

Would it make sense defining encodings for date related schema claim types that are especially useful to use in ZKP predicates?
- "iso860_date" – encodes to dateint e.g., 2023.06.26 is 20230626
- "iso860_datetime" - encodes to Unix Time e.g., seconds since Jan 1, 1970
Yes – these would be "numbers" by type, but with special encoding handling.