openid / openid/dchp

The credential response should be able to include either one digital presentation proof generated from one digital credential or several digital presentation proofs generated from multiple digital credentials

Open
#32 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
19
Forks
3
PR merge metrics
No merged PRs in 30d

Description

The credential response should be able to include either one digital presentation proof generated from one digital credential or several digital presentation proofs generated from multiple digital credentials

About ## 6. Credential Response

The binding to a public binding key present in a digital credential can be done in two ways:

a) each digital credential contains a different public binding key.
In that case, several digital signatures using the corresponding private binding key are associated with each digital presentation proof.

b) every digital credential contains a same public binding key.
In that case, a single digital signature using the corresponding private binding key is associated with the digital presentation proof.

Note: In both cases, to ensure the unlinkability property, each digital credential shall be used only once.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Section 6, “Credential Response,” and review how digital presentation proofs and binding signatures are currently defined. Determine how the response should represent one proof from one credential versus several proofs from multiple credentials, while preserving the stated unlinkability constraint. Done means the specification clearly supports both cases and explains the associated signature behavior.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.