search

uport-project / ethr-did

Create ethr DIDs
Apache License 2.0
260 stars 54 forks source link

`did:eth:` vs `did:ethr:` in readme document #9

Closed canadaduane closed 6 years ago

canadaduane commented 6 years ago

In the example DID document, the DID id value is presented as

id:'did:eth:0xf3beac30c498d9e26865f34fcaa57dbb935b0d74',

However, later, in the DID method subsection, it directs users to prepend did:ethr: to an Ethereum address to create a DID under this schema.

Are these in conflict (did:eth: vs did:ethr:)? If so, which is the correct DID method?

localredhead commented 6 years ago

Good catch! The correct DID method for this is did:ethr. I've updated the example in the documentation https://github.com/uport-project/ethr-did/commit/27ced502b76827961558a89175f8044ef69d2ab7

Where the eth:did comes from is for a different DID-resolver that does not support key management called eth-did-resolver as opposed to ethr-did-resolver.

Check out github.com/uport-project/eth-did-resolver for more information on the did:eth method.

canadaduane commented 6 years ago

Ok, thanks for the clarification! I'm still a little confused now, however. Are there two completely different Ethereum-based DID specs, one with did:eth: and one with did:ethr:?

Also, and I think this was just a mistake in your message, but is there also an eth:did?