- From: Oliver Terbu <oliver.terbu@consensys.net>
- Date: Sat, 23 Nov 2019 18:05:20 +0100
- To: Orie Steele <orie@transmute.industries>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, W3C Credentials CG <public-credentials@w3.org>
- Message-ID: <CALu3yZ+wvKt0wyfwPPwGLgfyc94pTrxh+J_c2eACYPVbhUMqPA@mail.gmail.com>
`did:key` sounds very similar to `did:nacl` that was proposed by uPort. We have not registered the DID method in the DID method registry yet. If `did:key` starts as a new W3C Work Item, then I would be interested, although I hope that https://github.com/uport-project/nacl-did can be used as an input document. Oliver On Sat, Nov 23, 2019 at 5:58 PM Orie Steele <orie@transmute.industries> wrote: > I'm interested, I created a web resolver and demo website from the current > version of the driver for testing purposes: > > https://github.com/transmute-industries/did-key > > I had a question before the spec was available, regarding multibase as the > only encoding format for the DID. > > Is it true that there will always only be a single DID per public key? > > I was hoping that this work could be extended to support a DID Document > representation for cryptographic key types, as well as formats, such as PEM > / JWK, secp256k1, RSA, etc... but it would be the case that the same key > encoded in different ways would result in different documents. > > Regarding did:peer, this is clearly very different, it does not involve > storing of events ( > https://openssi.github.io/peer-did-method-spec/index.html#backing-storage), > you can see a comparison in the peer did spec: > > > https://openssi.github.io/peer-did-method-spec/index.html#did-key-and-did-nacl > > > > > ᐧ > > On Sat, Nov 23, 2019 at 10:29 AM Manu Sporny <msporny@digitalbazaar.com> > wrote: > >> Decentralized Identifiers (DIDs) are a new type of identifier for >> verifiable, decentralized digital identity. These new identifiers are >> designed to enable the controller of a DID to prove control over it and >> to be implemented independently of any centralized registry, identity >> provider, or certificate authority. These sorts of identifiers often >> utilize a heavy-weight registry, such as ones utilizing Decentralized >> Ledger Technologies (DLT), to create, read, update, and deactivate DIDs. >> >> This specification describes a non-registry based DID Method based on >> expanding a cryptographic public key into a DID Document. This approach >> provides the simplest possible implementation of a DID Method that is >> able to achieve many, but not all, of the benefits of utilizing DIDs. >> >> https://digitalbazaar.github.io/did-method-key/ >> >> At this time, we are seeking another implementer that is willing to >> collaborate on maturing this DID Method and be a co-sponsor/editor on >> the specification. >> >> The request to add this as a work item to the CCG is here: >> >> https://github.com/w3c-ccg/community/issues/98 >> >> -- manu >> >> -- >> Manu Sporny (skype: msporny, twitter: manusporny) >> Founder/CEO - Digital Bazaar, Inc. >> blog: Veres One Decentralized Identifier Blockchain Launches >> https://tinyurl.com/veres-one-launches >> >> > > -- > *ORIE STEELE* > Chief Technical Officer > www.transmute.industries > > <https://www.transmute.industries> >
Received on Saturday, 23 November 2019 17:05:34 UTC