Daniel Buchner
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # DID C&C WG: Collaborating on ZKP Credential Schemes & Specifications Verifiable credentials use cryptography to strongly authenticate information shared between participants. There are many considerations when sharing information in the digital realm, which affect the privacy and security guarantees between the parties who exchange data. Some of these considerations include: 1. Eliminating tracability vectors from data exchanged between participants. 2. Enable participants to share only subsets or minimized derivatives of the data a credential contains. 3. Ensure that any status check and revocation mechanisms do not leak credential usage information. One way to limit information sharing and preserve privacy throughout the lifecycle of that information's use, is a set of cryptographic tools known as Zero-Knowledge Proofs (ZKPs). ZKPs allow participants to account for the issues listed above using cryptographic schemes that cut off tracking vectors, enable minimal disclosure of data, and ensure usage of credentials does not leave a trail third parties can observe to compromise user privacy. There are many ZKP schemes that have been developed over the years that can be used in decentralized identity systems, but few that have seen wide spread adoption. There is still a lot of work to be done to ensure the identity community is equipped with all the tools required to address a wide array of use cases, as well as specifications and libraries that ensure interoperability among various ZKP solutions. To that end, the DIF Claims & Credentials Working Group is starting a collaborative initiative to work on a range of ZKP solutions to address the credential use cases of DIF members, and the wider identity community. This includes: work on ZKP cryptographic schemes, specifications that ensure interop for credentials generated using different schemes, and the libraries and tooling to generate and validate credentials generated with different schemes. Two organizations have stepped up with contributions to kick-off this initiative: #### MATTR MATTR is committed to the community effort required to achieve a disruptive shift in digital identity technologies. We support the collective effort towards a more user-centric model that enhances user choice and privacy, and advocate that concepts like selective disclosure of information in digital interactions are essential to have at the forefront. One way selective disclosure is achievable that provides an array of unique benifets, is through the application of the branch of emerging cryptographic technologies known as "zero knowledge proofs". MATTR has been actively investing in the development of a performant multi-message digital signature scheme supporting selective reveal via "zero knowledge proofs". Our team has built on and contributed to work originating from the [Hyperledger Ursa](https://github.com/hyperledger/ursa) project, extending it to provide a solution compatible with [Verifiable Credentials](https://www.w3.org/TR/vc-data-model/). In the past month we have open sourced multiple repositories for the decentralized identity community to use and continue to develop. We are also currently seeking to standardize the digital signature scheme with a formal draft in progress. We are excited to participate in an effort with like-minded organisations who are committed to the continued development of work in this space. Relivant links - [JSONLD BBS Signature Specification](https://w3c-ccg.github.io/ldp-bbs2020/) - [JSONLD BBS Signature Implementation](https://github.com/mattrglobal/jsonld-signatures-bbs) - [BLS12-381 Key Pair](https://github.com/mattrglobal/bls12381-key-pair) - [BBS Signatures Implementation (WASM)](https://github.com/mattrglobal/bbs-signatures) - [BBS Signatures Implementation (Node)](https://github.com/mattrglobal/node-bbs-signatures) #### Microsoft Microsoft's decentralized identity team and Microsoft Research have been working on a SNARK-based ZKP scheme that is now in final draft stages. The white paper describing the scheme and the design of its cryptographic primitives will be shared by Daniel Buchner in a subsequent blog post. Microsoft will be contributing the paper in the coming days, and beginning work on an implementation of the scheme within the DIF C&C WG this summer. We encourage you to contribute to this effort, whether it be through the definition of use cases, code contributions, or work on specifications. It is critical that we equip the community with the tools to the preserve privacy and the personal safety of users in the digital realm. With this initiative, we hope to advance that cause, and we invite you to join us in doing so. ---- There are two problems with solely using digital signatures: the signature is a unique identifier that can be used to track the holder, and the signature IS the credential which when given to the verifier to validate, is a digital copy and can be used to impersonate the holder. Proof of knowledge of a signature allows a holder of a digital signature to present a proof of a valid signature instead of the signature itself. The verifier never sees the original signature preventing impersonation. ZKPs are also unlinkable i.e. one proof cannot be linked to another limiting correlatable information disclosure. Selective disclosure is a proof where only a subset of the information is shared instead of its entirety. In the context of verifiable credentials, they can be used to limit the number of claims shared with another party to those that are necessary to complete an interaction. For example, a government issued ID card may contain 10 claims about a subject like first name, surname, address, birth date, unique citizen ID, phone number, and others. One scenario may only need to know an address for delivery or a phone number and first name to begin an introduction. Selective disclosure would create a ZKP that only reveals those claims to the other party and all others will remain hidden. Luckily there are cryptographic primitives that support creating these proofs quickly and efficiently called short group signatures with efficient protocols. Camenisch-Lysyanskaya (CL), Boneh-Boyen-Shacum (BBS+), and Pointcheval-Saunders (PS) are 3 signatures that support signing multiple messages with one signature and creating the previously mentioned ZKPs. **TODO: Do we need to discuss how the signatures work?**

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully