fix(did-provider-key): align did:key resolver to spec #1332
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.
What issue is this PR fixing
fixes #1330
What is being changed
The did:key resolver implementations imported from transmute resolved to outdated Verification method formats.
This PR replaces those dependencies with a local implementation that also adheres better to the spec for defaults and behavior.
The verification methods default to
JsonWebKey2020
, unless otherwise specified through theoptions.publicKeyFormat
parameter.This implementation also supports
options.enableEncryptionKeyDerivation
, defaulting totrue
, that triggers the expression of the corresponding X25519keyAgreement
key for an Ed25519 public key.This implementation supports
Ed25519
,X25519
,Secp256k1
, andP-256
key types for did:key.Quality
Check all that apply:
pnpm i
,pnpm build
,pnpm test
,pnpm test:browser
locally.Notes
This PR is based on #1331, as changing the default verification methods in did:key triggers the corner case signaled in #1329 and fixed in #1331