2023-01-09 AnonCreds Specification Working Group Meeting

Owned by Stephen Curran
Last updated: Jan 09, 2023
2 min read

Summary

  • Several PRs
  • Revocation Interval
  • Update on prover_did?
  • Progress on the anoncreds_rs implementation
  • 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:

Meeting Preliminaries:

  • Welcome and Introductions
  • Announcements:
  • Updates the Agenda

Agenda

Open Issue

  • PRs for review and merging
  • Issues to Discuss
  • Any update on what "prover_did" is used for during AnonCreds processing?
    • Does the value require any special characteristics when it is used in the AnonCreds code?
    • Any insight on why it was added in the first place?
    • If we were to deprecate it as an input, would we need to use something else to replace it in the AnonCreds code?
  • Help with dependabot pull request: 113
  • Checkin: anoncreds-rs implementation progress, requests
  • Open Discussion

Future Calls

To Dos:

  • Issue to be added and further investigation into what happens to the nonce(s) by Belsy.
  • Backwards Compatibility
    • PRs in (#82, #105) that seem to change public data structures – ones that are handled outside of AnonCreds and/or by two or more participants (issuer, holder, verifier)
    • We want to retain compatibility with existing data – credentials that have been issued and the published AnonCreds objects on which they rely.
    • That extends to business logic – e.g. the handling of the objects not just by AnonCreds, AnonCreds Methods and Aries Frameworks, but also by business applications built on Aries.
    • Suggestion:
      • Include in the specification a statement about backward compatibility
        • Perhaps this is what Ankur had planned to do?
      • Formalize what data structures will be expected by AnonCreds
        • This is being done throughout the specification and verified against the current implementation.
      • As needed support sending and receiving data in "old" and "new" formats, but (for now) always sending "old" formats.
        • TBD if there are any such cases.

Action items