Summary
- AnonCreds in W3C Format - Status Update / Issues
- AnonCreds 0.2.0 Release – contents
- AnonCreds Release 1.0.0
- AnonCreds v2 Objects – verifiable encryption, equality proofs and domain proofs
- Open Discussion
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.
cifi | 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 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:
- AnonCreds annual review at the ToC – this Thursday, February 15th – Meeting Notice
- Workshop Weds 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 Format - Status/Updates
- Test Vectors Repo: https://github.com/TimoGlastra/anoncreds-w3c-test-vectors
- Attachment Format to use for Present Proof will be DIF Presentation Exchange - Aries RFC 0510
- ACA-Py work design document in repo
- AnonCreds RS PRs
- Recent updates to AnonCreds RS – 0.2.0 release
- AnonCreds v1.0 1.0.0
- AnonCreds V2 ZKP Capabilities
- How does Verifiable Encryption work?
- Issuer setup – anything? Encoding types?
- Issue process
- Holder/Verifier presentation request / presentation
- Decryption process
- Equality proofs – claims across two source verifiable credentials
- Presentation schema – two schema, two IDs, reference in one to the other ID?
- Domain proofs – consistent identifiers for a verifier – different across different verifiers
- Issuer setup?
- Issue process?
- Verifier presentation request?
- Holder presentation process
- How does Verifiable Encryption work?
- Claim Schema format
- Default encoding if no other information? E.g. if just the name is given.
- Dynamic encoding using AnonCreds v1 rules? Notably: "If integer or integerString, then integer, else stringified and hashed"
- link_secret automatically added as in AnonCreds v1?
- Externalized set for list of set members
- Date as ISO Date and encoded as Integer Date
- DateTime as ISO Date and encoded as Unix Time
- Research – what can be derived from JSON-LD information?
- Default encoding if no other information? E.g. if just the name is given.
- Open Discussion
To Dos:
Action items
- Links to be referenced in the spec and used where needed: