<?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 Markus Sabadello on Medium]]></title>
        <description><![CDATA[Stories by Markus Sabadello on Medium]]></description>
        <link>https://medium.com/@markus.sabadello?source=rss-87130a922e66------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dBtzMe0abHEBPOvTRlu6Cw.jpeg</url>
            <title>Stories by Markus Sabadello on Medium</title>
            <link>https://medium.com/@markus.sabadello?source=rss-87130a922e66------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 11:55:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@markus.sabadello/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[JSON-LD VCs are NOT “just JSON”]]></title>
            <link>https://medium.com/@markus.sabadello/json-ld-vcs-are-not-just-json-4488d279be43?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/4488d279be43</guid>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[data-integrity]]></category>
            <category><![CDATA[json-web-signature]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Sat, 14 Oct 2023 02:24:40 GMT</pubDate>
            <atom:updated>2023-10-14T02:26:04.028Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Experiments with JSON-LD VC payloads secured by JWS vs. Data Integrity</strong><br>Detailed results: <a href="https://github.com/peacekeeper/json-ld-vcs-not-just-json">https://github.com/peacekeeper/json-ld-vcs-not-just-json</a></p><p>In the world of Verifiable Credentials (VCs), it can be hard to keep track of various evolving formats and data models. A potpourri of similar-sounding terms can be found in specification documents, mailing lists and meeting notes, such as VCDM, VC-JWT, VC-JWS, JWT VCs, SD-JWT, SD-JWT-VC, SD JWS, VC JOSE COSE, SDVC, JsonWebSignature2020, etc.</p><p>Also, statements like the following can frequently be found in discussions:</p><ul><li>“Can we make @context optional. It’s simpler and not always needed.”</li><li>“If you don’t want to use @context and just ignore it, you could.”</li><li>“You can secure a JSON-LD VC using JWT.”</li><li>“You can use SD-JWT for any JSON payload, including JSON-LD.”</li><li>“JSON-LD is JSON.”</li></ul><p>One concrete question related to this is what it means if a VC using the JSON-LD-based W3C VC Data Model is secured by proof mechanisms that were designed without JSON-LD in mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*Y4kuIj4VHie1pmf1lBXTlQ.png" /></figure><h3>Experimentation</h3><p>To explore this, I conducted two experiments to describe what happens if you take a JSON-LD document based on the W3C VC Data Model, and you secure it once with <a href="https://w3c.github.io/vc-jose-cose/">JWS</a>, and once with <a href="https://w3c.github.io/vc-data-integrity/">Data Integrity</a>. The former signs the document, while the latter signs the underlying RDF graph of the document. The part where this gets interesting is the JSON-LD @context. For JWS, only the contents of the document matter. For Data Integrity, the contents of the @context matter as well. The two proof mechanisms have a rather different understanding of the “payload” that is to be secured.</p><h3>Experiment #1: Data Integrity changes, JWS doesn’t</h3><p>In the first experiment, we start with a JSON-LD document named <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/examples/example1a.input">example1a.input</a>. This document references a JSON-LD @context <a href="https://example.com/context1/,">https://example.com/context1/,</a> and the contents of that @context are as in the file <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/contexts/context1a.jsonld">context1a.jsonld</a>.</p><p>In a subsequent variation of this, we start with another JSON-LD document named <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/examples/example1b.input">example1b.input</a>, which is equivalent to the above example1a.input. This document also references the same JSON-LD @context <a href="https://example.com/context1/,">https://example.com/context1/,</a> but now, the contents of that @context are as in the file <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/contexts/context1b.jsonld">context1b.jsonld</a>, which is different from the file context1a.jsonld that was used above.</p><p>The result: If the contents of the JSON-LD @context change, even if the JSON-LD document stays the same, the Data Integrity signature also changes, whereas the JWS signature doesn’t change. This also means that verifying a Data Integrity signature would fail, whereas verifying a JWS signature would succeed.</p><h3>Experiment #2: JWS changes, Data Integrity doesn’t</h3><p>In the second experiment, we start with a JSON-LD document named <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/examples/example2a.input">example2a.input</a>. This document references a JSON-LD @context <a href="https://example.com/context2a/,">https://example.com/context2a/,</a> and the contents of that @context are as in the file <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/contexts/context2a.jsonld">context2a.jsonld</a>.</p><p>In a subsequent variation of this, we start with another JSON-LD document named <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/examples/example2b.input">example2b.input</a>, which is different from the above example2a.input. The difference is that the first document used the term “givenName”, while the second document uses the term “firstName”. The second document references a different JSON-LD @context <a href="https://example.com/context2b/,">https://example.com/context2b/,</a> and the contents of that @context are as in the file <a href="https://github.com/peacekeeper/json-ld-not-just-json/blob/main/contexts/context2b.jsonld">context2b.jsonld</a>, which is different from the file context2a.jsonld that was used above. The difference is that the first @context defines the term “givenName”, while the second @context defines the term “firstName”, however, they define them using the same URI, i.e. with equivalent semantics.</p><p>The result: Despite the fact that the JSON-LD document changes, the Data Integrity signature doesn’t change, whereas the JWS signature changes. This is because Data Integrity “understands” that even though the document has changed, the semantics of the RDF graph are still the same. JWS on the other hand “sees” only the JSON-LD document, not the semantics behind it. This also means that verifying a Data Integrity signature would succeed, whereas verifying a JWS signature would fail.</p><h3>Conclusion</h3><p>Depending on your perspective, you could interpret the results in different ways. You could call Data Integrity insecure, since it depends on information outside the JSON document. You could also call JWS insecure, since it fails to secure the JSON-LD data model.</p><p>The real point of this article is however NOT to say that any of the mentioned data models or proof mechanisms are inherently insecure, but rather to raise awareness of the nuances. To say “JSON-LD is JSON” is correct on the document layer, and wrong on the data model layer. Certain combinations of data models and proof mechanisms can lead to surprising results, if they are not understood properly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4488d279be43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transatlantic SSI Interop]]></title>
            <link>https://medium.com/@markus.sabadello/transatlantic-ssi-interop-52bac6be8dfe?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bac6be8dfe</guid>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Mon, 17 Jan 2022 21:12:23 GMT</pubDate>
            <atom:updated>2022-01-18T15:53:44.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, there are more and more initiatives working on decentralized identity infrastructures, or Self-Sovereign Identity (SSI). However, there is a big paradox underlying all those initiatives: Even though they often use the same technical specifications , e.g. W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs), they are in practice usually not compatible. There are just too many details where technological choices can diverge. Yes we all use DIDs and VCs. But do we use Data Integrity Proofs (formerly called Linked Data Proofs) or JWT Proofs? JSON-LD contexts or JSON schemas, or both? Do we use DIDComm (which version?), or CHAPI, or one of the emerging new variants of OpenID Connect? Which one of the many revocation mechanisms? Which DID methods? How do we format our deep links and encode our QR codes?</p><p>We all want to build the missing identity layer for the Internet, where everything is interoperable just like on the web. But we all do it in slightly different ways. So how can we solve this paradox? Do we create yet another interoperability working group?</p><p>No! We try out simple steps and make them work. We conduct concrete experiments that bridge gaps and cross borders. In this case, we planned and executed an experiment that demonstrates interoperability between prominent decentralized identity initiatives in the EU and the US, funded by the <a href="https://ngiatlantic.eu/">NGIatlantic.eu</a> program. Two companies collaborated on this project: <a href="https://danubetech.com/">Danube Tech (EU)</a> and <a href="https://digitalbazaar.com/">Digital Bazaar (US)</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*euJitbyUrukHH4tW6rsyGw.png" /><figcaption>EU-US collaboration on decentralized identity</figcaption></figure><p>In the EU, the <a href="https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/EBSI">European Blockchain Service Infrastructure (EBSI)</a> is building an ambitious network that could become the basis for a digital wallet for all EU citizens. In the US, the <a href="https://www.dhs.gov/science-and-technology/blockchain-portfolio">Department of Homeland Security‘s Silicon Valley Innovation Program (SVIP)</a> is working with companies around the world on personal digital credentials as well as trade use cases. Both projects have developed easy-to-understand narratives (student “Eva” in EBSI, immigrant “Louis” in SVIP). Both narratives are described further in the W3C’s DID Use Cases document (<a href="https://w3c.github.io/did-use-cases/#digitalPRC">here</a> and <a href="https://w3c.github.io/did-use-cases/#publicAuthorityCredentials">here</a>). So we thought, let’s conduct an experiment that combines narratives and technological elements from both the EU and US sides!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Un-evzcojZ0ba3RrWSe-2A.png" /><figcaption>SVIP (left side) and EBSI (right side)</figcaption></figure><p>We built and demonstrated two combined stories:</p><ol><li>Eva studied in the EU and would then like to apply for a US visa. In this story, there is an EU-based Issuer of a VC, and a US-based Verifier.</li><li>Louis is an immigrant in the US and would like to apply for PhD studies at an EU university. In this story, there is a US-based Issuer of a VC, and an EU-based Verifier.</li></ol><p>For a walkthrough video, see: <a href="https://youtu.be/1t9m-U-3lMk">https://youtu.be/1t9m-U-3lMk</a></p><p>For a more detailed report, see: <a href="https://github.com/danubetech/transatlantic-ssi-interop/">https://github.com/danubetech/transatlantic-ssi-interop/</a></p><p>In the broader decentralized identity community, both the EU- and US-based initiatives currently have strong influence. EBSI’s main strength is its ability to bring together dozens of universities and other organizations to build a vibrant community of VC Issuer and Verifiers. SVIP’s great value has been its continuous work on concrete test suites and interoperability events (“plugfests”) that involve multiple heterogeneous vendor solutions.</p><p>In this project, we used <a href="https://gitlab.grnet.gr/essif-lab/infrastructure_2/danubetech/SSI_Java_Libraries_project_summary">open-source libraries</a> supported by ESSIF-Lab, as well as the <a href="https://github.com/decentralized-identity/universal-resolver">Universal Resolver</a> project from the Decentralized Identity Foundation (DIF). We also used various components supplied by Digital Bazaar, such as the Veres Wallet.</p><p>We hope that our “Transatlantic SSI Interop” experiment can serve as an inspiration and blueprint for further work on interoperability not only between different DID methods and VC types, but also between different vendors, ecosystems, and even continents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_BX7OYoN9d039LiQWX7yw.png" /><figcaption>Wallet containing an EU Diploma and US Permanent Resident Card</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bac6be8dfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Report from EBSI4Austria]]></title>
            <link>https://medium.com/@markus.sabadello/report-from-ebsi4austria-b79c0ed8ab8d?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/b79c0ed8ab8d</guid>
            <category><![CDATA[ebsi]]></category>
            <category><![CDATA[ssi]]></category>
            <category><![CDATA[danube-tech]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Thu, 16 Dec 2021 13:17:05 GMT</pubDate>
            <atom:updated>2022-01-09T14:03:56.200Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2018, all European member states, together with Norway and Lichtenstein, signed a declaration stating the joint ambition to take advantage of blockchain technology. These 29 countries founded the European Blockchain Partnership (EBP), and within this partnership, they decided to build the so-called European Blockchain Services Infrastructure (EBSI).</p><p>EBSI was created aiming to, on the one hand, provide blockchain capabilities used by the partner of the EPB to implement and realize blockchain projects and use cases within these countries. Moreover, on the other hand, to achieve certain use cases on a European level. The so-called use case groups were defined and present the working groups related to a specific use case to support the latter idea. These use case groups consist of representatives of the EBP member counties, domain experts as well as the European Commission.</p><p>Initially, four use case groups were founded, namely the European Self-Sovereign Identity Framework (ESSIF), the diploma use case, document traceability, and secure document transfer. ESSIF focuses on digital identities where the user is in control over her identity data. The diploma use case focuses on educational diplomas of students and related processes such as issuing, verifying, revocation, and all of these processes in cross-border scenarios. Document traceability considers the anchoring of document-related identifiers like hashes on the blockcahin and secure document sharing on tax-related information transfer.</p><p>EBSI defined so-called use case groups that should be achieved using the provided capabilities to showcase their functionality and bring in expertise in the specific fields. Each use case group consists of representatives of the member states, domain experts, and the European Commission.</p><h3>About EBSI4Austria</h3><p>EBSI4Austria is a CEF funded project with two main objectives. First, EBSI4Austria aims to set up, operate and maintain the Austrian’s EBSI node. Second, we pilot the diploma use case on the Austrian level supported by two Universities and data providers as well as verifiers.</p><p>EBSI created a so-called early adopter program to speed up the use case integration of the participating countries. EBSI4Austria joined this ambiguous program already in the first wave reflecting our project’s motivation.</p><h3>Partners</h3><p>EBSI4Austria consists of three partners, namely two Universities such as <a href="https://www.tugraz.at/"><strong>Graz University of Technology (TU Graz)</strong></a> and the <a href="https://www.wu.ac.at/"><strong>Vienna University of Economics (WU Vienna)</strong></a><strong>,</strong> together with <a href="https://danubetech.com/"><strong>Danube Tech</strong></a>, a Vienna based company that provides leading expertise in Self-Sovereign Identity (SSI) as well as distributed systems and is involved in related standardization bodies. The Universities are responsible for issuing students’ diplomas and also verifying them. Austrian’s EBSI node is set up and operated at the department eGovernment innovation center (EGIZ), which is part of Graz University of technology.</p><h3>User Story</h3><p>Figure 1 illustrates the user story that is covered in our project. A student studying at the Graz University of Technology is finishing her bachelor’s program. TU Graz issues her diploma credential stating her bachelor’s degree, which the student stores in her wallet. Next, she wants to apply for a master’s program at the Vienna University of Economics and Business; thus, she presents her bachelor’s diploma credential. After successfully finishing her master’s program at WU Vienna, the university issues her master’s diploma credential to the student. The student is very ambitious; therefore, she applies for a Ph.D. position at the Berlin Institute of Technology by presenting her diplomas. All involved parties utilize the EBSI blockchain network to verify if the issuing universities are trusted issuers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bB_7YXmgH5F5TeNy0ZPnqA.png" /><figcaption><em>Figure 1: User Story of the Diploma Use Case</em></figcaption></figure><h3>Technology</h3><p>In order to implement our EBSI4Austria project, we used similar technologies as many other Self-Sovereign Identity (SSI) initiatives, i.e., based on building blocks such as Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).</p><p>We created two DIDs on the EBSI blockchain for the two universities, as follows:</p><ul><li>Test DID for TU Graz: <a href="https://dev.uniresolver.io/#did:ebsi:zuoS6VfnmNLduF2dynhsjBU">did:ebsi:zuoS6VfnmNLduF2dynhsjBU</a></li><li>Test DID for WU Vienna: <a href="https://dev.uniresolver.io/#did:ebsi:z23EQVGi5so9sBwytv6nMXMo">did:ebsi:z23EQVGi5so9sBwytv6nMXMo</a></li></ul><p>In addition, we registered them in EBSI’s Trusted Issuer Registry (TIR).</p><p>We also designed Verifiable Credentials to model digital versions of university diplomas. We implemented them using different credential and proof formats to accommodate changing requirements and guidelines in the EBSI specifications throughout the year. See here for some examples in different formats:</p><p>Example Diploma by TU Graz:</p><ul><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-tu-graz.jsonld">JSON-LD+LD-Proofs</a></li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-tu-graz.jsonldjwt">JSON-LD+JWT</a> (also see <a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-tu-graz.jsonldjwt.payload">JWT payload only</a>)</li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-tu-graz.jwt">JSON+JWT</a> (also see <a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-tu-graz.jwt.payload">JWT payload only</a>)</li></ul><p>Example Diploma by WU Wien:</p><ul><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/master_beispiel_de.png">Paper version</a> (in German)</li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/master_beispiel_en.png">Paper version</a> (in English)</li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-wu-wien.jsonld">JSON-LD+LD-Proofs</a></li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-wu-wien.jsonldjwt">JSON-LD+JWT</a> (also see <a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-wu-wien.jsonldjwt.payload">JWT payload only</a>)</li><li><a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-wu-wien.jwt">JSON+JWT</a> (also see <a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/verifiablecredentials/diploma-wu-wien.jwt.payload">JWT payload only</a>)</li></ul><p>We also designed our own (experimental) JSON-LD context in order to be able to work with Linked Data Proofs (see <a href="https://github.com/danubetech/ebsi4austria-examples/blob/main/context/essif-schemas-vc-2020-v1.jsonld">essif-schemas-vc-2020-v1.jsonld</a>). In our opinion, it would be preferable if JSON-LD contexts were provided by EBSI to all member states instead of having to do this separately for each EBSI pilot project.</p><p>We use the following technologies in our project:</p><ul><li><a href="https://uniresolver.io/">Universal Resolver</a> → For resolving DIDs.</li><li><a href="https://uniregistrar.io/">Universal Registrar</a> → For creating DIDs.</li><li><a href="https://uniissuer.io/">Universal Issuer</a> → For issuing VCs.</li><li><a href="https://univerifier.io/">Universal Verifier</a> → For verifying VCs.</li><li><a href="https://gitlab.grnet.gr/essif-lab/infrastructure_2/danubetech/SSI_Java_Libraries_project_summary">SSI Java Libraries</a></li><li><a href="https://github.com/weboftrustinfo/ld-signatures-java">ld-signatures-java</a> — For Linked Data Signatures.</li><li><a href="https://github.com/danubetech/verifiable-credentials-java">verifiable-credentials-java</a> — For Verifiable Credentials.</li></ul><p>We set up the following demonstration websites:</p><ul><li><a href="https://tugraz.ebsi4austria.danubetech.com/">https://tugraz.ebsi4austria.danubetech.com/</a> — Issuer demo website</li><li><a href="https://wuwien.ebsi4austria.danubetech.com/">https://wuwien.ebsi4austria.danubetech.com/</a> — Verifier demo website</li></ul><p>See <a href="https://github.com/danubetech/ebsi4austria-examples">this Github repository</a> for additional technical details about EBSI4Austria.</p><h3>Multi-University Pilot</h3><p>Within EBSI’s early adopter program, EBSI4Austria also joined the multi-university pilot (MU pilot) in which the focus is on issuing and verifying student diplomas between universities but in this case, even in a cross-border scenario. This multi-university pilot should underpin the possibilities even across countries.</p><p>While working on the MU pilot, we participated in several EBSI Early Adopter program meetings to identify issuers, verifiers, and types of credentials. We were in contact with members of Spanish EBSI pilot projects (especially from the SSI company Gataca), to compare our approaches to EBSI DIDs and Verifiable Credentials. We had several technical discussions and email exchanges regarding details of those credentials, e.g. about the JSON-LD contexts and exact proof formats we were planning to use. During these exchanges, we were able to exchange initial examples of verifiable credentials and verify them.</p><p>Within one of the “clusters” of the EBSI MU pilot, we also collaborated closely with the “UniCert” aka “EBSI4Germany” project led by the Technical University of Berlin, a member of the EBSI early adopter program and the German IDunion consortium. This collaboration proved to be particularly interesting for the following reasons:</p><p>1. Since TU Berlin participates both in EBSI and IDunion, they have unique insights into the similarities and differences between these different SSI networks.</p><p>2. TU Berlin was also able to share some experiences regarding the use of existing standards such as Europass and ELMO/EMREX, which can help with semantic interoperability of Verifiable Credentials use in EBSI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7PKtHquuVS6JdXau28rVQ.png" /><figcaption><em>Figure 2: Multi-university pilot scenario.</em></figcaption></figure><p>Note: This blog post was co-authored by Andreas Abraham (<a href="https://www.egiz.gv.at/">eGovernment Innovation Center</a>) and Markus Sabadello (<a href="https://danubetech.com/">Danube Tech</a>). The EBSI4Austria project was funded under agreement No INEA/CEF/ICT/A2020/2271545.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NZsc9LVVS9ySUUxPkOagPw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b79c0ed8ab8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Universal Resolver Infrastructure]]></title>
            <link>https://medium.com/decentralized-identity/the-universal-resolver-infrastructure-395281d2b540?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/395281d2b540</guid>
            <category><![CDATA[dif-working-groups]]></category>
            <category><![CDATA[dif]]></category>
            <category><![CDATA[did-method]]></category>
            <category><![CDATA[universal-resolver]]></category>
            <category><![CDATA[dif-id-wg]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Thu, 30 Jul 2020 18:30:42 GMT</pubDate>
            <atom:updated>2020-08-04T09:01:09.344Z</atom:updated>
            <content:encoded><![CDATA[<h4>A DIF-hosted resource for community development</h4><h3>Introduction</h3><p>It has been almost three years since DIF began working on the <a href="https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c">Universal Resolver</a> (GitHub: <a href="http://github.com/decentralized-identity/universal-resolver">Universal Resolver) </a>— a foundational piece of infrastructure for the Decentralized Identity ecosystem (see the <a href="https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c">original announcement</a>). Since then, our vision of being interoperable across ledgers and DID methods has seen a lot of support. Thanks to community contributions, the Universal Resolver now supports around 30 different DID methods.</p><p>Today, we are happy to announce an updated set of instances where the Universal Resolver is deployed. One stable and one experimental version will be iterated, maintained, and hosted by DIF as a service to the community!🎉</p><p>While this is undoubtedly a useful resource for research, experimentation, testing, and development, it is important that it not be mistaken for a <strong>production-grade</strong> universal resolver. It should be pointed out that:</p><ul><li>This infrastructure is <strong>neither intended or approved for production use cases </strong>and that <em>nobody should </em><strong><em>rely </em></strong><em>on it for anything other than for development and testing purposes</em>.</li><li>These two specific deployments are <strong>not production-ready.</strong> The preferred scenario continues to be that all DID-based information systems, run by a method operator or otherwise, production or otherwise, <strong>host their own instance </strong>of the Universal Resolver (or other DID Resolution tools).</li><li>DIF withholds the right to <strong>limit or modify </strong>the performance of this free service in case usage for production, commercial, and/or malicious purposes is detected.</li></ul><h3>Two Deployments</h3><p>The following two deployments are now available as a community service:</p><p>* <a href="https://resolver.identity.foundation/">https://resolver.identity.foundation/</a> — Hosted on <strong>IBM Cloud </strong>by <strong>DIF </strong>(thanks <strong>IBM</strong>!). While not considered production-ready, this instance is expected to be relatively stable. It will be tested before and after manual updates from time to time, with versioned releases.<br>* <a href="https://dev.uniresolver.io/">https://dev.uniresolver.io/</a> — Hosted on <strong>AWS </strong>by <strong>DIF</strong>. This instance is more experimental, will be updated frequently, and is connected to CI/CD processes. It may be down from time to time or have unexpected functionality changes.</p><p><strong>Note:</strong> For backward compatibility, the original URL <a href="https://uniresolver.io/">https://uniresolver.io/</a> will now redirect to <a href="https://dev.uniresolver.io/">https://dev.uniresolver.io/</a>.</p><h3>Documentation</h3><p>See the following links for more information about testing, release, and deployment processes of the Universal Resolver:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*XIWpNbmM0LVUCzY3" /><figcaption>Photo by <a href="https://unsplash.com/@polarmermaid">Anne Nygård</a></figcaption></figure><ul><li>AWS Architecture: <a href="https://github.com/decentralized-identity/universal-resolver/blob/master/docs/dev-system.md">https://github.com/decentralized-identity/universal-resolver/blob/master/docs/dev-system.md</a></li><li>CI/CD Process: <a href="https://github.com/decentralized-identity/universal-resolver/blob/master/docs/continuous-integration-and-delivery.md">https://github.com/decentralized-identity/universal-resolver/blob/master/docs/continuous-integration-and-delivery.md</a></li><li>Branching Strategy: <a href="https://github.com/decentralized-identity/universal-resolver/blob/master/docs/branching-strategy.md">https://github.com/decentralized-identity/universal-resolver/blob/master/docs/branching-strategy.md</a></li><li>Release process: <a href="https://github.com/decentralized-identity/universal-resolver/blob/master/docs/creating-releases.md">https://github.com/decentralized-identity/universal-resolver/blob/master/docs/creating-releases.md</a></li><li>Periodically, this standing work item is discussed in the <a href="https://identity.foundation/working-groups/identifiers-discovery.html">Identifiers and Discovery Working Group</a>, so that group’s recorded meetings and discussions on Slack and <a href="https://dif.groups.io/g/id-wg">mailing list</a> may contain further insight on the above topics.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=395281d2b540" width="1" height="1" alt=""><hr><p><a href="https://medium.com/decentralized-identity/the-universal-resolver-infrastructure-395281d2b540">The Universal Resolver Infrastructure</a> was originally published in <a href="https://medium.com/decentralized-identity">Decentralized Identity Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DIF ID WG: Starting work on cryptographic secret recovery]]></title>
            <link>https://medium.com/decentralized-identity/dif-id-wg-starting-work-on-cryptographic-secret-recovery-204117b6a2ab?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/204117b6a2ab</guid>
            <category><![CDATA[dif-working-groups]]></category>
            <category><![CDATA[code-donation]]></category>
            <category><![CDATA[key-recovery]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Wed, 27 May 2020 12:46:41 GMT</pubDate>
            <atom:updated>2020-07-17T14:56:51.925Z</atom:updated>
            <content:encoded><![CDATA[<h3>DIF I&amp;D WG: Starting work on cryptographic secret recovery</h3><p>One of the most important challenges that remain in decentralized identity architecture is the key management. The whole point of a <a href="https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf">Decentralized Public Key Infrastructure</a> (which is the underlying paradigm that has led to the development of Decentralized Identifiers and many other related technologies) is that individuals, organizations, and things create and manage their own cryptographic keys without reliance on a central authority or intermediary. But as we know, with great power comes great responsibility — in this case, while we have the power to wield private keys that control DIDs, we can also lose everything connected to those DIDs if we can’t retain and secure them. By definition, in a decentralized identity system, there is no centralized service to provide an “I forgot my password” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*4aae6QJN1jqTLYvd" /><figcaption>Photo by <a href="https://unsplash.com/@thisusuallyworks">Richard Payette</a></figcaption></figure><p>That is the starting condition. It is certainly possible to build safeguards and recovery mechanisms into a decentralized identity system. Such mechanisms can be as simple as creating a backup of a wallet that holds cryptographic keys or writing down a seed number on a piece of paper. Many key recovery techniques that are popular in the cryptocurrency community can also be applied to decentralized identity. Some of the better-known approaches are <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki">mnemonic seed phrases</a> or <a href="https://en.wikipedia.org/wiki/Shamir%27s_Secret_Sharing">Shamir’s Secret Sharing</a> algorithm.</p><p>Despite the existence of approaches to make key recovery simpler and better, there is still much need for innovation. This is the reason why the <a href="https://identity.foundation/working-groups/identifiers-discovery.html">DIF Identifiers &amp; Discovery Working Group</a> is excited to announce an open call for contributions and development of new secret recovery schemes, and implementations. To kick off work in this area, Microsoft, a member of the DIF I&amp;D WG, will be contributing a scheme called ‘Fuzzy Vault,’ which incorporates many desirable, human-friendly features into a single recovery scheme. Daniel Buchner of Microsoft will be posting soon to detail their contribution to the ‘Fuzzy Vault’ scheme to this DIF I&amp;D WG initiative. The whitepaper for the ‘Fuzzy Vault’ scheme will be published in this DIF repository: <a href="https://github.com/decentralized-identity/fuzzy-vault">https://github.com/decentralized-identity/fuzzy-vault</a>. The code implementation and any specifications required for ‘Fuzzy Vault’ will be developed within the DIF I&amp;D WG.</p><p>Another approach DIF participants have worked on is a mnemonic scheme encoded as a 3D experience, called Seed Quest. This scheme uses geo-temporal-spatial inputs, which are more human-friendly than traditional word inputs. The scheme provides 128 bits of entropy for seed recovery with a mnemonic sequence that requires minimal rehearsal: <a href="https://github.com/reputage/seedQuest">https://github.com/reputage/seedQuest</a>. DIF members have recently discussed ways to combine these schemes to maximize UX and recoverability.</p><p>These two efforts are just the beginning of DIF’s work in the area of secret retention and recovery. We encourage everyone to contribute their ideas, code, and insights to this vital work. For more information about participating in this new initiative, and the DIF I&amp;D WG in general, view its <a href="https://docs.google.com/document/d/1gV99R7G2bUlRerxznyd0ucwWPfc1v2F2gQVaTawIPYI/">Meeting Page</a>, read the group’s <a href="https://drive.google.com/open?id=1llda8Vv4AQ-RVNUj-Bv354x6-1P5tbBt">Charter</a>, and join DIF!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=204117b6a2ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/decentralized-identity/dif-id-wg-starting-work-on-cryptographic-secret-recovery-204117b6a2ab">DIF ID WG: Starting work on cryptographic secret recovery</a> was originally published in <a href="https://medium.com/decentralized-identity">Decentralized Identity Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DIDs are PIDs: Report from PIDapalooza]]></title>
            <link>https://medium.com/@markus.sabadello/dids-are-pids-report-from-pidapalooza-415fb8be0886?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/415fb8be0886</guid>
            <category><![CDATA[did]]></category>
            <category><![CDATA[identifier]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Sat, 16 Feb 2019 14:43:13 GMT</pubDate>
            <atom:updated>2019-02-27T05:15:39.221Z</atom:updated>
            <content:encoded><![CDATA[<p>Some time last summer, our community around Self-Sovereign Identity (SSI) and <a href="https://w3c-ccg.github.io/did-spec/">DIDs</a> made a fascinating discovery: <a href="https://pidapalooza.org/">PIDapalooza</a>, a conference whose tag line is “open identifiers deserve their own festival”.</p><p>We were immediately puzzled and intrigued at the same time — how was it possible that there was an entire community dedicated to PIDs (persistent identifiers) that our community around DIDs (decentralized identifiers) has not heard of before? A community that was obviously working on very similar concepts but so far has had zero overlap with ours? So, three of us DID people (Pam Dingle, Kaliya Young, and myself) independently submitted proposals to present on DIDs at the PIDapalooza conference in Dublin. Kaliya’s talk titled “DIDs are PIDs” was chosen by the organizers, but for logistical reasons I ended up going there instead. And I’m happy I had this opportunity!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Mq2SIP9rbWzDzI646avuw.jpeg" /><figcaption>Yes! Open identifiers deserve their own festival!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18CLcwNMBIIwuAumkqkyBg.jpeg" /><figcaption>The conference started with a ceremony to “light the eternal flame”, symbolizing persistence.</figcaption></figure><p>What a fun experience. I received a warm welcome, had some great conversations, and learned the following about the PID community:</p><ul><li>This community consists mostly of researchers from a wide variety of fields. They use different types of PIDs to identify objects that are of interest in their particular area, such as proteins, asteroids, neutrons, and many other things.</li><li>In addition, they use PIDs to identify scientific publications such as books, journals, or reports.</li><li>Finally, they also use PIDs to uniquely identify individuals such as researchers or employees.</li></ul><p>They have a quite mature set of technologies which they apply to the above use cases, including <a href="https://orcid.org/">ORCID</a> (PIDs for individuals), <a href="http://www.handle.net/">Handle.Net</a> in conjunction with <a href="https://www.doi.org/">DOI</a> (PIDs for publications), <a href="https://n2t.net/e/ark_ids.html">ARK IDs</a> (PIDs for both digital and physical objects), and others. They also have various tools for registering and resolving these identifiers, e.g. <a href="http://identifiers.org/">Identifiers.org</a> and <a href="https://n2t.net/">N2T</a>.</p><p>All of these PID systems are based on either DNS or other kinds of central or hierarchical registries. Some of them support various types of delegation. None of them are fully decentralized, and they would not qualify as “self-sovereign” the way we are designing DIDs. That’s okay! Different use cases require different technologies.</p><p>My conclusion was that DIDs are indeed PIDs, but due to their decentralized nature they are different from other kinds of PIDs that the PIDapalooza community has been using. I would describe the relationships as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJkPg-27xqbQEeXCFcReiQ.png" /><figcaption>DIDs are PIDs</figcaption></figure><p>The most interesting conversation I had at the conference was on how to bridge identifier systems; for example, how could DIDs be used within existing PID infrastructure. One example is to add DID support to a PID meta-resolver such as the one at <a href="http://identifiers.org/">Identifiers.org</a>. I reached out to the administrators of that resolver, and indeed, that tool can now resolve DIDs by delegating the <strong>did:</strong> prefix to DIF’s <a href="https://uniresolver.io/">Universal Resolver</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*OaFcteYMicOzNQzEfYqV6A.png" /><figcaption>Resolving a DID using the PID meta-resolver at Identifiers.org.</figcaption></figure><p>There are some drawbacks of this setup of course, especially a dependency on TWO centrally hosted third-party services (<strong>identifiers.org</strong> and <strong>uniresolver.io</strong>). Those of us working on DIDs would prefer resolving identifiers by “directly” reading from a DID’s decentralized target system. But conceptually, this is a first step to show that indeed DIDs are PIDs. I hope our two communities will be able to learn from each other more in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415fb8be0886" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DID Auth and the little I-am-me]]></title>
            <link>https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec14d757ff09</guid>
            <category><![CDATA[did-auth]]></category>
            <category><![CDATA[little-i-am-me]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 13:47:49 GMT</pubDate>
            <atom:updated>2018-09-04T14:14:37.895Z</atom:updated>
            <content:encoded><![CDATA[<p>We recently published a report on “DID Auth” (<a href="https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/raw/master/final-documents/did-auth.pdf">PDF</a>, <a href="https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md">MD</a>), which summarizes ideas and possible architectures that allow you to prove that you control a certain <a href="https://w3c-ccg.github.io/did-spec/">Decentralized Identifier</a> (DID). This report originated at the sixth <a href="http://weboftrust.info/">Rebooting-the-Web-of-Trust</a> workshop and is the result of a collaborative effort by several authors and contributors. There is also a <a href="http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/">webinar</a>.</p><p>But before further discussing DID Auth, let’s first start with a story.</p><p>The story of a cute little creature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3EDzDusaGlhxg9Qq_p4dKA.jpeg" /></figure><p>One day, a frog asks “Who are you?”, and the little creature realizes that it has a severe identity problem: It doesn’t know what kind of animal it is, and it doesn’t know its own name. So it ventures out into the world to find other animals — horses, fish, hippos, parrots, dogs — hoping that one of them would be able to tell what kind of animal it is. However, none of the other animals know the answer. Eventually, the little creature gets sad and desperate, almost starts to cry, and it asks itself, “Is it possible that I don’t exist at all? That I am no one?”. But then, after a few moments it suddenly stops and realizes “Of course I exist. I am me!”.</p><p>This story about the little I-am-me is from a 1970s <a href="https://www.amazon.com/Das-kleine-Ich-bin-ich/dp/3702658572">children’s book</a>. For young children, the moral of the story is that you are an independent person, and it doesn’t matter what your parents or other children say about you. For those of us who work on self-sovereign digital identity technologies however, the story of the little I-am-me also represents the essence of what we are aiming for: Identity that is inherent to us and that cannot be taken away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iys7tLnahF-wOR-KF8s0Kw.jpeg" /><figcaption>The little I-am-me went to many identity conferences in 2018, including Identiverse, the Internet Identity Workshop, European Identity Conference, Decentralized Web Summit, MyData, and others.</figcaption></figure><p>This takes us back to DID Auth. I would claim that with the advent of DID Auth, now for the first time in the history of digital identity, we will have ways to prove online that “I am me”. In earlier identity protocols, we have only ever been able to express statements like “according to identity provider X, my identifier is Y”, but never truly “I am me”. You will notice that the architecture diagrams in the DID Auth paper only show two participants (identity owner and relying party), whereas diagrams of earlier identity protocols typically contained three participants (identity provider, relying party, user). This is a fundamental shift.</p><p>In today’s emerging self-sovereign identity community, there is strong interest in a relationship-based understanding of identity. This idea, also described by Joe Andrieu as <a href="https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/functional-identity-primer.md">Functional Identity</a>, proposes that “identity is how we keep track of others, and how others keep track of us”, i.e. identity always depends on who we are interacting with. This approach tends to model identity mostly as a set of <a href="https://w3c.github.io/vc-data-model/">Verifiable Credentials</a>. This model however ignores the inherent aspect of our identity that does not depend on others. The little I-am-me had talked to all the other animals, but none of them was able to issue a Verifiable Credential about who it is. Still, it definitely has its own independent existence (= the very first principle of Christopher Allen’s famous <a href="http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html">blog post</a>).</p><p>While working on the DID Auth paper, the most interesting topic for me was that of semantics, i.e. what data format could actually be used to represent the seemingly simple statement “I am me”.</p><ol><li>One approach used by several communities is based on the classic <a href="https://tools.ietf.org/html/rfc7519">JSON Web Token (JWT)</a> format. DID Auth could use a profile of this format where the issand sub fields are the same, i.e. a self-signed token asserting one’s DID. But even though the JWT can contain an assertion of an identifier, it still remains plain JSON, which means it is limited in its ability to express semantically meaningful statements.</li><li>Another approach is to use the same format as <a href="https://w3c.github.io/vc-data-model/">Verifiable Credentials</a>, i.e. the JSON-LD serialization format of the RDF semantic graph model. In this approach, a self-signed Verifiable Credential like the following can demonstrate control of a DID:</li></ol><pre>{<br>  &quot;type&quot;: [&quot;VerifiablePresentation&quot;],<br>  &quot;issuer&quot;: &quot;did:example:123456789abcdefghi&quot;,<br>  &quot;issued&quot;: &quot;2018-09-04&quot;,<br>  &quot;claim&quot;: {<br>    &quot;id&quot;: &quot;did:example:123456789abcdefghi&quot;,<br>    &quot;publicKey&quot;: &quot;did:example:123456789abcdefghi#keys-2&quot;<br>  }<br>}</pre><p>But wait a second. While RDF is a semantic data model, does this piece of data really say “I am me”? No, it doesn’t. It only says “did:example:123456789abcdefghiis claiming that did:example:123456789abcdefghi‘s public key is #keys-2”. That’s maybe close, but not what we are looking for.</p><p>I would argue that it is impossible to formulate an RDF statement that actually says “I am me”, because RDF lacks the ability to express context and relativity. The only data model I am aware of that can do this is the XDI graph model with its built-in constructs for contextual statements, root nodes, and relative identifiers.</p><p>An XDI statement that expresses “I am did:example:123456789abcdefghi“ would look like this:</p><p>/$is/(=!:did:example:123456789abcdefghi)</p><p>And then finally, to express “I am me”, the following trivial statement describes an XDI local root node linking to itself via an $isequivalence arc.</p><p>/$is/</p><p>There is much more to explore as we build out data models and protocols for the self-sovereign identity vision, but proving control of identifiers, and the associated semantics will be key pieces in this journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*EIHF4kKA5YQwzMrGGM6EWw.jpeg" /></figure><p><em>(This article about DID Auth and the little I-am-me was inspired by a conversation with Joachim Lohkamp and Shermin Voshmgir in late 2017.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec14d757ff09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Universal Resolver for self-sovereign identifiers]]></title>
            <link>https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c?source=rss-87130a922e66------2</link>
            <guid isPermaLink="false">https://medium.com/p/48e6b4a5cc3c</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Markus Sabadello]]></dc:creator>
            <pubDate>Wed, 01 Nov 2017 14:43:23 GMT</pubDate>
            <atom:updated>2019-02-15T09:41:11.315Z</atom:updated>
            <content:encoded><![CDATA[<h4>On any blockchain or other decentralized system</h4><p>DIF is introducing a community preview of the Universal Resolver — a core building block of a decentralized identity system. This is a first step in fulfilling DIF’s mission to help individuals and organizations to control their digital identity, without being dependent on any intermediary party.</p><p>This tool fulfills a similar purpose as Bind does in the DNS system: resolution of identifiers. However, instead of working with domain names, we work with self-sovereign identifiers that can be created and registered directly by the entities they refer to. This is important, because identifiers are the basis for any identity and communications system — without identifiers, we cannot have relationships, transactions, data sharing or messaging between entities. Historically identifiers have always been assigned to us by some kind of corporate or state authority. The Universal Resolver lets us build architectures and protocols on top of identifiers that are completely self-sovereign. There is no longer a need for a central authority to issue, maintain and revoke identifiers.</p><p>However, just having an identifier is not enough. We need some further information in order to know how to communicate with the entity represented by the identifier. The job of a “Resolver” is to discover and retrieve this further information. At a minimum, this information includes elements such as service endpoints for communicating with the entity, as well as the cryptographic keys associated with it. The Universal Resolver performs this task to enable the basic building blocks of a self-sovereign identity world.</p><p>The Universal Resolver is directly related to the work that has been done by the <a href="http://weboftrust.info/">Rebooting-the-Web-of-Trust</a> and <a href="http://internetidentityworkshop.com/">Internet Identity Workshop</a> communities around a <a href="https://www.google.at/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwiL6LSByozXAhWEVBQKHbE_BqEQFgg8MAA&amp;url=http%3A%2F%2Fwww.weboftrust.info%2Fdownloads%2Fdpki.pdf&amp;usg=AOvVaw2YDgvyMxhMRmOv6MH8dfaK">Decentralized Public Key Infrastructure (DPKI)</a> and <a href="https://w3c-ccg.github.io/did-spec/">Decentralized Identifiers (DIDs)</a>, which support different “methods” for registering identifiers on decentralized systems such as the Bitcoin blockchain, Sovrin, Ethereum, IPFS, and others. Note that the DID spec is currently undergoing a “hardening” phase, and that the work presented here is an early developers’ implementation meant to encourage the participation of the community and to accelerate the joint development of key decentralized identity primitives.</p><h3>Extensible Driver Architecture</h3><p>DIF’s Universal Resolver provides a unified interface which can be used to resolve any kind of decentralized identifier. This enables higher level data formats (such as Verifiable Claims) and protocols (such as DIF’s Hub protocol) to be built on top of the identifier layer, no matter which blockchain or other system has been used to register the identifier. Internally, the Universal Resolver achieves this through an architecture consisting of “drivers” for each supported identifier type. A driver can be easily added via a Docker container, a Java API, or a remote HTTP GET call, as illustrated in the following diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Z_tUGSKjlkcaG6D2zf7faA.png" /></figure><p>Currently, early versions of the following drivers exist. They will be updated regularly to match the progress of the various specification documents:</p><ul><li><strong>did:sov</strong>, registered on the <a href="https://sovrin.org/">Sovrin</a> distributed ledger</li><li><strong>did:btcr</strong>, registered on the <a href="https://github.com/WebOfTrustInfo/btcr-hackathon/blob/master/README.md">Bitcoin</a> blockchain</li><li><strong>did:stack</strong>, used by <a href="http://blockstack.org/">Blockstack</a> (thank you Jude Nelson !)</li><li><strong>did:uport</strong>, used by <a href="https://www.uport.me/">uPort</a> (thank you Christian Lundqvist !)</li><li><strong>did:jolo</strong>, used by <a href="https://jolocom.io/">Jolocom</a> (thank you Charles Cunningham !)</li><li><strong>did:ipid</strong>, using <a href="https://github.com/jonnycrunch/ipid">IPFS and IPNS</a> (thank you Jonathan Holt !)</li><li><strong>did:v1</strong>, used by <a href="https://veres.one/">Veres One</a></li></ul><p>Drivers can internally function in different ways — some drivers may simply call a remote web service, while others may have direct access to a full node of the blockchain they use. The former option can make the driver usable even on mobile devices, while the latter option provides higher security guarantees for the resolution result.</p><h3>How can I deploy/use the Universal Resolver?</h3><p>An easy way to get started on your local machine is to clone the following Github repository, and use <strong>docker-compose</strong> to build and run the Universal Resolver as well as its drivers:</p><pre>git clone <a href="https://github.com/decentralized-identity/universal-resolver.git">https://github.com/decentralized-identity/universal-resolver.git</a><br>cd universal-resolver/<br>docker-compose -f docker-compose.yml pull<br>docker-compose -f docker-compose.yml up</pre><p>You should then be able to resolve identifiers locally using simple <strong>curl</strong> requests as follows:</p><pre>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:sov:WRfXPg8dantKVubE3HX8pw">http://localhost:8080/1.0/identifiers/did:sov:WRfXPg8dantKVubE3HX8pw</a><br>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:btcr:xkrn-xzcr-qqlv-j6sl">http://localhost:8080/1.0/identifiers/did:btcr:xkrn-xzcr-qqlv-j6sl</a><br>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:v1:test:nym:3AEJTDMSxDDQpyUftjuoeZ2Bazp4Bswj1ce7FJGybCUu">http://localhost:8080/1.0/identifiers/did:v1:test:nym:3AEJTDMSxDDQpyUftjuoeZ2Bazp4Bswj1ce7FJGybCUu</a><br>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:uport:2omWsSGspY7zhxaG6uHyoGtcYxoGeeohQXz">http://localhost:8080/1.0/identifiers/did:uport:2omWsSGspY7zhxaG6uHyoGtcYxoGeeohQXz</a><br>curl -X GET <a href="https://uniresolver.io/1.0/identifiers/did:jolo:e76fb4b4900e43891f613066b9afca366c6d22f7d87fc9f78a91515be24dfb21">http://localhost:8080/1.0/identifiers/did:jolo:e76fb4b4900e43891f613066b9afca366c6d22f7d87fc9f78a91515be24dfb21</a><br>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:stack:v0:16EMaNw3pkn3v6f2BgnSSs53zAKH4Q8YJg-0">http://localhost:8080/1.0/identifiers/did:stack:v0:16EMaNw3pkn3v6f2BgnSSs53zAKH4Q8YJg-0</a><br>curl -X GET <a href="http://localhost:8080/1.0/identifiers/did:ipid:QmYA7p467t4BGgBL4NmyHtsXMoPrYH9b3kSG6dbgFYskJm">http://localhost:8080/1.0/identifiers/did:ipid:QmYA7p467t4BGgBL4NmyHtsXMoPrYH9b3kSG6dbgFYskJm</a></pre><p>The response to these calls will be the DID Document, containing service endpoints and cryptographic keys associated with the entity the DID refers to.</p><h3>Next Steps</h3><p>We are now working on the following improvements and additional resources:</p><ul><li>At the moment, the Universal Resolver simply accepts an identifier as input, and returns the DID Document as a result. In the future, more advanced input options (such as queries for certain services or keys), as well as additional result information (such as “supplementary” details about the resolution process) can be supported.</li><li>We are working on client libraries in Java, Python, and NodeJS that will make it easy to access an instance of the Universal Resolver remotely (thank you Kyle Den Hartog and James Foley !)</li><li>We will formulate guidelines and recommendations for the community on how to contribute a new driver for a new type of decentralized identifier.</li><li>We will integrate the Universal Resolver with our work on Hubs, which allow storing and sharing of personal identity objects and files.</li><li>And last but not least, we are designing a component that will allow not only resolution, but also registration of decentralized identifiers. We call this the Universal Registrar — stay tuned!</li></ul><p>To learn more about DIF’s Universal Resolver, see <a href="https://github.com/decentralized-identity/universal-resolver/">https://github.com/decentralized-identity/universal-resolver/</a>.</p><p>To learn more about DIDs, see <a href="https://w3c-ccg.github.io/did-spec/">https://w3c-ccg.github.io/did-spec/</a>.</p><p>To visit DIF, see <a href="http://identity.foundation/">http://identity.foundation/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48e6b4a5cc3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c">A Universal Resolver for self-sovereign identifiers</a> was originally published in <a href="https://medium.com/decentralized-identity">Decentralized Identity Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>