Summary
- Reviewing the proposed data models for AnonCreds v2.0 - https://hackmd.io/ZlsnLoclSveePJOZljgMfA
- Revocation using zk-SAM
- 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:
- AnonCreds Workshop presented by Hyperledger is planned for May 31, 2023, 8:00 Pacific / 17:00 Central Europe. Details to be shared.
- I'll be talking at the Linux Foundation Open Source Summit, Metaverse Conference about Hyperledger AnonCreds and ZKPs.
- Updates to the Agenda?
Agenda
- Proposed data models discussion given what Mike Lodder has presented and documented here: https://hackmd.io/ZlsnLoclSveePJOZljgMfA
- Issuing AnonCreds v1.0:
- Schema – simple list of attribute names, schema name, version
- Attribute type is dynamically implied by the data in the credential – string or integer
- Credential Definition – a signing key for each attribute, an extra field that is the link secret
- Credential
- Raw and encoded claims
- Signature is added
- Schema – simple list of attribute names, schema name, version
- Issuing v2.0
- From document – items:
- Claims – Schema, Validators, Data
- Credential Schema, Credential Definition
- Credential
- Proposal that types are defined in the AnonCreds specification
- Credential Schema Object:
- Name, Description (should also have version?)
- Blindly Signed Claims
- Attribute name, type, validators
- link secret
- Claims
- Attribute name, type, validators
- Credential Definition
- Keys necessary to sign credentials
- Schema
- Revocation Registry
- Credential:
- Claims
- Signature
- Revocation Registry Handle
- Credential Definition ID
- From document – items:
- Signature Schemes
- CL
- BLS
- BBS+
- PS
- Issuing AnonCreds v1.0:
Future Calls
- Collect some use case specific examples and continue the discussions:
- Applying the data structures to a real use case or two
- What concrete uses other than link-secret is there for blinded data in a credential?