11 ms·
Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
- dsimmons 4y agoIn some ways it's surprising that it took us so long to arrive here, but very exciting that things are moving in this direction nonetheless!
- anonymousDan 4y agoCan someone explain how they are actually implemented? How/where can I create a new DID?
- jceb81 4y agoDIDs support multiple storage mechanisms. Each storage mechanism defines how to create, read, write/update, and delete DIDs. Here's a list of the already implemented and published mechanisms: https://w3c.github.io/did-spec-registries/#did-methods https://w3c.github.io/did-spec-registries/#did-methods. They range from no storage (e.g. did:key, you derive the DID from a public key but can't change/update anything about that DID) to stored on a webserver (e.g. did:web) to stored on a blockchain (e.g. did:ethr). Often, a DID is created from a public/private key pair that is used to sign a transaction that's specific to the DID method. The DID then becomes publicly visible with the associated configuration, e.g. multiple key pairs associated with the DID, service endpoints that allow an interaction with the DID, etc.
- CMCDragonkai 4y agoWhere does one submit an method implementation?
- not_foobar 4y agoLook into sidetree protocol, I've seen a lot of people building on top of it. Link: https://identity.foundation/sidetree/spec/ https://identity.foundation/sidetree/spec/
- CMCDragonkai 4y agoIs there a place to register a new did method? What does sidetree have to do with W3C sidetree spec?
- jfk13 4y agoWorth recalling that some major concerns have been expressed about this stuff. See discussion a month ago: https://news.ycombinator.com/item?id=31939871 https://news.ycombinator.com/item?id=31939871
- bmn__ 4y agoand also https://news.ycombinator.com/item?id=28691422 https://news.ycombinator.com/item?id=28691422 https://news.ycombinator.com/item?id=27004098 https://news.ycombinator.com/item?id=27004098
- m33k44 4y agoThis relies on public-key cryptography? If that is the case, then who is responsible for maintaining the private key? If that responsibility is with the user, then what happens if the user loses the private key? Does the user loses the identity as well? Is there a way to recover that?
- k__ 4y agoweb3auth offers such a service.
- t_mann 4y agoThere'll surely be custodial services if this takes off.
- jceb81 4y agoIt depends on the DID method that you're using. The DID method is kind of the identity management system for Decentralized Identifiers. Many DID methods are based on blockchains and with that there are usually no recovery mechanisms for DIDs in place - if you lose your private key the identifier can't be updated and you can't prove ownership over the identifier anymore which in turn renders associated credentials (see Verifiable Credentials https://w3c.github.io/vc-data-model/ https://w3c.github.io/vc-data-model/) unusable. Custodial services are a good way out. Another option with DIDs is that you can add more than one key to DID. This way you can have one key that is stored away somewhere safe and is only used for recovery purposes.
- ivan_gammel 4y agoThis reminds me of web service/UDDI registries, that were supposed to come, and all the WS buzz in early 2000s. Some of them came indeed only to be shut down in a few years.
- radicalbyte 4y agoThat's exactly the same comparison I've been making regards the W3C VC and DID specifications - we're basically repeating the bad parts of the WS specifications.
- sylvain_kerkour 4y agoHere is a link to the spec for those who, like me, found weird that it was missing from the announcement: https://www.w3.org/TR/did-core/ https://www.w3.org/TR/did-core/
- jfk13 4y agoInteresting that the announcement includes long lists of "testimonials" from W3C members and from "industry", but there are some glaring omissions. Why no endorsement from Apple, Microsoft, Google, or Mozilla? Even smaller players like Opera and Brave are missing.
- detaro 4y agoGoogle and Mozilla objected: https://www.w3.org/2022/06/DIDRecommendationDecision.html https://www.w3.org/2022/06/DIDRecommendationDecision.html
- Geee 4y agoGoogle is not very surprising, because they're probably the largest issuer of centralized identities. DIDs eat their core business.
- deleted 4y ago[deleted]
- merb 4y agowell google did not outright reject, they said, it's not complete and the final should wait until the methods are implemented and used in practice (like most stuff is done nowadays)
- PretzelPirate 4y agoIt is confusing because Microsoft works on Decentralized Identity and would almost certainly have wanted to be involved with this.
- jceb81 4y agoMicrosoft already has their own Decentralized Identity products in place. Check out https://www.microsoft.com/en-us/security/business/solutions/decentralized-identity https://www.microsoft.com/en-us/security/business/solutions/... They are and were also actively involved in the creation of standards and tooling, e.g. the did:ion sidetree-based DID method was created by them.
- cplli 4y agoI was initially pretty hyped when I read the abstract for DIDs, bookmarked the spec and read it later. The "spec" is a bunch of buzzwords and vague generic "concepts". The DIDs themselves mean basically nothing, it's the "methods" that actually must have their own specification and actually "do something". Another feeling you can quickly get from DIDs is that they're blockchain centric. The entire concept is "jack of all trades, master of none". I actually hope to be wrong, and see some more fully fledged implementations/examples of real world use-cases, because I love the idea of federated/decentralized identity.
- jceb81 4y agoMicrosoft has already lined up the tech in their products. So I'm confident that it's just a matter of time before it becomes available in a shop nearby.
- oofbey 4y agoMS has a habit lately of backing lots of standard proposals that fizzle and go nowhere.
- cplli 4y ago> lined up the tech in their products Link? Or an explanation as to what this means? > before it becomes available in a shop nearby Meaning what exactly? If you're saying Microsoft will implement DIDs, my question is, "Which of the 50+ methods?"
- jceb81 4y agoHere's the link: https://www.microsoft.com/en-us/security/business/solutions/decentralized-identity https://www.microsoft.com/en-us/security/business/solutions/... I haven't used their implementation yet but Microsoft initiated the did:ion method. I guess they'll support it :-D In general, the idea with DID methods is that you can support many methods without too much effort - for example the Universal Resolver implements already a good bunch: https://dev.uniresolver.io/ https://dev.uniresolver.io/ However, pointing in the direction of the many DID method implementations, I agree with you that they're confusing. Many people try their hands on implementing a new method. Most of the methods will not amount to much. I recommend focusing on simple methods like did:key or did:web to get started and high throughput methods like did:ion, did:elem, did:orb (all sidetree based) for production. did:ethr is also a good starting point for a public blockchain DID method that doesn't require a transaction to create the DID, i.e. no expenses required. did:ethr is also one of the oldest methods and can easily be used in existing Self-Sovereign Identity software solutions.
- gibsonf1 4y agoHere is a link to the Solid [1] DID method: https://solid.github.io/did-method-solid/ https://solid.github.io/did-method-solid/ [1] https://solidproject.org/ https://solidproject.org/
- missblit 4y ago> The Solid DID method specification is a specialisation of the Web DID method [DID-WEB] whereby write (create, update, delete) operations are more tightly specified. The Solid DID method is designed to be generic enough to be compatible with other Web-based systems which implement read and write operations using HTTP methods (RFC 7231). For this reason, we are considering whether to name the DID method did:https or did:rest or similar. From this paragraph it seems pretty messy that there's both did:web and did:solid. Is the idea that every random company under the sun writes their own slightly different did-url to https mapping? And that every user-agent implements all of them?
- boxslof 4y agoWhy not simply a uri with an uuid in it?
- k__ 4y agoMore flexibility. The did:peer: method, for example, encodes the did document directly in its URI.
- Loic 4y agoLike `data:text/plain;base64,SGVsbG8sIFdvcmxkIQ==`? I must be too old, I do not understand the interest of this stuff compared to controlling a domain.
- oofbey 4y agoYou need some public private key stuff to prove you own the uuid. Add in a PGP key and you’re pretty much done I think.
- gregmac 4y agoSo I've just scanned over this stuff, maybe someone can fill in some gaps for me. There's a list of DID methods "in development" [1]. Is this the list of methods, or is there a centralized registry, or are these just "known" methods? If there's a centralized registry -- then this isn't really "decentralized" is it? On top of that there's a land-grab that's already begun for the method names, and isn't that going to kill the spec? com, nft, object, web, are already registered by private orgs. But if it's not centralized, then it's not unique. What stops me from making my own "verifiable registry" [2] for eg `did:nft:internet` which cryptographically proves I own the internet? "Ceramic Network" (the owner of "nft" on the w3c site) says they own it in their registry .. but who's correct? [1] https://w3c.github.io/did-spec-registries/#did-methods https://w3c.github.io/did-spec-registries/#did-methods [2] https://www.w3.org/TR/did-core/#dfn-verifiable-data-registry https://www.w3.org/TR/did-core/#dfn-verifiable-data-registry
- radicalbyte 4y agoThat's the list of methods; and yes, there is very much a land grab going on right now. No, there's nothing stopping you making your own methods. But will anyone actually use it?
- oofbey 4y agoSo if I’m building a service that lets somebody login with a DID, and I’m using a DID library to verify your authN then that library needs a different code block for every one of those methods?? LOL. What could possibly go wrong? Or less sarcastically, how could this possibly be expected to work?
- cratermoon 4y agoYeah DID is a dumpster fire. It's a consulting company's dream spec. Anything is possible but almost nothing is required. It smells a bit like SAML all over again, wherein they try to satisfy every stakeholder and end up satisfying none.
- 4y ago
- deleted 4y ago[deleted]
- high_5 4y agoI guess I'll be able to drop LDAP when LDID will be introduced.
- k__ 4y agoYou will even be able to drop "in" did:ldap: if you want.
- nabla9 4y agoThe only required property in a DID document is id, so that is the only statement guaranteed to be in a DID document. DID is little more than list of defined names and their intended usage. It's not automatically bad, but it's just a skeleton without any meat. In some sense, DID is pre-emptive standard template. If new identity protocols write their standard to be convertible to DID, then they end up having systems that can interact (after some testing) if when their methods intersect.
- vorpalhex 4y agoFrom the snail DID: > Write out your DID document according to the data model in [DID-CORE]. Include properties from [DID-CORE], and any other metadata you deem suitable. You MAY type it out and print it onto your paper, you MAY hand write it in pen or pencil or crayon, you MAY use finger painting or cut out and glue small pieces of paper. Express yourself however you like. You SHOULD NOT use glitter or food.
- dakial1 4y agoI assume you'll have a cryptographic key to state that a DID belongs to you. But what happens if that key get lost/stolen? You lose all you online presence with no way to recover it?
- k__ 4y agoIf you use different keys for different purposes, then only one purpose is lost. Issuers of credentials can ensure that they have an experience date, so you can get a new cred issued with a new key, after the old is lost. Also, there are services that help to recover your key.
- naet 4y agoI wonder if this drives a schism in Google's Chrome implementation of W3C recommendations, given Google's objections to the spec. I feel like they already have shown a willingness to diverge from the specs and do what they feel is best, with a large number of experimental chrome features not included in w3c.
- nichochar 4y agoThe idea behind DIDs and VCs (verifiable credentials, that go along with did's to prove claims about an entity) is fantastic. Decentralize and normalize global IDs! Have ways to express data about them that contains the proof of ownership of the ID embedded. The issues are with the execution in my opinion: the spec is too complex, the did methods are not nearly mature enough / constrained enough (some don't even use PKI...), and verifiable credentials / presentations are hard to get going. For this to take off, they need to overcome a 3 sided market cold start (issuers, holders, controllers), with no clear monetization behind it. I hope it works but I'm guessing we're not quite there.
- ftlio 4y agoThere's still a lot to figure out in the space, and the blockchain adjacency always makes things feel like a land grab or first-mover obsessive. I don't think that much matters though. The majority of us will still keep our identity in centralized providers, but the real win is on the overhead of developers and the overall security model of identity on the web as the methods and registries get fleshed out. Something important to track is the OIDC-SIOP v2 spec [1]. As this gets adopted by libraries and services that people are already using to handle their auth, it becomes effectively easier to "turn on" self-custody of identities for your users. I imagine there will be a lot of different options in terms of methods and registries to choose to accept, and the centralized providers of today will probably have a large say in what methods and registries get accepted. Ultimately there are a lot of use cases enabled by deferring to the user for their identity and potentially other verifiable claims about themselves. The most obvious use case is phones using their secure elements to actually provide a password-less UX on the web while also allowing developers to skip dealing with user authentication. Less obvious (to most people) are things like verifying you own some NFT, or verifying that you have Bitcoin in some escrow so you're likely not a bot willing to get blacklisted on some platform. This is the step that's required to create the real land grab over semantic User space - where "JoeSchmoe" really is the one and only. [1] https://openid.net/specs/openid-connect-self-issued-v2-1_0.html https://openid.net/specs/openid-connect-self-issued-v2-1_0.h...
- lotw_dot_site 4y agoSo, I take it that the "decentralized" aspect of all this stuff really comes into play when all of the server hardware is surgically implanted into our limbs!
- dane-pgp 4y agoNo, the cloud systems still need to be there (to track when you are trying to use your identity), but they will rely on private keys that you can surgically implant in your limbs. In fact a more realistic (but symbolically equivalent) scenario is that you'll be expected to carry around a device with you at all times that is biometrically linked to your limbs, and auto-updates its code (and the EULA that you agreed to in perpetuity).
- docmechanic 4y ago"Whatsmore, DIDs have the unique property of enabling the controller to verify ownership of the DID using cryptography." Content-based identifiers (CIDS) for IPFS also verify content with cryptography, so not unique. CIDS are also decentralized. However, the following looks promising: * 4) DID metadata can be discovered (resolvable)."
- EVa5I7bHFq9mnYK 4y agoSo if you like something incorrect in Twitter, all your accounts in Google, Amazon and iPhone go dark simultaneously?
- alipitch 4y agoWhich did method supports rotation? did:key Not Supported did:web ??? Do only Proof-of-work methods (e.g. blockchains) support rotation? did:ion Are there no did method based on keybase like tech? https://www.w3.org/TR/2022/REC-did-core-20220719/#verification-method-rotation https://www.w3.org/TR/2022/REC-did-core-20220719/#verificati... 9.7 Verification Method Rotation Not all DID methods support verification method rotation. https://github.com/w3c-ccg/did-method-key/blob/f511ed730f7d2633ec136084bbc4c986f68483f0/index.html https://github.com/w3c-ccg/did-method-key/blob/f511ed730f7d2... The did:key Method v0.7 5.1 Key Rotation Not Supported This section is non-normative. https://github.com/w3c-ccg/did-method-web/blob/1b4225ffd9be0df84845e52017b4ee10f5aad472/index.html https://github.com/w3c-ccg/did-method-web/blob/1b4225ffd9be0... ??? https://lists.w3.org/Archives/Public/public-new-work/2021Sep/0000.html https://lists.w3.org/Archives/Public/public-new-work/2021Sep... * Proof-of-work methods (e.g. blockchains) are harmful for sustainability (s12y).
- geoah 4y agoKERI Supports rotation, check it out, it's pretty nice actually https://identity.foundation/keri/did_methods/ https://identity.foundation/keri/did_methods/