Closed ydennisy closed 6 years ago
Hey @ydennisy we are planning on adding this soon. Take a look at our generic did resolver: https://github.com/uport-project/did-resolver/
Can you elaborate what you mean by a http api?
Thanks @oed the resolver looks top notch!
By HTTP API, I mean some basic endpoints such as /registerDid
and /updateDid
that one can make GET
calls to create/update uport DIDs?
@ydennisy ok, creating a HTTP api like that is not entirely trivial since there is a cost in ether for each created DID.
@oed ok, so you mean there would need to be auth and payment mechanism built in?
Is this not the same issue with the SDK approach?
@oed happy to close this question, but could you share some details on when you plan to expose DID method usage to other devs?
@localredhead @ajunge @mirceanis Maybe you can provide some clarity here?
@ydennisy You can already do so today, by creating an ethereum address and registering it like this: https://github.com/uport-project/specs/blob/develop/pki/index.md
As we become fully DID spec compliant in our App over the next month we will be launching a few simpler methods, to make it easier for devs to create their own identities in their apps.
@ydennisy We have a new DID method that we will be rolling out in the app soon. Here is a library that will allow you to create and use the DIDs yourself https://github.com/uport-project/ethr-did
Feel free to re-open if you have more questions.
Thanks!
Hello! Is the uport-connect module using W3C DID methods? I can see a reserved namespace https://w3c-ccg.github.io/did-method-registry/ If the answer is yes, do you plan to expose a HTTP API to create, access these DIDs on ethereum?