Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve holder binding explanation #1604

Merged
merged 2 commits into from
Feb 27, 2024
Merged

Improve holder binding explanation #1604

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
303274a
improve holder binding explanation
chiarapaskulin Feb 27, 2024
a58a079
improve explanation
chiarapaskulin Feb 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/reference/services/credential-service.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,8 @@ The purpose of the "Create Offer" endpoint is to initiate interactive issuance a

By utilizing the "Create Offer" endpoint, the issuing party can initiate a request for the user's consent to issue a verifiable credential on their behalf. This interactive process ensures that the user actively participates in the credential issuance and has the opportunity to review and provide their consent before the credential is issued.

Furthermore, the "Create Offer" endpoint enables the issuing party to define and configure the holder binding properties of the credential. This means that the issued credential will be bound to the intended holder, making it non-transferable and restricted for use solely by the authorized holder.
Furthermore, the "Create Offer" endpoint enables the issuing party to define and configure the holder binding properties of the credential. This means that the issued VC will be bound to the intended holder, making it non-transferable and restricted for use solely by the authorized holder. When {{ field_ref("CreateCredentialOfferRequest", "holder_binding") }} is set to true, upon acceptance of the credential offer, the resulting VC will have `credentialSubject.id` set to the holder's wallet DID. Otherwise, it defaults to a static value `urn:vc:subject:0`. During proof creation, if the VC includes a holder DID within the `credentialSubject` field, the resulting proof will also include a _proof of ownership_ associated with the holder DID. This serves to authenticate to the verifier that the presenter of the proof indeed possesses the DID designated by the issuer within the `credentialSubject` field of the credential.


{{ proto_sample_start() }}
=== "TypeScript"
Expand Down
Loading