Page History

...

Recording of Call: 20230403 AnonCreds v2.0 Working Group Meeting Call Recording.mp4

Mike Lodder Presentation on ALLOSAUR Revocation: 20230403 AnonCreds v2.0 ALLOSAUR Revocation Overview - Mike Lodder.mp4

Mike Lodder Q&A on ALLOSAUR Revocation: 20230403 AnonCreds v2.0 ALLOSAUR Revocation Questions and Answers - Mike Lodder.mp4

Notices: 

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

...

• Mike Lodder  will continue the discussion of his proposal for AnonCreds v2.0, this time talking about the proposed ALLOSAUR accumulator/ZKP revocation scheme.
• Request: Support for Arrays and Nested data in AnonCreds – Kyle Robinson - Presentation: BC Digital Trust AnonCreds April 3 2023.pptx
  • Supported needed for arrays and nested data.
  • Suggestion is to use Data URLs (e.g., "data: application/json,...") – Aries RFC being posted Real Soon Now: 
    • Holder, verifier would at least know that the Attribute contained a string that was (in this case) JSON data, and could process it accordingly.
    • However – would lose ability to selectively disclose (all or nothing) or use predicates on such data.
    • Same approach is going to be used for images in attributes – "data: image/png,...")
• Plans for IIW?
• Next Meeting (two weeks):
  • ALLOSAUR Revocation 
  • Suspension vs./as well as revocation?Cancelled for IIW

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?

...