You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a parent issue to discuss and note DID Resolver support efforts.
Our did_core crate is structured in a way to support new implementations for did method resolvers. Currently (18/9/24) we support resolvers for did:peer, did:sov & did:web, but we are looking to grow, allowing our rust consumers and other parts of the vcx codebase (e.g. aries protocol) to utilize a wider range of methods.
For all implementations, a crate should be created for that method, and DidResolvable should be implemented (see did:peer, did:sov & did:web) for examples.
This is a parent issue to discuss and note DID Resolver support efforts.
Our did_core crate is structured in a way to support new implementations for did method resolvers. Currently (18/9/24) we support resolvers for did:peer, did:sov & did:web, but we are looking to grow, allowing our rust consumers and other parts of the vcx codebase (e.g. aries protocol) to utilize a wider range of methods.
For all implementations, a crate should be created for that method, and
DidResolvable
should be implemented (see did:peer, did:sov & did:web) for examples.To be developed
DidResolvable
#1287 (we already have a crate for creating and managing did:keys, just need an explicit resolver, should be trivial)DidResolvable
#1290DidResolvable
#1291DidResolvable
#1292did:ethr
resolver #1066DidResolvable
#1300Under Investigation
The text was updated successfully, but these errors were encountered: