Page Comparison

Summary

...

Call Link: https://zoom.us/j/97954159540?pwd=WWk3WmQ3MVh1SXBYZGVreGl0QllGdz09

Recording:

...

Widget Connector
url http://youtube.com/watch?v=5-x_4GU6v_E

Notices: 

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

Meeting Attendees

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

...

• Welcome and Introductions
• Announcements:
  • Next Meeting – Monday, February 24 will be at this time – 7:00 Pacific / 16:00 Central Europe vs. the usual 15:00 Pacific / Midnight Central Europe time.
• Any updates to the Agenda?

...

• BBS Support for AnonCreds v2 
  • Other issues to go
  Webinar – topics
  • . – verify alignment with the IETF draft – documenting what options are used/not used, design choices) parallel tests – PS and BBS
• Webinar AnonCreds v2 and "AnonCredsBBS"
  • Draft Agenda:
    • AnonCreds v2 – introduction
    • Capabilities – ZKP features
    • Signature Scheme support – Pluggable, with BBS and PS Signatures implemented. Hint at PQ.
    • Details of the BBS Support – alignment with the IETF CFRG
    standards
    • draft (BBS Signatures, BBS Blind Signatures, BBS pseudonymous identifiers)
    • Scalable Revocation
    • Next Steps
  • Timing?  Mid-march
• Presentation and demo to conclude the Revocation Manager Project - a Hyperledger Mentorship Program project.
• The did:webvh AnonCreds Method – https://hackmd.io/9cQkOktoSSeXxRiU5eWtaA?both
  • Publishing, resolving and verifying AnonCreds objects for a did:webvh DID
  • Mostly easy: did:webvh:<scid>:example.com/AnonCreds/schema/<name/<version>/<hash>
    • Attested Resources – using the hash of the resource placed in the identifier, and an attached Data Integrity proof.
    • Resolvable Identifiers are put into objects:
      • Schema identifier in CredDef
      • CredDef identifier in Verifiable Credential and Verifiable Presentation.
      • RevReg identifier in Verifiable Credential
    • Tricky – RevRegEntry (state of RevReg) have associated timestamps, and have to be "discovered" by the Holder, with the timestamp conveyed to the Verifier.
    • Solution:
      • RevRegDef has an updated list of RevRegEntry [timestamp, identifier] pairs in the Attested Resource, but outside of the RevRegDef resource itself.
        • Hash of the RevRegDef is consistent.
        • Proof is update each time the list is extended.
      • RevRegEntry is "just another" Attested Resource
      • Holder gets RevRegDef and finds timestamp (and hence, the identifier) for a RevRegEntry useful to satisfy the Presentation Request.
      • Verifier gets RevRegDef and finds the timestamp (and the identifier) for the RevRegEntry used by the Holder in the Presentation.
      • Both resolve the RevRegEntry identifier selected to get the actual RevRegEntry state (`[timestamp, state of each verifiable credential, accumulator]`).
  • Spec PR has been created and will be published beside the did:webvh spec (https://identity.foundation/didwebvh/), added to the info site (https://didwebvh.info).
  • Reference to the spec will be added to the AnonCreds DID Methods Registry – https://hyperledger.github.io/anoncreds-methods-registry/
  • Mike's comment about Provenance Logs – link to spec: https://github.com/cryptidtech/provenance-specifications/blob/main/specifications/provenance-logs.md
• Open Discussion

To Dos:

Action items

...