Skip to content

Support did-resolver interface #89

@yannik2002

Description

@yannik2002

Hi,

I noticed that this package uses as a standalone resolveDID() API rather than implementing the did-resolver interface that other DID methods (like did:web, did:ethr) use.

Are there any technical reasons preventing compatability or was this an intentional design choice?

Thanks in advance for your insights!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions