Charles E. Lehner

I think this is fixed; @cobward can you confirm?

Hi @nichonien, Can you say more about what why you need the resolver options, e.g. what are the use cases? `resolver_options` ([ResolverOptions](https://docs.rs/didkit-cli/latest/didkit_cli/opts/struct.ResolverOptions.html)) in the CLI includes options to use a...

The module and its package.json are generated using [wasm-pack](https://github.com/rustwasm/wasm-pack). To set the relevant fields (license, repository, etc), looks like would need to be done manually or by a script running...

@prorohit this appears to be a duplicate of #276 and https://github.com/spruceid/credible/issues/97. Is there a different issue you are facing here?

Possible approach: Implement a `MemoizedDIDResolver` struct that wraps a `DIDResolver` object, and itself implements the `DIDResolver` trait. Any DIDKit operation involving resolving DIDs or dereferencing DID URLs should cache the...

Hi @prorohit, Do you have an error message or stack trace coming from a DIDKit function call?

@prorohit are you still encountering this issue? Does calling the `version` function work? Do you want to discuss this via a different channel?

@peacekeeper great. It appears that DIDKit's support for `did:key:zQ3s` (Secp256k1) and `did:key:zru` (P-256) would be novel. But these are not currently enabled in our Docker image... I am opening another...

Adding the driver, for `did:tz` and some `did:key` prefixes, is happening here: https://github.com/decentralized-identity/universal-resolver/pull/222. Enabling more DID resolvers from DIDKit can be done by updating the regex for the didkit driver's...

Universal Resolver driver using DIDKit (didkit-http), enabling `did:tz` and some `did:key` prefixes, is merged in https://github.com/decentralized-identity/universal-resolver/pull/224. Keeping this issue open though, to track enabling more of DIDKit's DID methods in...