Versions Compared

Old Version 4

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

Excerpt
  • Proposed AnonCreds v2.0 Data Models - Presentation - Mike Lodder
  • Open Discussion

Recording of Call:   dummyfile.txt

Segment – Awesome Presentation by Mike Lodder: dummyfile.txt

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>

...

  • Mike Lodder will continue a discussion of the Data Models he is proposing for AnonCreds v2.0, this time talking about Presentations
    • Data Models HackMD document:  https://hackmd.io/ZlsnLoclSveePJOZljgMfA
    • Notes from Meeting:
      • Contents of the Issued Credential – easily mapped into other formats, such as the W3C VC Data Model.
        • Open question on where encoding occurs – within AnonCreds (better interoperability, less data to store, more computation) or by the Issuer.
      • PresentationSchema
        • A possibly published data structure used by the Verifier to ask for data from the Holder.
        • Atomic – when requested, a Proof based on a PresentationSchema is either proven or not.
        • Can use something like DIF Presentation exchange to AND/OR a set of PresentationSchemas in to a Presentation Request – plus adding an ID and a nonce.
        • Different types of proofs were covered – from plain signatures to range-proofs.
        • Different crypto can be used.
      • From Chat:
        • Is bulletproof more efficient than schnorr proofs?
          • Different purposes – Schnorr: Prove you know the hidden value, Bullet: Proof hidden value is in range.
        • Discussion of revocation scalability – details to be covered in a future meeting.
  • Plans for IIW?
  • Next Meeting (two weeks):
    • Suspension vs./as well as revocation?
    • 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?
    • ALLOSAUR Revocation

...