The did-ethr resolver works great on etherium address DIDs (ones whose hex string is 40 chars long), but returns with invalidDid for public key hex DIDs (ones whose hex string is 66 chars long). The spec that it (
) references is
https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md -- partial support wouldn't necessarily be a problem, except that I'm unable to override the resolver (I'm using
didkit-cli or equivalently
didkit-http) to use a custom DID resolver for did:ethr (such as universal resolver).
I think this ticket belongs to both ssi and didkit repos, since there are resolution paths for both of them. Though obviously the better solution is to have ssi support the whole did:ethr spec.
The did-ethr resolver works great on etherium address DIDs (ones whose hex string is 40 chars long), but returns with
invalidDidfor public key hex DIDs (ones whose hex string is 66 chars long). The spec that it (ssi/did-ethr/src/lib.rs
Line 27 in 6d82e3e
didkit-clior equivalentlydidkit-http) to use a custom DID resolver for did:ethr (such as universal resolver).I think this ticket belongs to both
ssianddidkitrepos, since there are resolution paths for both of them. Though obviously the better solution is to havessisupport the whole did:ethr spec.