W3C home > Mailing lists > Public > public-credentials@w3.org > November 2019

Re: Proposed work item: did:key DID Method

From: Lucas Tétreault <lucas@vivvo.com>
Date: Sat, 23 Nov 2019 17:48:36 +0000
To: Orie Steele <orie@transmute.industries>, Manu Sporny <msporny@digitalbazaar.com>
CC: W3C Credentials CG <public-credentials@w3.org>
Message-ID: <YT1PR01MB38653803A89D4C059970194CAD480@YT1PR01MB3865.CANPRD01.PROD.OUTLOOK.COM>
Thanks for the link to the comparison.

Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Orie Steele <orie@transmute.industries>
Sent: Saturday, November 23, 2019 10:57:25 AM
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: W3C Credentials CG <public-credentials@w3.org>
Subject: Re: Proposed work item: did:key DID Method

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





[https://mailfoogae.appspot.com/t?sender=ab3JpZUB0cmFuc211dGUuaW5kdXN0cmllcw%3D%3D&type=zerocontent&guid=25bea378-f85b-45c7-b4ed-faa228d8f280]ᐧ

On Sat, Nov 23, 2019 at 10:29 AM Manu Sporny <msporny@digitalbazaar.com<mailto: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://drive.google.com/a/transmute.industries/uc?id=1hbftCJoB5KdeV_kzj4eeyS28V3zS9d9c&export=download]<https://www.transmute.industries>
Received on Saturday, 23 November 2019 17:48:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:19:03 UTC