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.

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

[proposal] forward DID resolution options to the DID resolver when creating or verifying credentials #1343

Closed
mirceanis opened this issue Feb 22, 2024 · 0 comments · Fixed by #1344
Labels
enhancement New feature or request pinned don't close this just for being stale

Comments

@mirceanis
Copy link
Member

Is your feature request related to a problem? Please describe.
Issuing and verifying credentials and presentations relies on calls to the DID resolver. This resolver can behave differently depending on some options provided to it.

Describe the solution you'd like
The arguments object for createVerifiableCredential() and similar methods should accept a resolutionOptions parameter so that the resolver behavior can be tweaked to suit certain constraints.

Describe alternatives you've considered
The alternative is to use highly customized resolvers with these options hardcoded which severely limits the general purpose use of Veramo instances created like that.

Additional context
Example: resolving an Ed25519 did:key results in a document containing Multikey or JsonWebKey2020 verification methods by default. However, Ed25519Signature2020 proofs require the issuer keys to be expressed as Ed25519VerificationKey2020.
Having such resolution options would allow did:key resolvers to return properly formatted documents using the publicKeyFormat tweak that can be used with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned don't close this just for being stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant