Skip to content

Universal Resolver has no way to provide Resolution Options #476

@wip-abramson

Description

@wip-abramson

Per the DID Resolver spec, the resolver should take in a DID and a set of resolutionOptions. I couldnt see a way to provide these options currently to the universal resolver.

I was just playing around with did:key and wondering why some resolver to JsonWebKey and others to keys like Ed25519VerificationKey. How is the universal resolver deciding what format to represent the keys?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions