Add SD-JWT selective disclosure guidance for credential privacy#40
Open
chongkan wants to merge 1 commit into
Open
Add SD-JWT selective disclosure guidance for credential privacy#40chongkan wants to merge 1 commit into
chongkan wants to merge 1 commit into
Conversation
New subsection under Security & Privacy: - SD-JWT as recommended credential format for did:pkh holders - Key Binding algorithm table per network (ES256K, EdDSA) - Credential flow: issuance → storage → presentation → verification - Correlation mitigation via alsoKnownAs to pairwise-capable methods Addresses w3c-ccg#38 Signed-off-by: Eduardo Chongkan <e.chongkan@gmail.com>
TallTed
reviewed
Mar 16, 2026
|
|
||
| Some implementations might utlize a key derivation function, e.g., when | ||
| converting from an ed25519 public key to a Curve25519 ECDH key, used in the | ||
| Some implementations might utlize a key derivation function, e.g., when |
Contributor
There was a problem hiding this comment.
Suggested change
| Some implementations might utlize a key derivation function, e.g., when | |
| Some implementations might use a key derivation function, e.g., when |
TallTed
reviewed
Mar 16, 2026
Comment on lines
+241
to
243
| pkh implementations). It is expected that this is a relatively safe operation, | ||
| but implementers might consider that there exists no mathematical proof that | ||
| confirms this assumption. |
Contributor
There was a problem hiding this comment.
Suggested change
| pkh implementations). It is expected that this is a relatively safe operation, | |
| but implementers might consider that there exists no mathematical proof that | |
| confirms this assumption. | |
| pkh implementations). This operation is expected to be relatively safe, | |
| but implementers might consider that there exists no mathematical proof that | |
| confirms this expectation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds credential privacy guidance to the Security & Privacy Considerations section.
Why this matters for did:pkh
did:pkh identifiers are blockchain addresses — inherently public and correlatable. The spec currently has no guidance on how to handle credential privacy. SD-JWT is chain-agnostic and the Key Binding algorithms map directly to the verification method types already defined in the Networks table.
Related: #38 | W3C tracking
Signed-off-by: Eduardo Chongkan e.chongkan@gmail.com