<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Danube Tech on Medium]]></title>
        <description><![CDATA[Stories by Danube Tech on Medium]]></description>
        <link>https://medium.com/@danubetech?source=rss-444f5bc4d6fa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*exJ0ZPRNdIwcz2XWqW06wQ.png</url>
            <title>Stories by Danube Tech on Medium</title>
            <link>https://medium.com/@danubetech?source=rss-444f5bc4d6fa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:39:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danubetech/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Power of DIDs #6: Unlock the Power of Decentralized Identity with our Stats API]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-6-unlock-the-power-of-decentralized-identity-with-godiddys-graphql-api-edb203fb9913?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/edb203fb9913</guid>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Wed, 08 May 2024 07:56:35 GMT</pubDate>
            <atom:updated>2024-05-22T07:37:30.495Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Discover valuable insights that can inform your strategies and drive innovation in the decentralized identity ecosystem. In this blog series, we will delve into all you need to know about DIDs. Today we focus on DID usage across various identity networks with our new Stats API.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGbsOssqHXu8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGbsOssqHXu8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGbsOssqHXu8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2adb09200a216a61482b3af55834dd3b/href">https://medium.com/media/2adb09200a216a61482b3af55834dd3b/href</a></iframe><h3>What is Godiddy?</h3><p><a href="https://godiddy.com/">Godiddy</a> is a powerful tool that empowers developers to perform various actions on DIDs across multiple identity networks. One of the features godiddy offers is its <a href="https://docs.godiddy.com/en/apis/version-service">Version Service</a>, which provides functionality for tracking and retrieving historical versions of DIDs, representing a unique source of information about DIDs and their corresponding DID documents. This valuable data source is now accessible through our <a href="https://www.notion.so/Graph-QL-eca4a4a335e54f8cbbbdf908d4ad7a5e?pvs=21">GraphQL</a> interface!</p><h3>Why GraphQL?</h3><p>We chose GraphQL for this API due to the vast variety of data pertaining to DIDs and the potential for complex queries. GraphQL allows us to provide access to the extensive Version Service data, with numerous parameters that enable you to tailor the response to match your needs precisely.</p><p>We immediately put the API to work: our statistical analysis dashboard, stats.godiddy.com, was refactored to use the new service. With fine-tuned queries, underfetching and overfetching became a thing of the (RESTful) past.</p><p>The data queried from <a href="http://graphql.godiddy.com/">graphql.godiddy.com</a>, with or without visual representations, can inform decision-makers about many different things. One of benefits our Stats API gives is current trends in the DID creation, update and deactivation, potentially predicting future movement. It also allows you to see what DIDs have a certain service endpoint in their DID Document, like DIDComm. More about that, later in this blog.</p><h3>How to Get Access</h3><p>To gain full access to <a href="http://graphql.godiddy.com/">graphql.godiddy.com</a>, sign up at <a href="http://godiddy.com/">godiddy.com</a>. You will receive your API key in the login email, which can also be found in your Dashboard.</p><p>Let’s explore some examples of queries and the responses we get. Visit <a href="http://graphql.godiddy.com/">graphql.godiddy.com</a> to follow along.</p><h3>Examples</h3><h4>Counting DIDs</h4><p>We can start by issuing a simple query to get the number of DIDs created with the method ebsi:</p><pre>query Query($method: String) {<br>  didCount(method: &quot;ebsi&quot;)<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;didCount&quot;: 804276<br>  }<br>}</pre><p>Similarly, for the cheqd method and testnet network we use the following query:</p><pre>query Query($method: String, $network: String) {<br>  didCount(method: &quot;cheqd&quot;, network: &quot;testnet&quot;)<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;didCount&quot;: 18176<br>  }<br>}</pre><h4>Querying DID Lists</h4><p>Counting DIDs is useful, but we can obtain more information by querying lists of DIDs that match our criteria. For example, if we want to see the DIDs with a DIDComm service endpoint and are interested in the URL and endpoint alongside the DID, we could issue a query like this:</p><pre>query Query($serviceType: String) {<br>  didList(serviceType: &quot;DIDCommMessaging&quot;) {<br>    did<br>    didService {<br>      service_endpoint<br>      url<br>    }<br>  }<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;didList&quot;: [<br>      {<br>        &quot;did&quot;: &quot;did:ethr:sepolia:0x44f0da9ff7952c084fc138e16b203ae275b39275&quot;,<br>        &quot;didService&quot;: [<br>          {<br>            &quot;service_endpoint&quot;: &quot;\\\\&quot;&lt;https://ddc1.serveo.net/api/ssdt/messaging\\\\&gt;&quot;&quot;,<br>            &quot;url&quot;: &quot;did:ethr:sepolia:0x44f0da9ff7952c084fc138e16b203ae275b39275#service-1&quot;<br>          }<br>        ]<br>      },<br>      {<br>        &quot;did&quot;: &quot;did:ion:EiAXh4wW04iY8AQ8ijGiDpkidSVzsyng_UfRSiQtzYPCOg&quot;,<br>        &quot;didService&quot;: [<br>          {<br>            &quot;service_endpoint&quot;: &quot;\\\\&quot;null:3000airport/messaging\\\\&quot;&quot;,<br>            &quot;url&quot;: &quot;did:ion:EiAXh4wW04iY8AQ8ijGiDpkidSVzsyng_UfRSiQtzYPCOg#didcomm&quot;<br>          }<br>        ]<br>      },<br>      ...<br>    ]<br>  }<br>}</pre><p>The result shows all the DIDs that have the DIDComm service endpoints and their corresponding URL.</p><p>A similar request can give us DIDs with a Decentralized Web Node Service:</p><pre>query Query($serviceType: String) {<br>  didList(serviceType: &quot;DecentralizedWebNode&quot;) {<br>    did<br>    didService {<br>      service_endpoint<br>      url<br>    }<br>  }<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;didList&quot;: [<br>      {<br>        &quot;did&quot;: &quot;did:ion:EiBFBukkAcYhzPQKtVdWo9DTPEGZDFMBtSbJ0AqSzJK3BA&quot;,<br>        &quot;didService&quot;: [<br>          {<br>            &quot;service_endpoint&quot;: &quot;{\\\\&quot;nodes\\\\&quot;:[\\\\&quot;&lt;https://dwn.zion.fyi&gt;\\\\&quot;]}&quot;,<br>            &quot;url&quot;: &quot;did:ion:EiBFBukkAcYhzPQKtVdWo9DTPEGZDFMBtSbJ0AqSzJK3BA#zion_dwn&quot;<br>          }<br>        ]<br>      },<br>      {<br>        &quot;did&quot;: &quot;did:ion:EiDflt-aJzSWTXoTJ2rZ7dABrw4MsAJJbDHMqddFm3nNLQ&quot;,<br>        &quot;didService&quot;: [<br>          {<br>            &quot;service_endpoint&quot;: &quot;{\\\\&quot;nodes\\\\&quot;:[\\\\&quot;&lt;https://dwn.zion.fyi&gt;\\\\&quot;]}&quot;,<br>            &quot;url&quot;: &quot;did:ion:EiDflt-aJzSWTXoTJ2rZ7dABrw4MsAJJbDHMqddFm3nNLQ#zion_dwn&quot;<br>          }<br>        ]<br>      },<br>      ...<br>    ]<br>  }<br>}</pre><p>Again, we can see that the result contains all the DIDs that have the Decentralized Web Node service endpoints and their corresponding URL.</p><h4>Querying by Verification Type and Method</h4><p>Let’s look at another example where we’re searching for ebsi DIDs with a specific verification type, and we&#39;re only interested in the DID:</p><pre>query Query($verificationType: String, $method: String) {<br>  didList(verificationType: &quot;Ed25519VerificationKey2020&quot;, method: &quot;ebsi&quot;) {<br>    did<br>  }<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;didList&quot;: [<br>      {<br>        &quot;did&quot;: &quot;did:ebsi:z24Byr5NcPTQWzQ2N7maki6d&quot;<br>      },<br>      {<br>        &quot;did&quot;: &quot;did:ebsi:zxdVF4DwwK6hgNPxD5Tkwjx&quot;<br>      },<br>      ...<br>    ]<br>  }<br>}</pre><h4>Finding Duplicate Keys</h4><p>Another interesting example is a query for duplicate keys. If we look at the DID did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1, we can see its duplicate keys:</p><pre>query Query($did: String!, $withVersions: Boolean) {<br>  duplicateKeys(did: &quot;did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1&quot;, withVersions: true) {<br>    did<br>    url1<br>    url2<br>    version_id<br>  }<br>}</pre><p>Result:</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;duplicateKeys&quot;: [<br>      {<br>        &quot;did&quot;: &quot;did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1&quot;,<br>        &quot;url1&quot;: &quot;did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1#key-1&quot;,<br>        &quot;url2&quot;: &quot;did:ebsi:zd6Cndnct8nWSh8rXmQHdcb#key-1&quot;,<br>        &quot;version_id&quot;: &quot;0x89fcc51f4e8e33db5bce51a74155b82dfa7261377613d3c63300c76aa68c2619&quot;<br>      },<br>      {<br>        &quot;did&quot;: &quot;did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1&quot;,<br>        &quot;url1&quot;: &quot;did:ebsi:zy6NHYTY2FKr5ffJ7wjaYB1#key-1&quot;,<br>        &quot;url2&quot;: &quot;did:ebsi:ziA2gog9GfVjL6o72DvqZQa#key-1&quot;,<br>        &quot;version_id&quot;: &quot;0x978bac159fa3016968548b9937da95bc618f248a419480e30e7861f3211c5df4&quot;<br>      },<br>      ...<br>    ]<br>  }<br>}</pre><h3>Conclusion</h3><p>The Stats API opens up a world of possibilities for exploring and analyzing DID-related data. With its flexible querying capabilities and rich dataset, developers and decision-makers can gain valuable insights into the trends and patterns of DID usage across various identity networks.</p><p>We encourage you to explore the API and discover how it can benefit your projects and inform your strategies. If you have any questions or feedback, please don’t hesitate to reach out to our team.</p><p>Happy querying!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edb203fb9913" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-6-unlock-the-power-of-decentralized-identity-with-godiddys-graphql-api-edb203fb9913">The Power of DIDs #6: Unlock the Power of Decentralized Identity with our Stats API</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Press Release: K4 Security and Danube Tech Enter Strategic Partnership to Pioneer the Future of…]]></title>
            <link>https://medium.com/danube-tech/press-release-k4-security-and-danube-tech-enter-strategic-partnership-to-pioneer-the-future-of-fd1e3c8759aa?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd1e3c8759aa</guid>
            <category><![CDATA[press-release]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[verification]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 12:50:38 GMT</pubDate>
            <atom:updated>2023-11-09T13:02:05.426Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Press Release: K4 Security and Danube Tech Enter Strategic Partnership to Pioneer the Future of Decentralized Digital Identity</strong></h3><p><em>Seoul &amp; Vienna — November 9th 2023 — K4 Security Co Ltd, led by CEO Kyoungchul Park, and Danube Tech GmbH, under the leadership of CEO Markus Sabadello, announced the signing of a Memorandum of Understanding (MOU) to jointly develop and expand the decentralized identity (ID) market in Korea.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vd3Uu-aLqJgyCfmE1FLEhA.png" /><figcaption>Signing of the partnership between Danube Tech’s CEO Markus Sabadello (left) and <em>K4 Security Co Ltd’s CEO Kyoungchul Park (right).</em></figcaption></figure><p><strong>Empowering user anatomy in digital verification with Distributed ID</strong></p><p>Decentralized ID represents a seismic shift in digital identity verification by empowering users to manage and control their own identity data. This disruptive model eliminates the need for a central authority, enhancing both personal sovereignty and data security. The system allows individuals to selectively disclose identity information, ensuring greater privacy and relevance during the verification process.</p><p><strong>Towards a Global Standard</strong></p><p>Self-Sovereign Identity (SSI) or Decentralized Identity is fast becoming the universal standard for digital identity. With governments in Europe and around the world actively fostering its adoption, and the private sector recognizing its transformational potential, the timing for this partnership couldn’t be more auspicious.</p><p><strong>Collaboration</strong></p><p>The partnership will create a joint presence in Korea that utilizes Danube Tech GmbH’s products and technologies, and K4 Security’s reputation and relationships in the Korean market. The service will be especially focused on interoperability of Decentralized Identifiers and Verifiable Credentials between Korean based identity networks and European networks.</p><p><strong>A Word from the CEOs</strong></p><p>“We will establish international technological partnerships to promote the standardization and supply of decentralized identity (ID) technology,” stated K4 Security CEO Kyoungchul Park. “and expand international cooperation to revitalize the mobile ID and blockchain industries, including the development of blockchain-based public services.”</p><p>“We are truly excited about this partnership. We have always believed that decentralized identity should not stop at the borders of individual countries or even continents, but should instead be globally interoperable.” Stated Danube Tech CEO Markus Sabadello. ”With K4 Security, a leading Korean company in this field, we will collaborate on technologies that will interconnect digital identity infrastructures between Europe, Korea, and beyond.”</p><p><strong>About Danube Tech</strong></p><p>Danube Tech GmbH (<a href="https://www.danubetech.com/">https://www.danubetech.com</a>) is at the forefront of decentralized identity technology, standards, and interoperability in Europe.</p><p><strong>About K4 Security</strong></p><p>K4 Security (<a href="http://www.k4-security.com/en/home_en/">http://www.k4-security.com/en/home_en/</a>) is a leading firm in the Korean market, focusing on the standardization and practical application of decentralized identity solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd1e3c8759aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/press-release-k4-security-and-danube-tech-enter-strategic-partnership-to-pioneer-the-future-of-fd1e3c8759aa">Press Release: K4 Security and Danube Tech Enter Strategic Partnership to Pioneer the Future of…</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Beyond the Limitations of did:web]]></title>
            <link>https://medium.com/danube-tech/moving-beyond-the-limitations-of-did-web-c10f53eafdc3?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/c10f53eafdc3</guid>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[ssi]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Mon, 23 Oct 2023 15:54:27 GMT</pubDate>
            <atom:updated>2023-10-23T15:54:27.231Z</atom:updated>
            <content:encoded><![CDATA[<h3>Is it time to reassess the adoption of did:web in light of new ledger-based developments?</h3><p><em>Co-authored by: </em><a href="https://medium.com/u/87130a922e66?source=post_page-----bf81129c3d40--------------------------------"><em>Markus Sabadello</em></a><em> (Danube Tech), </em><a href="https://medium.com/u/d3f2b151de8d?source=post_page-----bf81129c3d40--------------------------------"><em>Alex Tweeddale</em></a><em> (cheqd), </em><a href="https://medium.com/u/2d7ca4c61292?source=post_page-----bf81129c3d40--------------------------------"><em>Carsten Stöcker</em></a><em> (Spherity GmbH), Alen Horvat (Netis).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M1rjB1WX328w4yaa" /></figure><h3>Executive summary</h3><p>did:web <strong>is becoming a honey trap</strong> for organisations looking to adopt decentralised identity and credential-based technology. While it is attractive due to its low cost and simplicity (the honey🍯), it is easy to get stuck with it beyond testing environments (the trap 🪤). There are a series of challenges and vulnerabilities with did:web which need to be fully understood before using the method in production environments.</p><p>These core issues run deep, to the point where <a href="https://w3c-ccg.github.io/did-method-web/">did:web</a> is beginning to falsely represent the true value and core purpose of DIDs, since the DIDs are not decentralised, cryptographically verifiable, tamper resistant, self-certifiable or persistently stored. And while there are proposals to improve did:web, such as <a href="https://trustoverip.github.io/tswg-did-method-webs-specification/">did:webs</a> and <a href="https://github.com/LedgerDomain/did-webplus">did:webplus</a> (which do have merit in their own right), we believe that it is now time to reconsider the adoption of a select few ledger-based alternatives.</p><p>Ledger-based approaches such as <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home">EBSI</a> and <a href="https://cheqd.io/?utm_source=medium&amp;utm_medium=social">cheqd</a> have reached a state of maturity where the value of their DID methods goes beyond simple DID resolution. These additional benefits include:</p><ol><li>Historically resolvable, traversable and persistent DID Document states, queryable through standardised DID URL dereferencing.</li><li>Fully resolvable, traversable and cryptographically verifiable trust registries, status lists and schemas, using DID-Linked Resources.</li><li>Machine readable governance rules and permissions for scalable trust frameworks, using DID-Linked Resources.</li><li>DID resolvable and cryptographically verifiable proof of ownership of decentralised, digital data stores, such as <a href="https://identity.foundation/decentralized-web-node/spec/">Decentralized Web Nodes (DWNs)</a>.</li><li>New commercial models for verifiable credentials including <a href="https://blog.cheqd.io/credential-payments-are-live-4bf4ea1ff7a8">payments to unlock ledger-based status lists or trust registries</a>.</li></ol><p>At the same time, more established ledgers such as <a href="https://www.hyperledger.org/projects/hyperledger-indy">Indy</a> and <a href="https://identity.foundation/ion/">ION</a> have continued to improve their tooling, developer experience and provide excellent options for general ledger-based DID resolution and digital credential ecosystems.</p><p>With these innovations, adopters can build fully decentralised trust ecosystems, without relying on centralised web domains or single points of failure. This realigns the value of DIDs far closer to their original purpose, than the regression and reliance on more centralised architecture perpetuated by did:web.</p><h3>Introduction</h3><p>The decentralised identity community has gradually drifted <em>away </em>from initially adopted <strong>decentralised </strong>DID Methods (such as did:sov and did:ethr) and towards the adoption of more <strong>centralised</strong> approaches, such as did:web (and even regressing to non-DID solutions such as X.509 Certificates).</p><p>This is because the simplicity and cost-effectiveness of establishing a credential ecosystem using did:web has led to a general sentiment that did:web is good enough <strong><em>“</em></strong><em>for now</em><strong><em>” </em></strong>or <strong><em>“</em></strong><em>until something better comes along</em><strong><em>”</em></strong>. At the same, the more established ledger-based approaches (did:sov, did:indy, did:ethr, did:ion) have had challenges with interoperability, regulatory uncertainty, scalability and integration effort.</p><p>Although the narrative of moving towards did:web has held sway, we believe that <strong>it is time to reassess its legitimacy in light of significant developments and innovations made by alternatives, </strong>coupled with the emergence of more accessible tooling to easily integrate with these methods . To illustrate why it is the right time for this, this paper aims to shed light on two key points:</p><h3>1. We’re sleepwalking back towards “centralised” identity 🧟</h3><p>did:web has <strong>significant concerns and vulnerabilities when used in production environments, </strong>which were never intended to be part of the design of DIDs.</p><p>These issues need to be thoroughly understood before deciding to use this method, and additionally, they are adversely affecting the reputation of DIDs in general. This is having the effect of <strong>undoing all the good work of establishing a “decentralised” identifier </strong>and has led to adopters regressing back to traditional identifier models like X.509 certificates, since did:web does not offer many significant benefits to justify the switch up costs and additional development.</p><h3>2. We’re too quick to dismiss new ledger-based innovations 🤔</h3><p>There is no denying that the community has a chequered history with ledger-based approaches to decentralised ID. Owing to these challenges, as well as a handful of illegitimate and immature ledger-based DID methods, there has been a widespread scepticism around any of the developments made in this space.</p><p>Yet, in the last year, a few ledger-based methods in particular have <strong>seen substantial improvements</strong>, <strong>many of which have gone unnoticed by the community</strong>. These improvements now offer a value proposition extending far beyond simple DID Resolution, including fully resolvable, cryptographically verifiable and persistent DIDs with linked trust registries, status lists and governance rules/permissions.</p><p>Therefore, we believe that it is now a viable option to move beyond the limitations of did:web, and begin considering a selection of alternatives, including ledger-based DID methods with greater confidence.</p><h3>What was the initial goal of DIDs? 🥅</h3><p>To help frame our argument, a good question to explore, reflect upon, and use as a reference point is: <strong><em>why were DIDs initially created?</em></strong></p><p>The idea for a <a href="https://www.w3.org/TR/did-core/">Decentralised Identifier (DID)</a> was initially conceived around 2015, close to the same time when Self-Sovereign Identity (SSI) emerged as a concept. One of the earliest documents that influenced this development was <a href="https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf">“Decentralised Public Key Infrastructure” (DPKI)</a>, drafted at Rebooting-the-Web-of-Trust (RWoT) #1 and co-authored by notable thought leaders in the SSI space, as well as <a href="https://en.wikipedia.org/wiki/Vitalik_Buterin">Vitalik Buterin</a>, who went on to found Ethereum.</p><p>This work recognised that the problem with <strong><em>traditional </em></strong>identity systems is that they were based on <strong>centralised and hierarchical roots of trust</strong>, which ultimately revolved around a small set of actors. In contrast, the <a href="https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf">DKPI paper</a> proposed that a new type of identifier was needed: one which was independent of central authorities and control.</p><p>At the time, a theoretical concept known as <a href="https://en.wikipedia.org/wiki/Zooko&#39;s_triangle">Zooko’s triangle</a> was often used to describe three desirable properties of identifier systems:</p><ol><li><strong>Human-meaningful</strong> 💡</li><li><strong>Secure</strong> 🔒</li><li><strong>Decentralised</strong> 🕸️</li></ol><p>The existing “identifier” system, the <a href="https://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a>, fulfilled the “secure” and “human-meaningful” properties,<strong> but did not fulfil the “decentralised” property.</strong></p><p>DIDs on the other hand were designed to be “secure” and “decentralised”, <strong>but not necessarily “human-meaningful”</strong>. This was why many of the original DID methods were based on distributed ledgers (did:sov, did:ethr). It was only several years later that other derivations of DID methods such as did:web, did:key, did:peer and did:jwk were developed.</p><h3>Why is this important to understand?</h3><p>The invention of, specifically, the <strong>did:web method</strong>, had a profound impact on the <a href="https://www.w3.org/2019/did-wg/">W3C DID Working Group</a>, as it was seen as a DID method that could fulfil the technical requirements of a DID (with regard to its syntax and capability for DID resolution), <strong>but it was not a “Decentralised Identifier” in the original sense. </strong>This is because it was <strong>not decentralised, persistent or cryptographically verifiable</strong>.</p><p>This created a level of dissonance between did:web, which has gained increasing adoption, and the <em>actual</em> purpose, utility and extensibility of DIDs — prompting a rhetorical question that we will consider throughout — <strong>if a DID is not decentralised,</strong> <strong>why use DIDs at all?</strong></p><h3>The did:web honey trap 🍯</h3><p><a href="https://w3c-ccg.github.io/did-method-web/">did:web</a> is undoubtedly very simple to use, cost-effective and is functional for proving the concept of DID resolution. Yet, <strong>it’s a bit like a honey trap</strong>.</p><p>This is because the reliance on did:web as the primary DID method supported in client applications, beyond testing environments, has significant vulnerabilities as well as having a negative effect on the reputation of DIDs. It pulls a lot of adopters in, who then get stuck with it as their idea of what DIDs are capable of eroding many of the fundamental properties of DIDs, which we will discuss in turn.</p><h3>DID Document Provenance and Versioning</h3><p>One unique and largely underappreciated feature of the <a href="https://www.w3.org/TR/did-core/">DID Core specification</a> <strong>is the feature of provenance</strong>, i.e. the ability to <strong>resolve DIDs back to a specific point in time</strong>, even if the DID Document has been significantly updated since that period.</p><p>DID Document provenance enables important use cases such as <strong>data and service portability, stable address books, key rotation, and key updates</strong>. To support this, the <a href="https://www.w3.org/TR/did-core/">DID Core specification</a> defines various DID parameters (<a href="https://www.w3.org/TR/did-core/#did-parameters">versionId</a>, <a href="https://www.w3.org/TR/did-core/#did-parameters">versionTime</a>) and metadata properties (<a href="https://www.w3.org/TR/did-core/#revocation-in-trustless-systems">updated</a>, <a href="https://www.w3.org/TR/did-core/#revocation-in-trustless-systems">nextUpdate</a>).</p><p>The <a href="https://w3c-ccg.github.io/did-method-web/">did:web method</a> simply does not support these features; and while it would theoretically be possible to extend the did:web method to add a version history (see did:web <a href="https://github.com/w3c-ccg/did-method-web/issues/61">issue #61</a>), it would never be immutable and cryptographically verifiable as it is in other DID methods. Recently, we’ve seen proposals such as <a href="https://trustoverip.github.io/tswg-did-method-webs-specification/">did:webs</a> which aims to use <a href="https://keri.one/">KERI</a> to witness and relay did:web event logs to add an extra layer of provenance.</p><p>This is a welcome improvement to did:web 👏 but may create interoperability challenges between did:webs witness “smart” applications and others, unless it’s implemented within something like the Universal Registrar / Resolver.</p><h3>Data Integrity and Tamper-Resistance</h3><p>Using centralised hosting providers, such as a web-domain, to store DIDs may have a significant difference in the longevity, authenticity and auditability of DIDs and any Verifiable Credentials reliant on the DID authentication. This is because:</p><ol><li><strong>DIDs may be spoofed or compromised</strong>: DIDs and DID Documents stored at a centralised web endpoint can be compromised and replaced by malicious actors.</li><li><strong>Hosting providers are known for down-time</strong>: Hosting providers (even highly reputable and sophisticated providers) could terminate accounts due to factors such as non-payment of fees, violation of Terms of Service, etc.</li><li><strong>did:web links may be deprecated and throw errors:</strong> A link pointing to a DID Document may be changed, resulting in a dead-link and error for a client application relying on the verification of a Credential signed by a deprecated DID.</li></ol><h3>Privacy and the “Phone Home” problem</h3><p><strong>The “Phone Home” problem is a significant privacy and confidentiality issue associated with the did:web method</strong>. With did:web, the issuer can track or record:</p><ol><li>Any time your DID is requested by a verifier,</li><li>The frequency of requests,</li><li>Timestamps of requests,</li><li>IP addresses,</li><li>User agent details.</li></ol><p><strong>This information can be correlated, allowing the “issuer” to potentially identify the interactions of specific “holders”</strong> — which is a significant risk to privacy and the legitimacy of DIDs and Verifiable Credential solutions. This is something that is incredibly important for adopters of the method to consider, because this results in the use of Verifiable Credentials replicating the same problems as “Web2” in terms of tracking and big data analytics.</p><h3>Self-Certifiability</h3><p>did:web DIDs have no inherent “self-certifiability”. This means that the DID identifier itself does not cryptographically link to the DID Document at all. This reduces the level of assurance a relying party will have in a did:web DID because the DID Document contents and associated keys may have been edited or spoofed without any cryptographic checks validating the DID’s authenticity.</p><p>There have been proposals to improve this aspect of did:web, such as <a href="https://github.com/LedgerDomain/did-webplus">did:webplus</a>, but again, while it is a reasonable attempt to paper over the cracks, it will still be vulnerable to other issues, which may be mitigated through alternative methods. Ultimately, while using did:web has been<strong><em> </em></strong>a practical approach to set up a decentralised identity solution quickly and efficiently, this comes at the cost of security, cryptographic integrity and provenance.</p><h3>The Slope of Enlightenment for Ledger-based DID Methods 📈</h3><p>There has undoubtedly been a history of hesitancy and scepticism around the <strong><em>need </em></strong>or <strong><em>requirement </em></strong>for ledger-based DID methods because centralised methods such as did:web, did:key and did:jwk can largely accomplish the <strong>same core value in terms of simple DID resolution</strong>.</p><p>Ledger-based DID Methods have also historically built a <strong>poor reputation. </strong>There are a myriad of ledger-based DID methods (likely over 100) within the <a href="https://www.w3.org/TR/did-spec-registries/">DID Spec Registries</a>, and largely these methods come with a catch, including</p><ol><li><strong>Interoperability challenges:</strong> with unique transaction types which require a particular software stack to utilise</li><li><strong>Scalability issues</strong>: with high transaction volumes and high volumes of requests</li><li><strong>Integration blockers: </strong>with poor/incomplete documentation and long integration timelines</li><li><strong>Blockchain hysteria: </strong>with too many projects professing to “put everything on the blockchain”, leading to privacy nightmares and valid questions of their legitimacy.</li></ol><p>However, more recently, we are beginning to see a level of maturity in<strong> a select few </strong>ledger-based DID methods that are <strong>starting to take advantage of the broader aspects of the DID Core spec</strong>.</p><p>We have also seen substantial developments in the interfaces for consuming and using ledger-based DID methods, with the <a href="https://dev.uniresolver.io/">Universal Resolver</a> and <a href="https://uniregistrar.io/">Registrar</a> projects providing a way to consume an array of ledger-based DID methods with interoperability, without bespoke integrations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*BkdpZasZl9rDSJdn" /></figure><p><a href="https://www.gartner.com/en/research/methodologies/gartner-hype-cycle#:~:text=Slope%20of%20Enlightenment%3A%20More%20instances,products%20appear%20from%20technology%20providers.">Gartner Hype Cycle</a> Graphic</p><p>Having initially peaked and then dropped off into the “Trough of Disillusionment”, we now think that a select few ledgers, with recent innovations, are climbing into the “Slope of Enlightenment”.</p><p>For this reason, we want to reiterate that <strong>not all ledgers</strong> should be viewed with the same hesitancy as the majority, and it is worth reassessing their maturity, legitimacy and capability to deliver on the fundamental components of DID Core, including:</p><h3>Persistent DID Document Version Lookup and Retrieval ↩️</h3><p>As described earlier as a omission of did:web,<strong> </strong>being able to <strong>persist and query historic versions of DID Document states is highly valuable in production environments, </strong>where Credentials are expected to have a long life span or in use cases where issuers frequently rotate their keys or update their DID Documents.</p><p>Going into production environments, it is very important for a “holder” to be able to prove that the keys signing their Credential were valid at the point of issuance, even if the issuer has rotated to new Verification Method keys multiple times since issuance.</p><p>Without version lookup and retrieval, Credentials will have a far shorter life cycle and Level of Assurance — these Credentials will likely need to be issued more frequently because key rotations will overwrite previous keys unless the historic information is persisted.</p><p>DID methods, for example, “<a href="https://docs.cheqd.io/identity/architecture/adr-list/adr-001-cheqd-did-method?utm_source=medium&amp;utm_medium=social">did:cheqd</a>” and “<a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/EBSI+DID+Method">did:ebsi</a>” both currently have working, production-ready DID Resolvers with query parameters to fetch historic versions of DID Document states from their respective methods, including standardised query parameters such as “versionId” and “versionTime”. For example:</p><ul><li>did:example:38428720–301e-4168-abac-c93581f08a3c?versionId=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?versionTime=X</li></ul><p>Service providers like <a href="https://godiddy.com/">Godiddy.com</a> provide the same functionality for several additional DID methods, creating the first of many value adds between ledger-based methods and did:web.</p><h3>Verifiable Trust Registries and Status Lists 🍏</h3><p>Trusted Issuer Lists are a <strong>critical component</strong> in the world of Decentralised Identifiers (DIDs) and Verifiable Credentials. They serve as a registry of trusted entities that are authorised to issue credentials or conduct other actions, thereby enhancing the trustworthiness and reliability of the credentials issued within the system. However, <strong>Trusted Issuer Lists have experienced a similar teething problem to did:web</strong>, in the sense that most approaches to them are based on centralised, traditional infrastructure.</p><p>Recently, several organisations and initiatives have made significant strides in <strong>implementing ledger-based Trusted Issuer Lists</strong>, including:</p><ol><li><a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home">European Blockchain Services Infrastructure</a> (EBSI)’s <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/Issuers+trust+model+-+Accreditation+of+Issuers">Trusted Issuer Model</a>, enabling DIDs and their associated Verifiable Attestations to be written to a<strong> permissioned Trusted Issuers Registry.</strong></li><li><a href="https://cheqd.io/?utm_source=medium&amp;utm_medium=social">cheqd’s</a> approach to DID-Linked Trust Registries, enabling DID Controllers to create Trusted Issuer Lists <strong>within a “Collection” of “Resources” associated and linked with their DID</strong>. This is made possible via an <a href="https://docs.cheqd.io/identity/guides/did-linked-resources?utm_source=medium&amp;utm_medium=social">emerging W3C specification called DID-Linked Resources</a>.</li><li><a href="https://www.oc-i.org/">Open Credentialing Initiative</a> (OCI)’s <a href="https://github.com/Open-Credentialing-Initiative/trusted-issuer-registry">Trusted Issuer Registry</a>, managed through a smart contract deployed on the public Ethereum blockchain.</li></ol><p>Similarly, <a href="https://www.w3.org/TR/vc-status-list/">Verifiable Credentials Status List v2021</a> is the most commonly adopted way of currently tackling credential revocation. However, this method <strong>requires an issuer to publish a public Verifiable Credential to a centralised server</strong>, which displays the latest revocation status of issued Credentials within a bitstring. The centralised nature of the server reflects similar issues to those raised earlier around did:web, particularly in terms of persistence, uptime, security, verifiability and data integrity.</p><p>Again, this is being solved by ledger infrastructure, with approaches such as:</p><ol><li>cheqd’s <a href="https://docs.cheqd.io/identity/tutorials/did-linked-resources/statuslist2021-resources?utm_source=medium&amp;utm_medium=social">ledger-based Status List 2021</a> which publishes each Status List entry and bitstring as a distinct <a href="https://docs.cheqd.io/identity/guides/did-linked-resources?utm_source=medium&amp;utm_medium=social">DID-Linked Resource</a>, resolvable and identifiable via a DID URL.</li><li>Ethereum’s <a href="https://eips.ethereum.org/EIPS/eip-5539">Ethereum Improvement Proposal (EIP)</a> worked on by the team at <a href="https://www.spherity.com/">Spherity</a>, which uses similar logic to Status List v2021, but with additional improvements to delegation.</li><li>Hyperledger’s <a href="https://hyperledger.github.io/anoncreds-spec/#issuer-create-and-publish-revocation-registry-objects">AnonCreds revocation</a> which uses cryptographic accumulator based Status Lists, written on ledger, to calculate whether a Credential is part of a revoked set in a privacy-preserving way (note that there has also been great work by the <a href="https://www.hyperledger.org/projects/hyperledger-indy">Indy</a> and AnonCreds communities <a href="https://hyperledger.github.io/anoncreds-spec/">to update the AnonCreds spec and make it ledger-agnostic</a>, meaning that this is no longer an Indy-specific approach).</li></ol><p>In combination with a ledger-based DID method, these <strong>on-chain trust lists create a robust, and importantly, decentralised way of managing additional contexts such as trusted issuers and credential statuses</strong>. They offer a balance of security, transparency, auditability, and control, while also providing resilience, privacy, and usability. All of which cannot currently be achieved using did:web or centralised alternatives.</p><h3>Universal Resolver and Registrar 💫</h3><p>One fundamental aspect of DIDs that should be kept in mind is that by the use of “methods”; this technology has always been designed to be an abstraction layer on top of pretty much any identifier system. No matter if an application uses <a href="https://w3c-ccg.github.io/did-method-web/">did:web</a>, a ledger-based DID method, or any other method such as <a href="https://w3c-ccg.github.io/did-method-key/">did:key</a>, there is always a common syntax and the common DID Document format which describes the subject. The exact process of obtaining the DID Document for a given DID of course is defined by the method and can vary greatly. In fact, this design has been a common point of discussion within the W3C DID WG, and there have been questions whether such an abstraction layer provides sufficient “useful interoperability”, considering the differences between DID methods.</p><p>Initiatives such as the well-known <a href="https://github.com/decentralized-identity/universal-resolver">Universal Resolver</a> and <a href="https://github.com/decentralized-identity/universal-registrar">Universal Registrar</a> open-source projects at the <a href="https://identity.foundation/">Decentralized Identity Foundation (DIF)</a> make it easy to use this abstraction layer not only in theory, but also in practice.</p><p>These components <strong>can be used to perform the standard DID operations (Resolve, Create, Update, Deactivate) across many different DID methods via a single “universal” interface.</strong> Building on top of such standard interfaces removes the complexity of bespoke integrations with each method and creates a more “future proof” way of interfacing with DIDs, since applications can easily plug in support for additional DID methods at any time, and layers of concern are cleanly separated. Commercially hosted services such as <a href="https://godiddy.com/">Godiddy.com</a> also offer this type of interoperability interface as a service.</p><h3>Realising the True Power of DIDs 💪</h3><p>A crucial point and takeaway is that <strong>did:web adoption presupposes that the power of a DID is in its ability to be resolved to fetch the keys listed in the DID Document</strong>. While this is often all that is required for a use case, it only uses a fraction of the potential of the DID Core specification’s extensible design.</p><p>Ledger-based DID methods haven now taken DIDs beyond simple resolution, and <strong>utilise the persistence and immutability of the architecture to provide trusted resolvable DID URLs to external ledger-rooted resources,</strong> such as <a href="https://identity.foundation/decentralized-web-node/spec/">Decentralized Web Nodes (DWNs)</a>, Trusted Issuer Lists, Status Lists, schemas and other governance information.</p><h3>DID-Linked Resources (DLRs) are game changers ⚡</h3><p><a href="https://github.com/w3c-ccg/DID-Linked-Resources">DID-Linked Resources (DLRs) is an emerging W3C specification</a> that takes ledger-based resources (such as Trusted Issuer Lists, Status Lists, Schema Registries, Overlay Capture Architecture etc) and identifies/retrieves them using DID URL patterns and dereferencing.</p><p>It enables organisations to leverage the benefits of on-chain, persistent and verifiable lists and resources, while <strong>creating a common syntax for identifying and retrieving them, across any ledger-based DID method. </strong>It also reuses the same trust patterns established in the <a href="https://www.w3.org/TR/did-core/">DID Core spec</a>, since the author of a DLR needs to sign the transaction with the same key material within the linked DID Document.</p><p>This generic architecture for DID-Linked Resources is shown in the diagram below, and for readers who want to learn more, we’d suggest reading <a href="https://docs.cheqd.io/identity/architecture/adr-list/adr-002-did-linked-resources?utm_source=medium&amp;utm_medium=social">cheqd’s Architecture Decision Record on their technical composition</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*CMqIaHSDWPPJGBKk" /></figure><p>DID-Linked Resources diagram</p><p>The DLR specification additionally provides a set of query parameters to identify and retrieve different derivations of digital resources, associated with a DID, which may be combined to create rich filters, including (but not limited to):</p><ul><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceId=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceCollectionId=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceName=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceType=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceName=X&amp;resourceType=X</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceName=X&amp;resourceType=X&amp;resourceVersionTime=XMLDatetime</li><li>did:example:38428720–301e-4168-abac-c93581f08a3c?resourceName=X&amp;resourceType=X&amp;resourceMetadata=true</li></ul><p>DID-Linked Resources has currently been fully implemented by chains such as <a href="https://cheqd.io/?utm_source=medium&amp;utm_medium=social">cheqd</a> and <a href="https://cardano.org/">Cardano</a> with <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home">EBSI</a> also interested in supporting them. DLRs can be applied for various use cases, such as:</p><ol><li>Ledger-agnostic <a href="https://hyperledger.github.io/anoncreds-methods-registry/#cheqd-anoncreds-method">AnonCreds</a></li><li>DID-Linked and fully verifiable <a href="https://docs.google.com/presentation/d/1CHvQ9MfGLxxGjJ4xaJ8aewiItuqHxwGEJhKCVL8iJFo/edit#slide=id.g227a2243257_0_81">Trust Registries</a></li><li>DID-Linked and fully verifiable <a href="https://docs.cheqd.io/identity/guides/did-linked-resources/technical-composition?utm_source=medium&amp;utm_medium=social">Schemas</a></li><li>DID-Linked and fully verifiable <a href="https://docs.cheqd.io/identity/tutorials/did-linked-resources/statuslist2021-resources?utm_source=medium&amp;utm_medium=social">Status Lists</a></li><li>Encrypted DID-Linked Status Lists, Trust Registries or Schemas with <a href="https://blog.cheqd.io/credential-payments-are-live-4bf4ea1ff7a8">Payments required to unlock</a>.</li></ol><p>Through using DID-Linked Resources, <strong>issuers can include ledger-based Resource in the contents of issued Verifiable Credentials</strong>. These resources can be relied upon by Verifiers with full confidence in their authenticity, data integrity and security. Not only can this add additional value to Credentials, but also does not create interoperability challenges as these are only optional “add ons”.</p><p>These benefits however, can only be realised using ledger-based DID methods, as with did:web, it would be <em>possible </em>to create DID-Linked Resources, but they would again be vulnerable to the same limitations as the DID method itself.</p><p>For this reason, <strong>DID-Linked Resources complement ledger-based DID methods, and ledger-based DID methods enable innovations like DID-Linked Resources</strong>. This specific development takes the benefits of using a ledger much further than simple DID resolution, allowing issuers to create far <strong>more robust roots of trust for full scale, production-ready Self-Sovereign Identity ecosystems</strong>.</p><h3>Decentralized Web Nodes (DWNs) and DID-Relative URLs to establish trust</h3><p>A <a href="https://identity.foundation/decentralized-web-node/spec/">Decentralized Web Node (DWN)</a> is a data storage and message relay mechanism which entities can use to locate public or private permissioned data related to a given Decentralised Identifier (DID). DWNs were created by the team at <a href="https://developer.tbd.website/">TBD</a> for the furtherance of <a href="https://developer.tbd.website/projects/web5/">Web5</a>, an internet based on identity primitives and digital credentials.</p><p><a href="https://identity.foundation/decentralized-web-node/spec/">The DWN specification</a> utilises the <a href="https://www.w3.org/TR/did-core/#services">“services” section of the DID Core spec</a> alongside query-based DID URL dereferencing to allow DID Controllers to point to specific storage or messaging endpoints. For example:</p><ul><li>did:example:alice?service=DecentralizedWebNode &amp;message= toBase64Url( JSON.stringify( { MESSAGE } ) )</li></ul><p>This syntax not only uses the security and provenance of a DID, but extends the value of DIDs away from purely resolution, and provides DIDs the ability to authoritatively identify external data and resources, where third parties can be confident that the data belongs to the DID Controller. This has a lot of overlap with DID-Linked Resources, and builds on very similar principles.</p><p>With did:web on the other hand, extensibility via the “services” section, while possible, is limited by the same vulnerabilities as the method itself.</p><h3>Looking ahead</h3><p>With one eye on the fragilities of centralised DID methods such as did:web, and another on the developments made by a selection of ledger-based DID methods, we hope to see a general movement away from the vulnerabilities of the former.</p><p>Already, several initiatives are underway that attempt to combine the benefits of did: web and ledger-based approaches. These include the <a href="https://trustoverip.github.io/tswg-did-method-webs-specification/">did:webs</a>, <a href="https://github.com/LedgerDomain/did-webplus">did:webplus</a> and the <a href="https://github.com/WebOfTrustInfo/rwot12-cologne/blob/main/draft-documents/beyond-did-web.md">recent RWOT advanced topic paper on moving beyond did:web</a>, which use the current did:web design as a starting point and propose to add a layer of cryptographic verifiability, auditability and persistence. While such improvements do not fully eliminate the downsides that come with a dependence on DNS and web infrastructure, they do provide good stepping stones away from some of the fragilities of their predecessor.</p><p>Looking forward towards the latter, we hope that some of the legitimate players and innovators in the ledger space can begin to undo some of the scepticism rooted here, for three reasons:</p><ol><li><strong>Technical innovation: </strong>As described above, DID URL dereferencing, service discovery and DID-Linked Resources provide additional benefits to the use of DIDs, in line with their initial conception; where notably, these benefits cannot be gained from using did:web.</li><li><strong>Regulatory clarity</strong>: We are now seeing strides made in regulatory clarity for ledger-based approaches in the context of <a href="https://www.electronicid.eu/en/blog/post/eidas-2-0-what-can-companies-expect-from-it/en">eIDAS 2.0</a>, with “electronic ledgers” now set to be listed as valid “qualified trust services” under the <a href="https://digital-strategy.ec.europa.eu/en/policies/electronic-identification">European Electronic Identification (‘eID’) framework</a>. 🤞</li><li><strong>Accessibility and interoperability:</strong> Open Source projects such as the <a href="https://github.com/decentralized-identity/universal-resolver">Universal Resolver</a> and <a href="https://github.com/decentralized-identity/universal-registrar">Registrar</a> provide interfaces for developers to utilise any supported DID method without a time-consuming integration, using REST APIs.</li></ol><p>Although we do not expect a full movement to ledger-based methods overnight, we hope that the information and explanations provided here help readers recognise the benefits that some ledger approaches can now provide over did:web; and, where the use case makes sense, we hope that adopters may be more open to considering these methods into their design decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10f53eafdc3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/moving-beyond-the-limitations-of-did-web-c10f53eafdc3">Moving Beyond the Limitations of did:web</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of DIDs #5: A Deep Dive into Service Endpoints and Digital Product Passports]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-5-a-deep-dive-into-service-endpoints-and-digital-product-passports-2c60f3e68f8d?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c60f3e68f8d</guid>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[digital-passport]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Thu, 20 Jul 2023 08:46:47 GMT</pubDate>
            <atom:updated>2023-07-20T08:48:53.929Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Discover how DIDs function as an indirection layer for endpoints, enabling versatile applications like digital product passports. Learn about the structure, dereferencing process, and additional features of DIDs.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FiRqMjNzo3M8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DiRqMjNzo3M8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FiRqMjNzo3M8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/774a2bc75b3849d1fbd4a4d635f72559/href">https://medium.com/media/774a2bc75b3849d1fbd4a4d635f72559/href</a></iframe><h3>Understanding Service Endpoints and Digital Product Passports</h3><p>Welcome to the 5th episode of ‘The Power of DIDs’. In today’s discussion, we will delve into the concept of service endpoints, and see how they can be applied in real-world cases, such as enabling digital product passports. Whenever we convert DIDs into DID documents, our main focus is usually the verification method. This method allows for secure interactions and authentication with the DID controller. An equally compelling feature of DID documents is ‘services’. These ‘services’ facilitate interaction with the DID subject, employing various protocols like DIDComm, DWN, activity pub, and others.</p><p>‘Services’ can also act as links to files or web pages containing data about the subject. In scenarios where the DID subject is a physical product, ‘services’ can guide us to a digital product passport. Let’s get a bit technical here. When we select a service from a DID document using the service DID parameter, we’re doing more than just resolving DIDs to DID documents. We’re dereferencing DID URLs to service endpoints. This dereferencing mechanism retains all the beneficial traits of DIDs. It’s decentralized, it can be cryptographically verified, and it’s persistent. The persistence of DIDs is particularly noteworthy because it lets us update the DID document without altering the DID. This allows us to create an indirection mechanism, thus ensuring location independence and data portability.</p><p>The idea of having location-independent identifiers isn’t a new concept. It’s always been valued, especially in the realm of web. Since the 1990s, communities have focused their efforts on developing something known as persistent URLs or pURLs. The persistence of these identifiers has largely been due to convention, social, or legal contracts. However, DIDs and DID URLs maintain their persistence due to the enforcement by the underlying DID method. This provides DID URLs the strength to form a direct link to information regarding a DID subject.</p><h3>The Technical Architecture of DIDs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OgBJVrfEi_CvvOpu1lbZEA.png" /></figure><p>Let’s delve into the technical architecture. The figure above showcases a DID document and a DID. This will look pretty familiar to you. The DID can be resolved to yield the DID document, and the DID document in turn contains the DID itself. By adding a service parameter to the DID, we can select a service from the DID document. This results in the formation of a DID URL, which can be dereferenced.</p><h3>DID URL Dereferencing: An Insight</h3><p>Now, what happens when the DID URL gets dereferenced? The dereferencing software chooses the service from the DID document, whose ID corresponds with the service parameter value in the DID URL. The dereferencer then retrieves the service endpoint value for this specific service from the DID document and presents it. This, in essence, is the output of the dereferencing process. And, as I pointed out earlier, the service endpoint may change over time, but the DID itself stays persistent.</p><p>Indeed, this is a powerful process. However, there are additional features at our disposal. For instance, we can append another DID parameter, referred to as ‘relative ref’, to the DID URL. In such a scenario, the result of the dereferencing process will yield the same service endpoint but with the ‘relative ref’ added to it. Thus, DID URLs not only identify single service endpoints but can also serve as the root of an entire namespace.</p><p>Another handy feature is the ‘version time’ DID parameter. This allows us to resolve DID documents at a prior point in time. In effect, the outcome of the DID URL dereferencing process will be a previous location of that service endpoint.</p><h3>Conclusion</h3><p>To wrap up, we explored how Decentralized Identifiers can function as an indirection layer for endpoints or any links pointing towards information about the subject or resource. In scenarios involving physical products, a DID URL can effectively serve as a persistent deep link, which can be dereferenced to a digital product passport. This operates efficiently without necessitating any central registries. Apart from this specific product use case, we believe that there are innumerable potential applications where such stable links can be advantageous.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c60f3e68f8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-5-a-deep-dive-into-service-endpoints-and-digital-product-passports-2c60f3e68f8d">The Power of DIDs #5: A Deep Dive into Service Endpoints and Digital Product Passports</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of DIDs #4: Decentralized Web Nodes (DWNs) with Decentralized Identifiers (DIDs)]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-4-decentralized-web-nodes-dwns-with-decentralized-identifiers-did-d3c93148ef7a?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3c93148ef7a</guid>
            <category><![CDATA[decentralized-apps]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[digital-identity]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 08:11:54 GMT</pubDate>
            <atom:updated>2023-06-23T08:08:58.442Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Unleashing the Potential: Empowering the Decentralized Web with DIDs and DWNs</strong></p><p><em>In the digital age, exchanging messages and data between entities is a fundamental part of everyday operations. However, the interfaces and infrastructure used for these exchanges often rely on centralized systems that can be vulnerable to security breaches, infrastructure failure, and data misuse. A move towards a decentralized web is on the horizon, where entities can manage and transact their data with others without reliance on location or provider-specific infrastructure, interfaces, or routing mechanisms. In the fourth episode of our blog series “The Power of DIDs”, we delve into the potential of the combination of DIDs and Decentralized Web Nodes.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FoxUlibQT3yU&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DoxUlibQT3yU&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=google" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1b235a6d8985da42e54340a78a20d8db/href">https://medium.com/media/1b235a6d8985da42e54340a78a20d8db/href</a></iframe><h3>What is a Decentralized Web Node (DWN)?</h3><p>A Decentralized Web Node (DWN) is a data storage and message relay node that entities can use to locate public or private permissioned data related to a given Decentralized Identifier (DID). DWNs form a mesh-like datastore construction that allows an entity to operate multiple nodes that sync to the same state across one another. This design enables the owning entity to secure, manage, and transact their data with others without reliance on location or provider-specific infrastructure, interfaces, or routing mechanisms.</p><h3>How DIDs and DWNs work together</h3><p>Decentralized Identifiers (DIDs) are used for describing the cryptographic keys and other fundamental PKI values linked to a unique, user-controlled, self-sovereign identifier in a target system (e.g., blockchain, distributed ledger). A DID Document Service Endpoint must be present in the DID Document of a target DID for DID Resolution to properly locate the URI for addressing a DID owner’s Decentralized Web Node. As a result, applications and services can use DIDs to discover and connect to DWNs in a trusted way.</p><h3>Try it out!</h3><p>In <a href="https://youtu.be/oxUlibQT3yU">this</a> video Zaïda Rivai explains how to create DIDs with DWN endpoints using <a href="https://godiddy.com/">godiddy.com</a>.</p><p>You can try to resolve various DIDs to DWN endpoints using CURL commands like the following:</p><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:ion:test:EiAvfKgnZHI-L2UZwx0bzq-IXmp_9rFO6uWFwjH1q_9-zg&quot;</pre><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:indy:idunion:test:H5KH5fSyDRRQ8ZCxB4Qpge&quot;</pre><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:ebsi:zkyJ5CdJJ8GePR6gVh964jx&quot;</pre><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:ethr:goerli:0x76b189f703a651c12d9317578188875af6e47376&quot;</pre><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:cheqd:testnet:ae129a39-cd24-4be7-888c-634728ab85cc&quot;</pre><pre>curl -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>     -H &quot;Accept: application/did+ld+json&quot; \<br>     -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:web:did-web.dev.godiddy.com:21271ffa-8b50-4474-8c40-be12fcd2121c&quot;</pre><h3>The Benefits of Using DWNs and DIDs</h3><p>The use of DIDs and DWNs presents several benefits. Here are a few:</p><ol><li><strong>Enhanced Security</strong>: DIDs are unique and user-controlled, providing a strong security layer. Coupled with DWNs, they enhance the privacy and security of data transactions.</li><li><strong>Interoperability</strong>: DWNs are designed to ensure multiple implementations can operate together, making them highly interoperable.</li><li><strong>Decentralization</strong>: Both DIDs and DWNs contribute to the decentralization of the web, reducing reliance on central authorities and mitigating the risk of a single point of failure.</li><li><strong>User Control</strong>: DIDs and DWNs put control in the hands of the user, enabling them to manage their data and transactions without needing to rely on provider-specific infrastructure.</li><li><strong>Scalability</strong>: The ability to operate multiple nodes that sync to the same state across one another allows for scalable data storage and transaction systems.</li></ol><h3>Updating the DID Document</h3><p>One of the pivotal attributes of DIDs is their capacity for modification, especially when it comes to changing the location of a Decentralized Web Node (DWN). Imagine you need to alter your DWN’s location for any number of reasons — perhaps you’ve switched to a different cloud service, or you’re adopting a more resilient infrastructure strategy. The beauty of DIDs is that you don’t need to generate an entirely new identifier in these situations. Instead, you can simply update the service endpoint in the DID document.</p><p>This feature of DIDs streamlines the process of transitioning to a new DWN location, saving you the time and effort of creating a new DID. This feature shows how the system of decentralized identities can easily change and adjust as needed. By allowing easy updates to the service endpoint, DIDs ensure that your digital identity remains resilient, portable, and under your control, even as underlying infrastructure elements evolve.</p><p>Let me show you how that works in practice. I created a DID (did:indy:danube:KnhzAxhka1brsHKqZpDx5F) on the 20th of June at 11:33:05 GMT+2 with a service endpoint “dwn.danubetech.com”:</p><pre>curl  -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>      -H &quot;Accept: application/did+ld+json&quot; \<br>      -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:indy:danube:KnhzAxhka1brsHKqZpDx5F?versionTime=2023-06-20T09:33:07Z&quot;</pre><p>I updated the same DID a few minutes later, changing the endpoint to “dwn.godiddy.com”. You can check with the following curl command, and see that service endpoint has changed:</p><pre>curl  -H &quot;Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0&quot; \<br>      -H &quot;Accept: application/did+ld+json&quot; \<br>      -X GET &quot;https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:indy:danube:KnhzAxhka1brsHKqZpDx5F?versionTime=2023-06-20T09:35:27Z&quot;</pre><p>The same can be observed using the search option in <a href="https://godiddy.com/app/search">https://godiddy.com/app/search</a>.</p><h3>In Conclusion</h3><p>The combination of DIDs and DWNs represents an exciting step forward in the development of a decentralized web. By placing control in the hands of users and removing the need for centralized systems, these technologies promise a future where data security, privacy, and user control are fundamental aspects of our digital interactions.</p><p>The decentralized web — powered by DIDs and DWNs — ushers in a new era of digital interaction. As we continue to develop these technologies and explore their potential, we can expect to see a more secure, user-centric, and decentralized digital landscape in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3c93148ef7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-4-decentralized-web-nodes-dwns-with-decentralized-identifiers-did-d3c93148ef7a">The Power of DIDs #4: Decentralized Web Nodes (DWNs) with Decentralized Identifiers (DIDs)</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of DIDs #3: Client-managed Secret Mode]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-3-client-managed-secret-mode-830fbf9e9d29?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/830fbf9e9d29</guid>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[digitalidentitymanagement]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Tue, 02 May 2023 07:09:12 GMT</pubDate>
            <atom:updated>2023-05-04T10:29:52.663Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Unlocking Decentralization and Privacy with Enhanced Key Management</strong></p><p><em>Welcome to the third post of our “The Power of DIDs” series! In earlier episodes, we </em><a href="https://medium.com/danube-tech/the-power-of-dids-1-did-resolution-d1d994130319"><strong><em>introduced</em></strong></a><em> the fundamentals of DIDs, showcased basic architectures, and </em><a href="https://medium.com/danube-tech/the-power-of-dids-2-creating-dids-5d1820631371"><strong><em>demonstrated</em></strong></a><em> how to create DIDs using internal secret mode, where the registrar and wallet components are co-located. Today, we’ll explore the client-managed secret mode (CMSM) in depth</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FdMeAXkCFCrE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DdMeAXkCFCrE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FdMeAXkCFCrE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/80f9f3eccc3136fb09eba7976c893f73/href">https://medium.com/media/80f9f3eccc3136fb09eba7976c893f73/href</a></iframe><p><strong>Architecture</strong></p><p>In our previous episode, we demonstrated how a client could use a registrar component to communicate with various verifiable data registries in “<em>internal secret mode</em>.” In this mode, the cryptographic keys needed for DID creation are stored in the wallet, which is part of the registrar component itself. We discussed how this approach is less than ideal for decentralization and self-sovereignty. In CMSM, the client interacts with the registrar while keeping the wallet for key operations on the client side, separating DID-specific operations from key operations to enhance decentralization and control over identifiers. In other words, the wallet component, responsible for key operations, is part of the client itself. The client continues to invoke the registrar component using similar inputs and outputs, but all key operations take place on the client side. This setup results in a back-and-forth communication between the client and registrar.</p><p><strong>The process</strong></p><p>The process typically begins with the client requesting the creation of a new DID. The registrar component might respond by instructing the client to generate a key first. Once the client completes this step, it invokes the registrar again, which may then instruct the client to sign a specific payload. Finally, the client invokes the registrar once more, and the DID is created and returned to the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6xmAF5wo2dbB21qoeyLBAg.jpeg" /><figcaption>Figure 1. Client-managed Secret Mode Architecture</figcaption></figure><p>There are two key advantages with using the CMSM:</p><ul><li>The client can be implemented generically, without needing to know anything about DID method-specific aspects.</li><li>The client retains full control over the cryptographic keys.</li></ul><p>Throughout this ongoing process, a field called “Job ID” helps manage the state and track progress between the client and registrar.</p><p>The CMSM architecture offers a powerful solution for enhancing decentralization and self-sovereignty in the DID ecosystem. The registrar handles all DID method-specific functions, such as creating payloads, constructing messages, and interacting with blockchains or web servers, while key operations like generating keys and signing payloads occur on the client side. This approach ensures that clients retain control over their cryptographic keys while benefiting from the registrar component’s expertise in handling DID method-specific functions. By examining the client and registrar components’ interaction within this mode, we can see how it ultimately leads to greater decentralization and control over identifiers. This balance between simplicity and security allows for the development of clients that can support various DID methods without needing to implement method-specific functionality themselves.</p><p><strong>Try it out!</strong></p><p>Try out creating a DID yourself using CMSM at our platform <a href="https://godiddy.com/">godiddy.com</a>. In <a href="https://www.youtube.com/watch?v=dMeAXkCFCrE&amp;t=76s&amp;ab_channel=DanubeTech">this</a> tutorial, our CEO Markus Sabadello explains how to create a DID yourself using CMSM. Documentation can be found <a href="https://docs.godiddy.com/en/advanced/did-registration-methods/ion-clientsecretmode-create">here</a>.</p><p><strong>Conclusion</strong></p><p>In this episode, we explored CMSM, which allows for better decentralization, privacy, and control of identifiers. This approach enables the implementation of clients that support various DID methods without requiring DID method-specific functionality, as all the heavy lifting is performed by the registrar component. This approach is ideal for maintaining decentralization and privacy. In our next episode, we will investigate more fascinating ways to utilize DIDs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=830fbf9e9d29" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-3-client-managed-secret-mode-830fbf9e9d29">The Power of DIDs #3: Client-managed Secret Mode</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of DIDs #2: Creating DIDs]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-2-creating-dids-5d1820631371?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d1820631371</guid>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 07:39:00 GMT</pubDate>
            <atom:updated>2023-04-24T07:39:00.955Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How Creating DIDs Establishes Trust and Enables Digital Identity</strong></p><p><em>As digital interactions grow, trust, security, and privacy become increasingly vital. Decentralized Identifiers (DIDs) offer a novel approach to establishing digital identities without relying on centralized authorities such as governments or corporations. In this blog series, we will delve into all you need to know about DIDs. Today we focus on what sets them apart from other technologies: creating DIDs.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBTpa4OEZ_fE%3Fstart%3D3%26feature%3Doembed%26start%3D3&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBTpa4OEZ_fE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBTpa4OEZ_fE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2865e9ad594a47d0ffb3a3d9e2a0c2b6/href">https://medium.com/media/2865e9ad594a47d0ffb3a3d9e2a0c2b6/href</a></iframe><p>Creating DIDs addresses the fundamental question of forming digital identities and connecting them to physical ones. DIDs arise from a technical process embodying self-sovereignty and independent existence. Unlike traditional digital identifiers, DIDs don’t rely on central authorities or intermediaries. Therefore, instead of being issued by an authority, DIDs are independently generated by a controller, emphasizing their decentralized essence.</p><p><strong>Concept of control</strong></p><p>When creating a DID, the controller generates cryptographic key pairs and performs additional steps. The keys used for creating the DID may not appear in the DID Document, and the key-generating controller might not be the same as the subject the DID refers to. The inherent control associated with DIDs is crucial — the entity that controls the DID also creates it, highlighting the autonomy and self-governance at the heart of decentralized digital identities.</p><p><strong>Creating a DID vs. Resolving a DID</strong></p><p>DID creation shares similarities with resolving a DID, as both follow an abstract process rather than a single, concrete architecture or protocol. If you want to know more about resolving a DID, check out our previous blog post <a href="https://medium.com/danube-tech/the-power-of-dids-1-did-resolution-f6cff47d6010">here</a>. Additionally, DID creation requires specific inputs, outputs, and states. The actual implementation depends on the chosen DID method, which can involve blockchains, webservers, peer-to-peer networks, domain names, or entirely local processes. This flexibility allows for diverse solutions, demonstrating the adaptability of decentralized digital identities to various environments and use cases.</p><p>However, DID creation differs from resolution in its complexity, often requiring multiple steps rather than a single operation. Some DID methods necessitate interaction with an onboarding service or transaction endorser, payment for transactions, or agreement to legal terms. These extra steps, which may include waiting for DID creation, contribute to the process’s complexity. As a result, user interfaces for DID creation must accommodate these interactions and steps, making them more intricate than those for resolving DIDs.</p><p><strong>Architecture</strong></p><p>When discussing the process of creating DIDs, we can adopt a similar model to <a href="https://medium.com/danube-tech/the-power-of-dids-1-did-resolution-f6cff47d6010">DID resolution</a>, involving three components. First, the client, which is an application or server intending to create a new DID. Second, the registrar component performs “create,” “update,” and “deactivate” operations for a DID. Finally, the verifiable data registry (VDR) is where DIDs are created and stored. It’s crucial to note that this is an abstract architecture, which can be implemented and deployed in various ways. The registrar, in particular, is not intended as a separate entity in a legal or business sense; rather, it is a logical component with a separation of concerns. The components can interact locally or through remote APIs, or a combination of both, allowing for different instantiations of this abstract model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U2jk15z0Gc6YfLKaX0hspg.jpeg" /></figure><p>In terms of flows, inputs, and outputs, the client invokes the registrar component, providing a DID method for creating a DID and an (often incomplete) DID document. The determination of the DID typically occurs at the end of the process, rather than being predetermined by the creator. The client also supplies options for controlling aspects of the DID’s creation and may provide access tokens or other secrets, depending on the flow and DID method.</p><p>The registrar handles DID method-specific operations, constructing payloads and interacting with the VDR to write the DID document contents. The process yields a DID and a state, both of which are returned to the client, along with metadata about the process. The state is necessary because creating DIDs involves multiple steps, unlike the single roundtrip in DID resolution. The client may need to interact with the registrar multiple times, with the registrar tracking the current state of the DID creation process. In some cases, the client may need to wait for the DID to be fully established or anchored on the ledger before the registrar can proceed. This state is modeled using a state component, and to maintain state continuity between the client and registrar, a “Job ID” field can be used to keep track of this state.</p><p><strong>Key management</strong></p><p>Key management is the most crucial aspect of creating a DID. Typically, the controller generates key pairs, which are used for creating and writing the DID. In our architectural vision, key operations can occur in various ways, typically within a wallet component. The wallet handling key operations can be part of the registrar component itself, combining DID and key operations in a single component, known as the internal secret mode. Alternatively, a wallet can be an external component that the registrar interacts with for key operations. We believe the preferred approach is the Client-managed Secret Mode mode, where the wallet is on the client side. In this mode, all key operations take place client-side, while the registrar handles DID operations.</p><p><strong>Try it out!</strong></p><p>Try out creating a DID yourself in our platform <a href="https://godiddy.com/">Godiddy.com</a>. In <a href="https://www.youtube.com/">this</a> tutorial, our CEO Markus Sabadello explains how to create a DID yourself. Documentation can be found <a href="https://docs.godiddy.com/en/apis/universal-registrar">here</a>. Also have a look at the <a href="https://identity.foundation/did-registration/">DID Registration specification</a>, which is being developed at the Decentralized Identity Foundation (DIF).</p><p><strong>Next steps</strong></p><p>You might be wondering, “<em>Does using a remote service for creating DIDs and associated keys contradict the idea of decentralization and privacy?</em>” You’re absolutely right! In our next episode, we’ll delve deeper into the client-managed secret mode, which more cleanly separates key operations and DID operations. This approach is better for decentralization and privacy, and we’ll explore its advantages in detail. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d1820631371" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-2-creating-dids-5d1820631371">The Power of DIDs #2: Creating DIDs</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of DIDs #1: DID Resolution]]></title>
            <link>https://medium.com/danube-tech/the-power-of-dids-1-did-resolution-d1d994130319?source=rss-444f5bc4d6fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1d994130319</guid>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <dc:creator><![CDATA[Danube Tech]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 07:26:11 GMT</pubDate>
            <atom:updated>2023-04-24T07:39:29.063Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How It Establishes Trust and Enables Digital Identity</strong></p><p><em>As we interact with the digital world, it becomes increasingly important to ensure trust, security, and privacy. Decentralized Identifiers (DIDs) are a new way to establish a digital identity without relying on centralized authorities such as governments or corporations. In this blog series, we will discuss everything you need to know about DIDs, starting with the most critical feature that DIDs offer: DID Resolution.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fyb9ATkwBFJA%3Fstart%3D1%26feature%3Doembed%26start%3D1&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dyb9ATkwBFJA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fyb9ATkwBFJA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4959e98366ff3616766c752d38e5800c/href">https://medium.com/media/4959e98366ff3616766c752d38e5800c/href</a></iframe><p><strong>What is DID Resolution?</strong></p><p>A DID is a digital address consisting of a string of characters that can refer to subjects in the physical world. The four core properties of DIDs, as defined in the W3C DID Core specification are: permanent, persistent identifiers; it never needs to change, cryptographically verifiable; control over a DID can be proven using cryptography, decentralized; there is no central registration authority required, and last, <strong>resolvable</strong>.</p><p>DID resolution is the process of obtaining a DID document or technical metadata for a given DID. This might sound dry or boring at first, but it is actually a crucial step. DID resolution establishes the link between physical identity and digital identity. This makes it possible to establish higher-level concepts such as reputation and trust. DID resolution enables us to share messages and data, establish connections and relationships and interact in and with the digital world.</p><p><strong>DIDs and other applications</strong></p><p>DID Resolution is a fundamental piece of functionality that enables a lot of higher-level protocols applications, and services. The information returned by DID Resolution can be used for various purposes, including:</p><ul><li>Verifiable Credentials (VCs); looking up a public key to verify a digital signature from the Issuer of a Verifiable Credential. This is required in an exchange of a VC between Holders, Issuers and Verifiers.</li><li>Establishing DIDComm connections or engaging in OpenID Connect transactions; obtaining the cryptographic data needed to establish authenticity, security and encryption of the transactions.</li><li><a href="https://identity.foundation/decentralized-web-node/spec/">Decentralized Web Nodes</a> or connecting to agents; discovering the (service) endpoints for interacting via secure protocols thereby making these connection possible.</li></ul><p><strong>Architecture</strong></p><p>DID Resolution has three components in the technical architecture: the client, the DID resolver, and the Verifiable Data Registries (VDRs). A client invokes the resolver. The resolver’s task is to look up the associated DID document from the Verifiable Data Registry, according to the DID method. Looking up a DID is method-specific, implying that the design of the individual DID methods determine how the process of looking up a DID works; defining the syntax of the DID and how to get from the DID to the DID document. DID documents are stored in plain text (on Verifiable Data Registries such as blockchains, or simply downloaded from a server or API), or are constructed from more dynamic virtual data structures, which require more complex DID resolution processes. The crucial part to understand here is that DID Resolution is not confined to <em>one single protocol</em>, unlike DNS or HTTP. It includes an <em>abstraction layer</em> that makes it possible to resolve any given DID to a document in many different ways, not only using blockchains, distributed ledgers, or databases, but also involving web servers or simple local processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-e-vHIqza_5Tel1ueqMcGw.jpeg" /></figure><p><strong>Interaction between the client and the DID resolver</strong></p><p>A similar abstract interface exists for the interaction between the client and the DID resolver. Unlike DNS, when the client invokes the resolver, there is no concrete way or specific client-server protocol. The client can invoke the resolver and transmit the DID, plus additional resolution options, in the request to the resolver. This could be a local process (by calling a local native library including in the same piece of software) or a remote service (by connecting to a remote DID resolver over protocols such as HTTPs or DIDComm).</p><p><strong>Additional functionalities of the DID resolver</strong></p><p>Various resolution options can be used to pass additional instructions to a DID resolver and control its behavior. For example, this makes it possible to transform the DID document between different representations (e.g. JSON-LD or CBOR), support different key formats (e.g. Base58 or JWK or Multibase), instruct the resolver to enable or disable caching, or perform some extra validation steps before returning to the client. And in addition to the DID document itself, the resolver can also return metadata about both the DID document and the resolution process, which can be useful in various ways.</p><p>This gives DID Resolution a lot of room for additional functionalities and innovation!</p><p><strong>Try it out</strong></p><p>To try out DID Resolution yourself, see the following resources:</p><ul><li><a href="http://godiddy.com/">Godiddy.com</a> documentation about DID Resolution: <a href="https://docs.godiddy.com/en/apis/universal-resolver">https://docs.godiddy.com/en/apis/universal-resolver</a></li><li>DIF Universal Resolver: <a href="https://dev.uniresolver.io/">https://dev.uniresolver.io/</a></li></ul><p><strong>Summary</strong></p><p>DID Resolution is a critical feature of DIDs that enables a lot of higher-level protocols, applications, and services. The architecture of DID Resolution includes the client, the DID resolver, and the Verifiable Data Registries. DID Resolution involves an <em>abstraction layer</em>, making it possible to resolve the DID document in many different ways.</p><p>As we move towards an increasingly digital world, the issue of digital identity has become more pressing. How can we establish and maintain trustworthy digital identities that provide us with privacy, security, and control? Decentralized Identifiers, or DIDs, hold the answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1d994130319" width="1" height="1" alt=""><hr><p><a href="https://medium.com/danube-tech/the-power-of-dids-1-did-resolution-d1d994130319">The Power of DIDs #1: DID Resolution</a> was originally published in <a href="https://medium.com/danube-tech">Danube Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>