mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-13 17:44:23 -05:00
get rid of docs folder
This commit is contained in:
parent
8be40065ba
commit
cfd29d13b6
116
docs/LICENSE
116
docs/LICENSE
@ -1,116 +0,0 @@
|
|||||||
CC0 1.0 Universal
|
|
||||||
|
|
||||||
Statement of Purpose
|
|
||||||
|
|
||||||
The laws of most jurisdictions throughout the world automatically confer
|
|
||||||
exclusive Copyright and Related Rights (defined below) upon the creator and
|
|
||||||
subsequent owner(s) (each and all, an "owner") of an original work of
|
|
||||||
authorship and/or a database (each, a "Work").
|
|
||||||
|
|
||||||
Certain owners wish to permanently relinquish those rights to a Work for the
|
|
||||||
purpose of contributing to a commons of creative, cultural and scientific
|
|
||||||
works ("Commons") that the public can reliably and without fear of later
|
|
||||||
claims of infringement build upon, modify, incorporate in other works, reuse
|
|
||||||
and redistribute as freely as possible in any form whatsoever and for any
|
|
||||||
purposes, including without limitation commercial purposes. These owners may
|
|
||||||
contribute to the Commons to promote the ideal of a free culture and the
|
|
||||||
further production of creative, cultural and scientific works, or to gain
|
|
||||||
reputation or greater distribution for their Work in part through the use and
|
|
||||||
efforts of others.
|
|
||||||
|
|
||||||
For these and/or other purposes and motivations, and without any expectation
|
|
||||||
of additional consideration or compensation, the person associating CC0 with a
|
|
||||||
Work (the "Affirmer"), to the extent that he or she is an owner of Copyright
|
|
||||||
and Related Rights in the Work, voluntarily elects to apply CC0 to the Work
|
|
||||||
and publicly distribute the Work under its terms, with knowledge of his or her
|
|
||||||
Copyright and Related Rights in the Work and the meaning and intended legal
|
|
||||||
effect of CC0 on those rights.
|
|
||||||
|
|
||||||
1. Copyright and Related Rights. A Work made available under CC0 may be
|
|
||||||
protected by copyright and related or neighboring rights ("Copyright and
|
|
||||||
Related Rights"). Copyright and Related Rights include, but are not limited
|
|
||||||
to, the following:
|
|
||||||
|
|
||||||
i. the right to reproduce, adapt, distribute, perform, display, communicate,
|
|
||||||
and translate a Work;
|
|
||||||
|
|
||||||
ii. moral rights retained by the original author(s) and/or performer(s);
|
|
||||||
|
|
||||||
iii. publicity and privacy rights pertaining to a person's image or likeness
|
|
||||||
depicted in a Work;
|
|
||||||
|
|
||||||
iv. rights protecting against unfair competition in regards to a Work,
|
|
||||||
subject to the limitations in paragraph 4(a), below;
|
|
||||||
|
|
||||||
v. rights protecting the extraction, dissemination, use and reuse of data in
|
|
||||||
a Work;
|
|
||||||
|
|
||||||
vi. database rights (such as those arising under Directive 96/9/EC of the
|
|
||||||
European Parliament and of the Council of 11 March 1996 on the legal
|
|
||||||
protection of databases, and under any national implementation thereof,
|
|
||||||
including any amended or successor version of such directive); and
|
|
||||||
|
|
||||||
vii. other similar, equivalent or corresponding rights throughout the world
|
|
||||||
based on applicable law or treaty, and any national implementations thereof.
|
|
||||||
|
|
||||||
2. Waiver. To the greatest extent permitted by, but not in contravention of,
|
|
||||||
applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
|
|
||||||
unconditionally waives, abandons, and surrenders all of Affirmer's Copyright
|
|
||||||
and Related Rights and associated claims and causes of action, whether now
|
|
||||||
known or unknown (including existing as well as future claims and causes of
|
|
||||||
action), in the Work (i) in all territories worldwide, (ii) for the maximum
|
|
||||||
duration provided by applicable law or treaty (including future time
|
|
||||||
extensions), (iii) in any current or future medium and for any number of
|
|
||||||
copies, and (iv) for any purpose whatsoever, including without limitation
|
|
||||||
commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes
|
|
||||||
the Waiver for the benefit of each member of the public at large and to the
|
|
||||||
detriment of Affirmer's heirs and successors, fully intending that such Waiver
|
|
||||||
shall not be subject to revocation, rescission, cancellation, termination, or
|
|
||||||
any other legal or equitable action to disrupt the quiet enjoyment of the Work
|
|
||||||
by the public as contemplated by Affirmer's express Statement of Purpose.
|
|
||||||
|
|
||||||
3. Public License Fallback. Should any part of the Waiver for any reason be
|
|
||||||
judged legally invalid or ineffective under applicable law, then the Waiver
|
|
||||||
shall be preserved to the maximum extent permitted taking into account
|
|
||||||
Affirmer's express Statement of Purpose. In addition, to the extent the Waiver
|
|
||||||
is so judged Affirmer hereby grants to each affected person a royalty-free,
|
|
||||||
non transferable, non sublicensable, non exclusive, irrevocable and
|
|
||||||
unconditional license to exercise Affirmer's Copyright and Related Rights in
|
|
||||||
the Work (i) in all territories worldwide, (ii) for the maximum duration
|
|
||||||
provided by applicable law or treaty (including future time extensions), (iii)
|
|
||||||
in any current or future medium and for any number of copies, and (iv) for any
|
|
||||||
purpose whatsoever, including without limitation commercial, advertising or
|
|
||||||
promotional purposes (the "License"). The License shall be deemed effective as
|
|
||||||
of the date CC0 was applied by Affirmer to the Work. Should any part of the
|
|
||||||
License for any reason be judged legally invalid or ineffective under
|
|
||||||
applicable law, such partial invalidity or ineffectiveness shall not
|
|
||||||
invalidate the remainder of the License, and in such case Affirmer hereby
|
|
||||||
affirms that he or she will not (i) exercise any of his or her remaining
|
|
||||||
Copyright and Related Rights in the Work or (ii) assert any associated claims
|
|
||||||
and causes of action with respect to the Work, in either case contrary to
|
|
||||||
Affirmer's express Statement of Purpose.
|
|
||||||
|
|
||||||
4. Limitations and Disclaimers.
|
|
||||||
|
|
||||||
a. No trademark or patent rights held by Affirmer are waived, abandoned,
|
|
||||||
surrendered, licensed or otherwise affected by this document.
|
|
||||||
|
|
||||||
b. Affirmer offers the Work as-is and makes no representations or warranties
|
|
||||||
of any kind concerning the Work, express, implied, statutory or otherwise,
|
|
||||||
including without limitation warranties of title, merchantability, fitness
|
|
||||||
for a particular purpose, non infringement, or the absence of latent or
|
|
||||||
other defects, accuracy, or the present or absence of errors, whether or not
|
|
||||||
discoverable, all to the greatest extent permissible under applicable law.
|
|
||||||
|
|
||||||
c. Affirmer disclaims responsibility for clearing rights of other persons
|
|
||||||
that may apply to the Work or any use thereof, including without limitation
|
|
||||||
any person's Copyright and Related Rights in the Work. Further, Affirmer
|
|
||||||
disclaims responsibility for obtaining any necessary consents, permissions
|
|
||||||
or other rights required for any use of the Work.
|
|
||||||
|
|
||||||
d. Affirmer understands and acknowledges that Creative Commons is not a
|
|
||||||
party to this document and has no duty or obligation with respect to this
|
|
||||||
CC0 or use of the Work.
|
|
||||||
|
|
||||||
For more information, please see
|
|
||||||
<http://creativecommons.org/publicdomain/zero/1.0/>
|
|
303
docs/README.md
303
docs/README.md
@ -1,303 +0,0 @@
|
|||||||
# Awesome Decentralized Identity [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)
|
|
||||||
*Self-Sovereign, Blockchain and Decentralized Identity Resources*
|
|
||||||
|
|
||||||
>A good self‐sovereign identity system will allow individuals to directly influence how companies, governments, and others correlate our interactions across different services and locations by default. It won’t fix all identity problems nor preclude alternative identity approaches, but it will put the individual in control of most uses of identity and give organizations a simpler, easier, more ethical way to use identity to improve how they provide services and products. When successful, it will not only enable individuals to exercise greater control over how companies and governments keep track of us, it will also illuminate those situations where self‐sovereign identity is restricted, facilitating a conversation about when and where such limits are appropriate. [Joe Andrieu -A Technology‐Free Definition of Self‐Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/blob/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)
|
|
||||||
|
|
||||||
**Note: becoming [decentralized-id.com](https://decentralized-id.com)**
|
|
||||||
>See [/decentralized-id/decentralized-id.github.io](https://github.com/decentralized-id/decentralized-id.github.io)
|
|
||||||
|
|
||||||
For now, this is still home and best maintained.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
[[**T**](#contents)]witter • [[**G**](#contents)]ithub • [[**B**](#contents)]log • [[**wp**](#contents)] whitepaper • [[**D**](#contents)]ocumentation • [[**F**](#contents)]orums • [[**C**](#contents)]hat • [[**tele**](#contents)]gram • [[**web**](#contents)]site
|
|
||||||
• [[**ϟ**](#contents)] related resource • [[**>**](#contents)] related section • [[**^**](#contents)] back to the contents.
|
|
||||||
|
|
||||||
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align=right width="170" height="170"/>
|
|
||||||
|
|
||||||
* [Link Shorthand](#link-shorthand)
|
|
||||||
* [What is Decentralized ID?](#what-is-decentralized-id-)
|
|
||||||
* [What is Self Sovereign Identity?](#self-sovereign-identity-)
|
|
||||||
* [DID Related Web Standards](did-related-web-standards-)
|
|
||||||
* [W3C](#w3c-)
|
|
||||||
* [DID the Decentralized Identifier](#did-the-decentralized-identifier-)
|
|
||||||
* [Verifiable Claims](#verifiable-claims-)
|
|
||||||
* [Decentralized Key Managment DKMS](#decentralized-key-management-dkms-)
|
|
||||||
* [DID Auth](#did-auth-)
|
|
||||||
* [Blockcerts](#blockcerts-)
|
|
||||||
* [Schema](#schema-)
|
|
||||||
* [DID Adoption](#did-adoption-)
|
|
||||||
* [Directory](#directory)
|
|
||||||
* [SSI\DID History](history.md)
|
|
||||||
* [Self Sovereign Identity](self-sovereign-identity)
|
|
||||||
* [GDPR](gdpr)
|
|
||||||
* [Humanitarian](humanitarian.md)
|
|
||||||
* [Identity Related GitHub Repositories](identity-github.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Rebooting Web of Trust](rebooting-web-of-trust.md)
|
|
||||||
* [Media](media.md) - Video, Podcasts and Slideshare
|
|
||||||
* [Decentralized Identity Foundation—DIF](identity-foundation.md)
|
|
||||||
* [Bitcoin](bitcoin.md)
|
|
||||||
* [Spidchain](bitcoin.md#spidchain-)
|
|
||||||
* [Ethereum](ethereum.md)
|
|
||||||
* [ERC-EIP](ethereum.md#erc-eip-)
|
|
||||||
* [uPort](ethereum.md#uport-)
|
|
||||||
* [Jolocom](ethereum.md#jolocom-)
|
|
||||||
* [Spidchain](ethereum.md#spidchain-)
|
|
||||||
* [Indy Ecosystem](indy-ecosystem/)
|
|
||||||
* [Adoption](indy-ecosystem/adoption.md)
|
|
||||||
* [Indy Github](indy-ecosystem/indy-github.md)
|
|
||||||
* [Literature](indy-ecosystem/literature.md)
|
|
||||||
* [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md)
|
|
||||||
* [VON](indy-ecosystem/VON.md)
|
|
||||||
* [Hyperledger Global Forum](hgf-2018/)
|
|
||||||
* [State Sponsored](state-sponsored.md)
|
|
||||||
* [Microsoft](microsoft.md)
|
|
||||||
* [IBM](ibm.md)
|
|
||||||
* [Sources](#sources-)
|
|
||||||
|
|
||||||
|
|
||||||
*Pull Requests Welcome*
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
![](https://i.imgur.com/9KpJRDr.png)
|
|
||||||
|
|
||||||
|
|
||||||
## What is Decentralized ID? [**^**](#contents)
|
|
||||||
|
|
||||||
That's a big question, and what follows are just some notes, until I work out a more thoughtful answer.
|
|
||||||
|
|
||||||
The essence of Decentralized-ID is in creating open standards for a privacy preserving internet-wide identity layer — not owned by any one particular organization, but interoperable between all.
|
|
||||||
|
|
||||||
It's impossible to have a conversation about decentralized-id without discussing blockchain and self sovereign identity:
|
|
||||||
* Self Sovereign Identity principles (with some help from the GDPR) have helped to shape the narrative around putting the identity owner in control over their personal information.
|
|
||||||
* Blockchain fueled longstanding efforts to create a privacy preserving internet-wide identity protocol, and inspired development of decentralized networks for online identification.
|
|
||||||
* The United Nations Sustainable Development Goals (SDGs) have also helped to fueled efforts for a global and widely accessible identity solution.
|
|
||||||
|
|
||||||
—[infominer.id](https://infominer.id)
|
|
||||||
|
|
||||||
## DID-SSI History
|
|
||||||
|
|
||||||
* [The Augmented Social Network and the IDCommons](/history.md#the-augmented-social-network-and-the-idcommons-)
|
|
||||||
* [Internet Identity Workshop—IIW](/history.md#internet-identity-workshop-)
|
|
||||||
* [Bitnation and the United Nations](/history.md#bitnation-and-the-united-nations-)
|
|
||||||
* [#Rebooting-Web-of-Trust (RWoT)](/history.md#rebooting-the-web-of-trust-)
|
|
||||||
* [ID2020 and the GDPR](/history.md#id2020-and-the-gdpr-)
|
|
||||||
* [Additional IID Standards History](/history.md#additional-iid-standards-history-)
|
|
||||||
|
|
||||||
## Self Sovereign Identity [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/3zz62kpl.png)
|
|
||||||
|
|
||||||
|
|
||||||
* [Christopher Allen](http://www.lifewithalacrity.com/)[[**info**](https://christophera.info/)] details the overarching history of internet idenitity standards and outlines [10 Principles of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md) in his seminal work [The Path to Self-Soverereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)[[**ϟ**](https://www.coindesk.com/path-self-sovereign-identity/amp/)]
|
|
||||||
* <a href="https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf"><u>A Technlogy-Free Definition of Self-Sovereign Identity</u></a> is a continuation of the discussion started by Allen, offering 3 "Core Characteristics of Sovereign Identity".
|
|
||||||
* [7 Myths of Self Sovereign Identity](https://medium.com/evernym/7-myths-of-self-sovereign-identity-67aea7416b1)
|
|
||||||
* [Inevitable Rise of Self-Sovereign Identity](https://sovrin.org/wp-content/uploads/2018/03/The-Inevitable-Rise-of-Self-Sovereign-Identity.pdf)
|
|
||||||
* [SSIMeetup](http://ssimeetup.org/) [[**S**](https://www.slideshare.net/SSIMeetup/presentations)] [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)] [[**tele**](https://t.me/SSIMeetup)]
|
|
||||||
\- SSI Meetup is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards.
|
|
||||||
* [SSI: A Roadmap for Adoption](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md)
|
|
||||||
* **[/awesome-decentralized-id/self-sovereign-identity](https://github.com/infominer33/awesome-decentralized-id/tree/master/self-sovereign-identity)** SSI documentation is still under development. This directory is to organize existing thought on SSI in one place for ease of study, and the development of new documentation.
|
|
||||||
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
|
|
||||||
|
|
||||||
|
|
||||||
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">0/ “Self-Sovereign Identity: A Progress Report”…</p>— Christopher Allen (@ChristopherA) <a href="https://twitter.com/ChristopherA/status/989120215702261761?ref_src=twsrc%5Etfw">April 25, 2018</a></blockquote>
|
|
||||||
|
|
||||||
|
|
||||||
## DID Related Web Standards [**^**](#contents)
|
|
||||||
|
|
||||||
### W3C [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/Lz6RTysl.png)
|
|
||||||
|
|
||||||
* [World Wide Web Consortium(W3C)](https://www.w3.org/) [[**T**](https://twitter.com/w3c)] [[**G**](https://github.com/w3c)]
|
|
||||||
>The [World Wide Web Consortium (W3C)](https://www.w3.org/Consortium/) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. Led by Web inventor and Director Tim Berners-Lee and CEO Jeffrey Jaffe, W3C's mission is to lead the Web to its full potential.
|
|
||||||
* <a href="https://lists.w3.org/Archives/Public/public-vc-wg/" target="_blank">Verifiable Claims WG - Mailing List</a> (and archives)
|
|
||||||
* [Credentials Community Group](https://www.w3.org/community/credentials/)[[**B**](https://w3c-ccg.github.io/)]
|
|
||||||
* <a href="http://lists.w3.org/Archives/Public/public-credentials/" target="_blank">Public mailing list for the Credentials Community Group</a> (and archives) - Anyone may read or write to this list.
|
|
||||||
* <a href="https://github.com/opencreds/website" target="_blank">/opencreds/website</a>
|
|
||||||
* [opencreds.org — Identity Credentials 1.0](https://opencreds.org/specs/source/identity-credentials/)
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/w3c-dvcg.github.io" target="_blank">/w3c-dvcg/w3c-dvcg.github.io</a> - Landing site for W3C Digital Verification Community Group. [<a href="https://www.w3.org/community/digital-verification/">**W**</a>]
|
|
||||||
* [JSON-LD 1.0, W3C Recommendation](https://www.w3.org/TR/json-ld/)
|
|
||||||
|
|
||||||
![](https://imgur.com/6MLNgXal.png)\
|
|
||||||
<sup><a href="https://www.youtube.com/watch?v=RllH91rcFdE">The Story of Open SSI Standards - Drummond Reed/Evernym SSIMeetup.org</a>[<b><a href="https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed">ϟ</a></b>]</sup>
|
|
||||||
|
|
||||||
#### DID the Decentralized Identifier [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/7NRcJbq.png"/></a>
|
|
||||||
|
|
||||||
* [A Universally Unique IDentifier (UUID) URN Namespace](https://www.ietf.org/rfc/rfc4122.txt) <-DID's modeled after
|
|
||||||
* [All you need to know about sequential UUID generators](https://blog.2ndquadrant.com/sequential-uuid-generators/)
|
|
||||||
* [w3c- Decentralized Identifiers (DIDs) v0.11](https://w3c-ccg.github.io/did-spec/)
|
|
||||||
* Authors:
|
|
||||||
* [Drummond Reed](https://equalsdrummond.name/) [[**T**](https://twitter.com/drummondreed)] ([Evernym](https://www.evernym.com/))
|
|
||||||
* [Manu Sporney](http://manu.sporny.org/)[[**T**](https://twitter.com/manusporny)] ([Digital Bazaar](https://digitalbazaar.com))
|
|
||||||
* Dave Longley ([Digital Bazaar](https://digitalbazaar.com))
|
|
||||||
* [Christopher Allen](http://www.lifewithalacrity.com/) [[**info**](https://github.com/ChristopherA/info)] ([Blockstream](https://blockstream.com/))
|
|
||||||
* Ryan Grant
|
|
||||||
* [Markus Sabadello (Peacekeeper)](http://mydata2016.org/speaker/markus-sabadello/) [[**T**](https://twitter.com/peacekeeper)] [[**G**](https://github.com/peacekeeper)] [[**B**](https://medium.com/@markus.sabadello)] ([Danube Tech](https://github.com/projectdanube))
|
|
||||||
* [Understanding Decentralized IDs (DIDs)](https://medium.com/@adam_14796/understanding-decentralized-ids-dids-839798b91809)
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/draft-documents/did-primer.md) [[**ϟ**](https://github.com/WebOfTrustInfo/rwot7-fall2018/blob/master/topics-and-advance-readings/did-primer-extended.md)]
|
|
||||||
* [Decentralized IDentifers (DIDs)](https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf)
|
|
||||||
* [Requirements for DIDs](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/requirements-for-dids.pdf)
|
|
||||||
* [DIDs in DPKI](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md)
|
|
||||||
* [What is a DID?](https://docs.google.com/document/d/1Ym85y_bDVN9xkRZ-oD-zlUUIeZjVGWNihfZBk2GQidk/edit)
|
|
||||||
* [The Path from an id (DID) to a Real-Life Something](https://hyperonomy.com/2019/01/04/the-path-from-a-id-did-to-a-real-life-something)
|
|
||||||
|
|
||||||
<a href="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png"><img src="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png?w=500"/></a>
|
|
||||||
|
|
||||||
#### Verifiable Claims [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/nsZ0X7r.png"/></a>
|
|
||||||
|
|
||||||
|
|
||||||
* [Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) [[**D**](https://www.w3.org/2017/vc/charter.html)]
|
|
||||||
* [Verifiable Claims Data Model 1.0](https://w3c.github.io/vc-data-model/) [[**G**](https://github.com/w3c/vc-data-model)] [[**D**](https://w3c.github.io/vc-use-cases/)]
|
|
||||||
* [Verifiable Credentials 101 for SSI – Tyler Ruff – Webinar 11](http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/)
|
|
||||||
|
|
||||||
|
|
||||||
### DID Auth [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/XMaq5cil.png)
|
|
||||||
|
|
||||||
|
|
||||||
* [DID Auth and the Little I-am-Me](https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09)
|
|
||||||
* [Introduction to DID Auth](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md) [[**ϟ**](http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/)]
|
|
||||||
|
|
||||||
<a href="http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/"><img src="https://i.imgur.com/YNlk8RY.png"/></a>\
|
|
||||||
http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10
|
|
||||||
|
|
||||||
|
|
||||||
### Decentralized Key Management-Agents [**^**](#Contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/0SLcjUv.png"/>
|
|
||||||
|
|
||||||
* [Decentralized Key Management (DKMS): An Essential Missing Piece of the SSI Puzzle - Drummond Reed](https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed)
|
|
||||||
* [Recommendations for Decentralized Key Management Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md)
|
|
||||||
* [Agent to Agent Communication](https://drive.google.com/file/d/1PHAy8dMefZG9JNg87Zi33SfKkZvUvXvx/view): Daniel Hardman explains the goals of agent to agent communication
|
|
||||||
|
|
||||||
|
|
||||||
![](https://i.imgur.com/5qc1qrG.png)\
|
|
||||||
<sup><a href="http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/">DKMS - An Essential Missing Piece of the SSI Puzzle. Drummond Reed. SSIMeetup.org</a></sup>
|
|
||||||
|
|
||||||
* <a href="https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2DjfY" target="_blank">Microsoft- Decentralized Identity — Own and Control Your Identity.</a>
|
|
||||||
![](https://i.imgur.com/ozOLCuW.png)
|
|
||||||
|
|
||||||
|
|
||||||
### Blockcerts [**^**](#contents)
|
|
||||||
* [Learning Machine](https://www.learningmachine.com/)
|
|
||||||
* [Academic Credentialing and the Blockchain](https://www.learningmachine.com/academic-credentialing-blockchain/)
|
|
||||||
* [Blockcerts](https://www.blockcerts.org), developed by learning machine is an open standard for issuing and verifying blockchain-based official records; The project offers open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard.
|
|
||||||
* [CXC (Carribean) Pilots E-Certificates on the Blockchain](https://www.cxc.org/cxc-pilots-e-certificates-on-the-blockchain/)
|
|
||||||
* [A Decentralized Approach to Blockcerts Credential Revocation](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/blockcerts-revocation.md)
|
|
||||||
|
|
||||||
|
|
||||||
### Schema [**^**](#contents)
|
|
||||||
* [Schema](https://schema.org) — a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet. Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences."
|
|
||||||
|
|
||||||
|
|
||||||
## DID Adoption [**^**](#contents)
|
|
||||||
|
|
||||||
**[DID Method Registry](https://w3c-ccg.github.io/did-method-registry/#the-registry)**
|
|
||||||
* did:example: - [DID Specification](https://w3c-ccg.github.io/did-spec/)
|
|
||||||
* did:btcr: - [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/)
|
|
||||||
* The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
|
|
||||||
* [btcr tx conversion playground](https://weboftrustinfo.github.io/btcr-tx-playground.github.io/)
|
|
||||||
* did:stack: - [Blockstack DID Method](https://github.com/blockstack/blockstack-core/blob/master/docs/blockstack-did-spec.md) [[**ϟ**](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287/9)]
|
|
||||||
- Blockstack is a network for decentralized applications where users own their identities and data. Blockstack utilizes a public blockchain to implement a decentralized naming layer, which binds a user's human-readable username to their current public key and a pointer to their data storage buckets.
|
|
||||||
* did:cnsnt: - Consent
|
|
||||||
* did:erc725: - [erc725 DID Method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Method-erc725.md)
|
|
||||||
* did:ipid: - [IPID DID method](https://did-ipid.github.io/ipid-did-method/)
|
|
||||||
- Implementation of the DID spec over IPFS (Interplanetary File System)
|
|
||||||
* did:life: - [lifeID DID Method](https://lifeid.github.io/did-method-spec/)
|
|
||||||
* did:sov: - [Sovrin DID Method](https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html)
|
|
||||||
* did:uport: - uPort
|
|
||||||
* did:v1: - [Veres One DID Method](https://w3c-ccg.github.io/didm-veres-one/)
|
|
||||||
* [**veres.one**](https://veres.one) — a permissionless public ledger designed specifically for the creation and management of decentralized identifiers (DIDs)
|
|
||||||
* did:dom: - Dominode
|
|
||||||
* did:ont: - [Ontology DID Method](https://github.com/ontio/ontology-DID/blob/master/docs/en/DID-ONT-method.md)
|
|
||||||
* did:vvo: - [Vivvo DID Method](https://vivvo.github.io/vivvo-did-scheme/spec/did-method-spec-template.html)
|
|
||||||
* did:icon: - [ICON DID Method](https://github.com/icon-project/icon-DID/blob/master/docs/ICON-DID-method.md)
|
|
||||||
* did:iwt: - [InfoWallet DID Method](https://github.com/infowallet/did_method/blob/master/did_method.md)
|
|
||||||
* did:ockam: - [Ockam DID Method](https://github.com/ockam-network/did-method-spec/blob/master/README.md)
|
|
||||||
* [did:ockam:](https://medium.com/ockam/an-introduction-to-did-ockam-8626d5aecc53) [[**ϟ**](https://twitter.com/Ockam_io/status/1064589363269365763)]
|
|
||||||
* did:ala: - [Alastria DID Method](https://github.com/alastria/alastria-identity/wiki/Alastria-DID-Method-Specification-(Quorum-version))
|
|
||||||
* did:op: - [Ocean Protocol DID Method](https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md)
|
|
||||||
* did:jlinc: - [JLINC Protocol DID Method](https://did-spec.jlinc.org/)
|
|
||||||
* did:ion: - [ION DID Method](https://github.com/decentralized-identity/ion-did-method)
|
|
||||||
* did:jolo: - Jolocom
|
|
||||||
* did:ethr: - [ETHR DID Method](https://github.com/uport-project/ethr-did-resolver/blob/develop/doc/did-method-spec.md)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
* [Peer DID Method Spec](https://dhh1128.github.io/peer-did-method-spec/index.html)
|
|
||||||
* [@ChristopherA on DID adoption](https://twitter.com/ChristopherA/status/989122017348784130)
|
|
||||||
> "22/ Over a dozen companies and organizations, using multiple blockchains (Bitcoin, Ethereum, Hyperledger, etc.), have committed to deploying DIDs, including IBM, Microsoft, Digital Bazaar, Consensys, Evernym, Learning Machine, British Columbia, and more:" —[How blockchain could solve the internet privacy problem](https://www.computerworld.com/article/3267930/blockchain/how-blockchain-could-solve-the-internet-privacy-problem.html)
|
|
||||||
|
|
||||||
![](https://oneworldidentity.com/wp-content/uploads/2018/10/companies.png)
|
|
||||||
|
|
||||||
2018 Identity Landsacpe brought to you by: [One World Identity](https://oneworldidentity.com/) — independent advisory and digital strategy consultancy focused on trust and the data economy.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Directory [**^**](#contents)
|
|
||||||
Other files and folders within this repository:
|
|
||||||
|
|
||||||
* [SSI\DID History](history.md)
|
|
||||||
* [Self Sovereign Identity](self-sovereign-identity)
|
|
||||||
* [Identity Related GitHub Repositories](identity-github.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Rebooting Web of Trust](rebooting-web-of-trust.md)
|
|
||||||
* [Media](assorted-media.md) - Video, Podcasts and Slideshare
|
|
||||||
* [GDPR](gdpr)
|
|
||||||
* [Humanitarian](humanitarian.md)
|
|
||||||
* [Decentralized Identity Foundation—DIF](identity-foundation.md)
|
|
||||||
* [Bitcoin](bitcoin.md)
|
|
||||||
* [Spidchain](bitcoin.md#spidchain-)
|
|
||||||
* [Ethereum](ethereum.md)
|
|
||||||
* [uPort](ethereum.md#uport-)
|
|
||||||
* [Jolocom](ethereum.md#jolocom-)
|
|
||||||
* [Spidchain](ethereum.md#spidchain-)
|
|
||||||
* [Indy Ecosystem](indy-ecosystem/)
|
|
||||||
* [Adoption](indy-ecosystem/adoption.md)
|
|
||||||
* [Indy Github](indy-ecosystem/indy-github.md)
|
|
||||||
* [Literature](indy-ecosystem/literature.md)
|
|
||||||
* [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md)
|
|
||||||
* [VON](indy-ecosystem/VON.md)
|
|
||||||
* [Hyperledger Global Forum](hgf-2018/)
|
|
||||||
* [State Sponsored](state-sponsored.md)
|
|
||||||
* [IBM](ibm.md)
|
|
||||||
* [Microsoft](microsoft.md)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Sources [**^**](#contents)
|
|
||||||
* [SSI Meetup](http://ssimeetup.org/) [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)][[**ϟ**](https://www.slideshare.net/SSIMeetup/presentations/)]
|
|
||||||
* [IIW-Wiki](https://iiw.idcommons.net/Main_Page)
|
|
||||||
* [wiki.idcommons.net](http://wiki.idcommons.net/Main_Page)
|
|
||||||
* [/WebOfTrustInfo](https://github.com/WebOfTrustInfo/)
|
|
||||||
* [/peacekeeper/blockchain-identity](https://github.com/peacekeeper/blockchain-identity)
|
|
||||||
* [identitywoman.net](https://identitywoman.net/)
|
|
||||||
* [windley.com/tags/identity](http://www.windley.com/tags/identity.shtml)
|
|
||||||
* [Kim Camerons Identity Blog](https://identityblog.com)
|
|
||||||
* [/indy-sovrin-evernym](https://github.com/infominer33/awesome-decentralized-id/blob/master/indy-sovrin-evernym/)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id) ([**^**](#contents))
|
|
||||||
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align="right" width="170" height="170"/></a>
|
|
||||||
|
|
||||||
**Tips Jar**
|
|
||||||
|
|
||||||
BTC— 1GvkjHtiy9LUjVkStnEAXxjhcoS56aCokY
|
|
||||||
|
|
||||||
![](https://imgur.com/yXLLm9Bl.png)
|
|
||||||
|
|
||||||
DOGE— DSzMxfABB8EwKiumzV7YHhS7HTvWAyM7QF
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0zBLoUP.png)
|
|
@ -1,13 +0,0 @@
|
|||||||
plugins:
|
|
||||||
- jekyll-seo-tag
|
|
||||||
- jekyll-github-metadata
|
|
||||||
- jekyll-redirect-from
|
|
||||||
|
|
||||||
url : "http://infominer.id/awesome-decentralized-id"
|
|
||||||
baseurl : "/awesome-decentralized-id"
|
|
||||||
title : "Decentralized Identity"
|
|
||||||
description : "Self-Sovereign, User-Owned and Controlled, Internet-Wide Identity."
|
|
||||||
author : "⧉ Infominer"
|
|
||||||
logo : "https://infominer.id/images/crypt0library.png"
|
|
||||||
repository : "infominer33/awesome-decentralized-id"
|
|
||||||
github : [metadata]
|
|
@ -1,22 +0,0 @@
|
|||||||
# Bitcoin Identity Standards and Applications
|
|
||||||
|
|
||||||
![](https://i.imgur.com/q32lAXY.png)
|
|
||||||
|
|
||||||
* [Bitnation taps Blockchain tech to aid Refugees](https://www.newsbtc.com/2015/09/09/bitnation-taps-blockchain-tech-to-aid-refugees/)[[**^**](#Bitnation-and-the-United-Nations)]
|
|
||||||
* [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/) — The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
|
|
||||||
|
|
||||||
## Spidchain
|
|
||||||
|
|
||||||
* [Spidchain](http://www.spidchain.com/) [[**wp**](https://drive.google.com/file/d/0B89WE3IIHmy1Z0ZSSWVmVEtaaG8/view)]
|
|
||||||
* "offers a platform for self-sovereign identity, including desktop and mobile apps for end-users. It uses Decentralized Identifiers (DIDs) - backed by optionally Bitcoin or Ethereum - to implement a marketplace for verifiable claims. The Spidchain applications allow individuals to create, recover, and revoke DIDs, to authenticate, to sign and verify files and claims, and more."
|
|
||||||
|
|
||||||
### Spidchain Bitcoin Repos [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/spidchain-btcr" target="_blank">/SpidChain/spidchain-btcr</a> - An implementation of the btcr standard for self sovereign distributed digital identity
|
|
||||||
* <a href="https://github.com/SpidChain/electrumx" target="_blank">/SpidChain/electrumx</a> Forked from kyuupichan/electrumx
|
|
||||||
- Alternative implementation of spesmilo/electrum-server
|
|
||||||
* <a href="https://github.com/SpidChain/btcr-spv" target="_blank">/SpidChain/btcr-spv</a> - Poc of an SPV implementation of BTCR
|
|
||||||
* <a href="https://github.com/SpidChain/satoshis-wheel-of-fortune" target="_blank">/SpidChain/satoshis-wheel-of-fortune</a> - Pick a name from a list randomly in a provably honest way
|
|
||||||
* <a href="https://github.com/SpidChain/txref-conversion-js" target="_blank">/SpidChain/txref-conversion-js</a> - Forked from WebOfTrustInfo/txref-conversion-js
|
|
||||||
- Javascript library for converting txids to txrefs and back
|
|
||||||
|
|
||||||
|
|
214
docs/ethereum.md
214
docs/ethereum.md
@ -1,214 +0,0 @@
|
|||||||
# Ethereum Identity
|
|
||||||
**Specifications, Literature, Applications**
|
|
||||||
|
|
||||||
![](https://i.imgur.com/XWeGM72.png)
|
|
||||||
|
|
||||||
* [Decentralized Digital Identity on Ethereum](https://www.slideshare.net/FabriceCroiseaux/ethcc-2018-decentralized-digital-identity-on-ethereum) -SlideShare
|
|
||||||
* [DEVCON1: Digital Identity](https://www.youtube.com/watch?v=QpaTOvAhLR4) — video from DEVCON1
|
|
||||||
* [Proof-of-Individuality](http://proofofindividuality.online/) — how to prove a person only has one account
|
|
||||||
* [Anti-Sybil Protocol using virtual pseudonym parties](https://medium.com/@unlisted/anti-sybil-protocol-using-virtual-pseudonym-parties-10276fcf3b20)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
* [ERC-EIP](#erc-eip-)
|
|
||||||
* [ERC725-735](#erc725-735-)
|
|
||||||
* [uPort](#uport-)
|
|
||||||
* [uPort GitHub Repos](#uport-github-repos-)
|
|
||||||
* [uPort DID](#uport-did-)
|
|
||||||
* [uPort Identification](#uport-identification-)
|
|
||||||
* [uPort Mobile](#uport-mobile-)
|
|
||||||
* [uPort Lambda](#uport-lambda-)
|
|
||||||
* [uPort React](#uport-react-)
|
|
||||||
* [uPort Assorted](#uport-assorted-)
|
|
||||||
* [Jolocom](#jolocom-)
|
|
||||||
* [Jolocom Github Repos](#jolocom-github-repos-)
|
|
||||||
* [Spidchain](#spidchain-)
|
|
||||||
* [Spid-Eth Repos](#spid-eth-repos-)
|
|
||||||
* [Assorted Ethereum Apps](#assorted-ethereum-apps-)
|
|
||||||
|
|
||||||
|
|
||||||
## ERC-EIP [**^**](#contents)
|
|
||||||
|
|
||||||
* [ERC: Lightweight Identity #1056](https://github.com/ethereum/EIPs/issues/1056) —This ERC describes a standard for creating and updating identities with a limited use of blockchain resources. An identity can have an unlimited number of delegates and attributes associated with it. Identity creation is as simple as creating a regular key pair ethereum account, which means that it's fee (no gas costs) and all ethereum accounts are valid identities. Furthermore this ERC is fully DID compliant.
|
|
||||||
* [ERC1056 ❤ ERC780 — an open identity and claims protocol for Ethereum](https://medium.com/uport/erc1056-erc780-an-open-identity-and-claims-protocol-for-ethereum-aef7207bc744)
|
|
||||||
* [EIP-780 Ethereum Claims Registry](https://github.com/ethereum/EIPs/issues/780)
|
|
||||||
* [EIP712](https://github.com/ethereum/EIPs/blob/f29527ab39357548b06b29e937a48f06ae099de7/EIPS/eip-712.md) - This is a standard for hashing and signing of typed structured data
|
|
||||||
* [ERC-1484 Digital Identity Aggregator](https://github.com/ethereum/EIPs/issues/1495) —A protocol for aggregating digital identity information that's broadly interoperable with existing, proposed, and hypothetical future digital identity standards.
|
|
||||||
* [EIP-1078](https://github.com/ethereum/EIPs/blob/ed621645c8f3bc5756492f327cda015f35d9f8da/EIPS/eip-1078.md) -
|
|
||||||
This presents a method to replace the usual signup/login design pattern with a minimal ethereum native scheme, that doesn’t require passwords, backing up private keys nor typing seed phrases.
|
|
||||||
* [ERC-1077 and ERC-1078: The magic of executable signed messages](https://ethereum-magicians.org/t/erc-1077-and-erc-1078-the-magic-of-executable-signed-messages-to-login-and-do-actions/351)
|
|
||||||
|
|
||||||
### ERC725-735 [**^**](#contents-)
|
|
||||||
|
|
||||||
* [ERC725](https://github.com/ethereum/EIPs/issues/725)
|
|
||||||
* The following describes standard functions for a unique identifiable proxy account to be used by humans, groups, organisations, objects and machines
|
|
||||||
* [ERC735](https://github.com/ethereum/EIPs/issues/735) - The following describes standard functions for adding, removing and holding of claims.
|
|
||||||
- These claims can attested from third parties (issuers) or self attested.
|
|
||||||
* [Origin partners on ERC725](https://coinjournal.net/origin-protocol-partners-on-new-erc-725-alliance-to-promote-the-adoption-of-blockchain-based-identity-standard)
|
|
||||||
* [Managing Identity with a UI—ERC-725](https://medium.com/originprotocol/managing-identity-with-a-ui-for-erc-725-5c7422b38c09)
|
|
||||||
* [Ethereum ERC725 Blockchain Based, Self-Sovereign Identity Management](https://bitcoinexchangeguide.com/ethereum-erc725-blockchain-based-self-sovereign-identity-management/)
|
|
||||||
* [erc725alliance.org](https://erc725alliance.org)
|
|
||||||
* [ERC: Lightweight Identity #1056](https://github.com/ethereum/EIPs/issues/1056) —This ERC describes a standard for creating and updating identities with a limited use of blockchain resources. An identity can have an unlimited number of delegates and attributes associated with it. Identity creation is as simple as creating a regular key pair ethereum account, which means that it's fee (no gas costs) and all ethereum accounts are valid identities. Furthermore this ERC is fully DID compliant.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## uPort [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/sPAP2g3.png)
|
|
||||||
|
|
||||||
* [uPort](https://www.uport.me/) [[**G**](https://github.com/uport-project/)] [[**T**](https://twitter.com/uport_me)]
|
|
||||||
* [Ethereum studio ConsenSys launches digital IDs and assets secured on Ubuntu phones](http://www.ibtimes.co.uk/ethereum-studio-consensys-launches-internet-people-digital-ids-assets-secured-unbuntu-phones-1542620)
|
|
||||||
* [Year in Review. What's to come in 2018](https://medium.com/uport/uport-year-in-review-whats-to-come-in-2018-15ccb9214439)
|
|
||||||
* [Different Approaches to Ethereum Identity Standards](https://medium.com/uport/different-approaches-to-ethereum-identity-standards-a09488347c87)
|
|
||||||
![](http://i.imgur.com/ASI0PaB.png)
|
|
||||||
|
|
||||||
## uPort Github Repos [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/developers" target="_blank">/uport-project/developers</a> - Developer portal for documentation and application management
|
|
||||||
* <a href="https://github.com/uport-project/specs" target="_blank">/uport-project/specs</a> - uPort Protocol Specs
|
|
||||||
* <a href="https://github.com/uport-project/uport-connect" target="_blank">/uport-project/uport-connect</a> - Main uPort library for front end developers
|
|
||||||
* <a href="https://github.com/uport-project/eth-typed-data" target="_blank">/uport-project/eth-typed-data</a> - A javascript library for working with typed structured data as defined by EIP712
|
|
||||||
* <a href="https://github.com/uport-project/uport-transports" target="_blank">/uport-project/uport-transports</a> - Set up communication channels between your app and a uPort client to handle requests and responses.
|
|
||||||
* <a href="https://github.com/uport-project/webcard" target="_blank">/uport-project/webcard</a> - Transaction Sharing
|
|
||||||
* <a href="https://github.com/uport-project/demo" target="_blank">/uport-project/demo</a> - uPort Demo dApp
|
|
||||||
* <a href="https://github.com/uport-project/uport-lite" target="_blank">/uport-project/uport-lite</a> - Lightweight uport registry lookup
|
|
||||||
* <a href="https://github.com/uport-project/eslint-config-uport" target="_blank">/uport-project/eslint-config-uport</a> - Shareable eslint config for uport libraries
|
|
||||||
* <a href="https://github.com/uport-project/uPort-live" target="_blank">/uport-project/uPort-live</a> - Forked from Siunami/uPort-live
|
|
||||||
* <a href="https://github.com/uport-project/uport-wordpress-plugin" target="_blank">/uport-project/uport-wordpress-plugin</a> - A Passwordless Login for uPort and Wordpress
|
|
||||||
* <a href="https://github.com/uport-project/community-projects" target="_blank">/uport-project/community-projects</a> - A list of community hackathon projects and other experiments.
|
|
||||||
* <a href="https://github.com/uport-project/udoor" target="_blank">/uport-project/udoor</a> - uPort Door Management
|
|
||||||
* <a href="https://github.com/uport-project/uport-bounties" target="_blank">/uport-project/uport-bounties</a>- A Library of uPort Bounties
|
|
||||||
* <a href="https://github.com/dconroy/CityKey" target="_blank">/dconroy/CityKey</a> - Adding uPort support to Chicago CityKey, adding all the benefits of Self Sovereign Identity to municipal services. http://citykeychained.com
|
|
||||||
|
|
||||||
### uPort DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-resolver" target="_blank">/uport-project/ethr-did-resolver</a> - DID resolver for Ethereum Addresses with support for key management
|
|
||||||
* <a href="https://github.com/uport-project/secp256k1-did-resolver" target="_blank">/uport-project/secp256k1-did-resolver</a> - Resolve DID documents for secp256k1 public keys
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-driver" target="_blank">/uport-project/uport-did-driver</a> - Driver for the uPort DID method
|
|
||||||
* <a href="https://github.com/uport-project/eth-did-resolver" target="_blank">/uport-project/eth-did-resolver</a> - DID resolver for Ethereum Addresses
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did" target="_blank">/uport-project/ethr-did</a> - Create ethr DIDs
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-registry" target="_blank">/uport-project/ethr-did-registry</a> - Backing for an experimental DID method
|
|
||||||
* <a href="https://github.com/uport-project/did-resolver" target="_blank">/uport-project/did-resolver</a> - Generic did-resolver
|
|
||||||
* <a href="https://github.com/uport-project/https-did-resolver" target="_blank">/uport-project/https-did-resolver</a> - DID resolver for HTTPS domains
|
|
||||||
* <a href="https://github.com/uport-project/nacl-did" target="_blank">/uport-project/nacl-did</a> - Light weight DID method, complete with Identity Creation tools, encryption and JWT signing
|
|
||||||
* <a href="https://github.com/uport-project/did-jwt" target="_blank">/uport-project/did-jwt</a> - Create and verify uPort and DID compliant JWT's in Javascript
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-resolver" target="_blank">/uport-project/uport-did-resolver</a> - DID resolver for uPort identities
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Identification [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/openid" target="_blank">/uport-project/openid</a> - uPort openid
|
|
||||||
* <a href="https://github.com/uport-project/kmnid" target="_blank">/uport-project/kmnid</a> - A kotlin implementation of MNID
|
|
||||||
* <a href="https://github.com/uport-project/uport-registry" target="_blank">/uport-project/uport-registry</a> - Core uPort registry contract for linking attributes to uPort identities.
|
|
||||||
* <a href="https://github.com/uport-project/uport-chrome-extension" target="_blank">/uport-project/uport-chrome-extension</a> - An experiment to test decentralized identity in a Browser Extension environment.
|
|
||||||
* <a href="https://github.com/uport-project/infrastructure" target="_blank">/uport-project/infrastructure</a> - Support services for Self-Sovereign Identity
|
|
||||||
* <a href="https://github.com/uport-project/mnid" target="_blank">/uport-project/mnid</a> - Multi Network Identifier - spec and reference implementation
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Mobile [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-sdk" target="_blank">/uport-project/uport-android-sdk</a> - Collections of tools and helper libraries for android to issue and use identities on the uPort platform
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-signer" target="_blank">/uport-project/uport-android-signer</a> - android ETH signer library to be used by uport app and sdk
|
|
||||||
* <a href="https://github.com/uport-project/uport-android" target="_blank">/uport-project/uport-android</a> - uPort app for android - under construction
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-demo" target="_blank">/uport-project/uport-ios-demo</a> - Demo iPhone app using uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile-issues" target="_blank">/uport-project/uport-mobile-issues</a> - This repository is a place for developers to report and track status of issues reported while using the uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile" target="_blank">/uport-project/uport-mobile</a> - uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-sdk" target="_blank">/uport-project/uport-ios-sdk</a> - uPort iOS SDK in Swift
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-core-eth" target="_blank">/uport-project/uport-ios-core-eth</a> - iOS Ethereum Toolkit for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-openssl" target="_blank">/uport-project/uport-ios-openssl</a> - iOS OpenSSL Framework for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner" target="_blank">/uport-project/UPTEthereumSigner</a> - Ethereum signer library for iOS
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Lambda [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/lambda-chasqui" target="_blank">/uport-project/lambda-chasqui</a> - running_man Messenger service running_man
|
|
||||||
* <a href="https://github.com/uport-project/lambda-agora" target="_blank">/uport-project/lambda-agora</a> - An open public space where an assembly of applications can share details and be discovered (pre-alpha)
|
|
||||||
* <a href="https://github.com/uport-project/lambda-champagne" target="_blank">/uport-project/lambda-champagne</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-niscani" target="_blank">/uport-project/lambda-niscani</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-sensui" target="_blank">/uport-project/lambda-sensui</a> - uPort tx funding service
|
|
||||||
* <a href="https://github.com/uport-project/" target="_blank">/uport-project/lambda-caleuche</a> - Caleuche. Event Hub Service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-idgraph" target="_blank">/uport-project/lambda-idgraph</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-olorun" target="_blank">/uport-project/lambda-olorun</a> - uPort private network support
|
|
||||||
* <a href="https://github.com/uport-project/lambda-fatima" target="_blank">/uport-project/lambda-fatima</a> - uPort badge event attestor
|
|
||||||
* <a href="https://github.com/uport-project/lambda-pututu" target="_blank">/uport-project/lambda-pututu</a> - Push notification service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-nisaba" target="_blank">/uport-project/lambda-nisaba</a> - Lambda functions for anti-sybill
|
|
||||||
* <a href="https://github.com/uport-project/lambda-unnu" target="_blank">/uport-project/lambda-unnu</a> - Creator of Identities
|
|
||||||
|
|
||||||
### uPort React [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-signer" target="_blank">/uport-project/react-native-uport-signer</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-signer-demo" target="_blank">/uport-project/react-native-signer-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/uport-react-native-demo" target="_blank">/uport-project/uport-react-native-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-connect" target="_blank">/uport-project/react-native-uport-connect</a> - Library for integrating uPort into your React Native app
|
|
||||||
* <a href="https://github.com/uport-project/react-uport-box" target="_blank">/uport-project/react-uport-box</a> - Truffle and React/Redux boilerplate with uPort Connect
|
|
||||||
* <a href="https://github.com/uport-project/react-native-passcode-android" target="_blank">/uport-project/react-native-passcode-android</a> - Forked from aldigjo/react-native-passcode-android
|
|
||||||
|
|
||||||
### uPort Assorted [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/champagne-dapp" target="_blank">/uport-project/champagne-dapp</a> - Champagne Project dApp
|
|
||||||
* <a href="https://github.com/uport-project/tweetnacl-k" target="_blank">/uport-project/tweetnacl-k</a> - kotlin implementation of tweetnacl
|
|
||||||
* <a href="https://github.com/uport-project/sample-data-generator" target="_blank">/uport-project/sample-data-generator</a>
|
|
||||||
* <a href="https://github.com/uport-project/bck-wallet" target="_blank">/uport-project/bck-wallet</a>
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner-Example" target="_blank">/uport-project/UPTEthereumSigner-Example</a> - Example app and unit tests for the UPTEthereumSigner repo
|
|
||||||
* <a href="https://github.com/uport-project/lastblock" target="_blank">/uport-project/lastblock</a> - Daemon that alerts when a new block is mined
|
|
||||||
* <a href="https://github.com/uport-project/service-tests" target="_blank">/uport-project/service-tests</a> - Test servers from the outside
|
|
||||||
* <a href="https://github.com/uport-project/paper" target="_blank">/uport-project/paper</a>
|
|
||||||
* <a href="https://github.com/uport-project/swift-rlp" target="_blank">/uport-project/swift-rlp</a> - Recursive Length Prefix in Swift - CocoaPod
|
|
||||||
* <a href="https://github.com/uport-project/SwiftKeccak" target="_blank">/uport-project/SwiftKeccak</a> - Ethereum compatible Keccak hash for Swift
|
|
||||||
* <a href="https://github.com/uport-project/ed2curve-js" target="_blank">/uport-project/ed2curve-js</a> - Convert Ed25519 signing keys into Curve25519 Diffie-Hellman keys
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Jolocom [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/BNmq1U9.png)
|
|
||||||
|
|
||||||
* [Jolocom](http://jolocom.com/)
|
|
||||||
* a "SmartWallet" for everyone to own their personal digital identity, using [Social Linked Data](https://github.com/solid/solid-spec), WebID, and verifiable claims standards via Ethereum smart contracts.
|
|
||||||
* [A universal identity layer we can only build together](https://stories.jolocom.com/a-universal-identity-layer-we-can-only-build-together-e297ed5ae4ed)
|
|
||||||
|
|
||||||
## Jolocom Github Repos [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/jolocom/docs" target="_blank">/jolocom/docs</a> - Documentation
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-app" target="_blank">/jolocom/smartwallet-app</a> - A decentralized self sovereign identity solution developed by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-lib" target="_blank">/jolocom/jolocom-lib</a> - Library for interacting with the identity solution provided by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-did-driver" target="_blank">/jolocom/jolocom-did-driver</a> - Universal Resolver DID Driver for the did:jolo identity space
|
|
||||||
* <a href="https://github.com/jolocom/generic-backend" target="_blank">/jolocom/generic-backend</a> - A generic backend implementation that makes use of the Jolocom Library for authentication, and for issuing credentials.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso" target="_blank">/jolocom/demo-sso</a> - A simple example web application integrating the Jolocom library for authentication.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso-mobile" target="_blank">/jolocom/demo-sso-mobile</a> - An example mobile application in React Native that showcases the interaction flows between the Smartwallet and another mobile app.
|
|
||||||
* <a href="https://github.com/jolocom/cred-types-jolocom-demo" target="_blank">/jolocom/cred-types-jolocom-demo</a> - Collection of metadata definitions for the demo Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/react-native-build-config" target="_blank">/jolocom/react-native-build-config</a> - Expose native build config to JS (android only for now)
|
|
||||||
* <a href="https://github.com/jolocom/credTypes-jolocom-core" target="_blank">/jolocom/credTypes-jolocom-core</a> - Collection of metadata definitions for the core Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/fueling-service" target="_blank">/jolocom/fueling-service</a> - Simple express service that can wire ether to requester.
|
|
||||||
* <a href="https://github.com/jolocom/registry-contract" target="_blank">/jolocom/registry-contract</a> - A basic smart contract on top of the Ethereum network that registers mappings between DID and IPFS DDO hashes.
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-webid-proxy" target="_blank">/jolocom/smartwallet-webid-proxy</a> - WebID proxy service
|
|
||||||
|
|
||||||
## Spidchain [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/azuC8lh.png)
|
|
||||||
|
|
||||||
* [Spidchain](http://www.spidchain.com/) [[**wp**](https://drive.google.com/file/d/0B89WE3IIHmy1Z0ZSSWVmVEtaaG8/view)]
|
|
||||||
* "offers a platform for self-sovereign identity, including desktop and mobile apps for end-users. It uses Decentralized Identifiers (DIDs) - backed by optionally Bitcoin or Ethereum - to implement a marketplace for verifiable claims. The Spidchain applications allow individuals to create, recover, and revoke DIDs, to authenticate, to sign and verify files and claims, and more."
|
|
||||||
|
|
||||||
### Spid-Eth Repos [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/eth-lightwallet" target="_blank">/SpidChain/eth-lightwallet</a> - Forked from ConsenSys/eth-lightwallet
|
|
||||||
- Lightweight JS Wallet for Node and the browser
|
|
||||||
* <a href="https://github.com/SpidChain/truffle" target="_blank">/SpidChain/truffle</a> - Forked from trufflesuite/truffle
|
|
||||||
- A development framework for Ethereum
|
|
||||||
* <a href="https://github.com/SpidChain/VotingSystem" target="_blank">/SpidChain/VotingSystem</a> - A dapp, library and smart contract to notarize votes on the ethereum blockchain
|
|
||||||
* <a href="https://github.com/SpidChain/ethers-wallet" target="_blank">/SpidChain/ethers-wallet</a> - Forked from ethers-io/ethers.js
|
|
||||||
- Complete Ethereum wallet implementation and library in JavaScript.
|
|
||||||
* <a href="https://github.com/SpidChain/nodejs-ethereum" target="_blank">/SpidChain/nodejs-ethereum</a> - Forked from b9lab/nodejs-ethereum
|
|
||||||
Example of using NodeJs with Ethereum
|
|
||||||
|
|
||||||
|
|
||||||
### Assorted Ethereum Apps [**^**](#contents)
|
|
||||||
|
|
||||||
* [Deloitte SmartID](http://www.deloitte.co.uk/smartid/) [[**G**](https://github.com/SmartIdentity/smartId-contracts)]
|
|
||||||
* "Smart Identity uses the Ethereum blockchain to represent an identity using a smart contract, attributes can be added by the identity owner and are stored in hash form"
|
|
||||||
* [Nuggets](http://www.nuggets.life/) [[**wp**](https://nuggets.life/images/Nuggets-White-Paper.pdf)]
|
|
||||||
* "is a blockchain platform giving users a single biometric tool for login, payment and identity verification. It stores an individual's information in a "personal cloud" in "zero-knowledge blockchain storage".
|
|
||||||
* [poa.network](https://poa.network/)[**[D](https://medium.com/poa-network/poa-network-how-honey-badger-bft-consensus-works-4b16c0f1ff94)**]
|
|
||||||
POA Network is an Ethereum-based platform that offers an open-source framework for smart contracts. POA Network is a sidechain to Ethereum utilizing [Proof of Authority](https://blockonomi.com/proof-of-authority/)
|
|
||||||
as its consensus mechanism.
|
|
||||||
* [Cryptonomica.net](https://cryptonomica.net) is an identity verification service based on [OpenPGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) and [Ethereum](https://www.ethereum.org) with legal framework and online dispute resolution for electronic contracts from London-based [court of arbitration](https://cryptonomica.net/#!/arbitration)
|
|
||||||
|
|
16
docs/gdpr.md
16
docs/gdpr.md
@ -1,16 +0,0 @@
|
|||||||
# EU General Data Protection Regulation Act
|
|
||||||
|
|
||||||
* [Is Self-Sovereign Identity the ultimate GDPR compliance tool? [**1**]](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-9d8110752f89) [[**2**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-40db94c1c437)] [[**3**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-7296a3b07769)]
|
|
||||||
|
|
||||||
|
|
||||||
* [EU Blockchain Forum - Blockchain and the GDPR](https://www.eublockchainforum.eu/sites/default/files/reports/20181016_report_gdpr.pdf)
|
|
||||||
[![](https://i.imgur.com/HADdi6N.jpg)](https://www.eublockchainforum.eu/sites/default/files/reports/20181016_report_gdpr.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
* [Blockchains and Data Protection in the European Union](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3080322)
|
|
||||||
* [IBM — How blockchain could address five areas associated with GDPR compliance](https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=61014461USEN)
|
|
||||||
* [GDPR - A reflection on the 'self-sovereign identity' and the Blockchain](https://www.linkedin.com/pulse/gdpr-reflection-self-sovereign-identity-blockchain-nicolas-ameye/)
|
|
||||||
* [GDPR and Privacy by Design, What developers need to know](https://medium.com/@sphereidentity/gdpr-and-privacy-by-design-what-developers-need-to-know-fa5a936da65a)
|
|
||||||
* [Privacy by Design The 7 Foundational Principles](https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf)
|
|
||||||
* [When GDPR Becomes Real, and Blockchain is no longer fairydust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/gdpr.md)
|
|
||||||
* [Self-Sovereign Privacy By Design](https://github.com/sovrin-foundation/protocol/blob/master/self_sovereign_privacy_by_design_v1.md)s
|
|
@ -1,668 +0,0 @@
|
|||||||
---
|
|
||||||
title: Microledgers and Edge-Chains — A Primer
|
|
||||||
description: A Transcript of Daniel Hardman of Evernym Presenting at Hyperledger Global Forum — 2018
|
|
||||||
image: "https://infominer.id/images/edge-card.png"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Hyperledger Global Forum 2018 — Microledgers and Edge-Chains
|
|
||||||
**A Primer - Daniel Hardman, Evernym**
|
|
||||||
|
|
||||||
<code>Editors Note: I've taken to working on youtube transcripts for podcasts and videos whos content is valuable and not readily accessible in text form, so that it will be easier for anyone to reference. -<a href="https://infominer.id">infominer</a></code>
|
|
||||||
|
|
||||||
[Evernym](https://evernym.com)’s Chief Architect [Daniel Hardman](https://www.evernym.com/team/daniel-hardman/) takes the Hyperledger community through Evernym’s work on Microledgers and Edge-Chains Architecture. Attendees will gain insight into the theory, applications and evolution in Hyperledger Indy along with a practical discussion of their potential.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/H5ijP94.png"/>\
|
|
||||||
<sup><a href="https://www.youtube.com/watch?v=iK5vd7-b1zA&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=100">Youtube: Hyperledger Global Forum- Microledgers and Edge-Chains: A Primer- Daniel Hardman, Evernym</a></sup>
|
|
||||||
|
|
||||||
* [Daniel Hardman, Chief Architect - Evernym](https://hgf18.sched.com/event/G8sN/microledgers-and-edge-chains-a-primer-daniel-hardman-evernym)
|
|
||||||
> Daniel Hardman has a quarter century of experience in enterprise software. As a technical director or chief architect, he’s led engineering teams at small startups, an incubator, and a continent-spanning business unit at a Fortune 500 company. He founded a dot com a few years back, serving as CEO and later CTO before selling the business. Daniel designed and personally coded complex scheduling software that runs the biggest supercomputers on the planet. He also worked on big data systems that use natural language processing and machine learning/AI to impute reputation to the entire observable internet. He is a member of Infraguard, has training in cybersecurity, and has spoken at industry conferences such as RSA. Daniel has an MBA plus a master’s degree in computational linguistics. He holds numerous patents and is a prolific blogger.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Microledgers and Edge-Chains](#microledgers-and-edge-chains-)
|
|
||||||
* [A Personal Arc](#a-personal-arc-)
|
|
||||||
* [Blockchain— the new centralization](#blockchain-the-new-centralization-)
|
|
||||||
* [Where Blockchain is Needed (or Not)](#where-blockchain-is-needed-or-not-)
|
|
||||||
* [Microledgers](#microledgers-)
|
|
||||||
* [How Blockchain is Still Relevant](#how-blockchain-is-still-relevant-)
|
|
||||||
* [App Centralization Continuum](#app-centralization-continuum-)
|
|
||||||
* [Teleomergent - More than a decentralized app](#teleomergent---more-than-a-decentralized-app-)
|
|
||||||
* [Dapps vs Edgechain Protocols](#dapps-vs-edgechain-protocols-)
|
|
||||||
* [Defining an Edgechain Protocol](#defining-an-edgechain-protocol-)
|
|
||||||
* [A Familiar Example—Buying a House](#a-familiar-examplebuying-a-house-)
|
|
||||||
* [Trust Ping Protocol](#trust-ping-protocol-)
|
|
||||||
* [Tic Tac Toe](#tic-tac-toe-)
|
|
||||||
* [DID method for peer (private pairwise) DIDs](#did-method-for-peer-private-pairwise-dids-)
|
|
||||||
* [Peer DID Method Spec](#peer-did-method-spec-)
|
|
||||||
* [Megaphone Protocol](#megaphone-protocol-)
|
|
||||||
* [Call to Action](#call-to-action-)
|
|
||||||
* [Q&A](#qa-)
|
|
||||||
* [Home](https://infominer.id)
|
|
||||||
|
|
||||||
## Microledgers and Edge-Chains [**^**](#contents)
|
|
||||||
**Lightly edited transcript from Youtube.**
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/Hu9v2Md.png"/>
|
|
||||||
|
|
||||||
Okay, I think we'll go ahead and get started. There are likely to be people trickling in, if they're like I am. If I didn't have to be here speaking I would take my time getting in the next session after lunch feeling a little bit sluggish... but anyway, they'll come in and and we'll already be in the presentation.
|
|
||||||
|
|
||||||
My name is Daniel Hardman, hopefully you've if you read about this session you might know a little bit about my background. I work with Hyperledger Indy project, mostly. I'm a maintainer there, and I also work for, well so I have a day job with Evernym... and then a side gig, where I work on the technical governance part of the Sovrin Foundation, which is closely connected to the Indy project.
|
|
||||||
|
|
||||||
Anyway, today I'm going to talk about some concepts that have been marinating in my mind and in the minds of some people that I work with for quite a while. Not all these ideas are originally mine I want to give credit where credit is due.
|
|
||||||
|
|
||||||
Lots of other smart people have been talking and thinking about this as well I'm just a spokesman for a lot of other people, and hopefully the title intrigued you a little bit.
|
|
||||||
|
|
||||||
Microledger's and edge-chains: I'm going to demystify that, and when you walk away I hope you're gonna think of this as not so much a super technical session that you've been to but instead a session that kind of has some intriguing ideas for you to think about later in whatever you're doing.
|
|
||||||
|
|
||||||
## A Personal Arc [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/5aXEDkg.png"/>
|
|
||||||
|
|
||||||
I'd like to start by taking you on a little bit of a personal journey. I started working in blockchain two and a half years ago, and when I first became aware of the basic concepts of how blockchain worked and so forth I became really excited about how blockchain had solved a bunch of problems
|
|
||||||
|
|
||||||
and how I was going to go conquer the world with all this new technology and it was awesome and that was a I lasted in that phase of my acquaintance with blockchain for, I don't know, several months but I start to encounter practical problems with some of the blockchain stuff I was doing.
|
|
||||||
|
|
||||||
and I hope as I describe the rest of this arc you'll smile a little bit to yourselves, and say, yeah I've kind of been through the same thing.
|
|
||||||
|
|
||||||
in a way this is kind of like the Gartner hype cycle you know there's the the spike of excitement and then the trough of disillusionment.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/BsTgEd0.png"/>
|
|
||||||
|
|
||||||
I went through learning about some of the performance and scaling issues that we had to deal with, and some of the complexity.
|
|
||||||
|
|
||||||
and then I started to realize that putting data on the blockchain had certain repercussions that I didn't always want to deal with, and that there needed to be some very careful thought about how we encrypted data.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/kdoyUEq.png"/>
|
|
||||||
|
|
||||||
and then I realized encrypting it wasn't enough, it just plain shouldn't be there at all. and so hopefully you guys are recognizing these kinds of patterns in your own thinking here and then I got into the whole all regulatory compliance of GDPR thing and gee this is getting harder and
|
|
||||||
harder.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/V5cyLYb.png"/>
|
|
||||||
|
|
||||||
Then I and several of my companions discovered this notion of microledgers, and we feel like it was kind of an aha moment for us. So I'll explain what microledgers are and I think you'll see how that's relevant to this arc when I'm done.
|
|
||||||
|
|
||||||
Let me just point out that that same kind of arc that I just described in my own thinking we're seeing unfold in lots of different ways in the whole blockchain space.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/oVC0WwF.png"/>
|
|
||||||
|
|
||||||
All of the things on this list here are examples of projects where somebody has thought hard about the original blockchain paradigm, and tweaked something in an interesting way because
|
|
||||||
of that same arc, and you know the tweaks are different.
|
|
||||||
|
|
||||||
* plasma is about taking smart contracts off the blockchain
|
|
||||||
* triple signed receipts is about preserving confidence in data but not having to keep a full history even though you have a strong proof that you're at the right state anyway
|
|
||||||
|
|
||||||
they all different things up there and if you don't know about all those, I didn't know about all of them either until I went and researched this talk, and I was looking for patterns.
|
|
||||||
|
|
||||||
I knew about some of them and I found some others there but the point is that I think the whole industry is going through a maturation phase where we're realizing that there's certain aspects of what blockchain can do that we love, and there's other aspects of what blockchain gives us that we don't love so much and we're trying to kind of wrestle against those constraints
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/ZBiVQ0J.png"/>
|
|
||||||
|
|
||||||
These are the two things that I think these arcs all have in common, mine and and the things on the previous slide: they're all trying to do less with the central big blockchain in some creative way so that they can keep the special value out of the blockchain but not have some of its downsides.
|
|
||||||
|
|
||||||
## Blockchain— the new centralization [**^**](#contents)
|
|
||||||
|
|
||||||
I want to just point out something I went and looked just for fun I went and looked up architecture diagrams with Google. I was looking for old client-server architecture diagrams okay and these are just three that I picked at random out of the Google image search results list
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/yYUdvNr.png"/>
|
|
||||||
|
|
||||||
you see that client-server is kind of this old paradigm where we have this notion of a centralized thing, and client-server equals bad, right?
|
|
||||||
|
|
||||||
we've been down that road we don't like that anymore, but here's what's interesting I also went and searched for some architecture diagrams about blockchain and some blockchain supposed to be highly decentralized and lo and behold there are lots and lots of evidence in these diagrams that blockchain is actually it just almost the exact same thing
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/py6olR5.png"/>
|
|
||||||
|
|
||||||
now there's some things about blockchain that are different I'm not arguing that they're identical but the point is there is this phenomenon sometimes that blockchain has been used in a way that's far more centralized than we like to admit yes there are nodes that spread the load around and yes the nodes create this notion of diverse or I mean diffuse trust and yet all of those nodes can be treated as one bundle in the middle
|
|
||||||
|
|
||||||
and in fact in a lot of architecture diagrams that you see in presentations at this conference and any other conference you will see a little graphic that represents the blockchain and a bunch of arrows coming to it from all over the place and what's that that's centralization
|
|
||||||
|
|
||||||
## Where Blockchain is Needed (or Not) [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/ugjLkS9.png"/>
|
|
||||||
|
|
||||||
so we don't necessarily need the blockchain for everything that we think we need it for the Vitalik, back in April, I'll let you read that quote there, well actually I'm going to read it because it's such a good one:
|
|
||||||
|
|
||||||
>Blockchains.. are a far less efficient computer and database than technologies that have existed for over 40 years... efficiency is not what block chains are built for - [Vitalik Buterin, April 2018](https://www.youtube.com/watch?v=jJt3yag96fU)
|
|
||||||
|
|
||||||
if you actually go and look up that quote he does a comparison of how much it costs to do certain kinds of computations on Ethereum versus AWS, and it's about a million to one difference in efficiency.
|
|
||||||
|
|
||||||
>"Let's say you and I, we are happy to do some transactions with each other.. We don't really need to use the blockchain unless we disagree with each other... Why would you need the mediator if you are actually in accordance...?" - Arther Gervais (Founder of Liquidity Netowrk), June 2018
|
|
||||||
|
|
||||||
Then founder of Liquidity Network, in June. This is a really good quote: - bottom line is this notion, you know what? Why would you need a mediator if you're actually agreeing with each other?
|
|
||||||
|
|
||||||
now there's an answer to that question but there's also, that question exposes some interesting things to think about.
|
|
||||||
|
|
||||||
I think smart people in the industry are starting to question some basic assumptions.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/ZfhYNAD.png"/>
|
|
||||||
|
|
||||||
here's my picture of an architecture that's centralized in blockchain oriented you got the blockchain in the middle here and you got the arrows coming to it right this is how I was thinking about my own particular problem which was the identity management relationship management problem that's at the core of identity when I first came into this world and if you see,
|
|
||||||
|
|
||||||
we've got two parties that each have a relationship and want to trust each other we have Alice we have Bob and Alice needs to know some things about her view of this relationship and she also needs to know some things about Bob's view of the relationship okay and these two views of the world
|
|
||||||
|
|
||||||
|
|
||||||
what's symmetrical and complimentary but they're using the blockchain in the middle as the trusted intermediary and like I said this view of the world sort of works but it chafed on me and it became increasingly uncomfortable as I learned some of the drawbacks and challenges to it
|
|
||||||
|
|
||||||
## Microledgers [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/kX93eTU.png"/>
|
|
||||||
|
|
||||||
Here's what I evolved to, and this is what I want to talk to you about, is the microledger notion. In this notion you still have a blockchain, and blockchain does have relevance it's highly relevant, but it's not the main mediator of the relationship between Alice and Bob.
|
|
||||||
|
|
||||||
Alice and Bob talk to each other directly and then they have this kind of back-channel thing that they can use to interact with the blockchain to the extent that they need to and I'm gonna talk about what they really need the blockchain for but it's not as much as we thought at least as much as I thought to begin with
|
|
||||||
|
|
||||||
so when you have this kind of a relationship what you have is two parties that are kind of at the edge of the old diagram, instead of the thing that's in the middle, you have the things that are at the edges okay and these things at the edge are talking to each other. this is how I get the concept of an edge chain
|
|
||||||
|
|
||||||
that's where that word in the title of the presentation comes from, is the notion that you can have some of the same characteristics of a blockchain, you can have high trust and tamper resistance, and diffuse patterns of communication and so forth. but, you don't have the blockchain sitting in the middle of it. it's all happening out at the edges
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/c0mtJW0.png"/>
|
|
||||||
|
|
||||||
|
|
||||||
okay so this evolves even further: if you have this person Alice having relationships with multiple people, she
|
|
||||||
continues to have these lateral side relationships. she doesn't have them through the blockchain.
|
|
||||||
|
|
||||||
now you might be saying well wait a minute if you take the blockchain and all those big arrows out what is it even useful for?
|
|
||||||
|
|
||||||
## How Blockchain is Still Relevant [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/uJ1Kkwq.png"/>
|
|
||||||
|
|
||||||
In my case it's useful for certain problems that require external trust. For example, there has to be a place where I can announce that a credential, upon which identity is based, has been revoked. The world needs to test for that condition when they're seeing credentials presented.
|
|
||||||
|
|
||||||
I know that there's people out here who aren't in the identity space. I think there's analogs to this in in non-identity world too.
|
|
||||||
|
|
||||||
There's certain things that you need to consult the blockchain for. The main things that aren't on this list are things like:
|
|
||||||
* talking to each other
|
|
||||||
* storing things
|
|
||||||
* doing computation
|
|
||||||
* interacting
|
|
||||||
None of that stuff has to go through smart contracts or any of that. It just has to have a few very small things that make this possible.
|
|
||||||
|
|
||||||
Besides revoking credentials, in the identity space:
|
|
||||||
* You have to be able to revoke a device: If you leave your phone in on the backseat of an uber you need to be able to quickly say don't let anybody use that phone to impersonate me.
|
|
||||||
* you need to be able to discover parties that are intending to be public
|
|
||||||
* you need a secret rendezvous spot: so if you think of secret agents that you know they're heading off into enemy territory, and they agree that if if they're not back by such-and-such a time, then they're going to meet in the square at midnight, or whatever...
|
|
||||||
You can use a blockchain kind of like that: agree that we'll rendezvous on the blockchain if we lose track of one another, or have to repair a relationship and we can't do it by direct conversation.
|
|
||||||
|
|
||||||
It turns out that Merkel proofs of state integrity between these two parties can be relevant.
|
|
||||||
|
|
||||||
This last one is where I get the name micro ledger for this talk. That is, the way that these two parties interact with each other, has to have some characteristics of proveability and tamper-resistance even though it's not on the main blockchain.
|
|
||||||
|
|
||||||
You can do that by doing some very simple (well it's not very simple... it's simple compared to other stuff) crypto on your local hard drive..
|
|
||||||
|
|
||||||
When you interact with the other, passing them Merkel proof-of-state and having them check it against what they have.
|
|
||||||
|
|
||||||
you end up knowing with confidence that both of you have the same thing, and and you haven't drifted or misinterpreted one another.
|
|
||||||
|
|
||||||
You end up basically having a tiny little ledger on your machine for the relationship. Alice would have one for the relationship she has with Bob. I'm talking tiny, I'm talking 5k 10k little tiny files.
|
|
||||||
|
|
||||||
They're not massive, they don't last necessarily forever, they don't store any significant amounts of information, but they just have an orderly sequence of hashes that show how state has evolved that's the micro ledger concept.
|
|
||||||
|
|
||||||
## App Centralization Continuum [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/lnKUizp.png"/>
|
|
||||||
|
|
||||||
After we started playing with this idea I started to see things a little bit different this is my journey again but I thought instead of it being kind of a time sequence I saw it as a continuum of centralization and I really think that's where my mental journey took me is I started out thinking blockchain was cool and I'm going to be decentralized but I wasn't really very decentralized in my thinking and took me a long time to get there
|
|
||||||
|
|
||||||
you know I started over with "put it all in the blockchain" which isn't so far away from traditional client-server
|
|
||||||
|
|
||||||
then you start seeing people talking about sub chains and side chains and things like that that's an example of moving farther to the right on the continuum
|
|
||||||
|
|
||||||
then you hear people talking about well just anchor it on the blockchain now we're starting to get pretty far over to the towards the right if you go all the way over to the right you have a pure edge chain where you really don't need the blockchain at all.
|
|
||||||
|
|
||||||
I don't think I'm gonna write any software that looks completely at that end of the continuum. I think the blockchain introduces some characteristics of trust that I really need but I think I can get pretty far over here get all the benefits from blockchain that I really care about but not have hardly any of the drawbacks or complications and the only price is complexity darn it
|
|
||||||
|
|
||||||
okay so I put up here on this picture, also I have gaps right here and edge chain protocols. when I first started exploring this notion of the edge chain, I was calling the thing that we were building a dApp. because it's a decentralized app, of course. but I realized that what the industry is calling a dApp is actually pretty far over to this side because it's typically running everything through a smart contract that does centralize computation.
|
|
||||||
|
|
||||||
there are dApps that aren't that way, so the DAP thing moves over towards the right. There are some gaps that get maybe almost this far, but you you can take it all the way over here, and I think if you go way over to the right side it's not really fair to call that a dApp because it's pretty different from what the industry thinks a dApp is.
|
|
||||||
|
|
||||||
## Teleomergent - More than a decentralized app [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/1E6jCjZ.png"/>
|
|
||||||
|
|
||||||
I'm gonna give you some examples here in just a minute. Just for kicks, I'm gonna introduce a new word to you, because this is why I'm excited about the right end of that continuum. I think that the things on the right end of that continuum have this characteristic.
|
|
||||||
|
|
||||||
this is a big word, you know, a $24.00 word. but it's "telly-o-mergent." If you're familiar with the word [teleology](https://www.merriam-webster.com/dictionary/teleology) or [telonomy](https://www.merriam-webster.com/dictionary/teleonomy), this has the notion that you have order from chaos.
|
|
||||||
|
|
||||||
Okay? but, it's not order that's decreed by some central party it's order that arises spontaneously. Teleonomy is used in discussions about evolution and biology and how a very complex ecosystem can manifest really sophisticated patterns of behavior even though there's not anybody out there telling the Zebras which direction to run when the Lions chase them
|
|
||||||
|
|
||||||
so you may have also heard the word chaotic before and you may have run into the notion of Adam Smith's invisible hand in the economy it's the notion that you give a bunch of independent actors the right incentives and lo and behold the free market causes an interesting dynamic to emerge that's useful
|
|
||||||
|
|
||||||
and that's what I think is the true characteristic at the far right side is that you give independent agents the ability to interact and these agents find useful ways to interact according to a protocol.
|
|
||||||
|
|
||||||
## Dapps vs Edgechain Protocols [**^**](#contents)
|
|
||||||
|
|
||||||
this is just a little compare and contrast I think I'm gonna skip over this suffice it to say that daps and edge chains have a lot in common but I think there's some interesting differences
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/cVg6gFH.png"/>
|
|
||||||
|
|
||||||
and I'll maybe during Q&A; we can come back to this slide if you have questions about it, but let me now actually give you some examples of what I'm talking about.
|
|
||||||
|
|
||||||
## Defining an Edgechain Protocol [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/vIDt6iO.png"/>
|
|
||||||
|
|
||||||
When you define an edge chain protocol you have to answer these four questions:
|
|
||||||
|
|
||||||
* what are the roles in my protocol?
|
|
||||||
* what types of messages do we exchange?
|
|
||||||
* what stage or sequencing rules apply?
|
|
||||||
* and how our trust and incentives managed?
|
|
||||||
|
|
||||||
## A Familiar Example—Buying a House [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/XEpCvty.png"/>
|
|
||||||
|
|
||||||
so here's a really familiar example, okay? no tech involved. how do you buy a house? What are the roles in buying a house?
|
|
||||||
|
|
||||||
well you have a buyer and a seller, and the realtor for the buyer and the realtor for the seller. you have a home inspector, you have a title company.
|
|
||||||
|
|
||||||
these are roles, and by the way, buying a house is a protocol. You can't just go order a title, insurance, on some arbitrary home, because that would be out of order for the, it's not the sequence.
|
|
||||||
|
|
||||||
You have to start by doing step one and then you go to step two and then you go to step three right and the parties in this interaction have responsibilities they can do certain things, and not other things.
|
|
||||||
|
|
||||||
The kinds of messages that get exchanged in this protocol: we have an offer to buy, a counter-offer, an acceptance or rejection, a home report, a title search. These are messages.
|
|
||||||
|
|
||||||
What are the state rules that apply? well this is an example state machine I drew. You start by negotiating and you can go round and round in circles in negotiating, eventually you exit the negotiating phase. you're in the preparing phase where you order a title search and a home report and all these things and anyway you end up consummating the deal or not consummating it
|
|
||||||
|
|
||||||
That is an edge protocol.
|
|
||||||
|
|
||||||
Why is it an edge protocol?
|
|
||||||
|
|
||||||
There's no blockchain involved, right? it's people out at the edge.
|
|
||||||
|
|
||||||
There's a hundred thousand things like this, ordering a hamburger is a protocol. You can't just walk up to somebody nd say, "here's seven twenty five." You have to walk up to him and say, "I want number three on the menu," then give him $7.25 after they ask you "is that to go or not?" "to go" right?
|
|
||||||
There's this whole protocol involved in that, that we all know. The reason I'm harping on this is because all kinds of business problems are solved by protocols all the time, and in fact, they're mostly edge protocols.
|
|
||||||
|
|
||||||
That's a cool thing if you can just hook them up to blockchain for just the parts that you need them for, and not all of it. The weight of what you're building goes way down.
|
|
||||||
|
|
||||||
## Trust Ping Protocol [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/pUnUIiD.png"/>
|
|
||||||
|
|
||||||
Here's a simple edge protocol that's techy. this one is relevant to the identity space. This is the trust ping protocol, and in Indy there is a HIPE (which is like an RFC) about how you ping another person.
|
|
||||||
|
|
||||||
You have their DID, for them that's their identifier, and given that identifier you should be able to reach out and talk to that person.
|
|
||||||
|
|
||||||
So how do you do it? According to the whole Indy technology should be able to do it no matter what transport you're used to send messages whether it's HTTP or mail or Bluetooth or whatever.
|
|
||||||
|
|
||||||
You should know some things when you engage in this trust ping about whether the person on the other side is trustworthy and how much trust might have been eroded by the kind of mechanisms you used in between you.
|
|
||||||
|
|
||||||
There's a HIPE about that, you can see the roles, the pinger and the pingee; and the message types.
|
|
||||||
|
|
||||||
let me give you a quick demo of this protocol. I'm gonna start up an indie agent, and that agent is going to be listening on email, and I'm going to talk to it by email, and I'm gonna use the trust ping protocol to to interact with it.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/SA01z4J.png"/>
|
|
||||||
|
|
||||||
This is the [trust ping protocol documentation](https://github.com/hyperledger/indy-hipe/pull/67), and the trust ping documentation says that if I want to ping somebody this is the kind of JSON message I need to send it.
|
|
||||||
|
|
||||||
So, I'm gonna send it one. Let's go over here to my email, and I'll bring up my little trust ping. nothing up my sleeve. here's the the JSON that I'm sending, which is just a direct copy and paste out of this HIPE here... so that's the that's the stuff that I sent.
|
|
||||||
|
|
||||||
and let's see... message was sent. that's good. now what we've got to see is if the message is going to come back... there we go.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/qe7MocA.png"/>
|
|
||||||
|
|
||||||
so the agent on the other side pinged me back and let's see what it sent me: it sent me an aim style message.
|
|
||||||
|
|
||||||
This is the JSON that I got back, it says "hi" from Indy agent. So, I've just engaged in a protocol.
|
|
||||||
|
|
||||||
Now what does blockchain add to this? I could do this entirely without blockchain, but there's some things I wouldn't have: I wouldn't have confidence in the other sender. Somebody could sit in between me in this protocol and mess with my mind, right? be a man-in-the-middle.
|
|
||||||
|
|
||||||
So most of the protocol is not modified, but by adding a little bit of blockchain pixie dust, I'll call it, I can increase the trust behind this protocol.
|
|
||||||
|
|
||||||
That's the kind of thing that I'm seeing over and over again as I get my head wrapped around this paradigm is you start with a paradigm that's really not very blockchain heavy, and then you say "what are the things that's wonderful about blockchain, that I need to add into this? and how can I do it as light as possible?"
|
|
||||||
|
|
||||||
## Tic Tac Toe [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/Ym9zesW.png"/>
|
|
||||||
|
|
||||||
okay so on to the next thing... here. Tic Tac Toe. We could also play tic-tac-toe. I'm gonna wait and see if I have enough time. I'll do a demo of tic-tac-toe if you feel like it later. but anyway I have a demo of that if you want to. this one was not there's no blockchain goodness on this this is all the way to the complete right side is being a pure hedge protocol because you don't need a blockchain to play tic-tac-toe okay.
|
|
||||||
|
|
||||||
## DID method for peer (private pairwise) DIDs [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/T3nCl47.png"/>
|
|
||||||
|
|
||||||
This is a more serious one. What if you want to manage a relationship? Alice and Bob live across the world, they use complicated technologies. Each of them has different technologies. One of them has a laptop, and a cell phone; and the other one has a desktop computer at work, and two cell phones, and something in the cloud.
|
|
||||||
|
|
||||||
They want to talk to each other and there's different pieces of software running on all these different things at different version levels and all this kind of stuff.
|
|
||||||
|
|
||||||
How does Alice tell Bob: "you shouldn't accept messages anymore from my old cell phone that I just sent to the recycling"?
|
|
||||||
|
|
||||||
I think they told me they were gonna wipe the hard drive on it but I just don't trust I'm gonna tell Bob not to do that. How does Alice say, "I upgraded my own world here, and I've got a new device, and now if I send messages from that device you
|
|
||||||
should trust them."
|
|
||||||
|
|
||||||
how does Alice say I'm gonna rotate my keys? all of these are concerns of managing a relationship, and you need a protocol to manage a relationship... and guess what? it's mostly an edge protocol.
|
|
||||||
|
|
||||||
## Peer DID Method Spec [**^**](#contents)
|
|
||||||
|
|
||||||
This is a more serious one that has pretty high stakes. I've been working on a method to describe how DIDs can be created, and the DID docs associated with those DIDs can be shared.
|
|
||||||
|
|
||||||
You can see the the roles here are the participants in the relationship and there's some message types that are described here there's actually a [DID method spec draft](https://dhh1128.github.io/peer-did-method-spec/index.html) and I'll show that to you really briefly here and you can go look it up yourself later if you want to
|
|
||||||
|
|
||||||
<a href="https://dhh1128.github.io/peer-did-method-spec/index.html"><img src="https://imgur.com/QlhWEmfl.png" /></a>
|
|
||||||
|
|
||||||
|
|
||||||
I'll give you the URL and you can go read it, but there's this whole spec behind this, and this is what has caused, I think, the most ruminating on the concept of a microledger... because the microledger as a persistence mechanism could provide high trust to back the did method that I'm mentioning.
|
|
||||||
|
|
||||||
## Megaphone Protocol [**^**](#contents)
|
|
||||||
|
|
||||||
Let me go on to another one that's maybe a little bit more interesting so this is just an imaginary one but I think I'd love if somebody in the audience wants to build this I'd be super excited and I would buy your app.
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/wzji3sc.png"/>
|
|
||||||
|
|
||||||
A megaphone protocol, what I'd like is something where if I'm sitting on the beach in Indonesia and a tsunami happens... I can grab my phone and push a button and say "run a tsunamis coming" and my phone contacts all the phones all around the resort where I'm staying which in turn contact all the phone's a mile inland and everybody starts running not just the people who can see the wave. Would that be cool?
|
|
||||||
|
|
||||||
I want basically a virtual megaphone, but here's a "why do I need blockchain?" there's a really good answer to this, I can't build this right now, because if everybody had a real megaphone in real life you'd have problems with people using it irresponsibly, wouldn't you?
|
|
||||||
|
|
||||||
So there's a trust problem, I can use blockchain to require people to put stake, or put their identity in escrow against their responsible behavior. So that a person can say, when it's a life-or-death situation, "I need an EpiPen right now!"
|
|
||||||
|
|
||||||
I'm willing to you know have a hundred dollars on the line or I'm willing to have my identity disclosed if I am shown to use that irresponsibly and that protocol can hook back to the blockchain as a basis for that trust but most of everything that's happening is all out on the edge.
|
|
||||||
|
|
||||||
you can see some of the other ones, you know, "my child is lost at Disneyland," or "I'm desperate to get on this plane as somebody in this line willing to send me to sell me their plane ticket 4000 euros?"
|
|
||||||
|
|
||||||
any of these kinds of things could be done with this kind of protocol, and you would just need peer-to-peer communication in your app. Or you could have the app go back to the cloud and talk to other apps through the cloud, if you needed to.
|
|
||||||
|
|
||||||
that would be more centralized but anyway there's some roles in this a speaker a listener and a relay so you could have an app and a person could talk through your app to another phone that was close to you and so the word would spread right if anybody's interested there's a link to the concept doc when you download the slides you can go read more about that protocol
|
|
||||||
|
|
||||||
## Call to Action [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/xLHfZ7b.png"/>
|
|
||||||
|
|
||||||
I hope that I haven't gone too too deep, I've tried to stay really high-level and I hope that I've been general enough that even if you're not in the Indy space, the identity space, you're thinking a little bit to yourself yeah maybe there's some ways that I'm taking for granted
|
|
||||||
|
|
||||||
that we need to use the blockchain for something... and maybe I should think from the other direction instead start thinking about the problem as an edge protocol problem and then say how do I sprinkle the the magic pixie dust a blockchain just enough to get the properties of trust or the constraints that I need
|
|
||||||
|
|
||||||
what I've found is that this is a very liberating experience. Two and a half years in, a lot of the problems that I initially thought were really yucky, I'm now thinking, "well if I flip it on its head I can get what I need to and I
|
|
||||||
don't have the performance problem or I don't have the scaling problem or I don't have the centralization and trust problem or the regulatory problem.
|
|
||||||
|
|
||||||
So I want to encourage you to do that. Think in terms of the edge, with a blockchain as a useful foundation that you can refer to but not necessarily as the place where it all happens. You don't have to compute everything in a smart contract.
|
|
||||||
|
|
||||||
there are some problems that you must use blockchain for but I'm just saying use it wisely, and not just peanut butter spread it on everything.
|
|
||||||
|
|
||||||
I would love to get some people here to work with me on this peer did method I think it's a very high value for the identity space that's one specific to my area of expertise so with that I'll go back and demo something if you want or we can go into QA I think we got about ten minutes
|
|
||||||
left which is good
|
|
||||||
|
|
||||||
## Q&A [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/HNmcUfN.png"/>
|
|
||||||
|
|
||||||
I was trying hard to not go till the very last second well it doesn't necessarily have to be a person but some entity on the edge yeah and I'm really using the term edge of course is really vague but what I mean by it mostly is it's not the thing in the center of the architecture diagram okay and then the second question the concept of the micro ledger is there any concept of persisting the final values of the micro ledger onto a blockchain yeah so this is if I go back to let's see the notion of anchoring something on a blockchain a number of people in industry are exploring different ways to do that and one of the things you could anchor on a blockchain is a micro ledger so if you needed to prove for example to a third party let's say Alice and Bob are interacting and it's it's a private personal relationship but let's say Bob doesn't fully trust Alice and maybe he's afraid that alice is gonna steal all of his cool music for his next album even because he's been sharing it with her so
|
|
||||||
he goes and he anchors some things on
|
|
||||||
the blockchain to provide evidence so
|
|
||||||
that if anybody ever you know if there's
|
|
||||||
ever an argument there's a third party
|
|
||||||
that's a witness that kind of a thing
|
|
||||||
and there's other kinds of use cases
|
|
||||||
like that too
|
|
||||||
hi so obviously it's a communication
|
|
||||||
protocol so I'm wondering if there was
|
|
||||||
any thoughts about communication
|
|
||||||
recording or if it could be useful in
|
|
||||||
any way I know there have been papers
|
|
||||||
for TLS communication recording but
|
|
||||||
obviously it's not easy to do at this
|
|
||||||
point with TLS and HTTPS so is there any
|
|
||||||
ideas about communication recording
|
|
||||||
between the agents or da DS and how it
|
|
||||||
could be possibly useful so that's an
|
|
||||||
interesting question I used to work at
|
|
||||||
Blue Coat which makes a line of products
|
|
||||||
actually blue coats been acquired by
|
|
||||||
Symantec so if you look this up now
|
|
||||||
online you're gonna have to look under
|
|
||||||
Symantec but anyway blue coat makes a
|
|
||||||
made a product called an SSL visibility
|
|
||||||
appliance and what it is is a
|
|
||||||
deliberately constructed
|
|
||||||
man-in-the-middle attack on a TLS
|
|
||||||
session so an enterprise does some fancy
|
|
||||||
magic with certificates to make it so
|
|
||||||
that when you inside the enterprise talk
|
|
||||||
to somebody outside the enterprise that
|
|
||||||
appliance catches the traffic and it man
|
|
||||||
in the Middle's both of you neither side
|
|
||||||
can tell that there's this thing in the
|
|
||||||
middle and the whole point of it is make
|
|
||||||
the TLS channel visible so that the
|
|
||||||
enterprise can look for malware that's
|
|
||||||
coming into the environment and stuff
|
|
||||||
like that so where I'm going with this
|
|
||||||
is that same kind of technique could be
|
|
||||||
used in agent to agent communication
|
|
||||||
however you would have to get the
|
|
||||||
consent of both ends of the conversation
|
|
||||||
you don't have the ability like you do
|
|
||||||
in an enterprise to simply say well
|
|
||||||
every browser in our enterprise is going
|
|
||||||
to accept this certificate authority
|
|
||||||
therefore nobody's going to get any
|
|
||||||
warnings when they click and and stuff
|
|
||||||
like that so self sovereign identity
|
|
||||||
technologies provide a protection
|
|
||||||
against that kind of sniffing happening
|
|
||||||
invisibly but it could be done and the
|
|
||||||
old the other thing I was going to say
|
|
||||||
is there's also a hype
|
|
||||||
a proposal about message tracing this is
|
|
||||||
cooperative voluntary message tracing
|
|
||||||
where people are trying to troubleshoot
|
|
||||||
a complex interaction and they say hey
|
|
||||||
please tell me when you get this message
|
|
||||||
and forward it on so that I can see
|
|
||||||
what's happening parties don't have to
|
|
||||||
follow it and but it's somewhat related
|
|
||||||
to recording so I I guess I can only
|
|
||||||
think of two those two comments about
|
|
||||||
the recording concept maybe we can talk
|
|
||||||
some more after Danny I actually have a
|
|
||||||
follow-up question and what what
|
|
||||||
happened here so I'm sure you're
|
|
||||||
familiar with signal in signal low using
|
|
||||||
a double ratchet it's right in Triple D
|
|
||||||
filmin and they create that end-to-end
|
|
||||||
encryption so how does this really
|
|
||||||
different when it comes to peer-to-peer
|
|
||||||
and then just creating that encryption
|
|
||||||
because you just mentioned that if
|
|
||||||
you're going to man in the middle attack
|
|
||||||
I'm quite familiar with what Bluecoat
|
|
||||||
does I work at Symantec as well so you
|
|
||||||
have access to the private key you are
|
|
||||||
able to record a session and then you're
|
|
||||||
able to replay it
|
|
||||||
so basically acting as a proxy so how
|
|
||||||
does this does not apply in this
|
|
||||||
scenario because if I'm able to actually
|
|
||||||
sit in between let's say I hold the
|
|
||||||
network and then I compromise one of the
|
|
||||||
parties then this is basically just a
|
|
||||||
broken channel well first of all indie
|
|
||||||
communication there's a this has not
|
|
||||||
been implemented but the hype has been
|
|
||||||
accepted is adopting signals double
|
|
||||||
ratchet algorithm so forward secrecy and
|
|
||||||
so forth is a property of the
|
|
||||||
communication channel the same way it
|
|
||||||
would be with signal the did method spec
|
|
||||||
that I talked about here one of the key
|
|
||||||
characteristics that it has is that when
|
|
||||||
you created did you must create it by
|
|
||||||
deriving it from the public key of a key
|
|
||||||
pair that exists and the reason that
|
|
||||||
that requirement exists is because you
|
|
||||||
don't want if you had it if you did well
|
|
||||||
let me take you down a different path if
|
|
||||||
if you started a D ID as just like let's
|
|
||||||
say some UUID and then later you
|
|
||||||
associated it with keys what could
|
|
||||||
happen is you could start it and a
|
|
||||||
person who's proactive and malicious
|
|
||||||
could notice what your D ID is
|
|
||||||
but you haven't asserted keys and jump
|
|
||||||
in and create the kind of man in a
|
|
||||||
middle situation that we're really
|
|
||||||
worried about here but because DIDS
|
|
||||||
require you to derive the thing from the
|
|
||||||
key the the did value from the key there
|
|
||||||
is no point in time where the creator of
|
|
||||||
the did is vulnerable to the man in the
|
|
||||||
middle attack that's only a partial
|
|
||||||
answer to your question let's talk about
|
|
||||||
it after yeah I had yet another
|
|
||||||
follow-up on this thread so the ietf has
|
|
||||||
a existing internet standard called the
|
|
||||||
host identity protocol and it does
|
|
||||||
exactly the same thing the intention
|
|
||||||
there is because right now in networks
|
|
||||||
there's the IP address is the identity
|
|
||||||
but this is not verifiable so they made
|
|
||||||
this protocol with the intention that it
|
|
||||||
existed to be compatible with the
|
|
||||||
Internet's tcp/ip stack so there is no
|
|
||||||
tie to and etherion network or a hyper
|
|
||||||
ledger implementation it's just part of
|
|
||||||
the general Internet can you give me
|
|
||||||
some context as to why this is existing
|
|
||||||
separate from that and we don't just use
|
|
||||||
the host identity protocol existing on
|
|
||||||
the internet already so that's a great
|
|
||||||
question there's several different
|
|
||||||
answers that are all kind of related
|
|
||||||
that kind of add up the first thing is
|
|
||||||
that this communication mechanism has to
|
|
||||||
work on things besides the Internet
|
|
||||||
so not everything has IP addresses and
|
|
||||||
still we have to be able to communicate
|
|
||||||
we certainly live in a highly IP centric
|
|
||||||
world but there's plenty of use cases
|
|
||||||
that are outside that the second thing
|
|
||||||
is that like with certificates my
|
|
||||||
understanding of the host identity
|
|
||||||
technology is that it focuses on servers
|
|
||||||
now of course it could be used for
|
|
||||||
clients and stuff too but TLS in general
|
|
||||||
even though it has
|
|
||||||
the option of identifying both parties
|
|
||||||
is almost a hundred percent used to
|
|
||||||
identify only the server side of an
|
|
||||||
interaction so when you want to identify
|
|
||||||
the client side what do you do you have
|
|
||||||
this great channel but you don't use
|
|
||||||
certificates you have an entirely
|
|
||||||
different mechanism which is
|
|
||||||
browser-based sessions and cookies and
|
|
||||||
all this other stuff to identify the
|
|
||||||
other party you log in you present some
|
|
||||||
credentials and I think the same kind of
|
|
||||||
phenomenon maybe is undermining some of
|
|
||||||
the value of that protocol where it's
|
|
||||||
it's going to be applied whether the
|
|
||||||
protocol is written that way or not it's
|
|
||||||
going to be applied just to identify
|
|
||||||
things that have a permanent presence
|
|
||||||
does it does it work for mobile phones
|
|
||||||
that are changing IP addresses
|
|
||||||
constantly and that are refreshing their
|
|
||||||
software and all that other stuff I
|
|
||||||
don't know enough to know maybe we can
|
|
||||||
can you share a link with me or
|
|
||||||
something and I'll go learn some more
|
|
||||||
about it
|
|
||||||
state channels are on my list of we're
|
|
||||||
right here
|
|
||||||
well state channels yeah the state
|
|
||||||
channels are an example of this kind of
|
|
||||||
thinking yeah I have one question
|
|
||||||
concerning the etch chain protocols as I
|
|
||||||
understood you you suggest we make small
|
|
||||||
protocols and different apps but what
|
|
||||||
when I want to glue them together
|
|
||||||
because they together build higher-level
|
|
||||||
protocols would I then try to make the
|
|
||||||
glue in the blockchain so things that
|
|
||||||
those protocols need store it there or
|
|
||||||
would I define let's say super H J chain
|
|
||||||
protocol
|
|
||||||
well yeah protocols are one of those
|
|
||||||
things that can be understood at there's
|
|
||||||
there's lower level ones and higher
|
|
||||||
level ones just like there's the OSI
|
|
||||||
stack and so forth in networking and you
|
|
||||||
can combine logical entities into bigger
|
|
||||||
constructs to make higher-level
|
|
||||||
protocols something that you said kind
|
|
||||||
of gets at this slide that I skipped
|
|
||||||
over one of the things that's different
|
|
||||||
between DAPs and edge chain protocols is
|
|
||||||
that edge chain protocols there there's
|
|
||||||
no set of apps that you have to have you
|
|
||||||
just need to have software that is
|
|
||||||
capable of playing all of the roles in
|
|
||||||
your protocol and it could be written by
|
|
||||||
ten different people and there could be
|
|
||||||
ten different providers of one of the
|
|
||||||
roles if you wanted right so think about
|
|
||||||
like buying a house we don't have only
|
|
||||||
one place that you go to get all the the
|
|
||||||
actors in the buy a house protocol and
|
|
||||||
yet DAPs are typically written where you
|
|
||||||
write a DAP that implements the whole
|
|
||||||
thing and so that's a little bit of a
|
|
||||||
paradigm shift
|
|
||||||
yeah yeah yeah
|
|
||||||
theirs doesn't have to be implemented on
|
|
||||||
server so it's not exactly micro
|
|
||||||
services but it's like that in the sense
|
|
||||||
that it's a bunch of little granular
|
|
||||||
things hi thanks this was really
|
|
||||||
interesting I was going to offer a bit
|
|
||||||
of nitpicking for the megaphone protocol
|
|
||||||
I think if you don't take in
|
|
||||||
consideration economic pressure
|
|
||||||
I think the protocol probably fall apart
|
|
||||||
because some people will be in such
|
|
||||||
situations that they'll be willing to
|
|
||||||
trade what they consider their important
|
|
||||||
identity to spam people nearby and
|
|
||||||
there'll be markets that will probably
|
|
||||||
show up saying hey if you can if you do
|
|
||||||
this for us we'll give you some money
|
|
||||||
and people might burn through their
|
|
||||||
identity because they don't see the
|
|
||||||
value of it or maybe they will try and
|
|
||||||
stack up multiple identities as much as
|
|
||||||
they can
|
|
||||||
obviously we we would expect this the
|
|
||||||
product or the system the overall
|
|
||||||
underlying self sovereign identity
|
|
||||||
system not to allow that but I think if
|
|
||||||
you don't count factor in economic
|
|
||||||
pressures especially for those of us who
|
|
||||||
are very poor like you won't be able to
|
|
||||||
expect some of the ways that the
|
|
||||||
protocol will be manipulated
|
|
||||||
that's good comment the the concept
|
|
||||||
document includes the notion that
|
|
||||||
megaphones have a volume and you can
|
|
||||||
select the volume if you say look I'm
|
|
||||||
tired and hungry and I'm a mom in an
|
|
||||||
airport and I have a baby and I need to
|
|
||||||
change the baby's diaper and I forgot a
|
|
||||||
diaper that's not a life-threatening
|
|
||||||
crisis so you don't need
|
|
||||||
life-threatening volume and so there's
|
|
||||||
probably different staking for different
|
|
||||||
levels of volume but I think there's
|
|
||||||
still you're right that there's
|
|
||||||
potential for abuse which is maybe one
|
|
||||||
of the reasons that nobody's been
|
|
||||||
working on it yet
|
|
||||||
okay well I think we should declare the
|
|
||||||
the session over and I'll be up here if
|
|
||||||
anybody wants to ask more questions a
|
|
||||||
couple of you asked me questions that I
|
|
||||||
want to get some more information about
|
|
||||||
if you just come and talk to me that'd
|
|
||||||
be great and thanks for your attention I
|
|
||||||
appreciate it
|
|
||||||
|
|
||||||
|
|
@ -1,475 +0,0 @@
|
|||||||
---
|
|
||||||
title: Verifiable Organizations Network - A Production Government Deployment of Hyperledger Indy
|
|
||||||
description: Transcript of Presentation by John Jordan and Stephen Curran at HGF 2018
|
|
||||||
image: "https://infominer.id/images/VON.png"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Hyperledger Global Forum 2018 — Verifiable Organizations Network
|
|
||||||
**A Production Government Deployment of Hyperledger Indy**
|
|
||||||
|
|
||||||
<code>Editors Note: I've taken to working on youtube transcripts for podcasts and videos whos content is valuable and not readily accessible in text form, so that it will be easier for anyone to reference. -<a href="https://infominer.id">infominer</a></code>
|
|
||||||
|
|
||||||
-Published on Dec 27, 2018
|
|
||||||
|
|
||||||
[John Jordan](https://twitter.com/jljordan42), Province of British Columbia & [Stephen Curran](https://twitter.com/scurranC3I), [CloudCompass Computing](https://cloudcompass.ca/)
|
|
||||||
|
|
||||||
Learn about the Province of British Columbia's experience deploying the first Hyperledger Indy based production ecosystem.
|
|
||||||
|
|
||||||
The [Verifiable Organizations Network](https://vonx.io) (VON) enables governments and organizations to exchange data in trustworthy ways based on open standards and technology.
|
|
||||||
|
|
||||||
VON's founding members are governments who are, by law, trusted issuers of data about organizations. The Province of British Columbia, Province of Ontario and the Government of Canada have come together to create the initial services needed to establish VON.
|
|
||||||
|
|
||||||
VON's founders have delivered new Indy-based open source components which form VON's backbone. [TheOrgBook](https://orgbook.gov.bc.ca/) is a publicly accessible repository of [verifiable claims](https://w3c.github.io/webpayments-ig/VCTF/charter/faq.html) about organizations. VON-X enables services to verify and issue credentials.
|
|
||||||
|
|
||||||
We present the Why, What and How including our strategy for bootstrapping VON using a two-sided market strategy.
|
|
||||||
|
|
||||||
<a href="https://youtu.be/g19VNv3DAd0"><img src="http://i.imgur.com/kODoTdj.png"/></a>
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Transcript](#transcript-)
|
|
||||||
* [Introduction](#introduction-)
|
|
||||||
* [Solving Problems](#solving-problems-)
|
|
||||||
* [Collaboration](#collaboration-)
|
|
||||||
* [Verifiable Proofs](#verifiable-proofs-)
|
|
||||||
* [Chicken-or-Egg Dilemma](#chicken-or-egg-dilemma-)
|
|
||||||
* [The Org Book](#the-org-book-)
|
|
||||||
* [BCGov Org Book](#bc-gov-org-book-)
|
|
||||||
* [Verifiable Credentials](#verifiable-credentials-)
|
|
||||||
* [Production Network—Live 9-10-18](#production-networklive-9-10-18-)
|
|
||||||
* [General Purpose](#general-purpose-)
|
|
||||||
* [Ontario Org Book](#ontario-org-book-)
|
|
||||||
* [Come to our Workshop](#come-to-our-workshop-)
|
|
||||||
* [Bootstrapping Mechanism](#bootstrapping-mechanism-)
|
|
||||||
* [dFlow](#dflow-)
|
|
||||||
* [Just the First Step](#just-the-first-step-)
|
|
||||||
* [Indy Catalyst](#indy-catalyst-)
|
|
||||||
* [Serving the Public](#serving-the-public-)
|
|
||||||
* [Q&A](#qa-)
|
|
||||||
* [Home](https://infominer.id)
|
|
||||||
|
|
||||||
## Transcript [**^**](#contents)
|
|
||||||
|
|
||||||
<code>**Editors Note** I just copy\pasted this youtube transcript, lightly edited for readability, and added screenshots for context. -infominer</code>
|
|
||||||
|
|
||||||
**Pull Requests Welcome**
|
|
||||||
|
|
||||||
## Introduction [**^**](#contents)
|
|
||||||
|
|
||||||
My name is John Jordan and I come from the province of British Columbia in Canada. This is my colleague Steven Curran we work together on this project.
|
|
||||||
|
|
||||||
I guess I'll just get started, and we'll have some slides, a demo, we should have some time for some questions
|
|
||||||
|
|
||||||
Ian is also here, one of our developers as well, he's a hyper ledger future developer. What we're gonna talk about today is what we're doing in the government of British Columbia, together with some of our peer provinces in the country — about how we're trying to solve some very long-standing difficult problems.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/bf3lLTq.png"/>
|
|
||||||
|
|
||||||
>**we're gonna focus on business services today and talk about how the government can start to do the things that it does today in paper**, which it underpins the economy.
|
|
||||||
>
|
|
||||||
>**money exists because the government says so businesses exist because the government registers them and allows them to operate** and the laws and so forth of the of the government allow commerce to occur
|
|
||||||
>
|
|
||||||
>**but we have no way of doing that in the digital economy right now** there's no business models in the digital economy other than basically buying stuff and getting your data exploited for advertising. so if you have a Visa card you're in.
|
|
||||||
>
|
|
||||||
>otherwise there's no other really interesting transactions going on and I think big part of that is because **we don't have any way of extending the trust of government into the digital realm in a way that is trustworthy**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/BVVoGaA.png"/>
|
|
||||||
|
|
||||||
so we're going to talk about that this is our fun slide this is where we're from Canada with a variety of animals quite a lot of space we come from Victoria BC I norm I actually grew up in Ottawa which is around the beaver and people think that's kind of humorous but so there you go that's her that's
|
|
||||||
her
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/UN0dT5b.png"/>
|
|
||||||
|
|
||||||
I also want to acknowledge that **I do all this work with [Carol Prest](https://www.linkedin.com/in/carol-prest-aa34b258/)** who is the registrar for BCS so I've been there for a couple years and **from day one we've been working together exploring how can we use the registry data as the foundational data for doing business.**
|
|
||||||
|
|
||||||
Unfortunately she's not available she's in India right now, but having this business partnership and having her in her organization behind this, and having the discipline of trying to **solve problems for business people** is what is making this project really fun and also useful
|
|
||||||
|
|
||||||
## Solving problems [**^**](#contents)
|
|
||||||
<img src="http://i.imgur.com/MrIep94.png"/>
|
|
||||||
|
|
||||||
We're gonna focus on a problem here which is **how do we help small business** we have sort of a an example of Mary's bakery but **it could be any kind of business** construction mining whatever it is and the problem is that these business people are very excited about starting a business is an exciting time in life but they don't realize sometimes that **they have quite a lot of obligations that they must fill for government**
|
|
||||||
|
|
||||||
We have examples where our research teams have gone out and talked to restauranteurs and they have released a building and so forth it's the perfect spot everything is great **and then they realize oh I've got six months of permits and licenses to do because we had to bring it up to building code and they didn't realize this and then there's all these dependencies and they weren't ready to fund that building for six months** so those are like real stories **we'd like to try and minimize that kind of stuff** because we want them to start their businesses and grow.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/FxeKL2D.png"/>
|
|
||||||
|
|
||||||
>you know the path is also very meandering and it can be in multiple different media you can be faxing you could be email you could be online you're in person and so forth.
|
|
||||||
>
|
|
||||||
>**All of this is a very difficult both for the business people but also on the government side**. We are also in different places verifying data all the time: who are you? whos business are you representing? Are you authorized to represent the businesses?
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/sIiI6Ni.png"/>
|
|
||||||
|
|
||||||
In the most complicated cases, for liquor and so forth, shareholders and employees have **criminal background checks.** They make sure that nobody owns more than 8 stores that sells liquor, and can take up to a year so.
|
|
||||||
|
|
||||||
## Collaboration [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/GM9FxgX.png"/>
|
|
||||||
|
|
||||||
We're collaborating with a couple of other jurisdictions. We're working with a team in **Ontario** and a
|
|
||||||
team **in the Government of Canada**, where I used to work, **The Procurement Agency**.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/oPuhVyP.png"/>
|
|
||||||
|
|
||||||
**When we say working together, we're actually writing code together**. There's no MOUs, no steering committees, no work groups. They have a couple devs and the business person, we have a couple of devs and a business person. We sprint together, write code.
|
|
||||||
|
|
||||||
All this stuff we're going to show you today has been co-developed, and significant portions have been done by each of the groups
|
|
||||||
|
|
||||||
## Verifiable Proofs [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/0MS4yEs.png">
|
|
||||||
|
|
||||||
This is the journey that we'd like to enable, it's a journey that we know well. The government gives you something, you take that something to another institution, you use it to prove something and you get and you get the outcome.
|
|
||||||
|
|
||||||
In this case it's the incorporation information that's given to Mary, she goes to the bank and she can open a bank account. Turns out that's a very general pattern, and this is the pattern that we see in the verifiable credentials realm.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/FNpnmLg.png"/>
|
|
||||||
|
|
||||||
So we have this pattern of: **holder** which *is a person or a business* but a business can't really hold something on their own. They have to have people holding it on behalf of the business.
|
|
||||||
|
|
||||||
They presented to a verifier, which is earlier in the workflow, the verifier says bring your list of things in and prove to me who you are, and you have various permits and licenses and so forth. You then get to enter their form which is usually not that pleasant, and then you are issued something which you hold.
|
|
||||||
|
|
||||||
**This is the pattern that we're very familiar with.**
|
|
||||||
|
|
||||||
We're sitting with a wallet full of these things. I have bank cards and identity cards and so forth and we're gonna explore how we can do that.
|
|
||||||
|
|
||||||
When we discovered that **we were pretty excited** it was about a year ago that **we stumbled across Hyperledger Indy** after having done a little bit of work with fabric
|
|
||||||
|
|
||||||
So it was just Stephen and I on the team and we thought it looked promising, that there was this pattern here we could solve some of these hard problems we've been working on for years but we realized we didn't have any of the software for different organizations or people.
|
|
||||||
|
|
||||||
## Chicken-or-Egg Dilemma [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/hHn9SLm.png"/>
|
|
||||||
|
|
||||||
Somebody mentioned it this morning, the classic chicken and egg problem: we don't have any software out there that we can issue to our issuers, don't have software to issue. We realized, in this case government is a little bit special, which I don't like to say very often.
|
|
||||||
|
|
||||||
It turns out our core business is issuing that's what we do every service we have is pretty much an issuer so we thought: what if we could give the services that we are dealing with in the business realm, somewhere to issue to?
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/9IHbEkL.png"/>
|
|
||||||
|
|
||||||
We purposely picked business realm because if we're dealing with business data we're not triggering all the personal identifiable information problems. In the BC we call it FoIT, the Freedom of Information Act and Privacy Protection Act. When you get into personal data, of course it triggers all of that which, is good but makes it very complicated to play with new technologies.
|
|
||||||
|
|
||||||
## The Org Book [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/6KxuQM9.png"/>
|
|
||||||
|
|
||||||
We just deal with open business data right now and we thought: what if we could create something where these issuers could issue data to? and it would be a public thing, and we call that **The Org Book.**
|
|
||||||
|
|
||||||
This is a bootstrapping technique that we're copying from Facebook. We're just playing with one side of the market. **We're gonna deal with the supply side: the issuers of credentials, more commonly known as permits and licenses.**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/o5KphnK.png"/>
|
|
||||||
|
|
||||||
Because they're public and because they're open we can create this directory of searchable verifiable data and we can build software for the issuers.
|
|
||||||
|
|
||||||
Our goal was how can we make it as easy as possible for existing services to be able to issue their credentials to this OrgBook starting with the foundational data of the registry, and we're going to show you that.
|
|
||||||
|
|
||||||
**When we started writing this code built on top of Hyperledger Indy we realized that there could be intermediate benefits.**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/voKqoaF.png"/>
|
|
||||||
|
|
||||||
So first there's some public good, and the searching and finding of data will show you that. It turns out we can also create [api's](https://bcgov.github.io/MyGovBC-notification-server/docs/api-overview/) to allow that data to be searchable, and we created an [enterprise agent](https://github.com/bcgov/von_agent) for services to verify the data in The Org Book.
|
|
||||||
|
|
||||||
So later when businesses have their own services for holding verifiable credentials, our issuers are ready.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/AdYRiK9.png"/>
|
|
||||||
|
|
||||||
## BC Gov Org Book [**^**](#contents)
|
|
||||||
|
|
||||||
Now I'm gonna hand it over to Stephen. This is what The Org Book looks like in British Columbia, so there's two instances and we'll show you them both but **this is the [British Columbia Org Book](https://orgbook.gov.bc.ca/en/home) and it's basically a kind of a Yelp type site.**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/nsurhhx.png"/>
|
|
||||||
|
|
||||||
**we've got five hundred twenty-five thousand active legal entities in British Columbia every one of them has a record in here** they have the credentials that the registries have issued to them
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/ngfzaPh.png"/>
|
|
||||||
|
|
||||||
Let's do a search we're into chocolate because we're in Switzerland so we'll talk about a Vancouver Island chocolatier. Purdy's chocolates, we can take a look at them. Search capability names we've got other capabilities for what searches we can provide ways to filter and things. When we get into it, we can see some information that the registry publishes, so previously registered.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/0mcU9ru.png"/>
|
|
||||||
|
|
||||||
**9:41** This is all public data, this is all open data. This is exactly what they hang on their walls inside the restaurant and things like that, there's really no place in BC it is actually published but in a very obscure places, very difficult to find. We've actually, as a byproduct of doing this exercise, created a pretty useful facility for citizens to use to find businesses, so we can take a look at them.
|
|
||||||
|
|
||||||
## Verifiable Credentials [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/yMMHV01.png"/>
|
|
||||||
|
|
||||||
this one has a couple of credentials they actually have a corporate entity and then a couple of names they do business under so [they've got several credentials](https://orgbook.gov.bc.ca/en/organization/BC0057742/cred/1902355) we can see a timeline of when they've got the different credentials so we can take a look at those in it and as the history builds up we haven't loaded all the history of all BC companies yet some of that is on paper which is going to be more challenging but that's that's not for us to worry about but we can load them up so if we can look at our registration we can see an active credential
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/vmZx8py.png"/>
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/umWHJO7.png"/>
|
|
||||||
|
|
||||||
so this is what a credential looks like online basically we present it with the key data that a person might be interested in and then at the bottom we can actually go [into the credential](https://orgbook.gov.bc.ca/en/organization/BC0057742/cred/1902355/verify) from an Hyperledger Indy perspective
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/l3LCLnu.png"/>
|
|
||||||
|
|
||||||
so this is the schema if you as they call it on the one side the populated data for this particular version of the
|
|
||||||
credential and then down below we get some really fun stuff
|
|
||||||
|
|
||||||
this allows any citizen to go and do the cryptography on
|
|
||||||
paper themselves to prove that this is a proven credential yeah and we say verified see the check up there that's
|
|
||||||
the that's the key
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/47eUSiL.png"/>
|
|
||||||
|
|
||||||
## Production Network—Live 9-10-18 [**^**](#contents)
|
|
||||||
|
|
||||||
okay I think that's most of what we wanted to show so the idea here that we wanted to talk about a little bit was the title of this, **this is a production system, we've been live since the 10th of September**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/cHws3Sb.png"/>
|
|
||||||
|
|
||||||
there's a little story there so let's go back to the home page and let me talk about a couple of things there the current statistics those are actual statistics we actually recreated the credentials and loaded them this week
|
|
||||||
|
|
||||||
so that's why **2.6 million were issued this week** we can do that the first weekend in September when we loaded it, it took 10 days to load the credentials so that kind of wasn't too good.
|
|
||||||
|
|
||||||
**we had Ontario coming behind us with about five times as many credentials** so we were a little nervous and did a couple of sprints to scale up its capabilities
|
|
||||||
|
|
||||||
BCGov, which has [the developers exchange](https://bcdevexchange.org/), is a pretty progressive environment for developing code. We've got a Red Hat open shift [kubernetes](https://kubernetes.io/) based platform
|
|
||||||
|
|
||||||
so basically we were able to use the capabilities of that platform to just spin up other instances and be able to scale up the the speed of loading and things like that so we got up to
|
|
||||||
|
|
||||||
we're now about 12 hours to load the full data set so we're creating issuing and holding about 2600 credentials per minute so decent speed it's kind of weird because we are a single holder for all of these organizations these don't the organizations don't have their own wallet and the first vision and the first thing that Indy wanted to support was the idea of a person having a wallet
|
|
||||||
|
|
||||||
so the database behind it was not the most scalable solution out of the box so the next thing we did as well to to make it scalable was to implement say an enterprise-grade wallet with Postgres in was the developer on that and we were pleased that yesterday his code was merged into the Indy SDK repo so it's now officially hyperledger code, which is kind of cool. So that's a contribution we've made to the to the ecosystem in Hyperledger Indy.
|
|
||||||
|
|
||||||
## General Purpose [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/rrQSzsd.png"/>
|
|
||||||
|
|
||||||
So one of the things you're seeing, is this is a BC site, but it's really very generic so what we've tried to do is make it completely agnostic of what the actual credentials that will be loaded in.
|
|
||||||
|
|
||||||
We do have the concept that it's a an organization so we've got names, we have addresses, the concept of addresses, we have the concept of credential types, we have the concept of dates in there... but other than that the structure is whatever the issuer happens to issue so, it's very flexible for others to use.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/sewb1Aq.png">
|
|
||||||
|
|
||||||
so that search that's up there is you know it was a decent amount of work uses solar and and and so on but is very generic so that other entities other jurisdictions can take this and basically spin up their own instance of this relatively easily using this code and be able to take advantage of the loading the naming the searching the display all of this is flexible and localized localizable
|
|
||||||
|
|
||||||
## Ontario Org Book [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/PMpdfJ8.png"/>
|
|
||||||
|
|
||||||
let's take a look at the Ontario one so [The Ontario Org Book](https://www.von.gov.on.ca/) looks quite different from BCS obviously the search panel is the same they have different things they want to show and what they they don't want to show
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/wfCQNDT.png"/>
|
|
||||||
|
|
||||||
so for example in Ontario they didn't want to show the structure of a company they actually have a contract that charges for that so they weren't able to do that through this
|
|
||||||
|
|
||||||
so every entity and every doing business as is a separate entity on this so because we were building with multiple jurisdictions in mind right
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/L97WeSB.png"/>
|
|
||||||
|
|
||||||
from the start we've we built it to be pretty flexible and so you're able to construct it on your own have your own skinning language support there's multiple language support is in there built in already I think those were the main things
|
|
||||||
|
|
||||||
## Come to our Workshop [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/GwrN03q.png"/>
|
|
||||||
|
|
||||||
the two more things that I wanted to touch on: **come to our workshop on Friday and Saturday** and what we're actually doing is building out issuers and verifiers
|
|
||||||
|
|
||||||
* [Hands-On with Verifiable Organizations Network - Part 1](https://www.youtube.com/watch?v=R5TB-goL3_o&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=108)
|
|
||||||
* [Hands-On with Verifiable Organizations Network - Part 2](https://www.youtube.com/watch?v=j-lM2hNq1TI&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=107)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/PE065NM.png"/>
|
|
||||||
|
|
||||||
So this is The Org Book, the central piece. What really is important is there's an API behind all this that a issuer of permits can use to learn about the company to fetch the credentials that are already there and have them proven and then issue credentials back to the org book.
|
|
||||||
|
|
||||||
A key part of this is that being easily able to extend this to many more permits and licensing providers could be within the government which we're working with.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/cdI0NGO.png"/>
|
|
||||||
|
|
||||||
almost every project team we talked to says "oh we can use that!" so we're building that out and trying to make that as easy as possible so our workshop on Friday involves building an issue or verifier and actually deploying it out so you can create your issue your own credentials
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/QyOUf4G.png"/>
|
|
||||||
|
|
||||||
## Bootstrapping Mechanism [**^**](#contents)
|
|
||||||
|
|
||||||
the other side of it that we think is going to be really important is well this is a bootstrapping mechanism we've realized there can be some life to this in that we're going to create we're going to be creating a pub sub subscription service basically so that a business that gets a credential and verifies it can subscribe to that credential in the future and get notified when it changes
|
|
||||||
|
|
||||||
so a big challenge in all government organizations is this ability to understand when things change and we think this can be a super light way for a business to get notified that:
|
|
||||||
|
|
||||||
"hey these two businesses just merged they've started a new entity", "those two entities no longer exist they've been dissolved in this new entity exists you should know that" and
|
|
||||||
|
|
||||||
so that webhook capability will just whatever you're subscribed to when when our credential changes we can notify you that it happened and then you can dig in to figure out how that affects your permit and licensing service
|
|
||||||
|
|
||||||
## dFlow [**^**](#contents)
|
|
||||||
|
|
||||||
the other piece that we'll show is thing called decentralized flow - [dFlow](https://dflow.orgbook.gov.bc.ca)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/a8WzejN.png"/>
|
|
||||||
|
|
||||||
so do you wanna go to that okay spicy wings we're gonna look at Spicy Wings. This is our dev site, this is just new, that we're playing with. This is a company that's got four different credentials from different organizations.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/jUyJEIk.png"/>
|
|
||||||
|
|
||||||
They've got a registration a PST that's a tax number from the province, a clearance letter for workman's compensation for a worker's insurance, and a business license from a from an entity from a municipality.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/2fQTCap.png"/>
|
|
||||||
|
|
||||||
So with [dFlow](https://dflow.orgbook.gov.bc.ca) what we can do is basically what you're saying is I have a goal as a businessman I have a goal that I want a business license in the city of Surrey and it's going to be for a restaurant what have I got to do to accomplish that what other things do I need and
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/YSIIWLQ.png"/>
|
|
||||||
|
|
||||||
what we've built here is a [dynamic workflow](https://github.com/bcgov/dFlow) that starts with the one you want I want a business license, and says "what are the prerequisites for getting a business license?" well that's been encaptured in the proof requests that the business requires before it will issue you the credential that they have to offer.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/PpzN2E9.png"/>
|
|
||||||
|
|
||||||
**19:34** so we can look at that proof require and then iteratively go back to that proof request and walk back a step and walk back a step all the way back until we get to the starting point and
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/XQK4hH3.png"/>
|
|
||||||
|
|
||||||
now we can display dynamically what does that company need in order to get a business licencse there their goal and then what have they already got that allows them to proceed
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/FvA5vMU.png"/>
|
|
||||||
|
|
||||||
so basically this company the ones in blue they already have and they can take a look at it the ones in yellow they're able to acquire now because they have all the prerequisites they haven't got it yet but they have the prerequisites for it and the ones in red they don't have the prerequisites they're just going to get rejected so no need to start in on those already
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/Pmtg8km.png"/>
|
|
||||||
|
|
||||||
the nice thing about this is all of these entities that are issuing credentials that are issuing permits and licenses don't have to know the whole journey that that's really hard to figure out all they have to know is what their prerequisites are and as soon as they express those in the form of a proof request we can dynamically walk that chain and figure out what what else they need compare that with what's in their wallet what credentials they already have and now we can give them a picture of where they are all right if we got a minute
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/ZdQrDU3.png"/>
|
|
||||||
|
|
||||||
**21:15** one of the things we're going to do in the workshop is in spinning up your issue or verifier is you'll have to connect to and create ended transactions on Indy blockchain on a distributed ledger
|
|
||||||
|
|
||||||
so this is a tool we created to be able to browse the network so we can look at in this case the four node network that we've got running we can look at the status of it
|
|
||||||
|
|
||||||
**21:50** we can do some operations like look at the Genesis transaction but we can also dig in and look at what are the transactions that actually exist on the ledger at this time
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/J6I6GkD.png"/>
|
|
||||||
|
|
||||||
we can do some searching for things and find all the ones that have tax in the name we can search by types of in this case we're looking for schema
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/QfgNVr1.png"/>
|
|
||||||
|
|
||||||
so this gives you a really good way of actually being able to see what is on the ledger you know get an idea as you register an issue or verifier take a look at what's there
|
|
||||||
|
|
||||||
so that's kind of a preview of the site and the ideas that have been emerging as a result of our work but there's a little bit more
|
|
||||||
|
|
||||||
## Just the First Step [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/kO6nCGy.png"/>
|
|
||||||
|
|
||||||
**22:55** one of the things that we're trying to do is, it's helpful for BC businesses but BC businesses do business all around the world and we want our businesses to be able to interact digitally with everybody else and like Steven mentioned it's not just businesses but it's professionals and so forth
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/8tyRlCK.png"/>
|
|
||||||
|
|
||||||
this model could work for professional engineering societies medical societies other kinds of things that have public accreditation that you need to check on
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/3O2CKLa.png"/>
|
|
||||||
|
|
||||||
**23:27** so we have this idea where we think The Org Book helps us establish our local neighborhood. businesses are gaining their credentials and and that's kind of building up our local ecosystem
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/aYIYVha.png"/>
|
|
||||||
|
|
||||||
That makes it easier for us to help them find their way like we just demonstrated because each of these issuers are going to automatically be able to express digitally the preconditions that are necessary for them to be able to allow you into their service and an issue a new permit/
|
|
||||||
|
|
||||||
## Indy Catalyst [**^**](#contents)
|
|
||||||
|
|
||||||
We think that's pretty pretty cool and as a result of this learning we've we've come up with this generalized model that has been accepted as a sub project of Indy.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/p8BME5z.png"/>
|
|
||||||
|
|
||||||
We're calling that [Indy Catalyst](https://github.com/bcgov/indy-catalyst) because this is sort of a bootstrapping capability, and that'll comprised of the code-behind [The Org Book](https://github.com/bcgov/TheOrgBook) in a more generalized fashion, and the code behind the issuer verifier service that we've built which we call [von-X](https://github.com/PSPC-SPAC-buyandsell/von-x) but we'll give some other sub named as an Indy Catalyst component.
|
|
||||||
|
|
||||||
## Serving the Public [**^**](#contents)
|
|
||||||
|
|
||||||
The big reason behind this is because I work for the government of BC, we're not a software development agency, were serving the public.
|
|
||||||
|
|
||||||
We want this to be part of a global capability, and
|
|
||||||
having a sustainable set of software in a well governed organization like Hyperledger, the Linux Foundation, we think is a good way to go.
|
|
||||||
**24:50**
|
|
||||||
We think that as these neighborhoods grow, hopefully well become will create what we call the verifiable organization Network
|
|
||||||
**25:01**
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/ANXXvan.png"/>
|
|
||||||
|
|
||||||
so this is sort of a concept where if you can use these kinds of tools and it doesn't have to be Hyperledger Indy it could be any system that is decentralized identifier—verifiable credential compliant
|
|
||||||
|
|
||||||
you'll be able to exchange verifiable data amongst businesses and that is really what we want to be able to do it's nice that they could come and do business with us like get the things they need but what's really more important is it that they transact amongst themselves that's what the economy lives.
|
|
||||||
|
|
||||||
That's the idea of the Verifiable Organisation Network and the coming code that we'll call a Hyperledger Indy Catalyst, so that is our talk for now.
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/dbHSiO7.png"/>
|
|
||||||
|
|
||||||
## Q&A [**^**](#contents)
|
|
||||||
|
|
||||||
**25:40** as Steven mentioned **we're having a workshop Friday and Saturday morning** and Ian and Steven and I'll do my best to help will walk you through actually creating an issue we're
|
|
||||||
creating schemas and doing your own decentralized workflow example.
|
|
||||||
|
|
||||||
**we're happy to take questions** just wanted to check any **prerequesites for the workshop**, any required software components to be installed before hand:
|
|
||||||
|
|
||||||
>you need a browser and you need a **docker hub ID** but you know you could do that while you're there yeah so the prerequisites are a docker hub ID and then everything else can be done in a browser and we've got all the guidance and so on but you don't need anything else I don't think about **Chrome** is ideal right chrome is probably the best we're using a tool called play with docker so you don't have to install anything on your machine it's super cool I promise no biometrics
|
|
||||||
|
|
||||||
so you did mention the verifiable claim and you you implied standards and I just want to confirm with the audience here because we had a side discussion.
|
|
||||||
|
|
||||||
>it's w3c compliant verifiable claims and then and so I don't want to ask about the the other adjuncts that the registrar and the verifier because you talk about those concepts but I'm trying to understand what standards you use or what you're developing on your own and what standards apply specifically the registrar?
|
|
||||||
|
|
||||||
right so right now it's Hyperledger Indy version of things but as they progress they'll they'll create the ID doc specs and the end verifiable credential base
|
|
||||||
|
|
||||||
but that's still emerging right in terms of how the agents communicate we're actually contributing quite a bit
|
|
||||||
to sort of this agent agent protocol and that's being done in the open as well right now in this sort of Hyperledger
|
|
||||||
Indy working groups but we want interoperability
|
|
||||||
|
|
||||||
we'd like our citizens to have a choice so they could use a DID method of their choice they could use software of their choice when it gets to personal data or this data we think if that's where the marketplace will provide options for citizens and businesses like the holder software so whatever standards emerge we would want to support those and we're helping shape some of those as well so
|
|
||||||
|
|
||||||
there isn't a specific standard for the agent agent protocol but it's a collaboration with the decentralized identity foundation and the w3c folks and the hyper ledger folks yeah one of the things we thought about as John alluded to early in the talk was oh we're gonna build this thing in our organizations they're gonna use our agent and they're gonna talk to our issuers and verifiers and we're gonna build all that stuff and then we realize no this is not what we should be doing we shouldn't be in the business of doing that we need to be in the business of issuing credentials
|
|
||||||
|
|
||||||
so we have to build software for that we need to make do it in a way that allows them to change as little as they need to we don't want them to have to read recreate their world we want them to just be an adjunct on just like they use a printer to print the verified credential the permit or the license so they can hang it on the wall we just want them to stamp out a digital version of that that's signed cryptographically right and
|
|
||||||
|
|
||||||
one of the things I say about that is like so this piece of software that we've been we sort of we take it for granted now but everything we've done is in the open every line of code every presentation every ticket it's all in github so it's all patchy
|
|
||||||
|
|
||||||
I mentioned we're contributing to the Hyperledger thing but sort of a line I say is like if your system can produce a CSV of your permit or license data then you're in our box we'll take care of the rest
|
|
||||||
|
|
||||||
you'll learn on the workshop that it's just an hour to to configure that thing to make it work for you and and that's how much work it takes kind of thing
|
|
||||||
|
|
||||||
we're trying to make it as easy as possible because we're from government we know like it's basically impossible to do IT things so we wanted to like you know make that as simple as possible
|
|
||||||
|
|
||||||
you have the concept of in this case the org book is the wallet right, and the issuers issued to it but it'll be using the same protocols in the future to issue two individual wallets which is the demand side right that sort of goes closely to the question I was going to ask
|
|
||||||
|
|
||||||
which is one of the points of blockchain is usually to have nodes under control of multiple entities where are the actual nodes right now from what I understand they're all under the control of the BC government so could there be like variances like an NGO holding onto one of the nodes, the production systems using the sovereign network to store the DID
|
|
||||||
|
|
||||||
there's a DID and a schema and a clerk read that you know credential definition and yeah on there but again in theory that could be another DID Network it's just there
|
|
||||||
aren't any other DID networks
|
|
||||||
|
|
||||||
so we're not gonna run the network we don't want to be running node but we're not running the network um the the thing you remember with verifiable credentials is they don't go on the ledger so none of the data about the organization's or about individuals goes on the ledger it all goes into a wallet
|
|
||||||
|
|
||||||
the weird thing we are doing is we've got this community wallet concept but once people have their own wallet we'll be issuing to their wallet directly we won't we may continue to issue to our own community wallet but for public credentials but for any other for the credentials once they have a wallet will be issuing to that wallet and they will be able to use it wherever they need to use it in whatever jurisdiction has systems that allow it
|
|
||||||
|
|
||||||
we are doing some collaboration with some folks from spark Telecom New Zealand that have a pretty nice implementation and we're using that as an opportunity to develop the early version of the agent agent protocol that's generalized
|
|
||||||
|
|
||||||
so as soon as we get code that map we had originally that just had Ontario and and Ottawa on it will expand to include New Zealand so we're looking forward to that and others
|
|
||||||
|
|
||||||
the schema you used for business registration is something that came from a standard about business registration or Ontario's doing the same one so that you guys just like get together in a darkroom and created or New Zealand I mean what happens with that
|
|
||||||
|
|
||||||
it's a schema that we co-created with Canada and Ontario
|
|
||||||
but we also looked at like standards in Canada that have evolved like I've been in this business for very it's not an ISO no no no there isn't such a thing in the world for that for businesses other than like maybe schema.org but it's
|
|
||||||
really not sufficient yeah so we evolved it together and so far
|
|
||||||
it's working you know
|
|
||||||
|
|
||||||
it's a bit tricky to get the minimal set but but again this helped with having multiple jurisdictions involved so we had a first, we did Ontario and we went wait this isn't gonna work we don't want that we're both Canadian entities we should be able to figure that out and that worked pretty well and then the other side of it was
|
|
||||||
|
|
||||||
once we got into things like the the doing business as well that's totally uncharted territory no not really yeah been done and we came up with something, Ontario came up with something even better, and we balance back and forth to figure out what a real
|
|
||||||
|
|
||||||
it's actually a relationship credential so we can have it point both ways the interesting thing there the thought process was a lot around we originally started oh you know how is The Org Book gonna show this and all that then we realized no that's not the right thinking what the thinking is is what is the business gonna want to do with this
|
|
||||||
|
|
||||||
what do they have to prove to somebody else and that's how you look at how how to build a credential is you stick it in the wallet of a business in this case or a person and figure out okay they've got to prove this to show that they're a
|
|
||||||
partnership to the bank how are they gonna do that and
|
|
||||||
|
|
||||||
that's the sort of mindset we had in building credentials so we built this so that's where the relationship credential came from which is I was very happy about because it's basically the edge in a graph so I'm terminal like that idea
|
|
||||||
|
|
||||||
the registration credentials are the nodes and this is a credential that demonstrates a linkage between the nodes of a knowning doing businesses name but that that those labels could be changed to is a director or as a beneficiary or any kind of relationship can be modeled this way between two things and so that generalizes the model to basically whatever you want which also gives it interesting properties in terms of visualization and analysis and relationship recommendation engines and that kind of stuff so it was fun hospital systems
|
|
||||||
|
|
||||||
we're gonna be talking with man Revere you know that's what an interesting thing is that you know like if you look at you know College of Physicians and Surgeons and other kind of public statements my you know engineering societies they publish these things already so they could have a version of this and then that just becomes part of the overall ecosystem so that you can for example have a prescription issued by a doctor to patient that patient brings the prescription to a pharmacy the pharmacy asks proof but at the same time can look at that credential say oh I'm gonna look up that doctor in this in the public you know verify in public doc hub or whatever the heck they call it and and they can subscribe to those things too so they can always know if that doctor currently licensed maybe that doctor has a restriction on the kinds of things they can prescribe so I think it's like it's a it's complementary to the peer-to-peer transaction when you have these public sort of hubs of trusted data we don't have them loaded today now like you come to the workshop we could
|
|
||||||
build another interesting one we're looking at is evident evidence so another function and the provincial
|
|
||||||
government is mining inspections things
|
|
||||||
like this so inspectors go out into the field out like offline and they are recording videos taking pictures making
|
|
||||||
notes and so forth and they would like to be able to be used data that they gather five you ten years from now and
|
|
||||||
be able to answer the question definitively it was this person using this device on this place at this time
|
|
||||||
and it data was unaltered well that's a credential you could have their phone issue a credential to an internal hub of
|
|
||||||
like this and you know ten years from now when there's a court case they can use that you can just ask for a proof
|
|
||||||
from it and at that point we know that it's unaltered and and we know who it was and we know what version it was and
|
|
||||||
what chunk of binary data was hashed in there
|
|
||||||
so we had to experiment with that that could be quite an interesting matter all right we're just about done any other
|
|
||||||
questions or great well hopefully some of you will come for a workshop and thanks for your time
|
|
||||||
[Applause]
|
|
||||||
|
|
||||||
|
|
||||||
**Contact Me for Research Based Content—[infominer.id](https://infominer.id)**
|
|
@ -1,42 +0,0 @@
|
|||||||
# Hyperledger Global Forum—2018
|
|
||||||
|
|
||||||
For Identity Related Presentations at HGF-2018
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/3WNoTB0.png"/>
|
|
||||||
|
|
||||||
Basel Congress Center — Basel, Switzerland — December 12-15,2018
|
|
||||||
|
|
||||||
* [Inaugural Hyperledger Global Forum Showcases Strong Community Momentum](https://www.linuxfoundation.org/press-release/2018/12/inaugural-hyperledger-global-forum-showcases-strong-community-momentum/)
|
|
||||||
>SAN FRANCISCO AND BASEL, SWITZERLAND – (December 12, 2018) – Hyperledger, an open source collaborative effort created to advance cross-industry blockchain technologies, today kicked off the first day of its Hyperledger Global Forum. The event has drawn more than 650 attendees from as far as Australia and Argentina for an extended conversation about the state of open source enterprise blockchain and vision for the Hyperledger community and technologies.
|
|
||||||
|
|
||||||
## Official Links
|
|
||||||
* https://events.linuxfoundation.org/events/hyperledger-global-forum-2018/
|
|
||||||
* https://hgf18.sched.com/
|
|
||||||
* [Youtube Playlist](https://www.youtube.com/playlist?list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP) (I've tried to pick out the identity specific presentations)
|
|
||||||
* [How Individuals are Taking Ownership of their Digital Identity](https://www.youtube.com/watch?v=SdrmA0YNSRw&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=4&t=0s)
|
|
||||||
* [MyCuID: Blockchains, Credentials and Credit Unions - Julie Esser, CULedger](https://www.youtube.com/watch?v=PQHx_b59sXg&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=19)
|
|
||||||
* [Ecosystem of Credentials: ATB, Telus & Customers - Mike Brown, ATB Financial](https://www.youtube.com/watch?v=QlFmAIPlpmc&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=8&t=0s)
|
|
||||||
* [Panel Discussion: Where Are We Now with Identity? - Moderated by Heather Dahl, The Sovrin Foundation](https://www.youtube.com/watch?v=2tEuUbE21s0&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=26)
|
|
||||||
* [To Authenticate or Validate, That is The Question - Avesta Hojjati, DigiCert Inc](https://www.youtube.com/watch?v=s4vN3D23dEM&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=30)
|
|
||||||
* [Hyperledger Supporting Blockcerts Compliant Digital Diplomas across Colombian Universities](https://www.youtube.com/watch?v=r2BGzIsB4ww&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=24&t=0s)
|
|
||||||
* [Live Demo of Omnitude Using Hyperledgy Indy and Fabric - James Worthington, Omnitude](https://www.youtube.com/watch?v=qXJfvFTgYg4&index=35&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP)
|
|
||||||
* [Cross Ledger Portable Identity with Indy and Corda - Mike Ward, R3](https://www.youtube.com/watch?v=KeHbYajhizc&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=38)
|
|
||||||
* [Panel Discussion: Is Blockchain GDPR Ready? - Moderated by Phillip Windley, Sovrin Foundation](https://www.youtube.com/watch?v=SmV0KBpNpaQ&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=46)
|
|
||||||
* [SDK Proxy: Hyperledger Fabric Identities for Lightweight IoT Devices](https://www.youtube.com/watch?v=AMwKr9Lt9d0&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=53)
|
|
||||||
* [Overview: Agents and Hyperledger Indy - Kyle Den Hartog, Evernym - Part 1](https://www.youtube.com/watch?v=P_9N-Kt1nFs&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=104)
|
|
||||||
* [Overview: Agents and Hyperledger Indy - Kyle Den Hartog, Evernym - Part 2](https://www.youtube.com/watch?v=ctwf02B722o&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=103)
|
|
||||||
* [Hands-On with Verifiable Organizations Network based on Hyperledger Indy - Part 1](https://www.youtube.com/watch?v=R5TB-goL3_o&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=108)
|
|
||||||
* [Hands-On with Verifiable Organizations Network based on Hyperledger Indy - Part 2](https://www.youtube.com/watch?v=j-lM2hNq1TI&list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP&index=107)
|
|
||||||
|
|
||||||
## Unofficial Transcripts
|
|
||||||
|
|
||||||
I think I've arranged all of the identity related talks in the previous section, except for the following two.
|
|
||||||
|
|
||||||
For my own convinience, and for anyone else who would like to browse the text, I've worked on the transcripts a bit to make the content easier to reference.
|
|
||||||
|
|
||||||
I'll do this for any other "essential" videos containing information that isn't widely available elsewhere, and am open to recommendations.
|
|
||||||
|
|
||||||
If you have any videos you'd like to see transcripts prepared in the following format, feel free to [contact me](https://infominer.id).
|
|
||||||
|
|
||||||
* [Microledgers and Edge-Chains - Daniel Hardman - Evernym](https://github.com/infominer33/awesome-decentralized-id/blob/master/hyperledger/hgf-2018/Microledgers-Edgechains-Hardman-HGF.md)
|
|
||||||
* [Verifiable Organizations Network: A Production Government Deployment of Hyperledger Indy](https://github.com/infominer33/awesome-decentralized-id/blob/master/hyperledger/hgf-2018/VerifiableOrganizationsNetwork-HGF.md)
|
|
271
docs/history.md
271
docs/history.md
@ -1,271 +0,0 @@
|
|||||||
# DID-SSI History
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
* [Losing Control over our Personal Information](#losing-control-over-our-personal-information) '80s
|
|
||||||
* [PGP - Web of Trust](#pgp---web-of-trust-) '91
|
|
||||||
* [International Planetwork Conference](#international-planetwork-conference-) '00s
|
|
||||||
* [XNS Public Trust Organization](#xns-public-trust-organization-)
|
|
||||||
* [The Augmented Social Network](#the-augmented-social-network-) '03
|
|
||||||
* [IDCommons](#idcommons-) '01
|
|
||||||
* [Identity Gang](#identity-gang-) '04
|
|
||||||
* [Kim Cameron - Laws of Identity](#kim-cameron---laws-of-identity)
|
|
||||||
* [Internet Identity Workshop—IIW](#internet-identity-workshop-) '05
|
|
||||||
* [W3C Credentials Community Group](#w3c-credentials-community-group-) '14
|
|
||||||
* [Bitnation](#bitnation-) '15
|
|
||||||
* [The United Nations Sustainable Development Goals](#the-united-nations-sustainable-development-goals-) '15
|
|
||||||
* [#Rebooting-Web-of-Trust (RWoT)](#rebooting-the-web-of-trust-)
|
|
||||||
* [Evernym](#evernym-)
|
|
||||||
* [ID2020 and the GDPR](#id2020-and-the-gdpr-) '16
|
|
||||||
* [The End of 2016](#the-end-of-2016-)
|
|
||||||
* [Decentralized Identity Foundation](#decentralized-identity-foundation-) '17
|
|
||||||
* [Standards History](#standards-history-)
|
|
||||||
* [Resources](#resources-)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
## Losing Control Over our Personal Information
|
|
||||||
|
|
||||||
![](https://i.imgur.com/ESDJa4P.png)
|
|
||||||
|
|
||||||
* [Security without Identification: Transaction Systems to Make Big Brother Obsolete](https://www.cs.ru.nl/~jhh/pub/secsem/chaum1985bigbrother.pdf) - David Chaum, 1985.
|
|
||||||
* The large-scale automated transaction systems of the near future can be designed to protect the privacy and maintain the security of both individuals and organizations.
|
|
||||||
> Computerization is robbing individuals of the ability to monitor and control the ways information about them is used. As organizations in both the private and the public sectors routinely exchange such informa- tion, individ.uals have no way of knowing if the information is inaccurate, obsolete, or otherwise inap- propriate. The foundation is being laid for a dossier society, in which computers could be used to infer individuals’ life-styles, habits, whereabouts, and asso- ciations from data collected in ordinary consumer transactions. Uncertainty about whether data will re- main secure against abuse by those maintaining or tapping it can have a “chilling effect,” causing people to alter their observable activities. As computerization becomes mclre pervasive, the potential for these prob- lems will grow dramatically.
|
|
||||||
|
|
||||||
* [Information Technology and Dataveillance](http://www.rogerclarke.com/DV/CACM88.html) - Roger Clarke, 1988.
|
|
||||||
> The concept of 'dataveillance' is introduced, and defined as the systematic monitoring of people's actions or communications through the application of information technology. Dataveillance's origins are traced, and an explanation provided as to why it is becoming the dominant means of monitoring individuals and populations.
|
|
||||||
>
|
|
||||||
> The paper identifies, classifies and describes the various dataveillance techniques. It then examines the benefits, and especially the dangers, arising from dataveillance. It considers the intrinsic and extrinsic controls that act to keep the application of dataveillance under control, and suggests some appropriate policy measures.
|
|
||||||
|
|
||||||
## PGP - Web of Trust [**^**](#contents)
|
|
||||||
|
|
||||||
[![](https://i.imgur.com/sMV9PE4.png)](https://www.philzimmermann.com/EN/essays/WhyIWrotePGP.html)
|
|
||||||
|
|
||||||
Phil [Zimmerman creates PGP](https://www.philzimmermann.com/EN/essays/WhyIWrotePGP.html), 1991.
|
|
||||||
* First time strong encryption widely available to general public.
|
|
||||||
* PGP’s web-of-trust provide early foundation for SSI. However, PGP is known as difficult to use and failed to reach wide adoption for personal communication\identification.
|
|
||||||
|
|
||||||
* [PGP -Web of Trust -linux.com](https://www.linux.com/learn/pgp-web-trust-core-concepts-behind-trusted-communication)
|
|
||||||
|
|
||||||
## International Planetwork Conference [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/RfKqBP9.png)
|
|
||||||
|
|
||||||
The first International [Planetwork](https://planetwork.net/about.html) Conference - Global Ecology and Information Technology, San Francisco, May 2000.
|
|
||||||
|
|
||||||
The community that developed around the Planetwork conferences, including [Linktank](https://planetwork.net/linktank.html), form an intellectual foundation for what became Self Sovereign Identity.
|
|
||||||
|
|
||||||
## XNS Public Trust Organization [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/BNpzEkE.png)
|
|
||||||
|
|
||||||
XNS Public Trust Organization. Founded in July 2000, shortly after Planetwork Conference. -[xdi.org - History](http://xdi.org/?page_id=13)
|
|
||||||
|
|
||||||
> to promote the concept of individuals owning their own digital identity and data based on a nascent technology being produced by two Technical Committees at OASIS: XRI (Extensible Resource Identifier) and XDI (Extensible Data Interchange).
|
|
||||||
|
|
||||||
## Augmented Social Network [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/B5Bja7O.png)
|
|
||||||
|
|
||||||
* *[The Augmented Social Network](http://asn.planetwork.net/): Building Identity and Trust into the Next-Generation Internet,* presented at the June 2003 Planetwork conference and published in [First Monday](http://www.uic.edu/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/1068/988) the Peer-Reviewed Journal on the Internet 8/4/03.
|
|
||||||
>"[This paper](http://asn.planetwork.net/asn-archive/AugmentedSocialNetwork.pdf) proposes the creation of an Augmented Social Network (ASN) that would build identity and trust into the architecture of the Internet"
|
|
||||||
|
|
||||||
## IDCommons [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/AOw2oXx.png)
|
|
||||||
|
|
||||||
The [Identity Commons](http://wiki.idcommons.net/History) (2001-Present) was originally created by Owen Davis and Andrew Nelson in 2001 to evangelize the creation of a decentralized user-centric identity infrastructure and to address the resulting social trust issues.
|
|
||||||
|
|
||||||
* Kaliya Young began working with Identity Commons following June 2004 Planetwork Conference. Working with Social Physics team, led by Paul Trevithick and Mary Ruddy, and included Doc Searls and Phil Windley, they wove a community around user-centric id that came together at the Digital Identity World conference, of 2004.
|
|
||||||
|
|
||||||
Resuling in a mailing list:
|
|
||||||
* [community@lists.idcommons.net](https://lists.idcommons.net/lists/info/community)
|
|
||||||
> The general community mailing list for Identity Commons. The list is also called the Identity Gang mailing list and was formerly idworkshop at googlegroups.
|
|
||||||
|
|
||||||
## Identity Gang [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/xbfK3EF.png)
|
|
||||||
|
|
||||||
* [The original identity gang](https://www.idcommons.org/the-original-identity-gang/)
|
|
||||||
Doc Searls invited identity leaders to appear on the Gilmore Gang podcast, where the name "Identity Gang" was coined.
|
|
||||||
|
|
||||||
At the encouragement of Doc Searls, a number of people began blogging about user-centric identity.
|
|
||||||
|
|
||||||
* [The Gillmor Gang - December 31, 2004](http://web.archive.org/web/20130729213722id_/http://itc.conversationsnetwork.org/shows/detail394.html) Featuring:
|
|
||||||
> * Steve Gillmor, contributing editor, ZDNet
|
|
||||||
> * Doc Searls, senior editor, Linux Journal
|
|
||||||
> * Craig Burton, founding member, Novell; co-founder, The Burton Group
|
|
||||||
> * Kim Cameron, Microsoft's Architect of Identity and Access Systems
|
|
||||||
> * Dave Winer, father of RSS and more
|
|
||||||
> * Marc Canter, Broadband Mechanics
|
|
||||||
> * Bryan Field-Elliot, CTO, Ping Identity Corporation
|
|
||||||
> * Phil Windley, Brigham Young University
|
|
||||||
> * Drummond Reed, CTO, Cordance
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
"Their most important contribution may have been the creation, in association with the Identity Gang, of the Internet Identity Workshop (2005-Present) working group." -[*Path to Self Sovereign Identity*](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)
|
|
||||||
|
|
||||||
* Paul Trevithick created the [Identity Gang Lexicon](https://web.archive.org/web/20080916112039/wiki.idcommons.net/Lexicon) -2005.
|
|
||||||
|
|
||||||
|
|
||||||
### Kim Cameron - Laws of Identity [**^**](#contents)
|
|
||||||
|
|
||||||
[![](http://i.imgur.com/570mUhZ.png)](https://identityblog.com)
|
|
||||||
|
|
||||||
* [Kim Cameron Identity Laws](https://channel9.msdn.com/Blogs/scobleizer/Kim-Cameron-Identity-Laws) [[**x**](https://www.identityblog.com/?m=200412)]
|
|
||||||
* [Laws of Identity - Whitepaper](https://web.archive.org/web/20080814163727/http://www.identityblog.com/stories/2004/12/09/thelaws.html)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Internet Identity Workshop [**^**](#contents)
|
|
||||||
![](https://www.yubico.com/wp-content/uploads/2013/10/IIW-blog.jpg)
|
|
||||||
|
|
||||||
|
|
||||||
In 2005, [Kaliya Young](https://identitywoman.net/)[[**T**](https://twitter.com/IdentityWoman)], [Phil Windley](https://windley.com)[[**T**](https://twitter.com/windley)][[**V**](https://vimeo.com/windley)][[**G**](https://github.com/windley)], [Drummond Reed](https://www.evernym.com/)[[**T**](https://twitter.com/drummondreed)][[**B**](https://equalsdrummond.name/)], and [Doc Searls](http://blogs.harvard.edu/doc/)[[**T**](https://twitter.com/dsearls)][[**B**](https://blogs.harvard.edu/doc)] hosted the first [Internet Identity Workshop](http://www.internetidentityworkshop.com/)(IIW)[[**T**](https://twitter.com/idworkshop)] in Berkeley to discuss "architectural and governance proposals for Internet-wide identity services and their underlying philosophies." -[Announcing IIW 2005](https://identitywoman.net/announcing-the-internet-identity-workshop-iiw2005/)
|
|
||||||
|
|
||||||
* [unconference.net](http://unconference.net/)
|
|
||||||
|
|
||||||
Since then, the IIW has met bi-anually, actively supporting the development of the identity software-ecosystem, including [OpenID](http://wiki.openid.net)('05), OpenID [2.0](http://wiki.openid.net/w/page/12995215/OpenID%20Authentication%202-1)('06), [OAuth](https://en.wikipedia.org/wiki/OAuth)('10), [FIDO](https://fidoalliance.org/)('13) and OpenID [Connect](https://en.wikipedia.org/wiki/OpenID_Connect)('14).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
* Markus Sabadello began work on [Project Danube](https://web.archive.org/web/20101221105543/http://projectdanube.org/), on the creation of an XDI based personal data store, always under the control of its users, as early as 2010.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
> Founded in 2011, the [Personal Data Ecosystem](https://www.idcommons.org/working-groups/personal-data-ecosystem-consortium/) Consortium advocates a user-centric approach to managing personal data
|
|
||||||
|
|
||||||
![](https://i.imgur.com/wuvo5BG.png)
|
|
||||||
|
|
||||||
IIW participants began the effort towards creating a truly [user centric identity](https://www.networkworld.com/article/2304596/access-control/what-is--user-centric--identity-.html), in contrast to identity solutions whos focus has been fulfilling the needs of the enterprise. The pioneers of decentralized identity have long struggled against the "[identity silo paradox](https://www.zdnet.com/article/the-identity-silo-paradox/)," that while the *identerati* continually work on solutions to break up these silos, the enterprise has had a strong financial incentive to retain them.
|
|
||||||
|
|
||||||
* [What is IIW?](https://vimeo.com/173562225) [[**ϟ**](https://vimeo.com/207961532)][[**ϟ**](https://www.prweb.com/releases/identitymovie/iiw2017/prweb14161721.htm)] short film about the [identirati](https://www.zdnet.com/article/the-identity-silo-paradox/)[[**ϟ**](https://www.forgerock.com/blog/who-are-the-identerati)] (a term for those working on identity standards for the purpose of breaking up id data silos, dating back to at least 2006).
|
|
||||||
* [*What is Sovereign Source Authority?*](https://www.moxytongue.com/2012/02/what-is-sovereign-source-authority.html) leads to the term Self Sovereign Identity.
|
|
||||||
* [Windhover Principles for Digital Identity](https://www.tokencommons.org/Windhover-Principles-for-Digital-Identity-Trust-Data.html)
|
|
||||||
* [HubID First to Deploy Windhover Principles and Framework for Digital Identity, Trust and Open Data](https://hubculture.com/hubs/47/news/689/)
|
|
||||||
* [WEForum - Personal Data: The Emergence of a New Asset Class](http://www3.weforum.org/docs/WEF_ITTC_PersonalDataNewAsset_Report_2011.pdf)
|
|
||||||
|
|
||||||
## W3C Credentials Community Group [**^**](#contents)
|
|
||||||
|
|
||||||
[8/14](https://www.w3.org/community/credentials/charter-20140808/) The [Credentials Community Group](https://www.w3.org/community/credentials/)[[**ϟ**](https://w3c-ccg.github.io/)] forms, hosted by [World Wide Web Consortium(W3C)](https://www.w3.org/)[[**T**](https://twitter.com/w3c)] [[**G**](https://github.com/w3c)] : "to forge a path for a secure, decentralized system of credentials that would empower both individual people and organizations on the Web to store, transmit, and receive digitally verifiable proof of qualifications and achievements." —proposed by [Manu Sporney](http://manu.sporny.org/)[[**T**](https://twitter.com/manusporny)] (of [digitalbazaar.com](https://digitalbazaar.com/))
|
|
||||||
|
|
||||||
* [Consensys begins work on uPort](https://medium.com/@ConsenSys/identity-is-defined-in-merriam-s-dictionary-as-who-someone-is-a3d6a69f5fa4) -2015
|
|
||||||
|
|
||||||
## Bitnation [**^**](#contents)
|
|
||||||
|
|
||||||
9\15 [Bitnation](https://bitnation.co/) "seeks to establish the concept of '*world citizenship*' via a bitcoin based identity, offering '[*Blockchain Emergency IDs*](https://refugees.bitnation.co/)' to refugees. [[**>**](#Bitcoin)]
|
|
||||||
|
|
||||||
## The United Nations Sustainable Development Goals [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="http://i.imgur.com/6ffztbs.png"/>
|
|
||||||
|
|
||||||
The same month, the UN unveiled it's *[Agenda for Sustainable Development](https://sustainabledevelopment.un.org/post2015/transformingourworld)*:
|
|
||||||
>* Promote peaceful and inclusive societies for sustainable development, provide access to justice for all and build effective, accountable and inclusive institutions at all levels
|
|
||||||
>* Substantially reduce corruption and bribery in all their forms
|
|
||||||
Develop effective, accountable and transparent institutions at all levels
|
|
||||||
>* **By 2030, [provide legal identity for all](https://sustainabledevelopment.un.org/sdg16), including birth registration**
|
|
||||||
>* Ensure public access to information and protect fundamental freedoms, in accordance with national legislation and international agreements—(*emphasis mine*)
|
|
||||||
* [DIGITAL IDENTITY AS A BASIC HUMAN RIGHT](https://impakter.com/digital-identity-basic-human-right/)
|
|
||||||
* [AID:Tech](https://aid.technology) [[**T**]](https://twitter.com/aidtechnology) — "is a voucher and digital identity solution for refugees. A digital record of a person's identity is stored on a smart card, along with various additional information. Blockchain technology is used to distribute all resources in a highly traceable manner." (another early example of blockchain for humanitarian aide)
|
|
||||||
* [World Bank - Digital IDs for Development](http://www.worldbank.org/en/events/2015/06/23/digital-ids-for-development)
|
|
||||||
* [Additional Info on Blockchain and the United Nations](https://infominer.id/research/UnitedNations.html)
|
|
||||||
|
|
||||||
|
|
||||||
## Rebooting the Web Of Trust [**^**](#contents)
|
|
||||||
|
|
||||||
In relation to SSI, '[Web of Trust](https://en.wikipedia.org/wiki/Web_of_trust)' is a network of relationships that attest to our identity claims. *Each party attesting to your identity information becomes a strand in your web of trust.*
|
|
||||||
|
|
||||||
The first [Rebooting Web of Trust](http://www.WebOfTrust.info)(RWoT) workshop was held during [November 2015](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust); attracting the likes of Vitalik Buterin, Peter Todd, Gregory Maxwell, Joel Dietz, Christopher Allen, and Jon Callas, [according to Andreas Antonopolis](https://news.bitcoin.com/andreas-antonopoulos-case-reputation-identity-systems/).
|
|
||||||
|
|
||||||
[That workshop](https://github.com/WebOfTrustInfo/), produced 5 technical white papers:\
|
|
||||||
[5 WoT-usecases](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/satisfying-real-world-use-cases.pdf) • [Decentralized PKI](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/dpki.pdf) • [Smart Signatures](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/smart-signatures.pdf) • [Creating a New World of Trust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/whats-the-next-step.pdf)
|
|
||||||
|
|
||||||
* [Opportunities Created by the Web of Trust for Controlling and Leveraging Personal Data](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/satisfying-real-world-use-cases.pdf)
|
|
||||||
> "Decentralized systems that are engineered to prevent concentrating power as they grow avoid this. They can in fact increase their credibility as more users provide their assessments as input. Protocols and structures that are distributed and self-sovereign also offer significantly improved robustness, portability, and versatility than conventional centralized or escrowed processes — especially when combined with secure cryptography."
|
|
||||||
|
|
||||||
* [Rebranding the Web of Trust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/rebranding-web-of-trust.pdf)
|
|
||||||
>The Web of Trust is a buzzword for a new model of decentralized self-sovereign identity. It’s a phrase that dates back almost twenty-five years, the classic definition derives from PGP [...] the vibrant blockchain community is also drawing new attention to the concept we aim to reboot it.
|
|
||||||
|
|
||||||
|
|
||||||
At the end of 2015, the Department of Homeland Security announced that it had funds available for the development of [Blockchain Security and Identity Verification Technologies](https://blog.aniljohn.com/2015/12/federal-gov-funds-for-identity-r-and-d.html).
|
|
||||||
|
|
||||||
## Evernym
|
|
||||||
|
|
||||||
![](http://untangled.world/wp-content/uploads/2017/08/everynym-logo-1400x357.png)
|
|
||||||
|
|
||||||
* [Evernym](https://www.evernym.com/)[[**T**](https://twitter.com/evernym)] originally created the Sovrin codebase, founded in 2013.
|
|
||||||
* [Identity System Essentials](https://www.evernym.com/wp-content/uploads/2017/02/Identity-System-Essentials.pdf) 3/16 (Original Evernym Identity WP submitted to ID2020\RWoT workshop)
|
|
||||||
* [Outlier Ventures invests in, becomes strategic partner of Evernym](https://coinreport.net/outlier-ventures-invests-becomes-strategic-partner-evernym/)[[**ϟ**](https://outlierventures.io/portfolio/evernym/)]
|
|
||||||
* [The Three Models of Digital Identity Relationships — How self-sovereign identity (SSI) is different, and why it’s better](https://medium.com/evernym/the-three-models-of-digital-identity-relationships-ca0727cb5186)
|
|
||||||
|
|
||||||
|
|
||||||
## ID2020 and the GDPR [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/ymviAssl.png)
|
|
||||||
|
|
||||||
* [4/16](https://edps.europa.eu/data-protection/data-protection/legislation/history-general-data-protection-regulation_en) the EU adopted the GDPR to be enacted as law May 2018.
|
|
||||||
* [Projects aim for legal identity for everyone - ID2020, ID4D aim to bring legal, binding, digital IDs to all world's citizens](https://www.secureidnews.com/news-item/projects-aims-for-legal-identity-for-everyone/)
|
|
||||||
* The second RWoT workshop ran in conjunction with the UN's [ID2020](https://id2020.org/) Summit in New York that [May](https://press.pwc.com/News-releases/id2020-to-kick-start-digital-identity-summit-at-un-with-pwc-support./s/9fe11be5-cbd8-486b-b4d2-d798f486d0f2); clearly a significant time for decentralized identity:
|
|
||||||
>1.1 Billion people live without an officially recognized identity — This lack of recognized identification deprives them of protection, access to services, and basic rights. ID2020 is a public-private partnership dedicated to solving the challenges of identity for these people through technology. - id2020.org
|
|
||||||
* [Identity Crisis: Clear Identity through Correlation](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/identity-crisis.pdf)
|
|
||||||
* [Christopher Allen](http://www.lifewithalacrity.com/)[[**info**](https://christophera.info/)] details the overarching history of internet idenitity standards in his seminal work (submitted to ID2020\RWoT workshop):
|
|
||||||
* **[The Path to Self-Soverereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)**[[**ϟ**](https://www.coindesk.com/path-self-sovereign-identity/amp/)] details the history of identity standards leading up to self-sovereign and details the 10 principles of self-sovereign identity.
|
|
||||||
> I am part of the team putting together the first ID2020 Summit on Digital Identity at the United Nations
|
|
||||||
* [Identity System Essentials](https://www.evernym.com/wp-content/uploads/2017/02/Identity-System-Essentials.pdf) 3/16 (Original Evernym Identity WP also submitted to ID2020\RWoT workshop)
|
|
||||||
|
|
||||||
|
|
||||||
Evident from the other [whitepapers](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/README.md) submitted to the second RWoT Workshop, the DID identifier had begun to emerge:
|
|
||||||
* [Decentralized Identifiers (DIDs) and Decentralized Identity Management (DIDM)](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/DID-Whitepaper.md)
|
|
||||||
>"Decentralized Identifiers (DID) stored in a permissioned blockchain enable principals to directly control their own identities with cryptographic proofs and secure, addressable network endpoints. DIDs further enable a Decentralized Identity Management (DIDM) infrastructure that will empower people and organizations to securely and confidentially manage and assert their identities."
|
|
||||||
* [Requirements for DIDs](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/requirements-for-dids.pdf)
|
|
||||||
>"Respect Network is conducting a research project for the [U.S. Department of Homeland Security](https://bravenewcoin.com/insights/u-s-department-of-homeland-security-funds-four-blockchain-companies-developing-new-cyber-security-technology), HSHQDC-16-C-00061, to analyze the applicability of blockchain technologies to a decentralized identifier system. Our thesis is that blockchains, or more generically distributed ledgers, are a potentially powerful new tool for “identity roots” — the starting points for an Internet identity. However “blockchain identity” may not fully address the core security and privacy principles needed in a complete identity system. In this case DIDs — Decentralized Identifiers rooted on a distributed ledger — may end up being a foundational building block for higher level identity management solutions. -
|
|
||||||
|
|
||||||
## The End of 2016 [**^**](#contents)
|
|
||||||
|
|
||||||
* [News Release: DHS S&T Awards $1.3 Million to Small Businesses for Cyber Security Research and Development](https://www.dhs.gov/science-and-technology/news/2016/08/12/news-release-dhs-st-awards-13-million-small-businesses-cyber) -2016
|
|
||||||
* [Applying Blockchain to Decentralized Identity](https://www.sbir.gov/sbirsearch/detail/1241097)
|
|
||||||
> Respect Network will research and develop a decentralized registry and discovery service for Decentralized Identifiers (DIDs) to integrate with the public blockchain. DIDs will allow principals to directly control their own identities with cryptographic proofs and secure, addressable network endpoints. DIDs will enable a Decentralized Identity Management (DIDM) infrastructure that will empower people and organizations to securely and confidentially manage and assert their identities. Open standards and established industry protocols will permit principals to selectively disclose identity claims, and to manage their privacy and digital relationships. Respect Network's thesis is that the combination of DIDs and DIDM architecture, using public and/or private blockchains as "identity backbones", can meet traditional information security principles of confidentiality, integrity, availability, non-repudiation and provenance. Further, our approach applies privacy-by-design principles, including user control, selective disclosure of information and pseudonymity.
|
|
||||||
* [Credentials on Public/Private Linked Ledgers](https://www.sbir.gov/sbirsearch/detail/1241085)
|
|
||||||
> A wide variety of applications could benefit from combining identity management technology with decentralized ledgers (aka blockchains). However, not every application uses the same data or requires the same consensus or authorization models. While a single solution is unlikely, we assert each application could benefit from a standard, configurable, decentralized ledger with flexible semantics. We will study the feasibility of this concept by building a proof-of-concept Linked Data ledger format and architecture.
|
|
||||||
|
|
||||||
|
|
||||||
* [Pan Canadian Trust Framework](https://diacc.ca/pan-canadian-trust-framework/) - 2016
|
|
||||||
>The Pan-Canadian Trust Framework (PCTF) enables Canada’s full and secure participation in the global digital economy through economic sector innovation and the enablement of modernized digital service delivery. The PCTF supports open government principles.
|
|
||||||
|
|
||||||
* Phil Windley [announces formation of the Sovrin Foundation](http://www.windley.com/archives/2016/09/announcing_the_sovrin_foundation.shtml) charged with maintaining its, public-permissioned, distributed ledger for identity, donated by Evernym -September 2016.
|
|
||||||
>Sovrin Foundation is a private-sector, international non-profit established to govern a global public utility for self-sovereign identity.
|
|
||||||
|
|
||||||
* MyData founded to give structure to an international movement, promoting the rights of individuals to have control over our personal information - [August, 2016](http://mydata2016.org/)
|
|
||||||
|
|
||||||
* Learning Machine working with MIT on an [open standard](https://medium.com/learning-machine-blog/blockchain-credentials-b4cf5d02bbb7) for blockchain credentials for the past year. Led by Chris Jagers, Kim Hamilton Duffy, and John Papinchak their Blockcerts prototype was released in October 2016.
|
|
||||||
|
|
||||||
|
|
||||||
## Decentralized Identity Foundation [**^**](#contents)
|
|
||||||
|
|
||||||
On May 22 at Consensus 2017 the formation of the Decentralized Identity Foundation (DIF) [was announced](https://www.ethnews.com/decentralized-identity-foundation-announces-formation-at-consensus-2017):
|
|
||||||
* [Conensus 2017 - Building an Foundation for Decentralized Identity](https://www.youtube.com/watch?v=l5laRZfn8AI) (video)
|
|
||||||
* [Decentralized Identity Foundation Grows To 56 Members In Our First Year](https://medium.com/decentralized-identity/decentralized-identity-foundation-grows-to-56-members-in-our-first-year-3ec117e811d8)
|
|
||||||
|
|
||||||
|
|
||||||
## Standards History [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/XtZQg0j.png)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/FBe3S0w.png)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/5R51G4Y.png)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/xmWkc4l.png)
|
|
||||||
|
|
||||||
|
|
||||||
<a href="https://www.youtube.com/watch?v=RllH91rcFdE">The Story of Open SSI Standards - Drummond Reed/Evernym SSIMeetup.org</a> [<a href="https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed">**ϟ**</a>]
|
|
||||||
|
|
||||||
|
|
||||||
## Resources [**^**](#contents)
|
|
||||||
* [A Brief History of Digital Identity](https://medium.com/humanizing-the-singularity/a-brief-history-of-digital-identity-9d6a773bf9f5)
|
|
||||||
* [A Step Back in Time: The History and Evolution of Digital Identity](https://www.iotevolutionworld.com/iot/articles/410328-step-back-time-history-evolution-digital-identity.htm)
|
|
||||||
* [Identity Commons-Wiki](http://wiki.idcommons.net/Main_Page)
|
|
||||||
* [IIW-Wiki](https://iiw.idcommons.net/Main_Page)
|
|
||||||
* [IIW - Past Workshops](https://internetidentityworkshop.com/past-workshops/)
|
|
||||||
* [identitywoman.net](https://identitywoman.net/)
|
|
||||||
* [windley.com/tags/identity](http://www.windley.com/tags/identity.shtml)
|
|
||||||
* [WoTinfo](https://github.com/WebOfTrustInfo/)
|
|
||||||
* [The Path to Self Sovereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)
|
|
@ -1,11 +0,0 @@
|
|||||||
# Humanitarian
|
|
||||||
* [Blockchain Can Empower Stateless Refugees](https://www.law360.com/technology/articles/1095148/blockchain-can-empower-stateless-refugees)
|
|
||||||
* [iRespond](https://www.irespond.org/) -international non-profit organization dedicated to solving the identity problem using a unique digital biometric identity solution
|
|
||||||
* [The Humanized Internet](http://www.thehumanizedinternet.org/) — "to defend the rights of vulnerable people, and give every human being worldwide secure, sovereign control over their own digital identity."
|
|
||||||
* [CheapID](http://guptaoption.com/cheapid/) - identity standard designed for use in conflicted environment like those many refugees or disaster victims may find themselves in.
|
|
||||||
* uses [State In A Box - Identity Services Architecture](http://guptaoption.com/4.SIAB-ISA.php)
|
|
||||||
* [World Identity Netowork](https://win.systems/)
|
|
||||||
* Blockchain for Impact [(BFI)-UN]((https://www.pvblic.org/blockchainforimpact))
|
|
||||||
* [Self-Sovereign Identity Systems for Humanitarian Interventions—A Case Study on Protective Cash Transfer Programs](https://repository.tudelft.nl/islandora/object/uuid:6cdb5450-9a81-47a9-8ffa-f9bd77c72448/datastream/OBJ1/download)
|
|
||||||
* [The Nail Finds a Hammer: Self-Sovereign Identity, Design Principles, and Property Rights in the Developing World](https://www.newamerica.org/future-property-rights/reports/nail-finds-hammer/)
|
|
||||||
|
|
21
docs/ibm.md
21
docs/ibm.md
@ -1,21 +0,0 @@
|
|||||||
# IBM Identity
|
|
||||||
**Specifications, Literature, Applications**
|
|
||||||
|
|
||||||
![](https://i.imgur.com/CvZI7R1.png)
|
|
||||||
|
|
||||||
* [Paving the Road to Self-Sovereign Identity with Blockchain, Open Standards](https://www.ibm.com/blogs/think/2017/10/self-sovereign-id-blockchain/)
|
|
||||||
* [github.com/IBM-Blockchain-Identity](https://github.com/IBM-Blockchain-Identity) (Docker based tutorial sandbox env)
|
|
||||||
* [How do we start tackling the existing identity problem](https://www.ibm.com/blogs/blockchain/2018/06/how-do-we-start-tackling-the-existing-identity-problem/)
|
|
||||||
* [Swipe Right on Verifiably Credentials](https://developer.ibm.com/code/2018/05/22/swipe-right-on-verifiable-credentials/)
|
|
||||||
* [WISeKey fully deployed its CertifyID integrating Digital Identity with Blockchain technology](https://globenewswire.com/news-release/2018/07/11/1535718/0/en/WISeKey-fully-deployed-its-CertifyID-integrating-Digital-Identity-with-Blockchain-technology.html)
|
|
||||||
* [Mooti](https://mooti.co/) [[**D**](https://docs.mooti.co/)]
|
|
||||||
* offers an "identity chain" technology that makes it possible to issue and revoke verified claims using elliptic curve cryptography (curve25519, secp256k1) and includes privay-enhancing features [[**ϟ**](https://www.cio.com/article/3147358/it-industry/ibm-building-blockchain-ecosystem.html)]
|
|
||||||
* [SecureKey](http://securekey.com/): [partners with IBM](http://www-03.ibm.com/press/us/en/pressrelease/51841.wss) to enable a new digital identity and attribute sharing network based on Hyperledger Fabric blockchain.
|
|
||||||
|
|
||||||
|
|
||||||
### /IBM-Blockchain-Identity [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-tutorial-sandbox" target="_blank">/IBM-Blockchain-Identity/indy-tutorial-sandbox</a> - Forked from brycecurtis/indy-tutorial-sandbox
|
|
||||||
A turnkey, Docker-based sandbox that enables quick and easy exploration of Hyperledger Indy concepts.
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-ssivc-tutorial" target="_blank">/IBM-Blockchain-Identityindy-ssivc-tutorial</a> - A turnkey, Docker-based tutorial for help developers get acquainted with Self-Sovereign Identity and Verifiable Credentials.
|
|
@ -1,137 +0,0 @@
|
|||||||
|
|
||||||
## Decentralized Identity Foundation
|
|
||||||
|
|
||||||
>A key piece of the decentralized identity equation is how people, organizations, and devices can be identified and located without centralized systems of identifiers (e.g. email addresses). DIF members are actively working on protocols and implementations that enable creation, resolution, and discovery of decentralized identifiers and names across decentralized systems, like blockchains and distributed ledgers.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
* [DIF](#dif---decentralized-identity-foundation-)
|
|
||||||
* [/decentralized-identity - GitHub](#-decentralized-identity---github-)
|
|
||||||
* [DIF - DID](#dif---did-)
|
|
||||||
* [DIF - DID-Auth](#dif---did-auth-)
|
|
||||||
* [DIF - Sidetree](#dif---sidetree-)
|
|
||||||
* [DIF - Hub](#dif---hub-)
|
|
||||||
* [DIF - Uniresolver](#dif---uniresolver-)
|
|
||||||
|
|
||||||
## DIF - Decentralized Identity Foundation
|
|
||||||
|
|
||||||
![](https://imgur.com/PXGV6Xyl.png)
|
|
||||||
|
|
||||||
* [Decentralized Identity Foundation](https://identity.foundation/) (DIF) [[**G**](https://github.com/decentralized-identity)] [[**T**](https://twitter.com/DecentralizedID)] [[**B**](https://medium.com/decentralized-identity)]
|
|
||||||
* <a href="https://github.com/decentralized-identity/org" target="_blank">DIF Organizational Materials</a>
|
|
||||||
* [Identity Hubs Capabilities Perspective](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/identity-hubs-capabilities-perspective.md) - Identity Hubs currently proposed in the Decentralized Identity Foundation (DIF) are a subset of a general Decentralized Identifier (DID).
|
|
||||||
* [On DIF Hubs and Sovrin Agents](https://forum.sovrin.org/t/on-dif-hubs-and-sovrin-agents/897?u=phil)
|
|
||||||
* [A Universal Resolver for self-sovereign identifiers](https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c) [[**G**](https://github.com/decentralized-identity/universal-resolver)] [[**>**](#Decentralized-Identity-Foundation)]
|
|
||||||
* [uniresolver.io](https://uniresolver.io/)
|
|
||||||
* [6/27 Masterclass on the DID Universal Resolver | Identiverse 2018](https://www.slideshare.net/Identiverse/627-masterclass-on-the-did-universal-resolver-identiverse-2018)
|
|
||||||
|
|
||||||
DIF members, who share the goal of “building an open source decentralized identity ecosystem for people, organizations, apps, and devices” include:
|
|
||||||
* [1kosmos](https://onekosmos.com/product-details/)
|
|
||||||
• [Accenture](https://www.accenture.com/us-en/insight-blockchain-id2020)
|
|
||||||
• [aetna](https://www.aetna.com/)
|
|
||||||
• [Authenteq](https://venturebeat.com/2018/08/30/authenteq-launches-blockchain-identity-verification-to-stop-online-trolls/)
|
|
||||||
• [auth0](https://auth0.com/)
|
|
||||||
• [BigchainDB](http://docs.bigchaindb.com/en/latest/)
|
|
||||||
• [BlockPass](https://www.blockpass.org/downloads/BlockpassWhitepaper.v1.3.2.pdf)
|
|
||||||
• [Blockchain-foundry](https://www.blockchainfoundry.co/blockchain-foundry-inc-announces-new-software-release-for-blockchain-based/)
|
|
||||||
• [Blockstack](https://github.com/blockstack/blockstack-core/blob/feature/docs-bns/docs/blockstack_naming_service.md#decentralized-identifiers-dids)
|
|
||||||
• [British Columbia Ministry of Citizens Services](https://vonx.io/about/)
|
|
||||||
• [botlabs](https://botlabs.org/)
|
|
||||||
• [Civic](https://www.civic.com/solutions/kyc-services/)
|
|
||||||
• [Consent](https://sovrin.org/steward/global-consent/)
|
|
||||||
• [Danube](https://github.com/projectdanube/xdi2)
|
|
||||||
• [datum](https://datum.org/)
|
|
||||||
• [Distributed ID](https://www.diid.io/)
|
|
||||||
• [diwala](https://diwala.io/)
|
|
||||||
• [Dominode](https://dominode.com/)
|
|
||||||
• [Enigma](https://blog.enigma.co/off-chain-identity-claims-with-enigma-2d5b23c31f92)
|
|
||||||
• [Enterprise Ethereum Alliance](https://entethalliance.org/participate/working-groups/)
|
|
||||||
• [Evernym](https://www.evernym.com/wp-content/uploads/2017/07/What-Goes-On-The-Ledger.pdf)
|
|
||||||
• [Equinix](https://www.equinix.com/)
|
|
||||||
• [gamecredits](https://medium.com/@gamecredits/introducing-blinking-blink-identity-management-on-the-blockchain-9258c7d76a8d)[[**ϟ**](https://blinking.id)]
|
|
||||||
• [Gem](https://epicenter.tv/episode/207/)
|
|
||||||
• [GS1](https://www.gs1.org/standards/id-keys)
|
|
||||||
• [Humanized-internet](https://www.thehumanizedinternet.org/)
|
|
||||||
• [Hyperledger](https://github.com/hyperledger/indy-sdk/blob/master/doc/getting-started/getting-started.md)
|
|
||||||
• [ID2020](https://id2020.org/manifesto/)
|
|
||||||
• [Ideo](https://medium.com/ideo-colab/a-framework-for-identity-f7f072829cbb)
|
|
||||||
• [identos](https://identos.com/)
|
|
||||||
• [IBM](https://www.ibm.com/blogs/blockchain/2018/06/self-sovereign-identity-why-blockchain/)
|
|
||||||
• [IOTA](https://medium.com/@iotasuppoter/iota-the-case-of-decentralized-digital-identity-de7b95042c12)
|
|
||||||
• [Jolocom](https://stories.jolocom.com/jolocom-brings-blockchain-identity-to-privacy-week-berlin-acdaee665f0)
|
|
||||||
• [KYC-Chain](https://kyc-chain.com/)
|
|
||||||
• [LNk-E](https://lnketech.com/)
|
|
||||||
• [Mastercard](https://newsroom.mastercard.com/press-releases/mastercard-microsoft-join-forces-to-advance-digital-identity-innovatioeuns/)
|
|
||||||
• [Meeco](https://meeco.me/)
|
|
||||||
• [MetaX](https://adtoken.com/uploads/white-paper.pdf)
|
|
||||||
• [Microsoft](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2DjfY)
|
|
||||||
• [Mooti](https://mooti.co/)
|
|
||||||
• [netki](https://bravenewcoin.com/insights/netki-launches-digital-id-solution-which-bitt-is-using-with-central-banks-in-the-caribbean)
|
|
||||||
• [NuID](https://nuid.io/pdfs/solution-overview.pdf)
|
|
||||||
• [Nuggets](https://www.mobilepaymentstoday.com/news/identity-and-payments-platform-nuggets-partners-with-iot-company/)
|
|
||||||
• [Ockam](https://www.ockam.io/)
|
|
||||||
• [Onfido](https://onfido.com/)
|
|
||||||
• [ONTology](https://ont.io/)
|
|
||||||
• [Pillar](https://pillarprojectfoundation.org/blog/announcing-the-pillar-project/)
|
|
||||||
• [R_Block](https://zinc.work/)
|
|
||||||
• [R3](https://www.gemalto.com/press/pages/gemalto-and-r3-pilot-blockchain-technology-to-put-users-in-control-of-their-digital-id.aspx)
|
|
||||||
• [remme](https://remme.io/features)
|
|
||||||
• [RSA](https://www.rsa.com/en-us/research-and-thought-leadership/rsa-labs)
|
|
||||||
• [SecureKey](https://www.ibm.com/blogs/blockchain/2018/05/self-sovereign-identity-our-recent-activity-as-a-sovrin-steward/)
|
|
||||||
• [\<sitekit>](https://www.sitekit.net/)
|
|
||||||
• [Sovrin](https://github.com/sovrin-foundation/sovrin/blob/master/spec/did-method-spec-template.html)
|
|
||||||
• [suru](https://surugroup.com/philosophy/suru-identity/)
|
|
||||||
• [Taqanu](https://www.taqanu.com/)
|
|
||||||
• [Tierion](https://medium.com/tierion/tierion-network-update-january-19-2018-fa88c6bee69f)
|
|
||||||
• [Trusted key](https://www.trustedkey.com/)
|
|
||||||
• [uPort](https://github.com/uport-project/ethr-did/blob/develop/docs/index.md)
|
|
||||||
• [Validatedid](https://www.validatedid.com/vidchain-the-future-of-digital-identity/)
|
|
||||||
• [Veridium](https://www.veridiumid.com/)
|
|
||||||
• [zinc](https://tykn.tech/project-zinc/)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## /decentralized-identity - GitHub [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/decentralized-identity.github.io" target="_blank">/decentralized-identity/decentralized-identity.github.io</a> - Site for the open source, community-driven group of dev and organizations working toward an interoperable, decentralized identity ecosystem
|
|
||||||
* <a href="https://github.com/decentralized-identity/org" target="_blank">/decentralized-identity/org</a> - DIF docs, wiki, and organizational material
|
|
||||||
* <a href="https://github.com/decentralized-identity/credential-manifest" target="_blank">/decentralized-identity/credential-manifest</a> - Format that normalizes the definition of requirements for the issuance of a credential
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-registrar" target="_blank">/decentralized-identity/universal-registrar</a> - Specifications and implementation of a universal identifier registrar
|
|
||||||
* <a href="https://github.com/decentralized-identity/attestations" target="_blank">decentralized-identity/attestations</a> - Attestation API implementations for various languages and platforms.
|
|
||||||
|
|
||||||
### DIF - DID [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-methods" target="_blank">/decentralized-identity/did-methods</a> - DID Method specs, docs, and materials
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-typescript" target="_blank">/decentralized-identity/did-common-typescript
|
|
||||||
</a> - A common bundle of shared code and modules for working with DIDs, DID Documents, and other DID-related activities
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-csharp" target="_blank">/decentralized-identity/did-security-csharp</a> - C# implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-typescript" target="_blank">/decentralized-identity/did-security-typescript</a> - Typescript implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-java" target="_blank">/decentralized-identity/did-common-java</a> - Shared DID Java library.
|
|
||||||
* <a href="https://github.com/decentralized-identity/ua-web-extension" target="_blank">/decentralized-identity/ua-web-extension</a> - Basic web extension version of a DID User Agent
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-recovery" target="_blank">/decentralized-identity/did-recovery</a> - Various methods for DID recovery
|
|
||||||
* <a href="https://github.com/decentralized-identity/web-polyfills" target="_blank">/decentralized-identity/web-polyfills</a> - Polyfills for proposed or emerging DID-centric Web APIs
|
|
||||||
* <a href="https://github.com/decentralized-identity/" target="_blank">/decentralized-identity/</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/http-did-auth-proxy" target="_blank">/decentralized-identity/http-did-auth-proxy</a> - Forked from bcgov/http-did-auth-proxy
|
|
||||||
DID Auth HTTP proxy.
|
|
||||||
|
|
||||||
### DIF - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-auth-jose" target="_blank">/decentralized-identity/did-auth-jose</a> - JOSE-based implementation of DID Authenticated Encryption
|
|
||||||
|
|
||||||
### DIF - Sidetree [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-ipfs" target="_blank">/decentralized-identity/sidetree-ipfs</a> - IPFS module for storing and accessing Sidetree entity operation data via content addressable storage
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-core" target="_blank">/decentralized-identity/sidetree-core</a> - The blockchain-agnostic server implementation of the Sidetree protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-bitcoin" target="_blank">/decentralized-identity/sidetree-bitcoin</a> - Blockchain-specific code for the Sidetree-based DID Method implementation on Bitcoin
|
|
||||||
* <a href="https://github.com/decentralized-identity/ion" target="_blank">/decentralized-identity/ion</a> - DID Method implementation using the Sidetree protocol on top of Bitcoin
|
|
||||||
|
|
||||||
### DIF - Hub [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js-sample" target="_blank">/decentralized-identity/hub-sdk-js-sample</a> - Sample app demonstrating use of the DIF Identity Hub JavaScript SDK.
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js" target="_blank">/decentralized-identity/hub-sdk-js</a> - JavaScript SDK for interacting with Identity Hubs
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-common-js" target="_blank">/decentralized-identity/hub-common-js</a> - Common interfaces for working with Identity Hubs in JavaScript/TypeScript
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-core" target="_blank">/decentralized-identity/hub-node-core</a> - Node.js implementation of the Identity Hub interfaces, business logic, and replication protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/identity-hub" target="_blank">/decentralized-identity/identity-hub</a> - Storage and compute nodes for decentralized identity data and interactions
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-reference" target="_blank">/decentralized-identity/hub-node-reference</a> - The official Identity Hub reference implementation bundle for Node.js
|
|
||||||
|
|
||||||
### DIF - Uniresolver [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver" target="_blank">/decentralized-identity/universal-resolver</a> - Universal Resolver implementation and drivers.
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-frontend" target="_blank">/decentralized-identity/universal-resolver-frontend</a> - Frontend web UI for Universal Resolver
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-python" target="_blank">/decentralized-identity/universal-resolver-python</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-java" target="_blank">/decentralized-identity/universal-resolver-java</a>
|
|
@ -1,953 +0,0 @@
|
|||||||
---
|
|
||||||
title: SSI-DID Github Repositories
|
|
||||||
description: A start at listing all DID-SSI related GitHub Repositories.
|
|
||||||
image: "https://infominer.id/images/github.jpeg"
|
|
||||||
---
|
|
||||||
|
|
||||||
# SSI-DID Github Repositories
|
|
||||||
|
|
||||||
Please send [a message](../index.html#contact), open an issue or submit a pull-request with any suggestions\recommendations.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Project Danube](#project-danube-)
|
|
||||||
* [XDI](#xdi-)
|
|
||||||
* [XDI Libraries](#xdi-libraries-)
|
|
||||||
* [XDI - Various Integrations](#xdi---various-integrations-)
|
|
||||||
* [XDI Configurations](#xdi-configurations-)
|
|
||||||
* [XDI Examples](#xdi-examples-)
|
|
||||||
* [XDI Plugins](#xdi-plugins-)
|
|
||||||
* [Aeternam](#aeternam-)
|
|
||||||
* [XDI Cloud](#xdi-cloud-)
|
|
||||||
* [XDI Server Deployed Via](#xdi-server-deployed-via-)
|
|
||||||
* [Services](#services-)
|
|
||||||
* [Digital Bazaar](#digital-bazaar-)
|
|
||||||
* [DB - Identity](#db---identity-)
|
|
||||||
* [DB - Credentials](#db---credentials-)
|
|
||||||
* [DB - DID](#db---did-)
|
|
||||||
* [DB - Linked Data](#db---linked-data-)
|
|
||||||
* [/WebOfTrustInfo](#weboftrustinfo)
|
|
||||||
* [RWoT Design Workshop](#rwot-design-workshop-)
|
|
||||||
* [RWoT BTCR](#rwot-btcr-)
|
|
||||||
* [RWoT Txref Conversion](#rwot-txref-conversion-)
|
|
||||||
* [RWoT Linked Data](#rwot-linked-data-)
|
|
||||||
* [/w3c](#w3c---world-wide-web-consortium-)
|
|
||||||
* [Verifiable Claims Working Group](#w3cverifiable-claims----vc-working-group)
|
|
||||||
* [Credentials Community Group](#w3c-ccg---credentials-community-group-)
|
|
||||||
* [CCG - DID](ccg---did-)
|
|
||||||
* [Verifiable Credentials](#ccg---verifiable-credentials-)
|
|
||||||
* [Linked Data](#ccg----linked-data-)
|
|
||||||
* [Digital Verification Community Group](#digital-verification-community-group-)
|
|
||||||
* [OpenCreds](#opencreds-)
|
|
||||||
* [Spidchain](#spidchain-)
|
|
||||||
* [BTCR](#spid-btcr-)
|
|
||||||
* [Ethereum](#spid-ethereum-)
|
|
||||||
* [Hackathon](#spid-hackathon-)
|
|
||||||
* [Ethereum](#ethereum-)
|
|
||||||
* [Assorted Ethereum Apps](#assorted-ethereum-apps)
|
|
||||||
* [uPort](#uport-)
|
|
||||||
* [uPort DID](#uport-did-)
|
|
||||||
* [uPort Identification](#uport-identification-)
|
|
||||||
* [uPort Mobile](#uport-mobile-)
|
|
||||||
* [uPort Lambda](#uport-lambda-)
|
|
||||||
* [uPort React](#uport-react-)
|
|
||||||
* [uPort Assorted](#uport-assorted-)
|
|
||||||
* [Jolocom](#jolocom-)
|
|
||||||
* [Learning Machine](#learning-machine-)
|
|
||||||
* [Blockcerts](#blockcerts-)
|
|
||||||
* [Blockcerts Json](#blockcerts-json-)
|
|
||||||
* [Blockcerts Web](#blockcerts-web-)
|
|
||||||
* [Blockcerts Mobile](#blockcerts-mobile-)
|
|
||||||
* [Sovrin Foundation](#sovrin-foundation-)
|
|
||||||
* [Sovrin - Indy](#sovrin-indy-)
|
|
||||||
* [Decentralized Identity Foundation](#decentralized-identity---dif-)
|
|
||||||
* [DIF - DID](#dif---did-)
|
|
||||||
* [DIF - DID-Auth](#dif---did-auth-)
|
|
||||||
* [DIF - Sidetree](#dif---sidetree-)
|
|
||||||
* [DIF - Hub](#dif---hub-)
|
|
||||||
* [DIF - Uniresolver](#dif---uniresolver-)
|
|
||||||
* [Veres One](#veres-one-)
|
|
||||||
* [/hyperledger Indy](#hyperledger-indy-)
|
|
||||||
* [/IBM-Blockchain-Identity](#ibm-blockchain-identity-)
|
|
||||||
* [Verifiable Organizations Network](#verifiable-organizations-network-)
|
|
||||||
* [BCGov - VON](#bcgov---von-)
|
|
||||||
* [VON - Indy](#von---indy-)
|
|
||||||
* [VON - Agents](#von-agents-)
|
|
||||||
* [BCGov - DID-Auth](#bcgov---did-auth-)
|
|
||||||
* [PSPC-SPAC-buyandsell](#pspc-spac-buyandsell-) - Public Services and Procurement Canada
|
|
||||||
* [Selfkey Foundation](#selfkey-foundation-)
|
|
||||||
* [Selfkey DID](#selfkey-did-)
|
|
||||||
* [Selfkey SmartContracts](#selfkey-smartcontracts-)
|
|
||||||
* [Selfkey Javascript](#selfkey-javascript-)
|
|
||||||
* [Selfkey Assorted](#selfkey-assorted)
|
|
||||||
* [Ockam Network](#ockam-network-)
|
|
||||||
* [Ontology](#ontology-)
|
|
||||||
* [TangleID](#tangleid-)
|
|
||||||
* [Simbol](#simbol-)
|
|
||||||
* [Assorted](#assorted-)
|
|
||||||
* [/peacekeeper/blockchain-identity](#peacekeeperblockchain-identity-)
|
|
||||||
* [/decentralized-id/decentralized-id.github.io](#decentralized-iddecentralized-idgithubio-)
|
|
||||||
* [HOME](https://infominer.id)
|
|
||||||
|
|
||||||
## /project-danube [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/indy-sdk-java" target="_blank">/projectdanube/indy-sdk-java</a> - Java binding to the native Indy SDK
|
|
||||||
* <a href="https://github.com/projectdanube/blockstack-cli-java" target="_blank">/projectdanube/blockstack-cli-java</a> - Java client for Blockstore
|
|
||||||
|
|
||||||
|
|
||||||
### XDI [**^**](#contents)
|
|
||||||
|
|
||||||
>[XDI.org](https://xdi.org) is a non-profit public trust organization whose purpose is to provide public infrastructure for digital identity, security, and privacy using the open standard XDI semantic data interchange protocol developed by the OASIS XDI Technical Committee.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-tutorial" target="_blank">/projectdanube/xdi-tutorial</a> - XDI Tutorial
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-swing" target="_blank">/projectdanube/XDINinja-swing</a> - XDI-enabled standalone client application
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tools" target="_blank">/projectdanube/xdi2-tools</a> - XDI2 maintenance and other tools
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-personal" target="_blank">/projectdanube/xdi2-connector-personal</a> - A connector plugin for the XDI2 server that maps data from Personal.com to XDI
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-docker" target="_blank">/projectdanube/xdi2-docker</a> - Dockerfiles for XDI2
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-buttonbuilder" target="_blank">/projectdanube/xdi2-connect-buttonbuilder</a> - "Button Builder" component for the XDI Connect protocol
|
|
||||||
|
|
||||||
### XDI libraries [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2" target="_blank">/projectdanube/xdi2</a> - XDI2 general purpose library and server
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-js" target="_blank">/projectdanube/xdi-js</a> - XDI client library for JavaScript
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-core" target="_blank">/projectdanube/xdi2-connect-core</a> - Shared library for the XDI Connect protocol
|
|
||||||
|
|
||||||
|
|
||||||
### XDI - Various Integrations [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-bdb" target="_blank">/projectdanube/xdi2-bdb</a> - Support for using BDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-mongodb" target="_blank">/projectdanube/xdi2-mongodb</a> - Support for using MongoDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-heroku" target="_blank">/projectdanube/xdi2-server-heroku</a> - XDI2 Server deployed via Heroku
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-redis" target="_blank">/projectdanube/xdi2-redis</a> - Support for using Redis as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tor" target="_blank">/projectdanube/xdi2-tor</a> - Integration of XDI and Tor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-ipfs" target="_blank">/projectdanube/xdi2-ipfs</a> - Integration of XDI and IPFS
|
|
||||||
* <a href="https://github.com/projectdanube/withsqlite" target="_blank">/projectdanube/withsqlite</a> - A module for a python dict that back ends on an sqlite3 database. It's bit like shelve but with json and sqlite3.
|
|
||||||
- Forked from jvasile/withsqlite
|
|
||||||
|
|
||||||
### XDI Configuration [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-selfhosted" target="_blank">/projectdanube/xdi2-selfhosted</a> - A configuration profile of the XDI2 server for self-hosting a single XDI graph.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-csp" target="_blank">/projectdanube/xdi2-csp</a> - A configuration profile of the XDI2 server for hosting a dynamic number of XDI graphs.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-registry" target="_blank">/projectdanube/xdi2-registry</a> -
|
|
||||||
A configuration profile of the XDI2 server for hosting a registry of XDI names and XDI numbers.
|
|
||||||
|
|
||||||
### XDI Examples [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-messaging" target="_blank">/projectdanube/xdi2-example-messaging</a> - XDI2 Examples: Basic messaging functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-advanced-server" target="_blank">/projectdanube/xdi2-example-advanced-server</a> - XDI2 Examples: Setting up advanced XDI servers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-core" target="_blank">/projectdanube/xdi2-example-core</a> - XDI2 Examples: Simple uses of the core functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-client" target="_blank">/projectdanube/xdi2-example-client</a> - XDI2 Examples: Writing XDI client applications.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-server" target="_blank">/projectdanube/xdi2-example-secp256k1-server</a> - Example XDI server using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-server" target="_blank">/projectdanube/xdi2-example-ec25519-server</a> - Example XDI server using cid-1 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-acmenews" target="_blank">/projectdanube/xdi2-connect-acmenews</a> - +acmenews XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-leshop" target="_blank">/projectdanube/xdi2-connect-leshop</a> - +leshop XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-client" target="_blank">/projectdanube/xdi2-example-secp256k1-client</a> - Example XDI client using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-client" target="_blank">/projectdanube/xdi2-example-ec25519-client</a> - Example XDI client using cid-1 cryptographic XDI numbers.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### XDI Plugins [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-secp256k1" target="_blank">/projectdanube/xdi2-crypto-secp256k1</a> - This is an secp256k1 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-ec25519" target="_blank">/projectdanube/xdi2-crypto-ec25519</a> - This is an Ed25519 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-facebook" target="_blank">/projectdanube/xdi2-connector-facebook</a> - A connector plugin for the XDI2 server that maps data from Facebook to XDI
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-meeco" target="_blank">/projectdanube/xdi2-connector-meeco</a> - A connector plugin for Meeco
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-plugin" target="_blank">/projectdanube/XDINinja-plugin</a> - A browser plugin that is like "Twitter for data"
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-cozy" target="_blank">/projectdanube/xdi2-connector-cozy</a> - A connector plugin for CozyCloud
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-filesys" target="_blank">/projectdanube/xdi2-filesys</a> - Plugin for an XDI2 server to integrate with a local filesystem
|
|
||||||
|
|
||||||
### Aeternam [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-sncf" target="_blank">/projectdanube/aeternam-xdi-sncf</a> - Aeternam PNR Demo: SNCF
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-db" target="_blank">/projectdanube/aeternam-xdi-db</a> - Aeternam PNR Demo: Deutsche Bahn
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-tests" target="_blank">/projectdanube/aeternam-xdi-tests</a> - XDI experimentation for ÆTERNAM / ÆVATAR
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-maria" target="_blank">/projectdanube/aeternam-xdi-maria</a> - Aeternam PNR Demo: Maria
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-webshop" target="_blank">/projectdanube/aeternam-xdi-webshop</a> - Aeternam PNR Demo: Webshop
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-oebb" target="_blank">/projectdanube/aeternam-xdi-oebb</a> - Aeternam PNR Demo: ÖBB
|
|
||||||
|
|
||||||
### XDI Cloud [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-cloudcards" target="_blank">/projectdanube/xdi2-cloudcards</a> - XDI Cloud Card Viewer
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-messenger" target="_blank">/projectdanube/xdi2-messenger</a> - XDI Cloud Messenger
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-manager" target="_blank">/projectdanube/xdi2-manager</a> - XDI Cloud Manager
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-pixel" target="_blank">/projectdanube/xdi2-pixel</a> - Tool to translate a personal cloud policy language (Pixel) to XDI link contracts.
|
|
||||||
|
|
||||||
### XDI Server Deployed Via [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-grizzly" target="_blank">/projectdanube/xdi2-server-grizzly</a> - XDI2 Server deployed via Grizzly
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-mina" target="_blank">/projectdanube/xdi2-server-mina</a> - XDI2 Server deployed via Apache MINA
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-netty" target="_blank">/projectdanube/xdi2-server-netty</a> - XDI2 Server deployed via netty
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-undertow" target="_blank">/projectdanube/xdi2-server-undertow</a> - XDI2 Server deployed via Undertow
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-vertx" target="_blank">/projectdanube/xdi2-server-vertx</a> - XDI2 Server deployed via vert.x
|
|
||||||
|
|
||||||
### Sevices [**^**](#contents)
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service" target="_blank">/projectdanube/xdi2-connect-service</a> - This is a "Connect Service" component for the XDI Browser binding.
|
|
||||||
* <a href="https://github.com/projectdanube/neustar-discovery-service" target="_blank">/projectdanube/neustar-discovery-service</a> - Neustar XDI Discovery Service based on XRI Resolution
|
|
||||||
- Forked from neustarpc/neustar-discovery-service
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service-war" target="_blank">/projectdanube/xdi2-connect-auth-service-war</a> - "Authorization Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service-war" target="_blank">/projectdanube/xdi2-connect-service-war</a> - "Connect Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-grapheditor" target="_blank">/projectdanube/xdi-grapheditor</a> - An XDI Graph Editor
|
|
||||||
-Forked from neustar/xdi-grapheditor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service" target="_blank">/projectdanube/xdi2-connect-auth-service</a> - This is a "Connect Auth Service" component for the XDI Browser binding.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Digital Bazaar [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock" target="_blank">/digitalbazaar/bedrock</a> - Bedrock: A core foundation for rich Web applications.
|
|
||||||
* <a href="https://github.com/digitalbazaar/forge" target="_blank">/digitalbazaar/forge</a> - A native implementation of TLS in Javascript and tools to write crypto-based and network-heavy webapps
|
|
||||||
* <a href="https://github.com/digitalbazaar/veres-delta-docs" target="_blank">/digitalbazaar/veres-delta-docs</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/uuid-random" target="_blank">/digitalbazaar/uuid-random</a>
|
|
||||||
|
|
||||||
|
|
||||||
### DB - Identity [**^**](#contents)
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity-composer" target="_blank">/digitalbazaar/bedrock-angular-identity-composer</a> - An bedrock-based AngularJS directive for composing an Identity from a set of credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-identity-http" target="_blank">/digitalbazaar/bedrock-identity-http</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-idp" target="_blank">/digitalbazaar/opencred-idp</a> - Open Credentials Identity Provider and demo websites
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity" target="_blank">/digitalbazaar/bedrock-angular-identity</a> - Bedrock AngularJS Identity Modules
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-identity" target="_blank">/digitalbazaar/bedrock-identity</a> - Bedrock identity
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-idp" target="_blank">/digitalbazaar/bedrock-idp</a> - Bedrock Identity Provider
|
|
||||||
|
|
||||||
### DB - Credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-data-model" target="_blank">/digitalbazaar/vc-data-model</a> - Verifiable Claims Data Model and Representations specification
|
|
||||||
- Forked from w3c/vc-data-model
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-test-suite" target="_blank">/digitalbazaar/vc-test-suite</a> - Verifiable Claims WG Test Suite
|
|
||||||
- Forked from w3c/vc-test-suite
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-js" target="_blank">/digitalbazaar/vc-js</a> - Verifiable Claims JavaScript library
|
|
||||||
* <a href="https://github.com/digitalbazaar/credentials-io" target="_blank">/digitalbazaar/credentials-io</a> - Library for reading/writing credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-rest" target="_blank">/digitalbazaar/bedrock-credentials-rest</a> - A RESTful API for credential storage
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/bedrock-credential-vocabs</a> - Semantic web vocabularies for processing credentials.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-address-credential-issuer" target="_blank">/digitalbazaar/bedrock-address-credential-issuer</a> - A module for issuing address credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-verifier" target="_blank">/digitalbazaar/opencred-verifier</a> - Open Credentials Verifier JavaScript API
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-idp" target="_blank">/digitalbazaar/opencred-idp</a> - Open Credentials Identity Provider and demo websites
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/bedrock-credential-notifications</a> - Notification issuing for credentials.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-mongodb" target="_blank">/digitalbazaar/bedrock-credentials-mongodb</a> - Credential storage in mongodb
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-context" target="_blank">/digitalbazaar/bedrock-credentials-context</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-card-displayer" target="_blank">/digitalbazaar/bedrock-angular-card-displayer</a> - Bedrock displayer for card-based credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credential-handler" target="_blank">/digitalbazaar/bedrock-credential-handler</a> - Credential Handler for DID-based credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-vc-store" target="_blank">/digitalbazaar/bedrock-web-vc-store</a> - A Javascript library for storing Verifiable Credentials for Bedrock web apps
|
|
||||||
* <a href="https://github.com/digitalbazaar/web-vc-query-creator" target="_blank">/digitalbazaar/web-vc-query-creator</a> - A Javascript library providing a simplified API for creating Verifiable Credentials queries for web apps.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity-composer" target="_blank">/digitalbazaar/bedrock-angular-identity-composer</a> - An bedrock-based AngularJS directive for composing an Identity from a set of credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-profile-composer" target="_blank">/digitalbazaar/bedrock-web-profile-composer</a> - A Javascript library for fulfilling Verifiable Credentials queries for Bedrock web apps
|
|
||||||
|
|
||||||
|
|
||||||
### DB - DID
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-whisper" target="_blank">/digitalbazaar/did-whisper</a> - DID whisper
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-whisper-server" target="_blank">/digitalbazaar/did-whisper-server</a> - A simple DID Whisper server
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-did-store" target="_blank">/digitalbazaar/bedrock-web-did-store</a> - Enables storage and management of DIDs in a Web App
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-authn-did" target="_blank">/digitalbazaar/bedrock-authn-did</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-ssh" target="_blank">/digitalbazaar/did-ssh</a>
|
|
||||||
bedrock-angular-authn-did
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-cli" target="_blank">/digitalbazaar/did-cli</a> - A client for managing Decentralized Identifiers
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-io" target="_blank">/digitalbazaar/did-io</a> - Decentralized identifier management library for browser and node.js
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-authn-did-jwt" target="_blank">/digitalbazaar/bedrock-authn-did-jwt</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-did-client" target="_blank">/digitalbazaar/bedrock-did-client</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-authn-did-jwt" target="_blank">/digitalbazaar/bedrock-angular-authn-did-jwt</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credential-handler" target="_blank">/digitalbazaar/bedrock-credential-handler</a> - Credential Handler for DID-based credentials
|
|
||||||
|
|
||||||
|
|
||||||
### DB - Linked Data
|
|
||||||
|
|
||||||
* <a href="https://github.com/digitalbazaar/php-json-ld" target="_blank">/digitalbazaar/php-json-ld</a> - PHP implementation of a JSON-LD Processor and API
|
|
||||||
* <a href="https://github.com/digitalbazaar/pyld" target="_blank">/digitalbazaar/pyld</a> - JSON-LD processor written in Python
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/jsonld.js</a> - A JSON-LD Processor and API implementation in JavaScript
|
|
||||||
* <a href="https://github.com/digitalbazaar/jsonld-signatures" target="_blank">/digitalbazaar/jsonld-signatures</a> - An implementation of the Linked Data Signatures specification for JSON-LD. Works in the browser and node.js.
|
|
||||||
* <a href="https://github.com/digitalbazaar/json-ld" target="_blank">/digitalbazaar/json-ld</a> - A Context-based JSON Serialization for Linked Data
|
|
||||||
* <a href="https://github.com/digitalbazaar/ocapld.js" target="_blank">/digitalbazaar/ocapld.js</a> - Linked Data Capabilities reference implementation
|
|
||||||
* <a href="https://github.com/digitalbazaar/cuckoo-ldp" target="_blank">/digitalbazaar/cuckoo-ldp</a> - Cuckoo Cycle Based Linked Data Proofs
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-ldn-receiver" target="_blank">/digitalbazaar/bedrock-ldn-receiver</a> - Bedrock module for Linked Data Notification Receiver
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-ldn-inbox" target="_blank">/digitalbazaar/bedrock-ldn-inbox</a> - Bedrock module for Linked Data Notification Inboxes
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-ldn" target="_blank">/digitalbazaar/bedrock-angular-ldn</a> - Bedrock AngularJS module for Linked Data Notification Sender+Consumer
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/json-ld.org</a> - Forked from json-ld/json-ld.org
|
|
||||||
JSON for Linked Data
|
|
||||||
* <a href="https://github.com/digitalbazaar/flex-ledger" target="_blank">/digitalbazaar/flex-ledger</a> - Forked from web-payments/flex-ledger
|
|
||||||
A decentralized Linked Data Ledger for the Web
|
|
||||||
|
|
||||||
## /WebOfTrustInfo
|
|
||||||
|
|
||||||
>The Web of Trust is a buzzword for a new model of decentralized self-sovereign identity. It’s a phrase that dates back almost twenty-five years, the classic definition derives from PGP.
|
|
||||||
|
|
||||||
\#RebootingWebOfTrust holds bi-annual design workshops where many of the ideas in SSI\DID were formed.
|
|
||||||
|
|
||||||
In advance of each workshop, all participants produce a one-or-two page topic paper on either:
|
|
||||||
|
|
||||||
* A specific problem that they wanted to solve with a web-of-trust solution, and why current solutions (PGP or CA-based PKI) can't address the problem?
|
|
||||||
* A specific solution related to the web-of-trust that you'd like others to use or contribute to?
|
|
||||||
|
|
||||||
The workshop itself also produces technical whitepapers, this Repository holds a record of the progression of thought in SSI, since November, 2015.
|
|
||||||
|
|
||||||
* <a href="Rebooting-Web-of-Trust.md">One Page List of RWoT Literature</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/self-sovereign-identity" target="_blank">/WebOfTrustInfo/self-sovereign-identity</a> - Articles and documents associated with designing and implementing identity technology using self-sovereign identity principles
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/website" target="_blank">/WebOfTrustInfo/website</a> - Website for http://www.WebOfTrust.info
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/community-resilience" target="_blank">/WebOfTrustInfo/community-resilience</a> - Rebooting Web of Trust Community Resilience Team
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/satyrn" target="_blank">/WebOfTrustInfo/satyrn</a> - A Markdown-based JavaScript Sandbox
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/sss" target="_blank">/WebOfTrustInfo/sss</a> - Library for the Shamir secret sharing scheme
|
|
||||||
- Forked from dsprenkels/sss
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/verifiable-news" target="_blank">/WebOfTrustInfo/verifiable-news</a> - TBD: W3C Credentials Community Group repository for curbing "social bots" and mitigating the spread of online misinformation and "fake news".
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/portable-reputation-toolkit" target="_blank">/WebOfTrustInfo/portable-reputation-toolkit</a>
|
|
||||||
|
|
||||||
### RWoT Design Workshop [**^**](#contents)
|
|
||||||
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot1-sf" target="_blank">/WebOfTrustInfo/rwot1-sf</a> - RWOT1 in San Francisco, California (November 2015)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot2-id2020" target="_blank">/WebOfTrustInfo/rwot2-id2020</a> - RWOT2 for the ID2020 UN Summit (May 2016)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot3-sf" target="_blank">/WebOfTrustInfo/rwot3-sf</a> - RWOT3 in San Francisco, California (October 2016)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot4-paris" target="_blank">/WebOfTrustInfo/rwot4-paris</a> - RWOT4 in Paris, France (April 2017)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot5-boston" target="_blank">/WebOfTrustInfo/rwot5-boston</a> - RWOT5 in Boston, Massachusetts (October 2017)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot6-santabarbara" target="_blank">/WebOfTrustInfo/rwot6-santabarbara</a> - RWOT6 in Santa Barbara, California (March 2018)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot7-toronto" target="_blank">/WebOfTrustInfo/rwot7-toronto</a> - RWOT7 in Toronto, Canada (September 2018)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot8-barcelona" target="_blank">/WebOfTrustInfo/rwot8-barcelona</a> - RWOT8 in Barcelona, Spain (March 2019)
|
|
||||||
|
|
||||||
### RWot BTCR [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-tx-playground.github.io" target="_blank">/WebOfTrustInfo/btcr-tx-playground.github.io</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-did-tools-js" target="_blank">/WebOfTrustInfo/btcr-did-tools-js</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-hackathon" target="_blank">/WebOfTrustInfo/btcr-hackathon</a> - Virtual hackathon to create spec and code for Bitcoin-based Decentralized Identifiers (DIDs)
|
|
||||||
|
|
||||||
### RWoT Txref Conversion
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-java" target="_blank">/WebOfTrustInfo/txref-conversion-java</a> - Java library for converting txids to txrefs and back
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-js" target="_blank">/WebOfTrustInfo/txref-conversion-js</a> - Javascript library for converting txids to txrefs and back
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-python" target="_blank">/WebOfTrustInfo/txref-conversion-python</a> - Python library to handle conversion between TxRef(bech32) <-> TxID
|
|
||||||
|
|
||||||
### RWoT Linked Data [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/" target="_blank">/WebOfTrustInfo/schemas</a> - Draft schemas for JSON-LD etc.
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/ld-signatures-java" target="_blank">/WebOfTrustInfo/ld-signatures-java</a> - Java implementation of Linked Data Signatures
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/ld-signatures-python" target="_blank">/WebOfTrustInfo/ld-signatures-python</a> - JSON-LD Signatures with JSON Web Signatures
|
|
||||||
|
|
||||||
|
|
||||||
## /w3c - World Wide Web Consortium [**^**](#contents)
|
|
||||||
|
|
||||||
### /w3c/verifiable-claims - VC Working Group
|
|
||||||
|
|
||||||
<a href="https://lists.w3.org/Archives/Public/public-vc-wg/" target="_blank">Verifiable Claims WG - Mailing List</a> (and archives)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c/verifiable-claims" target="_blank">/w3c/verifiable-claims</a> - W3C Verifiable Claims Working Group.
|
|
||||||
* <a href="https://github.com/w3c/vc-data-model" target="_blank">/w3c/vc-data-model</a> -Verifiable Claims Data Model and Representations specification.
|
|
||||||
* <a href="https://github.com/w3c/vc-use-cases" target="_blank">/w3c/vc-use-cases</a> - Verifiable Claims Use Cases.
|
|
||||||
* <a href="https://github.com/w3c/vc-test-suite" target="_blank">/w3c/vc-test-suite</a> - Verifiable Claims WG Test Suite.
|
|
||||||
* <a href="https://github.com/w3c/vc-imp-guide" target="_blank">/w3c/vc-imp-guide</a> - Verifiable Credentials Implementation Guidelines
|
|
||||||
|
|
||||||
### /w3c-ccg - Credentials Community Group [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="http://lists.w3.org/Archives/Public/public-credentials/" target="_blank">Public mailing list for the Credentials Community Group</a> (and archives) - Anyone may read or write to this list.
|
|
||||||
* <a href="https://github.com/w3c-ccg/meetings" target="_blank">/w3c-ccg/meetings</a> CCG Meeting Transcripts
|
|
||||||
* <a href=" https://github.com/w3c-ccg/community" target="_blank">/w3c-ccg/community</a> - CCG Community Repo
|
|
||||||
* <a href="https://github.com/w3c-ccg/announcements" target="_blank">/w3c-ccg/announcements</a> - CCG Announcements
|
|
||||||
* <a href="https://github.com/w3c-ccg/w3c-ccg-process" target="_blank">/w3c-ccg/w3c-ccg-process</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/registries-process" target="_blank">/w3c-ccg/registries-process</a>
|
|
||||||
|
|
||||||
#### CCG - DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-primer" target="_blank">/w3c-ccg/did-primer</a> - A Primer for Decentralized Identifiers
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-spec" target="_blank">/w3c-ccg/did-spec</a> - Decentralized Identifier (DID) 1.0 Specification - Data Model and Syntax
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-resolution" target="_blank">/w3c-ccg/did-resolution</a> Spec 1.0
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-use-cases" target="_blank">/w3c-ccg/did-use-cases</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-method-registry" target="_blank">/w3c-ccg/did-method-registry</a> - a list of all known DID Methods and their current level of maturity.
|
|
||||||
* <a href="https://github.com/w3c-ccg/didm-btcr" target="_blank">/w3c-ccg/didm-btcr</a> - WORK ITEM: BTCR DID Method Spec
|
|
||||||
* <a href="https://github.com/w3c-ccg/didm-veres-one" target="_blank">/w3c-ccg/didm-veres-one</a> - Veres One Decentralized Identifier Method Specification
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-wg-proposal" target="_blank">/w3c-ccg/did-wg-proposal</a> - Proposal to W3C membership for a DID Working Group.
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-wg-charter" target="_blank">/w3c-ccg/did-wg-charter</a> - EXPERIMENTAL charter for the W3C Decentralized Identifier Working Group
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-hackathon-2018" target="_blank">/w3c-ccg/did-hackathon-2018</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/data-minimization" target="_blank">/w3c-ccg/data-minimization</a> - Data Minimization, Selective Disclosure, and Progressive Trust
|
|
||||||
* <a href="https://github.com/w3c-ccg/credential-handler-api" target="_blank">/w3c-ccg/credential-handler-api</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/amira" target="_blank">/w3c-ccg/amira</a> - Amira Engagement Model.
|
|
||||||
* <a href="https://github.com/w3c-ccg/functional-identity" target="_blank">/w3c-ccg/functional-identity</a>
|
|
||||||
|
|
||||||
#### CCG - Verifiable Credentials [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c-ccg/vc-status-registry" target="_blank"></a> - REGISTRY: The Verifiable Credentials Status Scheme Registry.
|
|
||||||
* <a href="https://github.com/w3c-ccg/edu_occ_verifiable_credentials" target="_blank">/w3c-ccg/edu_occ_verifiable_credentials</a> - WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials.
|
|
||||||
* <a href="https://github.com/w3c-ccg/vc-examples" target="_blank">/w3c-ccg/vc-examples</a> - WORK ITEM: Verifiable Credentials Examples
|
|
||||||
|
|
||||||
#### CCG - Linked Data [**^**](#contents)
|
|
||||||
* <a href="https://github.com/w3c-ccg/ocap-ld" target="_blank">/w3c-ccg/ocap-ld</a> - WORK ITEM: Linked Data Object Capabilities specification
|
|
||||||
* <a href="https://github.com/w3c-ccg/ld-cryptosuite-registry" target="_blank">/w3c-ccg/ld-cryptosuite-registry</a> - REGISTRY: Linked Data Keys Registry
|
|
||||||
|
|
||||||
### Digital Verification Community Group [**^**](#contents)
|
|
||||||
> The mission of the W3C Digital Verification Community Group is to study, design, promote, and deploy systems that increase trust on the Web.
|
|
||||||
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/w3c-dvcg.github.io" target="_blank">/w3c-dvcg/w3c-dvcg.github.io</a> - Landing site for W3C Digital Verification Community Group.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/multibase" target="_blank">/w3c-dvcg/multibase</a> -
|
|
||||||
An IETF Internet Draft for the Multibase data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/hashlink" target="_blank">/w3c-dvcg/hashlink</a> - An IETF Internet Draft for the Hashlink data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/multihash" target="_blank">/w3c-dvcg/multihash</a> - An IETF Internet Draft for the Multihash data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/security-vocab" target="_blank">/w3c-dvcg/security-vocab</a> - The Linked Data Security Vocabulary
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-rsa2018" target="_blank">/w3c-dvcg/lds-rsa2018</a> -
|
|
||||||
Linked Data Signature Suite created in 2018
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/http-signatures" target="_blank">/w3c-dvcg/http-signatures</a> - Signing HTTP Messages specification
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/ld-proofs" target="_blank">/w3c-dvcg/ld-proofs</a> -
|
|
||||||
Linked Data Proofs Specification
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/ld-signatures" target="_blank">/w3c-dvcg/ld-signatures</a> - Linked Data Signatures enable digital signatures on Linked Data
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-ed25519-2018" target="_blank">/w3c-dvcg/lds-ed25519-2018</a> - Linked Data Signature Suite for Ed25519 2018
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-merkleproof2017" target="_blank">/w3c-dvcg/lds-merkleproof2017</a> - 2017 Signature suite for doing Merkle Proofs.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-redaction2016" target="_blank">/w3c-dvcg/lds-redaction2016</a> - Linked Data Signature Suite created in 2016 for performing Redacted
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/http-signatures-audit" target="_blank">/w3c-dvcg/http-signatures-audit</a> - Security considerations for HTTP Signatures specification.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-koblitz2016" target="_blank">/w3c-dvcg/lds-koblitz2016</a> - Linked Data Signature Suite for the Koblitz Elliptic Curve 2016
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-pseudonymous2016/" target="_blank">/w3c-dvcg/lds-pseudonymous2016/</a>
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-rsa2016/" target="_blank">/w3c-dvcg/lds-rsa2016/</a>
|
|
||||||
|
|
||||||
### /opencreds [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/opencreds/website" target="_blank">/opencreds/website</a> - The Open Credentials Website
|
|
||||||
* <a href="https://github.com/opencreds/minutes" target="_blank">/opencreds/minutes</a> -
|
|
||||||
Text and audio meeting minutes for W3C Credentials Community Group
|
|
||||||
|
|
||||||
## Spidchain [**^**](#contents)
|
|
||||||
|
|
||||||
* [Spidchain.com](http://www.spidchain.com/) -Blockchain for Self Sovereign Identity
|
|
||||||
|
|
||||||
### Spid Bitcoin [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/spidchain-btcr" target="_blank">/SpidChain/spidchain-btcr</a> - An implementation of the btcr standard for self sovereign distributed digital identity
|
|
||||||
* <a href="https://github.com/SpidChain/electrumx" target="_blank">/SpidChain/electrumx</a> Forked from kyuupichan/electrumx
|
|
||||||
- Alternative implementation of spesmilo/electrum-server
|
|
||||||
* <a href="https://github.com/SpidChain/btcr-spv" target="_blank">/SpidChain/btcr-spv</a> - Poc of an SPV implementation of BTCR
|
|
||||||
* <a href="https://github.com/SpidChain/satoshis-wheel-of-fortune" target="_blank">/SpidChain/satoshis-wheel-of-fortune</a> - Pick a name from a list randomly in a provably honest way
|
|
||||||
* <a href="https://github.com/SpidChain/txref-conversion-js" target="_blank">/SpidChain/txref-conversion-js</a> - Forked from WebOfTrustInfo/txref-conversion-js
|
|
||||||
- Javascript library for converting txids to txrefs and back
|
|
||||||
|
|
||||||
|
|
||||||
### Spid Ethereum [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/eth-lightwallet" target="_blank">/SpidChain/eth-lightwallet</a> - Forked from ConsenSys/eth-lightwallet
|
|
||||||
- Lightweight JS Wallet for Node and the browser
|
|
||||||
* <a href="https://github.com/SpidChain/truffle" target="_blank">/SpidChain/truffle</a> - Forked from trufflesuite/truffle
|
|
||||||
- A development framework for Ethereum
|
|
||||||
* <a href="https://github.com/SpidChain/VotingSystem" target="_blank">/SpidChain/VotingSystem</a> - A dapp, library and smart contract to notarize votes on the ethereum blockchain
|
|
||||||
* <a href="https://github.com/SpidChain/ethers-wallet" target="_blank">/SpidChain/ethers-wallet</a> - Forked from ethers-io/ethers.js
|
|
||||||
- Complete Ethereum wallet implementation and library in JavaScript.
|
|
||||||
* <a href="https://github.com/SpidChain/nodejs-ethereum" target="_blank">/SpidChain/nodejs-ethereum</a> - Forked from b9lab/nodejs-ethereum
|
|
||||||
Example of using NodeJs with Ethereum
|
|
||||||
|
|
||||||
### Spid Hackathon [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/chainpass" target="_blank">/SpidChain/chainpass</a> - App for Trenitalia hackathon - 09 / 16 / 2017 - Rome
|
|
||||||
* <a href="https://github.com/SpidChain/vipPrice" target="_blank">/SpidChain/vipPrice</a> - #internationalhackathon #spidchain
|
|
||||||
|
|
||||||
### Democracy Earth [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/democracyearth/self" target="_blank">/democracyearth/self</a> - Cryptgraphic peer authentication.
|
|
||||||
>We keep the identity 100% in the hands of the user. We took the decentralization approach to create a login protocol and Cryptography (SHA-256 hash function) to ensure security and identity. We allow users to show the information that they want, when they want and to they want.
|
|
||||||
* <a href="https://github.com/democracyearth/sovereign" target="_blank">/democracyearth/sovereign</a> - earth_americas Blockchain democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/paper" target="_blank">/democracyearth/paper</a> - On decentralized digital democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/community." target="_blank">/democracyearth/community.</a> - earth_americas Be an Ambassador or Student Ambassador anywhere in the world.
|
|
||||||
* <a href="https://github.com/democracyearth/vote" target="_blank">/democracyearth/vote</a> - Smart contracts for vote token.
|
|
||||||
* <a href="https://github.com/democracyearth/dapp" target="_blank">/democracyearth/dapp</a> - Liquid democracy smart contract implementation
|
|
||||||
* <a href="https://github.com/democracyearth/blockchain" target="_blank">/democracyearth/blockchain</a> - A block chain for democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/handbook" target="_blank">/democracyearth/handbook</a> - Forked from loomio/loomio-coop-handbook
|
|
||||||
- Handbook for Democracy Earth Foundation
|
|
||||||
* <a href="https://github.com/democracyearth/press-kit" target="_blank">/democracyearth/press-kit</a> - A set of resources about the Democracy Earth Foundation to share with journalists and media.
|
|
||||||
* <a href="https://github.com/democracyearth/exodus" target="_blank">/democracyearth/exodus</a> - Smart contracts enabling a Universal Basic Income for self-sovereign citizens earth_americas
|
|
||||||
* <a href="https://github.com/democracyearth/party" target="_blank">/democracyearth/party</a> - horse Trojan political party.
|
|
||||||
* <a href="https://github.com/democracyearth/balance-keeper" target="_blank">/democracyearth/balance-keeper</a> - token balance keeper daemon.
|
|
||||||
* <a href="https://github.com/democracyearth/dapp" target="_blank">/democracyearth/dapp</a> - Liquid democracy smart contract implementation
|
|
||||||
* <a href="https://github.com/democracyearth/DesignSystem" target="_blank">/democracyearth/DesignSystem</a>
|
|
||||||
* <a href="https://github.com/democracyearth/vzla-propone-cambio" target="_blank">/democracyearth/vzla-propone-cambio</a> - venezuelaVenezuela sera libre
|
|
||||||
* <a href="https://github.com/democracyearth/advocacy" target="_blank">/democracyearth/advocacy</a> - Toolkit with static and live documents that will concentrate relevant information aimed at advocacy efforts for liquid democracy around the world.
|
|
||||||
* <a href="https://github.com/democracyearth/protocol" target="_blank">/democracyearth/protocol</a> - Forked from arikan/bitcoin-voting
|
|
||||||
- bulb Cryptocurrency voting schema.
|
|
||||||
* <a href="https://github.com/democracyearth/dips" target="_blank">/democracyearth/dips</a> - Democracy Improvement Proposals
|
|
||||||
* <a href="https://github.com/democracyearth/micropayment-voting" target="_blank">/democracyearth/micropayment-voting</a> - eagle Vote as bitcoin micropayment.
|
|
||||||
* <a href="https://github.com/democracyearth/concept" target="_blank">/democracyearth/concept</a> - Forked from makingdevs/mecate-democra
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Ethereum [**^**](#contents)
|
|
||||||
* [ERC: Lightweight Identity #1056](https://github.com/ethereum/EIPs/issues/1056) —This ERC describes a standard for creating and updating identities with a limited use of blockchain resources. An identity can have an unlimited number of delegates and attributes associated with it. Identity creation is as simple as creating a regular key pair ethereum account, which means that it's fee (no gas costs) and all ethereum accounts are valid identities. Furthermore this ERC is fully DID compliant.
|
|
||||||
* [ERC-1484: Digital Identity Aggregator #1495](https://github.com/ethereum/EIPs/issues/1495) —A protocol for aggregating digital identity information that's broadly interoperable with existing, proposed, and hypothetical future digital identity standards.
|
|
||||||
* [ERC725](https://github.com/ethereum/EIPs/issues/725)
|
|
||||||
* The following describes standard functions for a unique identifiable proxy account to be used by humans, groups, organisations, objects and machines
|
|
||||||
* [ERC735](https://github.com/ethereum/EIPs/issues/735) - The following describes standard functions for adding, removing and holding of claims.
|
|
||||||
- These claims can attested from third parties (issuers) or self attested.
|
|
||||||
* [EIP712](https://github.com/ethereum/EIPs/blob/f29527ab39357548b06b29e937a48f06ae099de7/EIPS/eip-712.md) - This is a standard for hashing and signing of typed structured data
|
|
||||||
* [ERC: Ethereum Claims Registry #780](https://github.com/ethereum/EIPs/issues/780)
|
|
||||||
* [EIP-1078](https://github.com/ethereum/EIPs/blob/ed621645c8f3bc5756492f327cda015f35d9f8da/EIPS/eip-1078.md) -
|
|
||||||
This presents a method to replace the usual signup/login design pattern with a minimal ethereum native scheme, that doesn’t require passwords, backing up private keys nor typing seed phrases.
|
|
||||||
|
|
||||||
### Cryptonomica [**^**](#cryptonomica-)
|
|
||||||
|
|
||||||
[![](http://i.imgur.com/moVyrrt.png)](https://cryptonomica.github.io)
|
|
||||||
|
|
||||||
* <a href="https://github.com/Cryptonomica/cryptonomica" target="_blank">/Cryptonomica/cryptonomica</a> - Cryptonomica keys server
|
|
||||||
* <a href="https://github.com/Cryptonomica/cryptonomica.github.io" target="_blank">/Cryptonomica/cryptonomica.github.io</a> - Cryptonomica frontend
|
|
||||||
* <a href="https://github.com/Cryptonomica/arbitration-rules" target="_blank">/Cryptonomica/arbitration-rules</a> - Cryptonomica Arbitration Rules
|
|
||||||
* <a href="https://github.com/Cryptonomica/dappathon-tlv" target="_blank">/Cryptonomica/dappathon-tlv</a>
|
|
||||||
* <a href="https://github.com/Cryptonomica/Ethereum-IdentityVerification" target="_blank">/Cryptonomica/Ethereum-IdentityVerification</a> - Indentity verification and KYC for Ethereum blockchain
|
|
||||||
* <a href="https://github.com/Cryptonomica/ethnode.cryptonomica.net" target="_blank">/Cryptonomica/ethnode.cryptonomica.net</a> - Ethereum node with API on nodejs and web3.js
|
|
||||||
* <a href="https://github.com/Cryptonomica/Ethereum-IdentityProof" target="_blank">/Cryptonomica/Ethereum-IdentityProof</a> - Smart contract for Ethereum's account owner verification using Cryptonomica.net
|
|
||||||
* <a href="https://github.com/Cryptonomica/international-arbitration-law" target="_blank">/Cryptonomica/international-arbitration-law</a> - Repository for collecting information about international arbitration law and practice
|
|
||||||
|
|
||||||
|
|
||||||
### Assorted Ethereum Apps [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/XLNT/meirl" target="_blank">/XLNT/meirl</a> - Counterfactual and Upgradable Self-Sovereign Identity for Ethereum, using Gnosis Safe
|
|
||||||
|
|
||||||
## uPort [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/developers" target="_blank">/uport-project/developers</a> - Developer portal for documentation and application management
|
|
||||||
* <a href="https://github.com/uport-project/specs" target="_blank">/uport-project/specs</a> - uPort Protocol Specs
|
|
||||||
* <a href="https://github.com/uport-project/uport-connect" target="_blank">/uport-project/uport-connect</a> - Main uPort library for front end developers
|
|
||||||
* <a href="https://github.com/uport-project/eth-typed-data" target="_blank">/uport-project/eth-typed-data</a> - A javascript library for working with typed structured data as defined by EIP712
|
|
||||||
* <a href="https://github.com/uport-project/uport-transports" target="_blank">/uport-project/uport-transports</a> - Set up communication channels between your app and a uPort client to handle requests and responses.
|
|
||||||
* <a href="https://github.com/uport-project/webcard" target="_blank">/uport-project/webcard</a> - Transaction Sharing
|
|
||||||
* <a href="https://github.com/uport-project/demo" target="_blank">/uport-project/demo</a> - uPort Demo dApp
|
|
||||||
* <a href="https://github.com/uport-project/uport-lite" target="_blank">/uport-project/uport-lite</a> - Lightweight uport registry lookup
|
|
||||||
* <a href="https://github.com/uport-project/eslint-config-uport" target="_blank">/uport-project/eslint-config-uport</a> - Shareable eslint config for uport libraries
|
|
||||||
* <a href="https://github.com/uport-project/uPort-live" target="_blank">/uport-project/uPort-live</a> - Forked from Siunami/uPort-live
|
|
||||||
* <a href="https://github.com/uport-project/uport-wordpress-plugin" target="_blank">/uport-project/uport-wordpress-plugin</a> - A Passwordless Login for uPort and Wordpress
|
|
||||||
* <a href="https://github.com/uport-project/community-projects" target="_blank">/uport-project/community-projects</a> - A list of community hackathon projects and other experiments.
|
|
||||||
* <a href="https://github.com/uport-project/udoor" target="_blank">/uport-project/udoor</a> - uPort Door Management
|
|
||||||
* <a href="https://github.com/uport-project/uport-bounties" target="_blank">/uport-project/uport-bounties</a>- A Library of uPort Bounties
|
|
||||||
* <a href="https://github.com/dconroy/CityKey" target="_blank">/dconroy/CityKey</a> - Adding uPort support to Chicago CityKey, adding all the benefits of Self Sovereign Identity to municipal services. http://citykeychained.com
|
|
||||||
|
|
||||||
### uPort DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-resolver" target="_blank">/uport-project/ethr-did-resolver</a> - DID resolver for Ethereum Addresses with support for key management
|
|
||||||
* <a href="https://github.com/uport-project/secp256k1-did-resolver" target="_blank">/uport-project/secp256k1-did-resolver</a> - Resolve DID documents for secp256k1 public keys
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-driver" target="_blank">/uport-project/uport-did-driver</a> - Driver for the uPort DID method
|
|
||||||
* <a href="https://github.com/uport-project/eth-did-resolver" target="_blank">/uport-project/eth-did-resolver</a> - DID resolver for Ethereum Addresses
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did" target="_blank">/uport-project/ethr-did</a> - Create ethr DIDs
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-registry" target="_blank">/uport-project/ethr-did-registry</a> - Backing for an experimental DID method
|
|
||||||
* <a href="https://github.com/uport-project/did-resolver" target="_blank">/uport-project/did-resolver</a> - Generic did-resolver
|
|
||||||
* <a href="https://github.com/uport-project/https-did-resolver" target="_blank">/uport-project/https-did-resolver</a> - DID resolver for HTTPS domains
|
|
||||||
* <a href="https://github.com/uport-project/nacl-did" target="_blank">/uport-project/nacl-did</a> - Light weight DID method, complete with Identity Creation tools, encryption and JWT signing
|
|
||||||
* <a href="https://github.com/uport-project/did-jwt" target="_blank">/uport-project/did-jwt</a> - Create and verify uPort and DID compliant JWT's in Javascript
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-resolver" target="_blank">/uport-project/uport-did-resolver</a> - DID resolver for uPort identities
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Identification [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/openid" target="_blank">/uport-project/openid</a> - uPort openid
|
|
||||||
* <a href="https://github.com/uport-project/kmnid" target="_blank">/uport-project/kmnid</a> - A kotlin implementation of MNID
|
|
||||||
* <a href="https://github.com/uport-project/uport-registry" target="_blank">/uport-project/uport-registry</a> - Core uPort registry contract for linking attributes to uPort identities.
|
|
||||||
* <a href="https://github.com/uport-project/uport-chrome-extension" target="_blank">/uport-project/uport-chrome-extension</a> - An experiment to test decentralized identity in a Browser Extension environment.
|
|
||||||
* <a href="https://github.com/uport-project/infrastructure" target="_blank">/uport-project/infrastructure</a> - Support services for Self-Sovereign Identity
|
|
||||||
* <a href="https://github.com/uport-project/mnid" target="_blank">/uport-project/mnid</a> - Multi Network Identifier - spec and reference implementation
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Mobile [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-sdk" target="_blank">/uport-project/uport-android-sdk</a> - Collections of tools and helper libraries for android to issue and use identities on the uPort platform
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-signer" target="_blank">/uport-project/uport-android-signer</a> - android ETH signer library to be used by uport app and sdk
|
|
||||||
* <a href="https://github.com/uport-project/uport-android" target="_blank">/uport-project/uport-android</a> - uPort app for android - under construction
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-demo" target="_blank">/uport-project/uport-ios-demo</a> - Demo iPhone app using uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile-issues" target="_blank">/uport-project/uport-mobile-issues</a> - This repository is a place for developers to report and track status of issues reported while using the uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile" target="_blank">/uport-project/uport-mobile</a> - uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-sdk" target="_blank">/uport-project/uport-ios-sdk</a> - uPort iOS SDK in Swift
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-core-eth" target="_blank">/uport-project/uport-ios-core-eth</a> - iOS Ethereum Toolkit for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-openssl" target="_blank">/uport-project/uport-ios-openssl</a> - iOS OpenSSL Framework for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner" target="_blank">/uport-project/UPTEthereumSigner</a> - Ethereum signer library for iOS
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Lambda [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/lambda-chasqui" target="_blank">/uport-project/lambda-chasqui</a> - running_man Messenger service running_man
|
|
||||||
* <a href="https://github.com/uport-project/lambda-agora" target="_blank">/uport-project/lambda-agora</a> - An open public space where an assembly of applications can share details and be discovered (pre-alpha)
|
|
||||||
* <a href="https://github.com/uport-project/lambda-champagne" target="_blank">/uport-project/lambda-champagne</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-niscani" target="_blank">/uport-project/lambda-niscani</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-sensui" target="_blank">/uport-project/lambda-sensui</a> - uPort tx funding service
|
|
||||||
* <a href="https://github.com/uport-project/" target="_blank">/uport-project/lambda-caleuche</a> - Caleuche. Event Hub Service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-idgraph" target="_blank">/uport-project/lambda-idgraph</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-olorun" target="_blank">/uport-project/lambda-olorun</a> - uPort private network support
|
|
||||||
* <a href="https://github.com/uport-project/lambda-fatima" target="_blank">/uport-project/lambda-fatima</a> - uPort badge event attestor
|
|
||||||
* <a href="https://github.com/uport-project/lambda-pututu" target="_blank">/uport-project/lambda-pututu</a> - Push notification service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-nisaba" target="_blank">/uport-project/lambda-nisaba</a> - Lambda functions for anti-sybill
|
|
||||||
* <a href="https://github.com/uport-project/lambda-unnu" target="_blank">/uport-project/lambda-unnu</a> - Creator of Identities
|
|
||||||
|
|
||||||
### uPort React [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-signer" target="_blank">/uport-project/react-native-uport-signer</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-signer-demo" target="_blank">/uport-project/react-native-signer-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/uport-react-native-demo" target="_blank">/uport-project/uport-react-native-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-connect" target="_blank">/uport-project/react-native-uport-connect</a> - Library for integrating uPort into your React Native app
|
|
||||||
* <a href="https://github.com/uport-project/react-uport-box" target="_blank">/uport-project/react-uport-box</a> - Truffle and React/Redux boilerplate with uPort Connect
|
|
||||||
* <a href="https://github.com/uport-project/react-native-passcode-android" target="_blank">/uport-project/react-native-passcode-android</a> - Forked from aldigjo/react-native-passcode-android
|
|
||||||
|
|
||||||
### uPort Assorted [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/champagne-dapp" target="_blank">/uport-project/champagne-dapp</a> - Champagne Project dApp
|
|
||||||
* <a href="https://github.com/uport-project/tweetnacl-k" target="_blank">/uport-project/tweetnacl-k</a> - kotlin implementation of tweetnacl
|
|
||||||
* <a href="https://github.com/uport-project/sample-data-generator" target="_blank">/uport-project/sample-data-generator</a>
|
|
||||||
* <a href="https://github.com/uport-project/bck-wallet" target="_blank">/uport-project/bck-wallet</a>
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner-Example" target="_blank">/uport-project/UPTEthereumSigner-Example</a> - Example app and unit tests for the UPTEthereumSigner repo
|
|
||||||
* <a href="https://github.com/uport-project/lastblock" target="_blank">/uport-project/lastblock</a> - Daemon that alerts when a new block is mined
|
|
||||||
* <a href="https://github.com/uport-project/service-tests" target="_blank">/uport-project/service-tests</a> - Test servers from the outside
|
|
||||||
* <a href="https://github.com/uport-project/paper" target="_blank">/uport-project/paper</a>
|
|
||||||
* <a href="https://github.com/uport-project/swift-rlp" target="_blank">/uport-project/swift-rlp</a> - Recursive Length Prefix in Swift - CocoaPod
|
|
||||||
* <a href="https://github.com/uport-project/SwiftKeccak" target="_blank">/uport-project/SwiftKeccak</a> - Ethereum compatible Keccak hash for Swift
|
|
||||||
* <a href="https://github.com/uport-project/ed2curve-js" target="_blank">/uport-project/ed2curve-js</a> - Convert Ed25519 signing keys into Curve25519 Diffie-Hellman keys
|
|
||||||
|
|
||||||
|
|
||||||
## Jolocom [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/jolocom/docs" target="_blank">/jolocom/docs</a> - Documentation
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-app" target="_blank">/jolocom/smartwallet-app</a> - A decentralized self sovereign identity solution developed by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-lib" target="_blank">/jolocom/jolocom-lib</a> - Library for interacting with the identity solution provided by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-did-driver" target="_blank">/jolocom/jolocom-did-driver</a> - Universal Resolver DID Driver for the did:jolo identity space
|
|
||||||
* <a href="https://github.com/jolocom/generic-backend" target="_blank">/jolocom/generic-backend</a> - A generic backend implementation that makes use of the Jolocom Library for authentication, and for issuing credentials.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso" target="_blank">/jolocom/demo-sso</a> - A simple example web application integrating the Jolocom library for authentication.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso-mobile" target="_blank">/jolocom/demo-sso-mobile</a> - An example mobile application in React Native that showcases the interaction flows between the Smartwallet and another mobile app.
|
|
||||||
* <a href="https://github.com/jolocom/cred-types-jolocom-demo" target="_blank">/jolocom/cred-types-jolocom-demo</a> - Collection of metadata definitions for the demo Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/react-native-build-config" target="_blank">/jolocom/react-native-build-config</a> - Expose native build config to JS (android only for now)
|
|
||||||
* <a href="https://github.com/jolocom/credTypes-jolocom-core" target="_blank">/jolocom/credTypes-jolocom-core</a> - Collection of metadata definitions for the core Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/fueling-service" target="_blank">/jolocom/fueling-service</a> - Simple express service that can wire ether to requester.
|
|
||||||
* <a href="https://github.com/jolocom/registry-contract" target="_blank">/jolocom/registry-contract</a> - A basic smart contract on top of the Ethereum network that registers mappings between DID and IPFS DDO hashes.
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-webid-proxy" target="_blank">/jolocom/smartwallet-webid-proxy</a> - WebID proxy service
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Learning Machine [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/learningmachine/stage.blockcerts.github.io" target="_blank">/learningmachine/stage.blockcerts.github.io</a> - Web site
|
|
||||||
- Forked from blockchain-certificates/blockchain-certificates.github.io
|
|
||||||
* <a href="https://github.com/learningmachine/polymer-redux" target="_blank">/learningmachine/polymer-redux</a> - An example use-case to showcase the state/view abstraction in Polymer 3, LitElement and Redux context
|
|
||||||
* <a href="https://github.com/learningmachine/ajv" target="_blank">/learningmachine/ajv</a> -The fastest JSON-Schema Validator. Supports draft-06
|
|
||||||
- Forked from epoberezkin/ajv
|
|
||||||
* <a href="https://github.com/learningmachine/Foundatio" target="_blank">/learningmachine/Foundatio</a> - Pluggable foundation blocks for building distributed apps.
|
|
||||||
- Forked from FoundatioFx/Foundatio
|
|
||||||
|
|
||||||
### Blockcerts [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockcerts-verifier" target="_blank">/blockchain-certificates/blockcerts-verifier</a> - A Blockcerts verifier and viewer
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-issuer" target="_blank">/blockchain-certificates/cert-issuer</a> - Issues Blockcerts using either the Bitcoin or Ethereum blockchain
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-verifier" target="_blank">/blockchain-certificates/cert-verifier</a> - Python library for verifying Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-schema" target="_blank">/blockchain-certificates/cert-schema</a> - The schema for Blockcerts
|
|
||||||
- Forked from IMSGlobal/cert-schema
|
|
||||||
* <a href="https://github.com/blockchain-certificates/assets" target="_blank">/blockchain-certificates/assets</a>
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-verifier-js" target="_blank">/blockchain-certificates/cert-verifier-js</a> - Javascript library for verifying Blockcerts Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-tools" target="_blank">/blockchain-certificates/cert-tools</a> -Command line tools for designing certificate templates and instantiating a certificate batch
|
|
||||||
* <a href="https://github.com/blockchain-certificates/obi-baking" target="_blank">/blockchain-certificates/obi-baking</a> - Example of baking a blockcert into an Open Badge
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-core" target="_blank">/blockchain-certificates/cert-core</a>
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-test-resources" target="_blank">/blockchain-certificates/wallet-test-resources</a> - These are resources used to test implementations of the evolving blockcerts certificate standard and issuer conventions.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/pyld" target="_blank">/blockchain-certificates/pyld</a> - JSON-LD processor written in Python
|
|
||||||
- Forked from digitalbazaar/pyld
|
|
||||||
* <a href="https://github.com/blockchain-certificates/archived-cert-store" target="_blank">/blockchain-certificates/archived-cert-store</a> - Storage library and service for Blockchain Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/openbadges-validator-core" target="_blank">/blockchain-certificates/openbadges-validator-core</a> - Open Badges validation in python
|
|
||||||
- Forked from IMSGlobal/openbadges-validator-core
|
|
||||||
* <a href="https://github.com/blockchain-certificates/PodSpecs" target="_blank">/blockchain-certificates/PodSpecs</a> - A listing of CocoaPod .podspec files for all pods created in the Blockchain Certificates project.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/openbadges-bakery" target="_blank">/blockchain-certificates/openbadges-bakery</a> - An OpenBadges image baking library that works with PNGs and SVGs
|
|
||||||
- Forked from mozilla/openbadges-bakery
|
|
||||||
|
|
||||||
#### Blockcerts Json [**^**](#contents)
|
|
||||||
* <a href="https://github.com/blockchain-certificates/JSONLD" target="_blank">/blockchain-certificates/JSONLD</a> - An iOS framework for processing JSON-LD files.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/JSONLDProcessor" target="_blank">/blockchain-certificates/JSONLDProcessor</a> - An iOS framework for processing JSON-LD files.
|
|
||||||
|
|
||||||
|
|
||||||
#### Blockcerts Web [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-viewer" target="_blank">/blockchain-certificates/cert-viewer</a> - A web app for viewing and validating Blockchain Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockcerts-playground.github.io" target="_blank">/blockchain-certificates/blockcerts-playground.github.io</a> - In-browser tool to experiment with Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockchain-certificates.github.io" target="_blank">/blockchain-certificates/blockchain-certificates.github.io</a>
|
|
||||||
- Forked from mmistakes/minimal-mistakes
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-web-component" target="_blank">/blockchain-certificates/cert-web-component</a> - A web component for displaying blockchain certificates.
|
|
||||||
|
|
||||||
#### Blockcerts Mobile [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-android" target="_blank">/blockchain-certificates/wallet-android</a> - An Android app for Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/BlockcertsFramework-iOS" target="_blank">/blockchain-certificates/BlockcertsFramework-iOS</a> - An iOS wallet for viewing, validating, and sharing certs
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-iOS" target="_blank">/blockchain-certificates/wallet-iOS</a> - An iOS wallet for Blockcerts
|
|
||||||
|
|
||||||
|
|
||||||
## Sovrin Foundation [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin.org" target="_blank">/sovrin-foundation/sovrin.org</a> - the foundation web site
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin" target="_blank">/sovrin-foundation/sovrin</a>
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-sip" target="_blank">/sovrin-foundation/sovrin-sip</a> - controlled techical docs/standards for Sovrin Foundation
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sov-docs-conf" target="_blank">/sovrin-foundation/sov-docs-conf</a> - A repository containing the code that builds the Sovrin documentation website's shared repository sidebar
|
|
||||||
* <a href="https://github.com/sovrin-foundation/ssi-protocol" target="_blank">/sovrin-foundation/ssi-protocol</a> - Document the interactions and conventions that make self-sovereign identity interoperable.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/protocol" target="_blank">/sovrin-foundation/protocol</a>
|
|
||||||
* <a href="https://github.com/sovrin-foundation/steward-tools" target="_blank">/sovrin-foundation/steward-tools</a> - tools for Sovrin steward
|
|
||||||
* <a href="https://github.com/sovrin-foundation/token-plugin" target="_blank">/sovrin-foundation/token-plugin</a> - source code and tests for Sovrin Ledger plugins
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-test-automation" target="_blank">/sovrin-foundation/sovrin-test-automation</a> - quality assurance automation for Sovrin repos.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/agent-sdk" target="_blank">/sovrin-foundation/agent-sdk</a> - Reference Agent
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-connector-preview" target="_blank">/sovrin-foundation/sovrin-connector-preview</a> - Forked from evernym/sovrin-connector-preview
|
|
||||||
* <a href="https://github.com/sovrin-foundation/pipeline-test" target="_blank">/sovrin-foundation/pipeline-test</a> - Test integrations, hooks and build pipelines.
|
|
||||||
|
|
||||||
|
|
||||||
### Sovrin - Indy [**^**](#contents)
|
|
||||||
* <a href="https://github.com/sovrin-foundation/indy-dev" target="_blank">/sovrin-foundation/indy-dev</a> - Forked from michaeldboyd/indy-dev</a> - This is a quick way to setup a development environment to experiment with IndySDK
|
|
||||||
* <a href="https://github.com/sovrin-foundation/libsovtoken" target="_blank">/sovrin-foundation/libsovtoken</a> - This is a payment handler library to work with libindy. It may one day be merged into libindy.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-indy-android-dependencies" target="_blank">/sovrin-foundation/sovrin-indy-android-dependencies</a> - indy-android-dependencies
|
|
||||||
* <a href="https://github.com/sovrin-foundation/connector-app" target="_blank">/sovrin-foundation/connector-app</a> - Reference mobile edge agent for use with the Sovrin Network built from Hyperledger Indy.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/indy-android-dependencies" target="_blank">/sovrin-foundation/indy-android-dependencies</a> - Dependencies required to build indy-sdk
|
|
||||||
|
|
||||||
|
|
||||||
## /decentralized-identity - DIF [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/decentralized-identity.github.io" target="_blank">/decentralized-identity/decentralized-identity.github.io</a> - Site for the open source, community-driven group of dev and organizations working toward an interoperable, decentralized identity ecosystem
|
|
||||||
* <a href="https://github.com/decentralized-identity/org" target="_blank">/decentralized-identity/org</a> - DIF docs, wiki, and organizational material
|
|
||||||
* <a href="https://github.com/decentralized-identity/credential-manifest" target="_blank">/decentralized-identity/credential-manifest</a> - Format that normalizes the definition of requirements for the issuance of a credential
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-registrar" target="_blank">/decentralized-identity/universal-registrar</a> - Specifications and implementation of a universal identifier registrar
|
|
||||||
* <a href="https://github.com/decentralized-identity/attestations" target="_blank">decentralized-identity/attestations</a> - Attestation API implementations for various languages and platforms.
|
|
||||||
|
|
||||||
### DIF - DID [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-methods" target="_blank">/decentralized-identity/did-methods</a> - DID Method specs, docs, and materials
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-typescript" target="_blank">/decentralized-identity/did-common-typescript
|
|
||||||
</a> - A common bundle of shared code and modules for working with DIDs, DID Documents, and other DID-related activities
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-csharp" target="_blank">/decentralized-identity/did-security-csharp</a> - C# implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-typescript" target="_blank">/decentralized-identity/did-security-typescript</a> - Typescript implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-java" target="_blank">/decentralized-identity/did-common-java</a> - Shared DID Java library.
|
|
||||||
* <a href="https://github.com/decentralized-identity/ua-web-extension" target="_blank">/decentralized-identity/ua-web-extension</a> - Basic web extension version of a DID User Agent
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-recovery" target="_blank">/decentralized-identity/did-recovery</a> - Various methods for DID recovery
|
|
||||||
* <a href="https://github.com/decentralized-identity/web-polyfills" target="_blank">/decentralized-identity/web-polyfills</a> - Polyfills for proposed or emerging DID-centric Web APIs
|
|
||||||
* <a href="https://github.com/decentralized-identity/" target="_blank">/decentralized-identity/</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/http-did-auth-proxy" target="_blank">/decentralized-identity/http-did-auth-proxy</a> - Forked from bcgov/http-did-auth-proxy
|
|
||||||
DID Auth HTTP proxy.
|
|
||||||
|
|
||||||
### DIF - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-auth-jose" target="_blank">/decentralized-identity/did-auth-jose</a> - JOSE-based implementation of DID Authenticated Encryption
|
|
||||||
|
|
||||||
### DIF - Sidetree [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-ipfs" target="_blank">/decentralized-identity/sidetree-ipfs</a> - IPFS module for storing and accessing Sidetree entity operation data via content addressable storage
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-core" target="_blank">/decentralized-identity/sidetree-core</a> - The blockchain-agnostic server implementation of the Sidetree protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-bitcoin" target="_blank">/decentralized-identity/sidetree-bitcoin</a> - Blockchain-specific code for the Sidetree-based DID Method implementation on Bitcoin
|
|
||||||
* <a href="https://github.com/decentralized-identity/ion" target="_blank">/decentralized-identity/ion</a> - DID Method implementation using the Sidetree protocol on top of Bitcoin
|
|
||||||
|
|
||||||
### DIF - Hub [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js-sample" target="_blank">/decentralized-identity/hub-sdk-js-sample</a> - Sample app demonstrating use of the DIF Identity Hub JavaScript SDK.
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js" target="_blank">/decentralized-identity/hub-sdk-js</a> - JavaScript SDK for interacting with Identity Hubs
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-common-js" target="_blank">/decentralized-identity/hub-common-js</a> - Common interfaces for working with Identity Hubs in JavaScript/TypeScript
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-core" target="_blank">/decentralized-identity/hub-node-core</a> - Node.js implementation of the Identity Hub interfaces, business logic, and replication protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/identity-hub" target="_blank">/decentralized-identity/identity-hub</a> - Storage and compute nodes for decentralized identity data and interactions
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-reference" target="_blank">/decentralized-identity/hub-node-reference</a> - The official Identity Hub reference implementation bundle for Node.js
|
|
||||||
|
|
||||||
### DIF - Uniresolver [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver" target="_blank">/decentralized-identity/universal-resolver</a> - Universal Resolver implementation and drivers.
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-frontend" target="_blank">/decentralized-identity/universal-resolver-frontend</a> - Frontend web UI for Universal Resolver
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-python" target="_blank">/decentralized-identity/universal-resolver-python</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-java" target="_blank">/decentralized-identity/universal-resolver-java</a>
|
|
||||||
|
|
||||||
## Veres One [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/veres-one/veres-one" target="_blank">/veres-one/veres-one</a> - A ledger for acquiring and managing decentralized identifiers
|
|
||||||
* <a href="https://github.com/veres-one/did-veres-one" target="_blank">/veres-one/did-veres-one</a> - A Decentralized Identifier utility library for Veres One
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-validator" target="_blank">/veres-one/veres-one-validator</a> - A ledger validator that accepts either signatures or proof of work
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-context" target="_blank">/veres-one/veres-one-context</a>
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-consensus-continuity-elector-selection" target="_blank">/veres-one/veres-one-consensus-continuity-elector-selection</a>
|
|
||||||
* <a href="https://github.com/veres-one/did-client-veres-one" target="_blank">/veres-one/did-client-veres-one</a> - DID client APIs for Veres One
|
|
||||||
* <a href="https://github.com/veres-one/docs.veres.one" target="_blank">/veres-one/docs.veres.one</a> - Documentation for the Veres One Project
|
|
||||||
* <a href="https://github.com/veres-one/status.testnet.veres.one" target="_blank">/veres-one/status.testnet.veres.one</a> - Testnet status dashboard website
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-project" target="_blank">/veres-one/veres-one-project</a>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## /hyperledger Indy [**^**](#contents)
|
|
||||||
* [/indy-plenum](https://github.com/hyperledger/indy-plenum) - Byzantine Fault Tolerant Protocol [[**wiki**](https://github.com/hyperledger/indy-plenum/wiki)]
|
|
||||||
> "Byzantine fault tolerance is a sub-field of fault tolerance research inspired by the Byzantine Generals' Problem, which is a generalized version of the Two Generals' Problem."
|
|
||||||
* [Storage components](https://github.com/hyperledger/indy-plenum/blob/master/docs/storage.md) - As of now, RocksDB is used as a key-value database for all Storages.
|
|
||||||
* [/indy-sdk](https://github.com/hyperledger/indy-sdk) - Everything needed to build applications that interact with an Indy distributed identity ledger.
|
|
||||||
* [MAINTAINERS.md](https://github.com/hyperledger/indy-sdk/blob/master/MAINTAINERS.md)
|
|
||||||
* [/indy-node](https://github.com/hyperledger/indy-node) - The server portion of a distributed ledger purpose-built for decentralized identity.
|
|
||||||
* [/indy-anoncreds](https://github.com/hyperledger/indy-anoncreds) - Anonymous credentials protocol implementation in python
|
|
||||||
* [/indy-agent](https://github.com/hyperledger/indy-agent) - reference agents and associated tools.
|
|
||||||
* [/indy-test-automation](https://github.com/hyperledger/indy-test-automation) - Automation tools for testing of Indy Project components.
|
|
||||||
* [/indy-post-install-automation](https://github.com/hyperledger/indy-post-install-automation)
|
|
||||||
* [/indy-hipe](https://github.com/hyperledger/indy-hipe) -
|
|
||||||
Hyperledger Indy Project Enhancements
|
|
||||||
* https://indy.readthedocs.io/projects/hipe/en/latest/
|
|
||||||
* [/indy-crypto](https://github.com/hyperledger/indy-crypto) - shared crypto library for Hyperledger Indy components. To be:
|
|
||||||
* [/ursa](https://github.com/hyperledger/ursa) [[**ϟ**](https://www.hyperledger.org/blog/2018/12/04/welcome-hyperledger-ursa)][[**ϟ**](https://www.coindesk.com/hyperledger-launches-cryptography-toolbox-for-blockchain-developers)]
|
|
||||||
> "includes the Hyperledger Indy-Crypto code base that is the building block for anonymous credentials, the verifiable credentials protocol, in indy-sdk used by the Sovrin Network. [...] We are hopeful the shared library will help other platforms better incorporate and use ZKP-based credentials and leverage Sovrin for their identity component." (From Nathan George on Sovrin Telegram) [[**wiki**](https://wiki.hyperledger.org/projects/ursa)]
|
|
||||||
|
|
||||||
### IDChain [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ID-Chain/IEA-API" target="_blank">/ID-Chain/IEA-API</a> - Institutional Edge Agent Generic API
|
|
||||||
* <a href="https://github.com/ID-Chain/Common" target="_blank">/ID-Chain/Common</a> - Common Repository for IdentityChain Project
|
|
||||||
* <a href="https://github.com/ID-Chain/tlabshack" target="_blank">/ID-Chain/tlabshack</a> - Repository to hold files for the tlabshack hackathon
|
|
||||||
* <a href="https://github.com/ID-Chain/ID-Chain.github.io" target="_blank">/ID-Chain/ID-Chain.github.io</a> - Documentation site for IdentityChain Project
|
|
||||||
* <a href="https://github.com/ID-Chain/Cloud-Agent" target="_blank">/ID-Chain/Cloud-Agent</a> - Indy Cloud Agent using Google Firebase Cloud Messaging
|
|
||||||
* <a href="https://github.com/ID-Chain/Chamber-Of-Commerce" target="_blank">/ID-Chain/Chamber-Of-Commerce</a> - Institutional Edge Agent Legacy Example (Verifier + Issuer)
|
|
||||||
* <a href="https://github.com/ID-Chain/Government" target="_blank">/ID-Chain/Government</a> - Institutional Edge Agent Legacy Example (Initial Issuer)
|
|
||||||
* <a href="https://github.com/ID-Chain/IEA-Admin-UI" target="_blank">/ID-Chain/IEA-Admin-UI</a> - Admin User Interface to manage the Institutional Edge Agent API
|
|
||||||
* <a href="https://github.com/ID-Chain/Schema-Extensions" target="_blank">/ID-Chain/Schema-Extensions</a> - High level Schema Extensions (Compiler & Checker)
|
|
||||||
* <a href="https://github.com/ID-Chain/Mobile-Edge-Agent" target="_blank">/ID-Chain/Mobile-Edge-Agent</a> - Mobile Edge Agent Application
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### /IBM-Blockchain-Identity [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-tutorial-sandbox" target="_blank">/IBM-Blockchain-Identity/indy-tutorial-sandbox</a> - Forked from brycecurtis/indy-tutorial-sandbox
|
|
||||||
A turnkey, Docker-based sandbox that enables quick and easy exploration of Hyperledger Indy concepts.
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-ssivc-tutorial" target="_blank">/IBM-Blockchain-Identityindy-ssivc-tutorial</a> - A turnkey, Docker-based tutorial for help developers get acquainted with Self-Sovereign Identity and Verifiable Credentials.
|
|
||||||
|
|
||||||
|
|
||||||
## Verifiable Organizations Network [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/BC-Policy-Framework-For-GitHub" target="_blank">/bcgov/BC-Policy-Framework-For-GitHub</a> - Policy information for BC Government employees using GitHub
|
|
||||||
* <a href="https://github.com/bcgov/design-system" target="_blank">/bcgov/design-system</a> - British Columbia Government Design System for Digital Services
|
|
||||||
|
|
||||||
### BCGov - VON [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/TheOrgBook" target="_blank">/bcgov/TheOrgBook</a> - A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
|
||||||
* <a href="https://github.com/bcgov/von" target="_blank">/bcgov/von</a> - Verifiable Organizations Network
|
|
||||||
* <a href="https://github.com/bcgov/von-connector" target="_blank">/bcgov/von-connector</a> - Verifiable Organization Network Connector
|
|
||||||
* <a href="https://github.com/bcgov/von-network" target="_blank">/bcgov/von-network</a> - A portable development level Indy Node network.
|
|
||||||
* <a href="https://github.com/bcgov/von-ledger-explorer" target="_blank">/bcgov/von-ledger-explorer</a> - The VON Ledger Explorer
|
|
||||||
* <a href="https://github.com/bcgov/dFlow" target="_blank">/bcgov/dFlow</a> - A demonstration of the verifiable organization network showing a new restaurant gathering the permits necessary to open.
|
|
||||||
|
|
||||||
#### VON - Indy [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/indy-catalyst" target="_blank">/bcgov/indy-catalyst</a> - Hyperledger Indy Catalyst is a set of application level software components designed to accelerate the adoption of trustworthy entity to entity communications.
|
|
||||||
* <a href="https://github.com/bcgov/indy-sdk-postgres-storage" target="_blank">/bcgov/indy-sdk-postgres-storage</a> - PostgreSQL plug-in for use with the indy-sdk
|
|
||||||
|
|
||||||
#### VON - Agents [**^**](#contents)
|
|
||||||
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/von-personal-agent" target="_blank">/bcgov/von-personal-agent</a> - A personal agent for the von network.
|
|
||||||
* <a href="https://github.com/bcgov/VON-ESB-DRS-Agent" target="_blank">/bcgov/VON-ESB-DRS-Agent</a> - Piloting the Dispute Resolution Suite with connections to the OrgBook
|
|
||||||
* <a href="https://github.com/bcgov/von-agent-template" target="_blank">/bcgov/von-agent-template</a> - Template for a von-x based agent
|
|
||||||
* <a href="https://github.com/bcgov/von-bc-registries-agent" target="_blank">/bcgov/von-bc-registries-agent</a>
|
|
||||||
* <a href="https://github.com/bcgov/von_agent" target="_blank">/bcgov/von_agent</a> Forked from PSPC-SPAC-buyandsell/von_agent - VON agents using indy-sdk
|
|
||||||
|
|
||||||
|
|
||||||
### BCGov - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-extension" target="_blank">/bcgov/did-auth-extension</a> - DID Auth browser extension.
|
|
||||||
* <a href="https://github.com/bcgov/http-did-auth-proxy" target="_blank">/bcgov/http-did-auth-proxy</a> - DID Auth HTTP proxy.
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-relying-party" target="_blank">/bcgov/did-auth-relying-party</a> - DID Auth relying party.
|
|
||||||
|
|
||||||
### /PSPC-SPAC-buyandsell [**^**](#contents)
|
|
||||||
**Public Services and Procurement Canada: buyandsell.gc.ca --- Services publics et Approvisionnement Canada : Achatsetventes.gc.ca**
|
|
||||||
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_tails" target="_blank">/PSPC-SPAC-buyandsell/von_tails</a> - Tails file server for von_anchor issuer and holder-prover anchors
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_base" target="_blank">/PSPC-SPAC-buyandsell/von_base</a>
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_anchor" target="_blank">/PSPC-SPAC-buyandsell/von_anchor</a> - VON anchor classes for interaction with sovrin/indy ledger via indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-image" target="_blank">/PSPC-SPAC-buyandsell/von-image</a> - Standard docker images for building VON components
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-x" target="_blank">/PSPC-SPAC-buyandsell/von-x</a> - VON-X is a Python library enabling rapid deployment of Hyperledger Indy credential issuer, holder, and verifier services, particularly for integration with TheOrgBook.
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/didauth" target="_blank">/PSPC-SPAC-buyandsell/didauth</a> - DID authentication by way of HTTP Signatures for Hyperledger Indy agents
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_agent" target="_blank">/PSPC-SPAC-buyandsell/von_agent</a> - VON agents using indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_connector" target="_blank">/PSPC-SPAC-buyandsell/von_connector</a> - service wrapper API per agent, via django application
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/ReferenceVonActuator" target="_blank">/PSPC-SPAC-buyandsell/ReferenceVonActuator</a> - Java implementation of actuator of reference von_connector implementation
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_conx" target="_blank">/PSPC-SPAC-buyandsell/von_conx</a> - Reference implementation (sample) for a VON Connector using tools of VON_X
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/demo-agent" target="_blank">/PSPC-SPAC-buyandsell/demo-agent</a> - agent and api wrapper code base
|
|
||||||
|
|
||||||
## Selfkey Foundation [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkeyfoundation.github.io" target="_blank">/SelfKeyFoundation/selfkeyfoundation.github.io</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-developers" target="_blank">/SelfKeyFoundation/selfkey-developers</a> - SelfKey Developer Site
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-developer-portal" target="_blank">/SelfKeyFoundation/selfkey-developer-portal</a> - Developer Resources for SelfKey SDK's
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-platform" target="_blank">/SelfKeyFoundation/selfkey-platform</a> - Temporarily hosted here until ready for public consumption.
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-download-portal" target="_blank">/SelfKeyFoundation/selfkey-download-portal</a> - Download links and information for SelfKey software releases
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-net" target="_blank">/SelfKeyFoundation/selfkey-net</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/Identity-Wallet" target="_blank">/SelfKeyFoundation/Identity-Wallet</a> - Code for the SelfKey Identity Wallet
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-ui" target="_blank">/SelfKeyFoundation/selfkey-ui</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-simulation" target="_blank">/SelfKeyFoundation/selfkey-simulation</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-payments" target="_blank">/SelfKeyFoundation/selfkey-payments</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-lib" target="_blank">/SelfKeyFoundation/selfkey-lib</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-network-demo" target="_blank">/SelfKeyFoundation/selfkey-network-demo</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-extension" target="_blank">/SelfKeyFoundation/selfkey-extension</a> - SelfKey Extension
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-service" target="_blank">/SelfKeyFoundation/selfkey-service</a> - SelfKey Service
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-aspnetcore-demo" target="_blank">/SelfKeyFoundation/selfkey-aspnetcore-demo</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/face-rec" target="_blank">/SelfKeyFoundation/face-rec</a> - Selfkey Face Recognition API
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/passport-selfkey" target="_blank">/SelfKeyFoundation/passport-selfkey</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-login" target="_blank">/SelfKeyFoundation/selfkey-login</a> - Components for external "log-in with selfkey"
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/matomo" target="_blank">/SelfKeyFoundation/matomo</a> - SelfKey Foundation Matomo server
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/Marketplaces" target="_blank">/SelfKeyFoundation/Marketplaces</a> - Marketplace Applications
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/identity-wallet-mobile" target="_blank">/SelfKeyFoundation/identity-wallet-mobile</a> - The React Native mobile application for SelfKey.
|
|
||||||
|
|
||||||
### Selfkey DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-did" target="_blank">/SelfKeyFoundation/selfkey-did</a> - Library for DID managemente and issuance and verification of verifiable credentials
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-claim-registry" target="_blank">/SelfKeyFoundation/selfkey-claim-registry</a> - Public claim registry for Selfkey DIDs
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-did-resolver" target="_blank">/SelfKeyFoundation/selfkey-did-resolver</a> - Library for resolving DIDs in SelfKey method space
|
|
||||||
|
|
||||||
### Selfkey SmartContracts [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-commerce" target="_blank">/SelfKeyFoundation/selfkey-commerce</a> - Payment, Escrow and Affiliate Smart Contract Development
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-token" target="_blank">/SelfKeyFoundation/selfkey-token</a> - Crowdsale Smart Contract
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-identity" target="_blank">/SelfKeyFoundation/selfkey-identity</a> - Smart contracts supporting SelfKey identity platform
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-staking" target="_blank">/SelfKeyFoundation/selfkey-staking</a> - Contracts that implement staking and marketplace deposit functionality for SelfKey
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/identity-contracts" target="_blank">/SelfKeyFoundation/identity-contracts</a> - Development on self-sovereign identity and verifiable claims
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-name-registry" target="_blank">/SelfKeyFoundation/selfkey-name-registry</a> - Smart contract for registering names
|
|
||||||
|
|
||||||
### Selfkey Javascript [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/keythereum" target="_blank">/SelfKeyFoundation/keythereum</a> - Forked from ethereumjs/keythereum - Create, import and export Ethereum keys
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-js-client" target="_blank">/SelfKeyFoundation/selfkey-js-client</a> - JavaScript Client Library for integrating Login with SelfKey
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-nodejs-demo" target="_blank">/SelfKeyFoundation/selfkey-nodejs-demo</a> - Demo Site For Testing SelfKey Marketplace and LWS Integrations
|
|
||||||
|
|
||||||
### Selfkey Assorted [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/trezor-wallet-provider" target="_blank">/SelfKeyFoundation/trezor-wallet-provider</a> - Forked from HartgerV/trezor-wallet-provider - Trezor wallet provider for the Web3 ProviderEngine
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/lws-app" target="_blank">/SelfKeyFoundation/lws-app</a> - lws-app react app prototype
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/airtable-proxy" target="_blank">/SelfKeyFoundation/airtable-proxy</a> - A proxy service for airtable
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/react-jsonschema-form-material-theme" target="_blank">/SelfKeyFoundation/react-jsonschema-form-material-theme</a> - Widgets and templates using material-ui
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/react-jsonschema-form" target="_blank">react-jsonschema-form</a> - Forked from rodrigopavezi/react-jsonschema-form
|
|
||||||
A React component for building Web forms from JSON Schema.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Ockam Network [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ockam-network/ockam" target="_blank">/ockam-network/ockam</a> - Tools for building identity, trust and interoperability into connected devices.
|
|
||||||
* <a href="https://github.com/ockam-network/did" target="_blank">/ockam-network/did</a> - A golang package to work with Decentralized Identifiers (DIDs)
|
|
||||||
* <a href="https://github.com/ockam-network/did-method-spec" target="_blank">/ockam-network/did-method-spec</a> - Ockam DID Method Specification
|
|
||||||
|
|
||||||
## Ontology [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ontio/ontology" target="_blank">/ontio/ontology</a> - Official Go implementation of the Ontology protocol. https://dev-docs.ont.io/#/
|
|
||||||
* <a href="https://github.com/ontio/documentation" target="_blank">/ontio/documentation</a> - Ontology Documents https://ont.io
|
|
||||||
* <a href="https://github.com/ontio/ontology-DID" target="_blank">/ontio/ontology-DID</a> - Ontology decentralized identification protocol based on W3C DID specifications.
|
|
||||||
* <a href="https://github.com/ontio/ontology-crypto" target="_blank">/ontio/ontology-crypto</a>
|
|
||||||
* <a href="https://github.com/ontio/OWallet" target="_blank">/ontio/OWallet</a> - a comprehensive Ontology desktop wallet
|
|
||||||
* <a href="https://github.com/ontio/ontology-dapi" target="_blank">/ontio/ontology-dapi</a> - A lightweight Javascript library for interacting with Ontology node and Ontology wallets
|
|
||||||
* <a href="https://github.com/ontio/ontology-ddxf" target="_blank">/ontio/ontology-ddxf</a> - Distributed data eXchange Framework,which allows to build data marketplaces .
|
|
||||||
|
|
||||||
## TangleID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/TangleID/TangleID/" target="_blank">/TangleID/TangleID/</a> - Secure self-sovereign identity built on IOTA/Tangle
|
|
||||||
identity
|
|
||||||
* <a href="https://github.com/TangleID/api-examples/" target="_blank">/TangleID/api-examples/</a> - API examples for TangleID
|
|
||||||
* <a href="https://github.com/TangleID/TangleID.github.io/" target="_blank">/TangleID/TangleID.github.io/</a> - TangleID Landing Page
|
|
||||||
* <a href="https://github.com/TangleID/tangleid-client/" target="_blank">/TangleID/tangleid-client/</a> - TangleID Client/Mobile application
|
|
||||||
* <a href="https://github.com/TangleID/demo-site/" target="_blank">/TangleID/demo-site/</a> - A sample web illustrating how to issue claims to the participants with TangleID
|
|
||||||
* <a href="https://github.com/TangleID/docs" target="_blank">/TangleID/docs</a> - TangleID API Documentation
|
|
||||||
- Forked from lord/slate
|
|
||||||
* <a href="https://github.com/TangleID/sample-issuer/" target="_blank">/TangleID/sample-issuer/</a> - TangleID Sample Issuer
|
|
||||||
|
|
||||||
## Simbol [**^**](#contents)
|
|
||||||
|
|
||||||
AR\VR\Mixed
|
|
||||||
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-design" target="_blank">/wearesimbol/simbol-design</a>
|
|
||||||
* <a href="https://github.com/wearesimbol/a-simbol" target="_blank">/wearesimbol/a-simbol</a> - A-Frame component for Simbol
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol" target="_blank">/wearesimbol/simbol</a> - Social and Communications platform WebXR sites with a self-sovereign identity
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-server" target="_blank">/wearesimbol/simbol-server</a> - Simple Web and WebSocket server, specially for sites that use Simbol
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-demo" target="_blank">/wearesimbol/simbol-demo</a> - Create a fullstack Simbol virtual world very easily
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Assorted [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/bnelson777/id.ly" target="_blank">/bnelson777/id.ly</a> - Cross-platform self-sovereign identity business card and messaging app
|
|
||||||
|
|
||||||
|
|
||||||
## /peacekeeper/blockchain-identity [**^**](#contents)
|
|
||||||
|
|
||||||
>Projects/companies working on blockchain and identity
|
|
||||||
|
|
||||||
* [/peacekeeper/blockchain-identity](https://github.com/peacekeeper/blockchain-identity) - The Original list of Blockchain Identity Initiatives.
|
|
||||||
|
|
||||||
Maintained by, [Markus Sabadello (Peacekeeper)](https://medium.com/@markus.sabadello)
|
|
||||||
|
|
||||||
## /decentralized-id/decentralized-id.github.io [**^**](#contents)
|
|
||||||
You can join in on the research, and help build this educational resource.
|
|
||||||
|
|
||||||
* [/awesome-decentralized-id](https://github.com/infominer33/awesome-decentralized-id) is becoming
|
|
||||||
* [decentralized-id.com](https://github.com/decentralized-id/decentralized-id.github.io)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
Cover Image Source:
|
|
||||||
|
|
||||||
<a href="https://github.myshopify.com/products/die-cut-github-stickers" target="_blank"><img src="http://i.imgur.com/RhbNQXF.png"/></a><br/>
|
|
||||||
<a href="https://github.myshopify.com/products/die-cut-github-stickers" target="_blank">https://github.myshopify.com/products/die-cut-github-stickers</a>
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id)
|
|
@ -1,953 +0,0 @@
|
|||||||
---
|
|
||||||
title: SSI-DID Github Repositories
|
|
||||||
description: A start at listing all DID-SSI related GitHub Repositories.
|
|
||||||
image: "https://infominer.id/images/github.jpeg"
|
|
||||||
---
|
|
||||||
|
|
||||||
# SSI-DID Github Repositories
|
|
||||||
|
|
||||||
Please send [a message](../index.html#contact), open an issue or submit a pull-request with any suggestions\recommendations.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Project Danube](#project-danube-)
|
|
||||||
* [XDI](#xdi-)
|
|
||||||
* [XDI Libraries](#xdi-libraries-)
|
|
||||||
* [XDI - Various Integrations](#xdi---various-integrations-)
|
|
||||||
* [XDI Configurations](#xdi-configurations-)
|
|
||||||
* [XDI Examples](#xdi-examples-)
|
|
||||||
* [XDI Plugins](#xdi-plugins-)
|
|
||||||
* [Aeternam](#aeternam-)
|
|
||||||
* [XDI Cloud](#xdi-cloud-)
|
|
||||||
* [XDI Server Deployed Via](#xdi-server-deployed-via-)
|
|
||||||
* [Services](#services-)
|
|
||||||
* [Digital Bazaar](#digital-bazaar-)
|
|
||||||
* [DB - Identity](#db---identity-)
|
|
||||||
* [DB - Credentials](#db---credentials-)
|
|
||||||
* [DB - DID](#db---did-)
|
|
||||||
* [DB - Linked Data](#db---linked-data-)
|
|
||||||
* [/WebOfTrustInfo](#weboftrustinfo)
|
|
||||||
* [RWoT Design Workshop](#rwot-design-workshop-)
|
|
||||||
* [RWoT BTCR](#rwot-btcr-)
|
|
||||||
* [RWoT Txref Conversion](#rwot-txref-conversion-)
|
|
||||||
* [RWoT Linked Data](#rwot-linked-data-)
|
|
||||||
* [/w3c](#w3c---world-wide-web-consortium-)
|
|
||||||
* [Verifiable Claims Working Group](#w3cverifiable-claims----vc-working-group)
|
|
||||||
* [Credentials Community Group](#w3c-ccg---credentials-community-group-)
|
|
||||||
* [CCG - DID](ccg---did-)
|
|
||||||
* [Verifiable Credentials](#ccg---verifiable-credentials-)
|
|
||||||
* [Linked Data](#ccg----linked-data-)
|
|
||||||
* [Digital Verification Community Group](#digital-verification-community-group-)
|
|
||||||
* [OpenCreds](#opencreds-)
|
|
||||||
* [Spidchain](#spidchain-)
|
|
||||||
* [BTCR](#spid-btcr-)
|
|
||||||
* [Ethereum](#spid-ethereum-)
|
|
||||||
* [Hackathon](#spid-hackathon-)
|
|
||||||
* [Ethereum](#ethereum-)
|
|
||||||
* [Assorted Ethereum Apps](#assorted-ethereum-apps)
|
|
||||||
* [uPort](#uport-)
|
|
||||||
* [uPort DID](#uport-did-)
|
|
||||||
* [uPort Identification](#uport-identification-)
|
|
||||||
* [uPort Mobile](#uport-mobile-)
|
|
||||||
* [uPort Lambda](#uport-lambda-)
|
|
||||||
* [uPort React](#uport-react-)
|
|
||||||
* [uPort Assorted](#uport-assorted-)
|
|
||||||
* [Jolocom](#jolocom-)
|
|
||||||
* [Learning Machine](#learning-machine-)
|
|
||||||
* [Blockcerts](#blockcerts-)
|
|
||||||
* [Blockcerts Json](#blockcerts-json-)
|
|
||||||
* [Blockcerts Web](#blockcerts-web-)
|
|
||||||
* [Blockcerts Mobile](#blockcerts-mobile-)
|
|
||||||
* [Sovrin Foundation](#sovrin-foundation-)
|
|
||||||
* [Sovrin - Indy](#sovrin-indy-)
|
|
||||||
* [Decentralized Identity Foundation](#decentralized-identity---dif-)
|
|
||||||
* [DIF - DID](#dif---did-)
|
|
||||||
* [DIF - DID-Auth](#dif---did-auth-)
|
|
||||||
* [DIF - Sidetree](#dif---sidetree-)
|
|
||||||
* [DIF - Hub](#dif---hub-)
|
|
||||||
* [DIF - Uniresolver](#dif---uniresolver-)
|
|
||||||
* [Veres One](#veres-one-)
|
|
||||||
* [/hyperledger Indy](#hyperledger-indy-)
|
|
||||||
* [/IBM-Blockchain-Identity](#ibm-blockchain-identity-)
|
|
||||||
* [Verifiable Organizations Network](#verifiable-organizations-network-)
|
|
||||||
* [BCGov - VON](#bcgov---von-)
|
|
||||||
* [VON - Indy](#von---indy-)
|
|
||||||
* [VON - Agents](#von-agents-)
|
|
||||||
* [BCGov - DID-Auth](#bcgov---did-auth-)
|
|
||||||
* [PSPC-SPAC-buyandsell](#pspc-spac-buyandsell-) - Public Services and Procurement Canada
|
|
||||||
* [Selfkey Foundation](#selfkey-foundation-)
|
|
||||||
* [Selfkey DID](#selfkey-did-)
|
|
||||||
* [Selfkey SmartContracts](#selfkey-smartcontracts-)
|
|
||||||
* [Selfkey Javascript](#selfkey-javascript-)
|
|
||||||
* [Selfkey Assorted](#selfkey-assorted)
|
|
||||||
* [Ockam Network](#ockam-network-)
|
|
||||||
* [Ontology](#ontology-)
|
|
||||||
* [TangleID](#tangleid-)
|
|
||||||
* [Simbol](#simbol-)
|
|
||||||
* [Assorted](#assorted-)
|
|
||||||
* [/peacekeeper/blockchain-identity](#peacekeeperblockchain-identity-)
|
|
||||||
* [/decentralized-id/decentralized-id.github.io](#decentralized-iddecentralized-idgithubio-)
|
|
||||||
* [HOME](https://infominer.id)
|
|
||||||
|
|
||||||
## /project-danube [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/indy-sdk-java" target="_blank">/projectdanube/indy-sdk-java</a> - Java binding to the native Indy SDK
|
|
||||||
* <a href="https://github.com/projectdanube/blockstack-cli-java" target="_blank">/projectdanube/blockstack-cli-java</a> - Java client for Blockstore
|
|
||||||
|
|
||||||
|
|
||||||
### XDI [**^**](#contents)
|
|
||||||
|
|
||||||
>[XDI.org](https://xdi.org) is a non-profit public trust organization whose purpose is to provide public infrastructure for digital identity, security, and privacy using the open standard XDI semantic data interchange protocol developed by the OASIS XDI Technical Committee.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-tutorial" target="_blank">/projectdanube/xdi-tutorial</a> - XDI Tutorial
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-swing" target="_blank">/projectdanube/XDINinja-swing</a> - XDI-enabled standalone client application
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tools" target="_blank">/projectdanube/xdi2-tools</a> - XDI2 maintenance and other tools
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-personal" target="_blank">/projectdanube/xdi2-connector-personal</a> - A connector plugin for the XDI2 server that maps data from Personal.com to XDI
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-docker" target="_blank">/projectdanube/xdi2-docker</a> - Dockerfiles for XDI2
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-buttonbuilder" target="_blank">/projectdanube/xdi2-connect-buttonbuilder</a> - "Button Builder" component for the XDI Connect protocol
|
|
||||||
|
|
||||||
### XDI libraries [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2" target="_blank">/projectdanube/xdi2</a> - XDI2 general purpose library and server
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-js" target="_blank">/projectdanube/xdi-js</a> - XDI client library for JavaScript
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-core" target="_blank">/projectdanube/xdi2-connect-core</a> - Shared library for the XDI Connect protocol
|
|
||||||
|
|
||||||
|
|
||||||
### XDI - Various Integrations [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-bdb" target="_blank">/projectdanube/xdi2-bdb</a> - Support for using BDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-mongodb" target="_blank">/projectdanube/xdi2-mongodb</a> - Support for using MongoDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-heroku" target="_blank">/projectdanube/xdi2-server-heroku</a> - XDI2 Server deployed via Heroku
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-redis" target="_blank">/projectdanube/xdi2-redis</a> - Support for using Redis as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tor" target="_blank">/projectdanube/xdi2-tor</a> - Integration of XDI and Tor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-ipfs" target="_blank">/projectdanube/xdi2-ipfs</a> - Integration of XDI and IPFS
|
|
||||||
* <a href="https://github.com/projectdanube/withsqlite" target="_blank">/projectdanube/withsqlite</a> - A module for a python dict that back ends on an sqlite3 database. It's bit like shelve but with json and sqlite3.
|
|
||||||
- Forked from jvasile/withsqlite
|
|
||||||
|
|
||||||
### XDI Configuration [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-selfhosted" target="_blank">/projectdanube/xdi2-selfhosted</a> - A configuration profile of the XDI2 server for self-hosting a single XDI graph.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-csp" target="_blank">/projectdanube/xdi2-csp</a> - A configuration profile of the XDI2 server for hosting a dynamic number of XDI graphs.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-registry" target="_blank">/projectdanube/xdi2-registry</a> -
|
|
||||||
A configuration profile of the XDI2 server for hosting a registry of XDI names and XDI numbers.
|
|
||||||
|
|
||||||
### XDI Examples [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-messaging" target="_blank">/projectdanube/xdi2-example-messaging</a> - XDI2 Examples: Basic messaging functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-advanced-server" target="_blank">/projectdanube/xdi2-example-advanced-server</a> - XDI2 Examples: Setting up advanced XDI servers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-core" target="_blank">/projectdanube/xdi2-example-core</a> - XDI2 Examples: Simple uses of the core functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-client" target="_blank">/projectdanube/xdi2-example-client</a> - XDI2 Examples: Writing XDI client applications.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-server" target="_blank">/projectdanube/xdi2-example-secp256k1-server</a> - Example XDI server using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-server" target="_blank">/projectdanube/xdi2-example-ec25519-server</a> - Example XDI server using cid-1 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-acmenews" target="_blank">/projectdanube/xdi2-connect-acmenews</a> - +acmenews XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-leshop" target="_blank">/projectdanube/xdi2-connect-leshop</a> - +leshop XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-client" target="_blank">/projectdanube/xdi2-example-secp256k1-client</a> - Example XDI client using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-client" target="_blank">/projectdanube/xdi2-example-ec25519-client</a> - Example XDI client using cid-1 cryptographic XDI numbers.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### XDI Plugins [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-secp256k1" target="_blank">/projectdanube/xdi2-crypto-secp256k1</a> - This is an secp256k1 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-ec25519" target="_blank">/projectdanube/xdi2-crypto-ec25519</a> - This is an Ed25519 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-facebook" target="_blank">/projectdanube/xdi2-connector-facebook</a> - A connector plugin for the XDI2 server that maps data from Facebook to XDI
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-meeco" target="_blank">/projectdanube/xdi2-connector-meeco</a> - A connector plugin for Meeco
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-plugin" target="_blank">/projectdanube/XDINinja-plugin</a> - A browser plugin that is like "Twitter for data"
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-cozy" target="_blank">/projectdanube/xdi2-connector-cozy</a> - A connector plugin for CozyCloud
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-filesys" target="_blank">/projectdanube/xdi2-filesys</a> - Plugin for an XDI2 server to integrate with a local filesystem
|
|
||||||
|
|
||||||
### Aeternam [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-sncf" target="_blank">/projectdanube/aeternam-xdi-sncf</a> - Aeternam PNR Demo: SNCF
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-db" target="_blank">/projectdanube/aeternam-xdi-db</a> - Aeternam PNR Demo: Deutsche Bahn
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-tests" target="_blank">/projectdanube/aeternam-xdi-tests</a> - XDI experimentation for ÆTERNAM / ÆVATAR
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-maria" target="_blank">/projectdanube/aeternam-xdi-maria</a> - Aeternam PNR Demo: Maria
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-webshop" target="_blank">/projectdanube/aeternam-xdi-webshop</a> - Aeternam PNR Demo: Webshop
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-oebb" target="_blank">/projectdanube/aeternam-xdi-oebb</a> - Aeternam PNR Demo: ÖBB
|
|
||||||
|
|
||||||
### XDI Cloud [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-cloudcards" target="_blank">/projectdanube/xdi2-cloudcards</a> - XDI Cloud Card Viewer
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-messenger" target="_blank">/projectdanube/xdi2-messenger</a> - XDI Cloud Messenger
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-manager" target="_blank">/projectdanube/xdi2-manager</a> - XDI Cloud Manager
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-pixel" target="_blank">/projectdanube/xdi2-pixel</a> - Tool to translate a personal cloud policy language (Pixel) to XDI link contracts.
|
|
||||||
|
|
||||||
### XDI Server Deployed Via [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-grizzly" target="_blank">/projectdanube/xdi2-server-grizzly</a> - XDI2 Server deployed via Grizzly
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-mina" target="_blank">/projectdanube/xdi2-server-mina</a> - XDI2 Server deployed via Apache MINA
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-netty" target="_blank">/projectdanube/xdi2-server-netty</a> - XDI2 Server deployed via netty
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-undertow" target="_blank">/projectdanube/xdi2-server-undertow</a> - XDI2 Server deployed via Undertow
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-vertx" target="_blank">/projectdanube/xdi2-server-vertx</a> - XDI2 Server deployed via vert.x
|
|
||||||
|
|
||||||
### Sevices [**^**](#contents)
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service" target="_blank">/projectdanube/xdi2-connect-service</a> - This is a "Connect Service" component for the XDI Browser binding.
|
|
||||||
* <a href="https://github.com/projectdanube/neustar-discovery-service" target="_blank">/projectdanube/neustar-discovery-service</a> - Neustar XDI Discovery Service based on XRI Resolution
|
|
||||||
- Forked from neustarpc/neustar-discovery-service
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service-war" target="_blank">/projectdanube/xdi2-connect-auth-service-war</a> - "Authorization Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service-war" target="_blank">/projectdanube/xdi2-connect-service-war</a> - "Connect Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-grapheditor" target="_blank">/projectdanube/xdi-grapheditor</a> - An XDI Graph Editor
|
|
||||||
-Forked from neustar/xdi-grapheditor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service" target="_blank">/projectdanube/xdi2-connect-auth-service</a> - This is a "Connect Auth Service" component for the XDI Browser binding.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Digital Bazaar [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock" target="_blank">/digitalbazaar/bedrock</a> - Bedrock: A core foundation for rich Web applications.
|
|
||||||
* <a href="https://github.com/digitalbazaar/forge" target="_blank">/digitalbazaar/forge</a> - A native implementation of TLS in Javascript and tools to write crypto-based and network-heavy webapps
|
|
||||||
* <a href="https://github.com/digitalbazaar/veres-delta-docs" target="_blank">/digitalbazaar/veres-delta-docs</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/uuid-random" target="_blank">/digitalbazaar/uuid-random</a>
|
|
||||||
|
|
||||||
|
|
||||||
### DB - Identity [**^**](#contents)
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity-composer" target="_blank">/digitalbazaar/bedrock-angular-identity-composer</a> - An bedrock-based AngularJS directive for composing an Identity from a set of credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-identity-http" target="_blank">/digitalbazaar/bedrock-identity-http</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-idp" target="_blank">/digitalbazaar/opencred-idp</a> - Open Credentials Identity Provider and demo websites
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity" target="_blank">/digitalbazaar/bedrock-angular-identity</a> - Bedrock AngularJS Identity Modules
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-identity" target="_blank">/digitalbazaar/bedrock-identity</a> - Bedrock identity
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-idp" target="_blank">/digitalbazaar/bedrock-idp</a> - Bedrock Identity Provider
|
|
||||||
|
|
||||||
### DB - Credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-data-model" target="_blank">/digitalbazaar/vc-data-model</a> - Verifiable Claims Data Model and Representations specification
|
|
||||||
- Forked from w3c/vc-data-model
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-test-suite" target="_blank">/digitalbazaar/vc-test-suite</a> - Verifiable Claims WG Test Suite
|
|
||||||
- Forked from w3c/vc-test-suite
|
|
||||||
* <a href="https://github.com/digitalbazaar/vc-js" target="_blank">/digitalbazaar/vc-js</a> - Verifiable Claims JavaScript library
|
|
||||||
* <a href="https://github.com/digitalbazaar/credentials-io" target="_blank">/digitalbazaar/credentials-io</a> - Library for reading/writing credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-rest" target="_blank">/digitalbazaar/bedrock-credentials-rest</a> - A RESTful API for credential storage
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/bedrock-credential-vocabs</a> - Semantic web vocabularies for processing credentials.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-address-credential-issuer" target="_blank">/digitalbazaar/bedrock-address-credential-issuer</a> - A module for issuing address credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-verifier" target="_blank">/digitalbazaar/opencred-verifier</a> - Open Credentials Verifier JavaScript API
|
|
||||||
* <a href="https://github.com/digitalbazaar/opencred-idp" target="_blank">/digitalbazaar/opencred-idp</a> - Open Credentials Identity Provider and demo websites
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/bedrock-credential-notifications</a> - Notification issuing for credentials.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-mongodb" target="_blank">/digitalbazaar/bedrock-credentials-mongodb</a> - Credential storage in mongodb
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credentials-context" target="_blank">/digitalbazaar/bedrock-credentials-context</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-card-displayer" target="_blank">/digitalbazaar/bedrock-angular-card-displayer</a> - Bedrock displayer for card-based credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credential-handler" target="_blank">/digitalbazaar/bedrock-credential-handler</a> - Credential Handler for DID-based credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-vc-store" target="_blank">/digitalbazaar/bedrock-web-vc-store</a> - A Javascript library for storing Verifiable Credentials for Bedrock web apps
|
|
||||||
* <a href="https://github.com/digitalbazaar/web-vc-query-creator" target="_blank">/digitalbazaar/web-vc-query-creator</a> - A Javascript library providing a simplified API for creating Verifiable Credentials queries for web apps.
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-identity-composer" target="_blank">/digitalbazaar/bedrock-angular-identity-composer</a> - An bedrock-based AngularJS directive for composing an Identity from a set of credentials
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-profile-composer" target="_blank">/digitalbazaar/bedrock-web-profile-composer</a> - A Javascript library for fulfilling Verifiable Credentials queries for Bedrock web apps
|
|
||||||
|
|
||||||
|
|
||||||
### DB - DID
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-whisper" target="_blank">/digitalbazaar/did-whisper</a> - DID whisper
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-whisper-server" target="_blank">/digitalbazaar/did-whisper-server</a> - A simple DID Whisper server
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-web-did-store" target="_blank">/digitalbazaar/bedrock-web-did-store</a> - Enables storage and management of DIDs in a Web App
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-authn-did" target="_blank">/digitalbazaar/bedrock-authn-did</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-ssh" target="_blank">/digitalbazaar/did-ssh</a>
|
|
||||||
bedrock-angular-authn-did
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-cli" target="_blank">/digitalbazaar/did-cli</a> - A client for managing Decentralized Identifiers
|
|
||||||
* <a href="https://github.com/digitalbazaar/did-io" target="_blank">/digitalbazaar/did-io</a> - Decentralized identifier management library for browser and node.js
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-authn-did-jwt" target="_blank">/digitalbazaar/bedrock-authn-did-jwt</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-did-client" target="_blank">/digitalbazaar/bedrock-did-client</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-authn-did-jwt" target="_blank">/digitalbazaar/bedrock-angular-authn-did-jwt</a>
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-credential-handler" target="_blank">/digitalbazaar/bedrock-credential-handler</a> - Credential Handler for DID-based credentials
|
|
||||||
|
|
||||||
|
|
||||||
### DB - Linked Data
|
|
||||||
|
|
||||||
* <a href="https://github.com/digitalbazaar/php-json-ld" target="_blank">/digitalbazaar/php-json-ld</a> - PHP implementation of a JSON-LD Processor and API
|
|
||||||
* <a href="https://github.com/digitalbazaar/pyld" target="_blank">/digitalbazaar/pyld</a> - JSON-LD processor written in Python
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/jsonld.js</a> - A JSON-LD Processor and API implementation in JavaScript
|
|
||||||
* <a href="https://github.com/digitalbazaar/jsonld-signatures" target="_blank">/digitalbazaar/jsonld-signatures</a> - An implementation of the Linked Data Signatures specification for JSON-LD. Works in the browser and node.js.
|
|
||||||
* <a href="https://github.com/digitalbazaar/json-ld" target="_blank">/digitalbazaar/json-ld</a> - A Context-based JSON Serialization for Linked Data
|
|
||||||
* <a href="https://github.com/digitalbazaar/ocapld.js" target="_blank">/digitalbazaar/ocapld.js</a> - Linked Data Capabilities reference implementation
|
|
||||||
* <a href="https://github.com/digitalbazaar/cuckoo-ldp" target="_blank">/digitalbazaar/cuckoo-ldp</a> - Cuckoo Cycle Based Linked Data Proofs
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-ldn-receiver" target="_blank">/digitalbazaar/bedrock-ldn-receiver</a> - Bedrock module for Linked Data Notification Receiver
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-ldn-inbox" target="_blank">/digitalbazaar/bedrock-ldn-inbox</a> - Bedrock module for Linked Data Notification Inboxes
|
|
||||||
* <a href="https://github.com/digitalbazaar/bedrock-angular-ldn" target="_blank">/digitalbazaar/bedrock-angular-ldn</a> - Bedrock AngularJS module for Linked Data Notification Sender+Consumer
|
|
||||||
* <a href="https://github.com/digitalbazaar/" target="_blank">/digitalbazaar/json-ld.org</a> - Forked from json-ld/json-ld.org
|
|
||||||
JSON for Linked Data
|
|
||||||
* <a href="https://github.com/digitalbazaar/flex-ledger" target="_blank">/digitalbazaar/flex-ledger</a> - Forked from web-payments/flex-ledger
|
|
||||||
A decentralized Linked Data Ledger for the Web
|
|
||||||
|
|
||||||
## /WebOfTrustInfo
|
|
||||||
|
|
||||||
>The Web of Trust is a buzzword for a new model of decentralized self-sovereign identity. It’s a phrase that dates back almost twenty-five years, the classic definition derives from PGP.
|
|
||||||
|
|
||||||
\#RebootingWebOfTrust holds bi-annual design workshops where many of the ideas in SSI\DID were formed.
|
|
||||||
|
|
||||||
In advance of each workshop, all participants produce a one-or-two page topic paper on either:
|
|
||||||
|
|
||||||
* A specific problem that they wanted to solve with a web-of-trust solution, and why current solutions (PGP or CA-based PKI) can't address the problem?
|
|
||||||
* A specific solution related to the web-of-trust that you'd like others to use or contribute to?
|
|
||||||
|
|
||||||
The workshop itself also produces technical whitepapers, this Repository holds a record of the progression of thought in SSI, since November, 2015.
|
|
||||||
|
|
||||||
* <a href="Rebooting-Web-of-Trust.md">One Page List of RWoT Literature</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/self-sovereign-identity" target="_blank">/WebOfTrustInfo/self-sovereign-identity</a> - Articles and documents associated with designing and implementing identity technology using self-sovereign identity principles
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/website" target="_blank">/WebOfTrustInfo/website</a> - Website for http://www.WebOfTrust.info
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/community-resilience" target="_blank">/WebOfTrustInfo/community-resilience</a> - Rebooting Web of Trust Community Resilience Team
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/satyrn" target="_blank">/WebOfTrustInfo/satyrn</a> - A Markdown-based JavaScript Sandbox
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/sss" target="_blank">/WebOfTrustInfo/sss</a> - Library for the Shamir secret sharing scheme
|
|
||||||
- Forked from dsprenkels/sss
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/verifiable-news" target="_blank">/WebOfTrustInfo/verifiable-news</a> - TBD: W3C Credentials Community Group repository for curbing "social bots" and mitigating the spread of online misinformation and "fake news".
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/portable-reputation-toolkit" target="_blank">/WebOfTrustInfo/portable-reputation-toolkit</a>
|
|
||||||
|
|
||||||
### RWoT Design Workshop [**^**](#contents)
|
|
||||||
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot1-sf" target="_blank">/WebOfTrustInfo/rwot1-sf</a> - RWOT1 in San Francisco, California (November 2015)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot2-id2020" target="_blank">/WebOfTrustInfo/rwot2-id2020</a> - RWOT2 for the ID2020 UN Summit (May 2016)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot3-sf" target="_blank">/WebOfTrustInfo/rwot3-sf</a> - RWOT3 in San Francisco, California (October 2016)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot4-paris" target="_blank">/WebOfTrustInfo/rwot4-paris</a> - RWOT4 in Paris, France (April 2017)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot5-boston" target="_blank">/WebOfTrustInfo/rwot5-boston</a> - RWOT5 in Boston, Massachusetts (October 2017)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot6-santabarbara" target="_blank">/WebOfTrustInfo/rwot6-santabarbara</a> - RWOT6 in Santa Barbara, California (March 2018)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot7-toronto" target="_blank">/WebOfTrustInfo/rwot7-toronto</a> - RWOT7 in Toronto, Canada (September 2018)
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/rwot8-barcelona" target="_blank">/WebOfTrustInfo/rwot8-barcelona</a> - RWOT8 in Barcelona, Spain (March 2019)
|
|
||||||
|
|
||||||
### RWot BTCR [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-tx-playground.github.io" target="_blank">/WebOfTrustInfo/btcr-tx-playground.github.io</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-did-tools-js" target="_blank">/WebOfTrustInfo/btcr-did-tools-js</a>
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/btcr-hackathon" target="_blank">/WebOfTrustInfo/btcr-hackathon</a> - Virtual hackathon to create spec and code for Bitcoin-based Decentralized Identifiers (DIDs)
|
|
||||||
|
|
||||||
### RWoT Txref Conversion
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-java" target="_blank">/WebOfTrustInfo/txref-conversion-java</a> - Java library for converting txids to txrefs and back
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-js" target="_blank">/WebOfTrustInfo/txref-conversion-js</a> - Javascript library for converting txids to txrefs and back
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/txref-conversion-python" target="_blank">/WebOfTrustInfo/txref-conversion-python</a> - Python library to handle conversion between TxRef(bech32) <-> TxID
|
|
||||||
|
|
||||||
### RWoT Linked Data [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/" target="_blank">/WebOfTrustInfo/schemas</a> - Draft schemas for JSON-LD etc.
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/ld-signatures-java" target="_blank">/WebOfTrustInfo/ld-signatures-java</a> - Java implementation of Linked Data Signatures
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/ld-signatures-python" target="_blank">/WebOfTrustInfo/ld-signatures-python</a> - JSON-LD Signatures with JSON Web Signatures
|
|
||||||
|
|
||||||
|
|
||||||
## /w3c - World Wide Web Consortium [**^**](#contents)
|
|
||||||
|
|
||||||
### /w3c/verifiable-claims - VC Working Group
|
|
||||||
|
|
||||||
<a href="https://lists.w3.org/Archives/Public/public-vc-wg/" target="_blank">Verifiable Claims WG - Mailing List</a> (and archives)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c/verifiable-claims" target="_blank">/w3c/verifiable-claims</a> - W3C Verifiable Claims Working Group.
|
|
||||||
* <a href="https://github.com/w3c/vc-data-model" target="_blank">/w3c/vc-data-model</a> -Verifiable Claims Data Model and Representations specification.
|
|
||||||
* <a href="https://github.com/w3c/vc-use-cases" target="_blank">/w3c/vc-use-cases</a> - Verifiable Claims Use Cases.
|
|
||||||
* <a href="https://github.com/w3c/vc-test-suite" target="_blank">/w3c/vc-test-suite</a> - Verifiable Claims WG Test Suite.
|
|
||||||
* <a href="https://github.com/w3c/vc-imp-guide" target="_blank">/w3c/vc-imp-guide</a> - Verifiable Credentials Implementation Guidelines
|
|
||||||
|
|
||||||
### /w3c-ccg - Credentials Community Group [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="http://lists.w3.org/Archives/Public/public-credentials/" target="_blank">Public mailing list for the Credentials Community Group</a> (and archives) - Anyone may read or write to this list.
|
|
||||||
* <a href="https://github.com/w3c-ccg/meetings" target="_blank">/w3c-ccg/meetings</a> CCG Meeting Transcripts
|
|
||||||
* <a href=" https://github.com/w3c-ccg/community" target="_blank">/w3c-ccg/community</a> - CCG Community Repo
|
|
||||||
* <a href="https://github.com/w3c-ccg/announcements" target="_blank">/w3c-ccg/announcements</a> - CCG Announcements
|
|
||||||
* <a href="https://github.com/w3c-ccg/w3c-ccg-process" target="_blank">/w3c-ccg/w3c-ccg-process</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/registries-process" target="_blank">/w3c-ccg/registries-process</a>
|
|
||||||
|
|
||||||
#### CCG - DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-primer" target="_blank">/w3c-ccg/did-primer</a> - A Primer for Decentralized Identifiers
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-spec" target="_blank">/w3c-ccg/did-spec</a> - Decentralized Identifier (DID) 1.0 Specification - Data Model and Syntax
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-resolution" target="_blank">/w3c-ccg/did-resolution</a> Spec 1.0
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-use-cases" target="_blank">/w3c-ccg/did-use-cases</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-method-registry" target="_blank">/w3c-ccg/did-method-registry</a> - a list of all known DID Methods and their current level of maturity.
|
|
||||||
* <a href="https://github.com/w3c-ccg/didm-btcr" target="_blank">/w3c-ccg/didm-btcr</a> - WORK ITEM: BTCR DID Method Spec
|
|
||||||
* <a href="https://github.com/w3c-ccg/didm-veres-one" target="_blank">/w3c-ccg/didm-veres-one</a> - Veres One Decentralized Identifier Method Specification
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-wg-proposal" target="_blank">/w3c-ccg/did-wg-proposal</a> - Proposal to W3C membership for a DID Working Group.
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-wg-charter" target="_blank">/w3c-ccg/did-wg-charter</a> - EXPERIMENTAL charter for the W3C Decentralized Identifier Working Group
|
|
||||||
* <a href="https://github.com/w3c-ccg/did-hackathon-2018" target="_blank">/w3c-ccg/did-hackathon-2018</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/data-minimization" target="_blank">/w3c-ccg/data-minimization</a> - Data Minimization, Selective Disclosure, and Progressive Trust
|
|
||||||
* <a href="https://github.com/w3c-ccg/credential-handler-api" target="_blank">/w3c-ccg/credential-handler-api</a>
|
|
||||||
* <a href="https://github.com/w3c-ccg/amira" target="_blank">/w3c-ccg/amira</a> - Amira Engagement Model.
|
|
||||||
* <a href="https://github.com/w3c-ccg/functional-identity" target="_blank">/w3c-ccg/functional-identity</a>
|
|
||||||
|
|
||||||
#### CCG - Verifiable Credentials [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/w3c-ccg/vc-status-registry" target="_blank"></a> - REGISTRY: The Verifiable Credentials Status Scheme Registry.
|
|
||||||
* <a href="https://github.com/w3c-ccg/edu_occ_verifiable_credentials" target="_blank">/w3c-ccg/edu_occ_verifiable_credentials</a> - WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials.
|
|
||||||
* <a href="https://github.com/w3c-ccg/vc-examples" target="_blank">/w3c-ccg/vc-examples</a> - WORK ITEM: Verifiable Credentials Examples
|
|
||||||
|
|
||||||
#### CCG - Linked Data [**^**](#contents)
|
|
||||||
* <a href="https://github.com/w3c-ccg/ocap-ld" target="_blank">/w3c-ccg/ocap-ld</a> - WORK ITEM: Linked Data Object Capabilities specification
|
|
||||||
* <a href="https://github.com/w3c-ccg/ld-cryptosuite-registry" target="_blank">/w3c-ccg/ld-cryptosuite-registry</a> - REGISTRY: Linked Data Keys Registry
|
|
||||||
|
|
||||||
### Digital Verification Community Group [**^**](#contents)
|
|
||||||
> The mission of the W3C Digital Verification Community Group is to study, design, promote, and deploy systems that increase trust on the Web.
|
|
||||||
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/w3c-dvcg.github.io" target="_blank">/w3c-dvcg/w3c-dvcg.github.io</a> - Landing site for W3C Digital Verification Community Group.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/multibase" target="_blank">/w3c-dvcg/multibase</a> -
|
|
||||||
An IETF Internet Draft for the Multibase data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/hashlink" target="_blank">/w3c-dvcg/hashlink</a> - An IETF Internet Draft for the Hashlink data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/multihash" target="_blank">/w3c-dvcg/multihash</a> - An IETF Internet Draft for the Multihash data format
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/security-vocab" target="_blank">/w3c-dvcg/security-vocab</a> - The Linked Data Security Vocabulary
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-rsa2018" target="_blank">/w3c-dvcg/lds-rsa2018</a> -
|
|
||||||
Linked Data Signature Suite created in 2018
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/http-signatures" target="_blank">/w3c-dvcg/http-signatures</a> - Signing HTTP Messages specification
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/ld-proofs" target="_blank">/w3c-dvcg/ld-proofs</a> -
|
|
||||||
Linked Data Proofs Specification
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/ld-signatures" target="_blank">/w3c-dvcg/ld-signatures</a> - Linked Data Signatures enable digital signatures on Linked Data
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-ed25519-2018" target="_blank">/w3c-dvcg/lds-ed25519-2018</a> - Linked Data Signature Suite for Ed25519 2018
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-merkleproof2017" target="_blank">/w3c-dvcg/lds-merkleproof2017</a> - 2017 Signature suite for doing Merkle Proofs.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-redaction2016" target="_blank">/w3c-dvcg/lds-redaction2016</a> - Linked Data Signature Suite created in 2016 for performing Redacted
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/http-signatures-audit" target="_blank">/w3c-dvcg/http-signatures-audit</a> - Security considerations for HTTP Signatures specification.
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-koblitz2016" target="_blank">/w3c-dvcg/lds-koblitz2016</a> - Linked Data Signature Suite for the Koblitz Elliptic Curve 2016
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-pseudonymous2016/" target="_blank">/w3c-dvcg/lds-pseudonymous2016/</a>
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/lds-rsa2016/" target="_blank">/w3c-dvcg/lds-rsa2016/</a>
|
|
||||||
|
|
||||||
### /opencreds [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/opencreds/website" target="_blank">/opencreds/website</a> - The Open Credentials Website
|
|
||||||
* <a href="https://github.com/opencreds/minutes" target="_blank">/opencreds/minutes</a> -
|
|
||||||
Text and audio meeting minutes for W3C Credentials Community Group
|
|
||||||
|
|
||||||
## Spidchain [**^**](#contents)
|
|
||||||
|
|
||||||
* [Spidchain.com](http://www.spidchain.com/) -Blockchain for Self Sovereign Identity
|
|
||||||
|
|
||||||
### Spid Bitcoin [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/spidchain-btcr" target="_blank">/SpidChain/spidchain-btcr</a> - An implementation of the btcr standard for self sovereign distributed digital identity
|
|
||||||
* <a href="https://github.com/SpidChain/electrumx" target="_blank">/SpidChain/electrumx</a> Forked from kyuupichan/electrumx
|
|
||||||
- Alternative implementation of spesmilo/electrum-server
|
|
||||||
* <a href="https://github.com/SpidChain/btcr-spv" target="_blank">/SpidChain/btcr-spv</a> - Poc of an SPV implementation of BTCR
|
|
||||||
* <a href="https://github.com/SpidChain/satoshis-wheel-of-fortune" target="_blank">/SpidChain/satoshis-wheel-of-fortune</a> - Pick a name from a list randomly in a provably honest way
|
|
||||||
* <a href="https://github.com/SpidChain/txref-conversion-js" target="_blank">/SpidChain/txref-conversion-js</a> - Forked from WebOfTrustInfo/txref-conversion-js
|
|
||||||
- Javascript library for converting txids to txrefs and back
|
|
||||||
|
|
||||||
|
|
||||||
### Spid Ethereum [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/eth-lightwallet" target="_blank">/SpidChain/eth-lightwallet</a> - Forked from ConsenSys/eth-lightwallet
|
|
||||||
- Lightweight JS Wallet for Node and the browser
|
|
||||||
* <a href="https://github.com/SpidChain/truffle" target="_blank">/SpidChain/truffle</a> - Forked from trufflesuite/truffle
|
|
||||||
- A development framework for Ethereum
|
|
||||||
* <a href="https://github.com/SpidChain/VotingSystem" target="_blank">/SpidChain/VotingSystem</a> - A dapp, library and smart contract to notarize votes on the ethereum blockchain
|
|
||||||
* <a href="https://github.com/SpidChain/ethers-wallet" target="_blank">/SpidChain/ethers-wallet</a> - Forked from ethers-io/ethers.js
|
|
||||||
- Complete Ethereum wallet implementation and library in JavaScript.
|
|
||||||
* <a href="https://github.com/SpidChain/nodejs-ethereum" target="_blank">/SpidChain/nodejs-ethereum</a> - Forked from b9lab/nodejs-ethereum
|
|
||||||
Example of using NodeJs with Ethereum
|
|
||||||
|
|
||||||
### Spid Hackathon [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SpidChain/chainpass" target="_blank">/SpidChain/chainpass</a> - App for Trenitalia hackathon - 09 / 16 / 2017 - Rome
|
|
||||||
* <a href="https://github.com/SpidChain/vipPrice" target="_blank">/SpidChain/vipPrice</a> - #internationalhackathon #spidchain
|
|
||||||
|
|
||||||
### Democracy Earth [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/democracyearth/self" target="_blank">/democracyearth/self</a> - Cryptgraphic peer authentication.
|
|
||||||
>We keep the identity 100% in the hands of the user. We took the decentralization approach to create a login protocol and Cryptography (SHA-256 hash function) to ensure security and identity. We allow users to show the information that they want, when they want and to they want.
|
|
||||||
* <a href="https://github.com/democracyearth/sovereign" target="_blank">/democracyearth/sovereign</a> - earth_americas Blockchain democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/paper" target="_blank">/democracyearth/paper</a> - On decentralized digital democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/community." target="_blank">/democracyearth/community.</a> - earth_americas Be an Ambassador or Student Ambassador anywhere in the world.
|
|
||||||
* <a href="https://github.com/democracyearth/vote" target="_blank">/democracyearth/vote</a> - Smart contracts for vote token.
|
|
||||||
* <a href="https://github.com/democracyearth/dapp" target="_blank">/democracyearth/dapp</a> - Liquid democracy smart contract implementation
|
|
||||||
* <a href="https://github.com/democracyearth/blockchain" target="_blank">/democracyearth/blockchain</a> - A block chain for democracy.
|
|
||||||
* <a href="https://github.com/democracyearth/handbook" target="_blank">/democracyearth/handbook</a> - Forked from loomio/loomio-coop-handbook
|
|
||||||
- Handbook for Democracy Earth Foundation
|
|
||||||
* <a href="https://github.com/democracyearth/press-kit" target="_blank">/democracyearth/press-kit</a> - A set of resources about the Democracy Earth Foundation to share with journalists and media.
|
|
||||||
* <a href="https://github.com/democracyearth/exodus" target="_blank">/democracyearth/exodus</a> - Smart contracts enabling a Universal Basic Income for self-sovereign citizens earth_americas
|
|
||||||
* <a href="https://github.com/democracyearth/party" target="_blank">/democracyearth/party</a> - horse Trojan political party.
|
|
||||||
* <a href="https://github.com/democracyearth/balance-keeper" target="_blank">/democracyearth/balance-keeper</a> - token balance keeper daemon.
|
|
||||||
* <a href="https://github.com/democracyearth/dapp" target="_blank">/democracyearth/dapp</a> - Liquid democracy smart contract implementation
|
|
||||||
* <a href="https://github.com/democracyearth/DesignSystem" target="_blank">/democracyearth/DesignSystem</a>
|
|
||||||
* <a href="https://github.com/democracyearth/vzla-propone-cambio" target="_blank">/democracyearth/vzla-propone-cambio</a> - venezuelaVenezuela sera libre
|
|
||||||
* <a href="https://github.com/democracyearth/advocacy" target="_blank">/democracyearth/advocacy</a> - Toolkit with static and live documents that will concentrate relevant information aimed at advocacy efforts for liquid democracy around the world.
|
|
||||||
* <a href="https://github.com/democracyearth/protocol" target="_blank">/democracyearth/protocol</a> - Forked from arikan/bitcoin-voting
|
|
||||||
- bulb Cryptocurrency voting schema.
|
|
||||||
* <a href="https://github.com/democracyearth/dips" target="_blank">/democracyearth/dips</a> - Democracy Improvement Proposals
|
|
||||||
* <a href="https://github.com/democracyearth/micropayment-voting" target="_blank">/democracyearth/micropayment-voting</a> - eagle Vote as bitcoin micropayment.
|
|
||||||
* <a href="https://github.com/democracyearth/concept" target="_blank">/democracyearth/concept</a> - Forked from makingdevs/mecate-democra
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Ethereum [**^**](#contents)
|
|
||||||
* [ERC: Lightweight Identity #1056](https://github.com/ethereum/EIPs/issues/1056) —This ERC describes a standard for creating and updating identities with a limited use of blockchain resources. An identity can have an unlimited number of delegates and attributes associated with it. Identity creation is as simple as creating a regular key pair ethereum account, which means that it's fee (no gas costs) and all ethereum accounts are valid identities. Furthermore this ERC is fully DID compliant.
|
|
||||||
* [ERC-1484: Digital Identity Aggregator #1495](https://github.com/ethereum/EIPs/issues/1495) —A protocol for aggregating digital identity information that's broadly interoperable with existing, proposed, and hypothetical future digital identity standards.
|
|
||||||
* [ERC725](https://github.com/ethereum/EIPs/issues/725)
|
|
||||||
* The following describes standard functions for a unique identifiable proxy account to be used by humans, groups, organisations, objects and machines
|
|
||||||
* [ERC735](https://github.com/ethereum/EIPs/issues/735) - The following describes standard functions for adding, removing and holding of claims.
|
|
||||||
- These claims can attested from third parties (issuers) or self attested.
|
|
||||||
* [EIP712](https://github.com/ethereum/EIPs/blob/f29527ab39357548b06b29e937a48f06ae099de7/EIPS/eip-712.md) - This is a standard for hashing and signing of typed structured data
|
|
||||||
* [ERC: Ethereum Claims Registry #780](https://github.com/ethereum/EIPs/issues/780)
|
|
||||||
* [EIP-1078](https://github.com/ethereum/EIPs/blob/ed621645c8f3bc5756492f327cda015f35d9f8da/EIPS/eip-1078.md) -
|
|
||||||
This presents a method to replace the usual signup/login design pattern with a minimal ethereum native scheme, that doesn’t require passwords, backing up private keys nor typing seed phrases.
|
|
||||||
|
|
||||||
### Cryptonomica [**^**](#cryptonomica-)
|
|
||||||
|
|
||||||
[![](http://i.imgur.com/moVyrrt.png)](https://cryptonomica.github.io)
|
|
||||||
|
|
||||||
* <a href="https://github.com/Cryptonomica/cryptonomica" target="_blank">/Cryptonomica/cryptonomica</a> - Cryptonomica keys server
|
|
||||||
* <a href="https://github.com/Cryptonomica/cryptonomica.github.io" target="_blank">/Cryptonomica/cryptonomica.github.io</a> - Cryptonomica frontend
|
|
||||||
* <a href="https://github.com/Cryptonomica/arbitration-rules" target="_blank">/Cryptonomica/arbitration-rules</a> - Cryptonomica Arbitration Rules
|
|
||||||
* <a href="https://github.com/Cryptonomica/dappathon-tlv" target="_blank">/Cryptonomica/dappathon-tlv</a>
|
|
||||||
* <a href="https://github.com/Cryptonomica/Ethereum-IdentityVerification" target="_blank">/Cryptonomica/Ethereum-IdentityVerification</a> - Indentity verification and KYC for Ethereum blockchain
|
|
||||||
* <a href="https://github.com/Cryptonomica/ethnode.cryptonomica.net" target="_blank">/Cryptonomica/ethnode.cryptonomica.net</a> - Ethereum node with API on nodejs and web3.js
|
|
||||||
* <a href="https://github.com/Cryptonomica/Ethereum-IdentityProof" target="_blank">/Cryptonomica/Ethereum-IdentityProof</a> - Smart contract for Ethereum's account owner verification using Cryptonomica.net
|
|
||||||
* <a href="https://github.com/Cryptonomica/international-arbitration-law" target="_blank">/Cryptonomica/international-arbitration-law</a> - Repository for collecting information about international arbitration law and practice
|
|
||||||
|
|
||||||
|
|
||||||
### Assorted Ethereum Apps [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/XLNT/meirl" target="_blank">/XLNT/meirl</a> - Counterfactual and Upgradable Self-Sovereign Identity for Ethereum, using Gnosis Safe
|
|
||||||
|
|
||||||
## uPort [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/developers" target="_blank">/uport-project/developers</a> - Developer portal for documentation and application management
|
|
||||||
* <a href="https://github.com/uport-project/specs" target="_blank">/uport-project/specs</a> - uPort Protocol Specs
|
|
||||||
* <a href="https://github.com/uport-project/uport-connect" target="_blank">/uport-project/uport-connect</a> - Main uPort library for front end developers
|
|
||||||
* <a href="https://github.com/uport-project/eth-typed-data" target="_blank">/uport-project/eth-typed-data</a> - A javascript library for working with typed structured data as defined by EIP712
|
|
||||||
* <a href="https://github.com/uport-project/uport-transports" target="_blank">/uport-project/uport-transports</a> - Set up communication channels between your app and a uPort client to handle requests and responses.
|
|
||||||
* <a href="https://github.com/uport-project/webcard" target="_blank">/uport-project/webcard</a> - Transaction Sharing
|
|
||||||
* <a href="https://github.com/uport-project/demo" target="_blank">/uport-project/demo</a> - uPort Demo dApp
|
|
||||||
* <a href="https://github.com/uport-project/uport-lite" target="_blank">/uport-project/uport-lite</a> - Lightweight uport registry lookup
|
|
||||||
* <a href="https://github.com/uport-project/eslint-config-uport" target="_blank">/uport-project/eslint-config-uport</a> - Shareable eslint config for uport libraries
|
|
||||||
* <a href="https://github.com/uport-project/uPort-live" target="_blank">/uport-project/uPort-live</a> - Forked from Siunami/uPort-live
|
|
||||||
* <a href="https://github.com/uport-project/uport-wordpress-plugin" target="_blank">/uport-project/uport-wordpress-plugin</a> - A Passwordless Login for uPort and Wordpress
|
|
||||||
* <a href="https://github.com/uport-project/community-projects" target="_blank">/uport-project/community-projects</a> - A list of community hackathon projects and other experiments.
|
|
||||||
* <a href="https://github.com/uport-project/udoor" target="_blank">/uport-project/udoor</a> - uPort Door Management
|
|
||||||
* <a href="https://github.com/uport-project/uport-bounties" target="_blank">/uport-project/uport-bounties</a>- A Library of uPort Bounties
|
|
||||||
* <a href="https://github.com/dconroy/CityKey" target="_blank">/dconroy/CityKey</a> - Adding uPort support to Chicago CityKey, adding all the benefits of Self Sovereign Identity to municipal services. http://citykeychained.com
|
|
||||||
|
|
||||||
### uPort DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-resolver" target="_blank">/uport-project/ethr-did-resolver</a> - DID resolver for Ethereum Addresses with support for key management
|
|
||||||
* <a href="https://github.com/uport-project/secp256k1-did-resolver" target="_blank">/uport-project/secp256k1-did-resolver</a> - Resolve DID documents for secp256k1 public keys
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-driver" target="_blank">/uport-project/uport-did-driver</a> - Driver for the uPort DID method
|
|
||||||
* <a href="https://github.com/uport-project/eth-did-resolver" target="_blank">/uport-project/eth-did-resolver</a> - DID resolver for Ethereum Addresses
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did" target="_blank">/uport-project/ethr-did</a> - Create ethr DIDs
|
|
||||||
* <a href="https://github.com/uport-project/ethr-did-registry" target="_blank">/uport-project/ethr-did-registry</a> - Backing for an experimental DID method
|
|
||||||
* <a href="https://github.com/uport-project/did-resolver" target="_blank">/uport-project/did-resolver</a> - Generic did-resolver
|
|
||||||
* <a href="https://github.com/uport-project/https-did-resolver" target="_blank">/uport-project/https-did-resolver</a> - DID resolver for HTTPS domains
|
|
||||||
* <a href="https://github.com/uport-project/nacl-did" target="_blank">/uport-project/nacl-did</a> - Light weight DID method, complete with Identity Creation tools, encryption and JWT signing
|
|
||||||
* <a href="https://github.com/uport-project/did-jwt" target="_blank">/uport-project/did-jwt</a> - Create and verify uPort and DID compliant JWT's in Javascript
|
|
||||||
* <a href="https://github.com/uport-project/uport-did-resolver" target="_blank">/uport-project/uport-did-resolver</a> - DID resolver for uPort identities
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Identification [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/openid" target="_blank">/uport-project/openid</a> - uPort openid
|
|
||||||
* <a href="https://github.com/uport-project/kmnid" target="_blank">/uport-project/kmnid</a> - A kotlin implementation of MNID
|
|
||||||
* <a href="https://github.com/uport-project/uport-registry" target="_blank">/uport-project/uport-registry</a> - Core uPort registry contract for linking attributes to uPort identities.
|
|
||||||
* <a href="https://github.com/uport-project/uport-chrome-extension" target="_blank">/uport-project/uport-chrome-extension</a> - An experiment to test decentralized identity in a Browser Extension environment.
|
|
||||||
* <a href="https://github.com/uport-project/infrastructure" target="_blank">/uport-project/infrastructure</a> - Support services for Self-Sovereign Identity
|
|
||||||
* <a href="https://github.com/uport-project/mnid" target="_blank">/uport-project/mnid</a> - Multi Network Identifier - spec and reference implementation
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Mobile [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-sdk" target="_blank">/uport-project/uport-android-sdk</a> - Collections of tools and helper libraries for android to issue and use identities on the uPort platform
|
|
||||||
* <a href="https://github.com/uport-project/uport-android-signer" target="_blank">/uport-project/uport-android-signer</a> - android ETH signer library to be used by uport app and sdk
|
|
||||||
* <a href="https://github.com/uport-project/uport-android" target="_blank">/uport-project/uport-android</a> - uPort app for android - under construction
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-demo" target="_blank">/uport-project/uport-ios-demo</a> - Demo iPhone app using uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile-issues" target="_blank">/uport-project/uport-mobile-issues</a> - This repository is a place for developers to report and track status of issues reported while using the uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-mobile" target="_blank">/uport-project/uport-mobile</a> - uPort mobile app
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-sdk" target="_blank">/uport-project/uport-ios-sdk</a> - uPort iOS SDK in Swift
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-core-eth" target="_blank">/uport-project/uport-ios-core-eth</a> - iOS Ethereum Toolkit for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/uport-ios-openssl" target="_blank">/uport-project/uport-ios-openssl</a> - iOS OpenSSL Framework for uPort SDK
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner" target="_blank">/uport-project/UPTEthereumSigner</a> - Ethereum signer library for iOS
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### uPort Lambda [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/lambda-chasqui" target="_blank">/uport-project/lambda-chasqui</a> - running_man Messenger service running_man
|
|
||||||
* <a href="https://github.com/uport-project/lambda-agora" target="_blank">/uport-project/lambda-agora</a> - An open public space where an assembly of applications can share details and be discovered (pre-alpha)
|
|
||||||
* <a href="https://github.com/uport-project/lambda-champagne" target="_blank">/uport-project/lambda-champagne</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-niscani" target="_blank">/uport-project/lambda-niscani</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-sensui" target="_blank">/uport-project/lambda-sensui</a> - uPort tx funding service
|
|
||||||
* <a href="https://github.com/uport-project/" target="_blank">/uport-project/lambda-caleuche</a> - Caleuche. Event Hub Service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-idgraph" target="_blank">/uport-project/lambda-idgraph</a>
|
|
||||||
* <a href="https://github.com/uport-project/lambda-olorun" target="_blank">/uport-project/lambda-olorun</a> - uPort private network support
|
|
||||||
* <a href="https://github.com/uport-project/lambda-fatima" target="_blank">/uport-project/lambda-fatima</a> - uPort badge event attestor
|
|
||||||
* <a href="https://github.com/uport-project/lambda-pututu" target="_blank">/uport-project/lambda-pututu</a> - Push notification service
|
|
||||||
* <a href="https://github.com/uport-project/lambda-nisaba" target="_blank">/uport-project/lambda-nisaba</a> - Lambda functions for anti-sybill
|
|
||||||
* <a href="https://github.com/uport-project/lambda-unnu" target="_blank">/uport-project/lambda-unnu</a> - Creator of Identities
|
|
||||||
|
|
||||||
### uPort React [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-signer" target="_blank">/uport-project/react-native-uport-signer</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-signer-demo" target="_blank">/uport-project/react-native-signer-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/uport-react-native-demo" target="_blank">/uport-project/uport-react-native-demo</a>
|
|
||||||
* <a href="https://github.com/uport-project/react-native-uport-connect" target="_blank">/uport-project/react-native-uport-connect</a> - Library for integrating uPort into your React Native app
|
|
||||||
* <a href="https://github.com/uport-project/react-uport-box" target="_blank">/uport-project/react-uport-box</a> - Truffle and React/Redux boilerplate with uPort Connect
|
|
||||||
* <a href="https://github.com/uport-project/react-native-passcode-android" target="_blank">/uport-project/react-native-passcode-android</a> - Forked from aldigjo/react-native-passcode-android
|
|
||||||
|
|
||||||
### uPort Assorted [**^**](#contents)
|
|
||||||
* <a href="https://github.com/uport-project/champagne-dapp" target="_blank">/uport-project/champagne-dapp</a> - Champagne Project dApp
|
|
||||||
* <a href="https://github.com/uport-project/tweetnacl-k" target="_blank">/uport-project/tweetnacl-k</a> - kotlin implementation of tweetnacl
|
|
||||||
* <a href="https://github.com/uport-project/sample-data-generator" target="_blank">/uport-project/sample-data-generator</a>
|
|
||||||
* <a href="https://github.com/uport-project/bck-wallet" target="_blank">/uport-project/bck-wallet</a>
|
|
||||||
* <a href="https://github.com/uport-project/UPTEthereumSigner-Example" target="_blank">/uport-project/UPTEthereumSigner-Example</a> - Example app and unit tests for the UPTEthereumSigner repo
|
|
||||||
* <a href="https://github.com/uport-project/lastblock" target="_blank">/uport-project/lastblock</a> - Daemon that alerts when a new block is mined
|
|
||||||
* <a href="https://github.com/uport-project/service-tests" target="_blank">/uport-project/service-tests</a> - Test servers from the outside
|
|
||||||
* <a href="https://github.com/uport-project/paper" target="_blank">/uport-project/paper</a>
|
|
||||||
* <a href="https://github.com/uport-project/swift-rlp" target="_blank">/uport-project/swift-rlp</a> - Recursive Length Prefix in Swift - CocoaPod
|
|
||||||
* <a href="https://github.com/uport-project/SwiftKeccak" target="_blank">/uport-project/SwiftKeccak</a> - Ethereum compatible Keccak hash for Swift
|
|
||||||
* <a href="https://github.com/uport-project/ed2curve-js" target="_blank">/uport-project/ed2curve-js</a> - Convert Ed25519 signing keys into Curve25519 Diffie-Hellman keys
|
|
||||||
|
|
||||||
|
|
||||||
## Jolocom [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/jolocom/docs" target="_blank">/jolocom/docs</a> - Documentation
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-app" target="_blank">/jolocom/smartwallet-app</a> - A decentralized self sovereign identity solution developed by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-lib" target="_blank">/jolocom/jolocom-lib</a> - Library for interacting with the identity solution provided by Jolocom.
|
|
||||||
* <a href="https://github.com/jolocom/jolocom-did-driver" target="_blank">/jolocom/jolocom-did-driver</a> - Universal Resolver DID Driver for the did:jolo identity space
|
|
||||||
* <a href="https://github.com/jolocom/generic-backend" target="_blank">/jolocom/generic-backend</a> - A generic backend implementation that makes use of the Jolocom Library for authentication, and for issuing credentials.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso" target="_blank">/jolocom/demo-sso</a> - A simple example web application integrating the Jolocom library for authentication.
|
|
||||||
* <a href="https://github.com/jolocom/demo-sso-mobile" target="_blank">/jolocom/demo-sso-mobile</a> - An example mobile application in React Native that showcases the interaction flows between the Smartwallet and another mobile app.
|
|
||||||
* <a href="https://github.com/jolocom/cred-types-jolocom-demo" target="_blank">/jolocom/cred-types-jolocom-demo</a> - Collection of metadata definitions for the demo Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/react-native-build-config" target="_blank">/jolocom/react-native-build-config</a> - Expose native build config to JS (android only for now)
|
|
||||||
* <a href="https://github.com/jolocom/credTypes-jolocom-core" target="_blank">/jolocom/credTypes-jolocom-core</a> - Collection of metadata definitions for the core Jolocom credential types.
|
|
||||||
* <a href="https://github.com/jolocom/fueling-service" target="_blank">/jolocom/fueling-service</a> - Simple express service that can wire ether to requester.
|
|
||||||
* <a href="https://github.com/jolocom/registry-contract" target="_blank">/jolocom/registry-contract</a> - A basic smart contract on top of the Ethereum network that registers mappings between DID and IPFS DDO hashes.
|
|
||||||
* <a href="https://github.com/jolocom/smartwallet-webid-proxy" target="_blank">/jolocom/smartwallet-webid-proxy</a> - WebID proxy service
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Learning Machine [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/learningmachine/stage.blockcerts.github.io" target="_blank">/learningmachine/stage.blockcerts.github.io</a> - Web site
|
|
||||||
- Forked from blockchain-certificates/blockchain-certificates.github.io
|
|
||||||
* <a href="https://github.com/learningmachine/polymer-redux" target="_blank">/learningmachine/polymer-redux</a> - An example use-case to showcase the state/view abstraction in Polymer 3, LitElement and Redux context
|
|
||||||
* <a href="https://github.com/learningmachine/ajv" target="_blank">/learningmachine/ajv</a> -The fastest JSON-Schema Validator. Supports draft-06
|
|
||||||
- Forked from epoberezkin/ajv
|
|
||||||
* <a href="https://github.com/learningmachine/Foundatio" target="_blank">/learningmachine/Foundatio</a> - Pluggable foundation blocks for building distributed apps.
|
|
||||||
- Forked from FoundatioFx/Foundatio
|
|
||||||
|
|
||||||
### Blockcerts [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockcerts-verifier" target="_blank">/blockchain-certificates/blockcerts-verifier</a> - A Blockcerts verifier and viewer
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-issuer" target="_blank">/blockchain-certificates/cert-issuer</a> - Issues Blockcerts using either the Bitcoin or Ethereum blockchain
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-verifier" target="_blank">/blockchain-certificates/cert-verifier</a> - Python library for verifying Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-schema" target="_blank">/blockchain-certificates/cert-schema</a> - The schema for Blockcerts
|
|
||||||
- Forked from IMSGlobal/cert-schema
|
|
||||||
* <a href="https://github.com/blockchain-certificates/assets" target="_blank">/blockchain-certificates/assets</a>
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-verifier-js" target="_blank">/blockchain-certificates/cert-verifier-js</a> - Javascript library for verifying Blockcerts Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-tools" target="_blank">/blockchain-certificates/cert-tools</a> -Command line tools for designing certificate templates and instantiating a certificate batch
|
|
||||||
* <a href="https://github.com/blockchain-certificates/obi-baking" target="_blank">/blockchain-certificates/obi-baking</a> - Example of baking a blockcert into an Open Badge
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-core" target="_blank">/blockchain-certificates/cert-core</a>
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-test-resources" target="_blank">/blockchain-certificates/wallet-test-resources</a> - These are resources used to test implementations of the evolving blockcerts certificate standard and issuer conventions.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/pyld" target="_blank">/blockchain-certificates/pyld</a> - JSON-LD processor written in Python
|
|
||||||
- Forked from digitalbazaar/pyld
|
|
||||||
* <a href="https://github.com/blockchain-certificates/archived-cert-store" target="_blank">/blockchain-certificates/archived-cert-store</a> - Storage library and service for Blockchain Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/openbadges-validator-core" target="_blank">/blockchain-certificates/openbadges-validator-core</a> - Open Badges validation in python
|
|
||||||
- Forked from IMSGlobal/openbadges-validator-core
|
|
||||||
* <a href="https://github.com/blockchain-certificates/PodSpecs" target="_blank">/blockchain-certificates/PodSpecs</a> - A listing of CocoaPod .podspec files for all pods created in the Blockchain Certificates project.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/openbadges-bakery" target="_blank">/blockchain-certificates/openbadges-bakery</a> - An OpenBadges image baking library that works with PNGs and SVGs
|
|
||||||
- Forked from mozilla/openbadges-bakery
|
|
||||||
|
|
||||||
#### Blockcerts Json [**^**](#contents)
|
|
||||||
* <a href="https://github.com/blockchain-certificates/JSONLD" target="_blank">/blockchain-certificates/JSONLD</a> - An iOS framework for processing JSON-LD files.
|
|
||||||
* <a href="https://github.com/blockchain-certificates/JSONLDProcessor" target="_blank">/blockchain-certificates/JSONLDProcessor</a> - An iOS framework for processing JSON-LD files.
|
|
||||||
|
|
||||||
|
|
||||||
#### Blockcerts Web [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-viewer" target="_blank">/blockchain-certificates/cert-viewer</a> - A web app for viewing and validating Blockchain Certificates
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockcerts-playground.github.io" target="_blank">/blockchain-certificates/blockcerts-playground.github.io</a> - In-browser tool to experiment with Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/blockchain-certificates.github.io" target="_blank">/blockchain-certificates/blockchain-certificates.github.io</a>
|
|
||||||
- Forked from mmistakes/minimal-mistakes
|
|
||||||
* <a href="https://github.com/blockchain-certificates/cert-web-component" target="_blank">/blockchain-certificates/cert-web-component</a> - A web component for displaying blockchain certificates.
|
|
||||||
|
|
||||||
#### Blockcerts Mobile [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-android" target="_blank">/blockchain-certificates/wallet-android</a> - An Android app for Blockcerts
|
|
||||||
* <a href="https://github.com/blockchain-certificates/BlockcertsFramework-iOS" target="_blank">/blockchain-certificates/BlockcertsFramework-iOS</a> - An iOS wallet for viewing, validating, and sharing certs
|
|
||||||
* <a href="https://github.com/blockchain-certificates/wallet-iOS" target="_blank">/blockchain-certificates/wallet-iOS</a> - An iOS wallet for Blockcerts
|
|
||||||
|
|
||||||
|
|
||||||
## Sovrin Foundation [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin.org" target="_blank">/sovrin-foundation/sovrin.org</a> - the foundation web site
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin" target="_blank">/sovrin-foundation/sovrin</a>
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-sip" target="_blank">/sovrin-foundation/sovrin-sip</a> - controlled techical docs/standards for Sovrin Foundation
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sov-docs-conf" target="_blank">/sovrin-foundation/sov-docs-conf</a> - A repository containing the code that builds the Sovrin documentation website's shared repository sidebar
|
|
||||||
* <a href="https://github.com/sovrin-foundation/ssi-protocol" target="_blank">/sovrin-foundation/ssi-protocol</a> - Document the interactions and conventions that make self-sovereign identity interoperable.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/protocol" target="_blank">/sovrin-foundation/protocol</a>
|
|
||||||
* <a href="https://github.com/sovrin-foundation/steward-tools" target="_blank">/sovrin-foundation/steward-tools</a> - tools for Sovrin steward
|
|
||||||
* <a href="https://github.com/sovrin-foundation/token-plugin" target="_blank">/sovrin-foundation/token-plugin</a> - source code and tests for Sovrin Ledger plugins
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-test-automation" target="_blank">/sovrin-foundation/sovrin-test-automation</a> - quality assurance automation for Sovrin repos.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/agent-sdk" target="_blank">/sovrin-foundation/agent-sdk</a> - Reference Agent
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-connector-preview" target="_blank">/sovrin-foundation/sovrin-connector-preview</a> - Forked from evernym/sovrin-connector-preview
|
|
||||||
* <a href="https://github.com/sovrin-foundation/pipeline-test" target="_blank">/sovrin-foundation/pipeline-test</a> - Test integrations, hooks and build pipelines.
|
|
||||||
|
|
||||||
|
|
||||||
### Sovrin - Indy [**^**](#contents)
|
|
||||||
* <a href="https://github.com/sovrin-foundation/indy-dev" target="_blank">/sovrin-foundation/indy-dev</a> - Forked from michaeldboyd/indy-dev</a> - This is a quick way to setup a development environment to experiment with IndySDK
|
|
||||||
* <a href="https://github.com/sovrin-foundation/libsovtoken" target="_blank">/sovrin-foundation/libsovtoken</a> - This is a payment handler library to work with libindy. It may one day be merged into libindy.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/sovrin-indy-android-dependencies" target="_blank">/sovrin-foundation/sovrin-indy-android-dependencies</a> - indy-android-dependencies
|
|
||||||
* <a href="https://github.com/sovrin-foundation/connector-app" target="_blank">/sovrin-foundation/connector-app</a> - Reference mobile edge agent for use with the Sovrin Network built from Hyperledger Indy.
|
|
||||||
* <a href="https://github.com/sovrin-foundation/indy-android-dependencies" target="_blank">/sovrin-foundation/indy-android-dependencies</a> - Dependencies required to build indy-sdk
|
|
||||||
|
|
||||||
|
|
||||||
## /decentralized-identity - DIF [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/decentralized-identity.github.io" target="_blank">/decentralized-identity/decentralized-identity.github.io</a> - Site for the open source, community-driven group of dev and organizations working toward an interoperable, decentralized identity ecosystem
|
|
||||||
* <a href="https://github.com/decentralized-identity/org" target="_blank">/decentralized-identity/org</a> - DIF docs, wiki, and organizational material
|
|
||||||
* <a href="https://github.com/decentralized-identity/credential-manifest" target="_blank">/decentralized-identity/credential-manifest</a> - Format that normalizes the definition of requirements for the issuance of a credential
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-registrar" target="_blank">/decentralized-identity/universal-registrar</a> - Specifications and implementation of a universal identifier registrar
|
|
||||||
* <a href="https://github.com/decentralized-identity/attestations" target="_blank">decentralized-identity/attestations</a> - Attestation API implementations for various languages and platforms.
|
|
||||||
|
|
||||||
### DIF - DID [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-methods" target="_blank">/decentralized-identity/did-methods</a> - DID Method specs, docs, and materials
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-typescript" target="_blank">/decentralized-identity/did-common-typescript
|
|
||||||
</a> - A common bundle of shared code and modules for working with DIDs, DID Documents, and other DID-related activities
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-csharp" target="_blank">/decentralized-identity/did-security-csharp</a> - C# implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-security-typescript" target="_blank">/decentralized-identity/did-security-typescript</a> - Typescript implementation of DID security and privacy controls
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-common-java" target="_blank">/decentralized-identity/did-common-java</a> - Shared DID Java library.
|
|
||||||
* <a href="https://github.com/decentralized-identity/ua-web-extension" target="_blank">/decentralized-identity/ua-web-extension</a> - Basic web extension version of a DID User Agent
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-recovery" target="_blank">/decentralized-identity/did-recovery</a> - Various methods for DID recovery
|
|
||||||
* <a href="https://github.com/decentralized-identity/web-polyfills" target="_blank">/decentralized-identity/web-polyfills</a> - Polyfills for proposed or emerging DID-centric Web APIs
|
|
||||||
* <a href="https://github.com/decentralized-identity/" target="_blank">/decentralized-identity/</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/http-did-auth-proxy" target="_blank">/decentralized-identity/http-did-auth-proxy</a> - Forked from bcgov/http-did-auth-proxy
|
|
||||||
DID Auth HTTP proxy.
|
|
||||||
|
|
||||||
### DIF - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/did-auth-jose" target="_blank">/decentralized-identity/did-auth-jose</a> - JOSE-based implementation of DID Authenticated Encryption
|
|
||||||
|
|
||||||
### DIF - Sidetree [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-ipfs" target="_blank">/decentralized-identity/sidetree-ipfs</a> - IPFS module for storing and accessing Sidetree entity operation data via content addressable storage
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-core" target="_blank">/decentralized-identity/sidetree-core</a> - The blockchain-agnostic server implementation of the Sidetree protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/sidetree-bitcoin" target="_blank">/decentralized-identity/sidetree-bitcoin</a> - Blockchain-specific code for the Sidetree-based DID Method implementation on Bitcoin
|
|
||||||
* <a href="https://github.com/decentralized-identity/ion" target="_blank">/decentralized-identity/ion</a> - DID Method implementation using the Sidetree protocol on top of Bitcoin
|
|
||||||
|
|
||||||
### DIF - Hub [**^**](#contents)
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js-sample" target="_blank">/decentralized-identity/hub-sdk-js-sample</a> - Sample app demonstrating use of the DIF Identity Hub JavaScript SDK.
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-sdk-js" target="_blank">/decentralized-identity/hub-sdk-js</a> - JavaScript SDK for interacting with Identity Hubs
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-common-js" target="_blank">/decentralized-identity/hub-common-js</a> - Common interfaces for working with Identity Hubs in JavaScript/TypeScript
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-core" target="_blank">/decentralized-identity/hub-node-core</a> - Node.js implementation of the Identity Hub interfaces, business logic, and replication protocol.
|
|
||||||
* <a href="https://github.com/decentralized-identity/identity-hub" target="_blank">/decentralized-identity/identity-hub</a> - Storage and compute nodes for decentralized identity data and interactions
|
|
||||||
* <a href="https://github.com/decentralized-identity/hub-node-reference" target="_blank">/decentralized-identity/hub-node-reference</a> - The official Identity Hub reference implementation bundle for Node.js
|
|
||||||
|
|
||||||
### DIF - Uniresolver [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver" target="_blank">/decentralized-identity/universal-resolver</a> - Universal Resolver implementation and drivers.
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-frontend" target="_blank">/decentralized-identity/universal-resolver-frontend</a> - Frontend web UI for Universal Resolver
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-python" target="_blank">/decentralized-identity/universal-resolver-python</a>
|
|
||||||
* <a href="https://github.com/decentralized-identity/universal-resolver-java" target="_blank">/decentralized-identity/universal-resolver-java</a>
|
|
||||||
|
|
||||||
## Veres One [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/veres-one/veres-one" target="_blank">/veres-one/veres-one</a> - A ledger for acquiring and managing decentralized identifiers
|
|
||||||
* <a href="https://github.com/veres-one/did-veres-one" target="_blank">/veres-one/did-veres-one</a> - A Decentralized Identifier utility library for Veres One
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-validator" target="_blank">/veres-one/veres-one-validator</a> - A ledger validator that accepts either signatures or proof of work
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-context" target="_blank">/veres-one/veres-one-context</a>
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-consensus-continuity-elector-selection" target="_blank">/veres-one/veres-one-consensus-continuity-elector-selection</a>
|
|
||||||
* <a href="https://github.com/veres-one/did-client-veres-one" target="_blank">/veres-one/did-client-veres-one</a> - DID client APIs for Veres One
|
|
||||||
* <a href="https://github.com/veres-one/docs.veres.one" target="_blank">/veres-one/docs.veres.one</a> - Documentation for the Veres One Project
|
|
||||||
* <a href="https://github.com/veres-one/status.testnet.veres.one" target="_blank">/veres-one/status.testnet.veres.one</a> - Testnet status dashboard website
|
|
||||||
* <a href="https://github.com/veres-one/veres-one-project" target="_blank">/veres-one/veres-one-project</a>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## /hyperledger Indy [**^**](#contents)
|
|
||||||
* [/indy-plenum](https://github.com/hyperledger/indy-plenum) - Byzantine Fault Tolerant Protocol [[**wiki**](https://github.com/hyperledger/indy-plenum/wiki)]
|
|
||||||
> "Byzantine fault tolerance is a sub-field of fault tolerance research inspired by the Byzantine Generals' Problem, which is a generalized version of the Two Generals' Problem."
|
|
||||||
* [Storage components](https://github.com/hyperledger/indy-plenum/blob/master/docs/storage.md) - As of now, RocksDB is used as a key-value database for all Storages.
|
|
||||||
* [/indy-sdk](https://github.com/hyperledger/indy-sdk) - Everything needed to build applications that interact with an Indy distributed identity ledger.
|
|
||||||
* [MAINTAINERS.md](https://github.com/hyperledger/indy-sdk/blob/master/MAINTAINERS.md)
|
|
||||||
* [/indy-node](https://github.com/hyperledger/indy-node) - The server portion of a distributed ledger purpose-built for decentralized identity.
|
|
||||||
* [/indy-anoncreds](https://github.com/hyperledger/indy-anoncreds) - Anonymous credentials protocol implementation in python
|
|
||||||
* [/indy-agent](https://github.com/hyperledger/indy-agent) - reference agents and associated tools.
|
|
||||||
* [/indy-test-automation](https://github.com/hyperledger/indy-test-automation) - Automation tools for testing of Indy Project components.
|
|
||||||
* [/indy-post-install-automation](https://github.com/hyperledger/indy-post-install-automation)
|
|
||||||
* [/indy-hipe](https://github.com/hyperledger/indy-hipe) -
|
|
||||||
Hyperledger Indy Project Enhancements
|
|
||||||
* https://indy.readthedocs.io/projects/hipe/en/latest/
|
|
||||||
* [/indy-crypto](https://github.com/hyperledger/indy-crypto) - shared crypto library for Hyperledger Indy components. To be:
|
|
||||||
* [/ursa](https://github.com/hyperledger/ursa) [[**ϟ**](https://www.hyperledger.org/blog/2018/12/04/welcome-hyperledger-ursa)][[**ϟ**](https://www.coindesk.com/hyperledger-launches-cryptography-toolbox-for-blockchain-developers)]
|
|
||||||
> "includes the Hyperledger Indy-Crypto code base that is the building block for anonymous credentials, the verifiable credentials protocol, in indy-sdk used by the Sovrin Network. [...] We are hopeful the shared library will help other platforms better incorporate and use ZKP-based credentials and leverage Sovrin for their identity component." (From Nathan George on Sovrin Telegram) [[**wiki**](https://wiki.hyperledger.org/projects/ursa)]
|
|
||||||
|
|
||||||
### IDChain [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ID-Chain/IEA-API" target="_blank">/ID-Chain/IEA-API</a> - Institutional Edge Agent Generic API
|
|
||||||
* <a href="https://github.com/ID-Chain/Common" target="_blank">/ID-Chain/Common</a> - Common Repository for IdentityChain Project
|
|
||||||
* <a href="https://github.com/ID-Chain/tlabshack" target="_blank">/ID-Chain/tlabshack</a> - Repository to hold files for the tlabshack hackathon
|
|
||||||
* <a href="https://github.com/ID-Chain/ID-Chain.github.io" target="_blank">/ID-Chain/ID-Chain.github.io</a> - Documentation site for IdentityChain Project
|
|
||||||
* <a href="https://github.com/ID-Chain/Cloud-Agent" target="_blank">/ID-Chain/Cloud-Agent</a> - Indy Cloud Agent using Google Firebase Cloud Messaging
|
|
||||||
* <a href="https://github.com/ID-Chain/Chamber-Of-Commerce" target="_blank">/ID-Chain/Chamber-Of-Commerce</a> - Institutional Edge Agent Legacy Example (Verifier + Issuer)
|
|
||||||
* <a href="https://github.com/ID-Chain/Government" target="_blank">/ID-Chain/Government</a> - Institutional Edge Agent Legacy Example (Initial Issuer)
|
|
||||||
* <a href="https://github.com/ID-Chain/IEA-Admin-UI" target="_blank">/ID-Chain/IEA-Admin-UI</a> - Admin User Interface to manage the Institutional Edge Agent API
|
|
||||||
* <a href="https://github.com/ID-Chain/Schema-Extensions" target="_blank">/ID-Chain/Schema-Extensions</a> - High level Schema Extensions (Compiler & Checker)
|
|
||||||
* <a href="https://github.com/ID-Chain/Mobile-Edge-Agent" target="_blank">/ID-Chain/Mobile-Edge-Agent</a> - Mobile Edge Agent Application
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### /IBM-Blockchain-Identity [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-tutorial-sandbox" target="_blank">/IBM-Blockchain-Identity/indy-tutorial-sandbox</a> - Forked from brycecurtis/indy-tutorial-sandbox
|
|
||||||
A turnkey, Docker-based sandbox that enables quick and easy exploration of Hyperledger Indy concepts.
|
|
||||||
|
|
||||||
<a href="https://github.com/IBM-Blockchain-Identity/indy-ssivc-tutorial" target="_blank">/IBM-Blockchain-Identityindy-ssivc-tutorial</a> - A turnkey, Docker-based tutorial for help developers get acquainted with Self-Sovereign Identity and Verifiable Credentials.
|
|
||||||
|
|
||||||
|
|
||||||
## Verifiable Organizations Network [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/BC-Policy-Framework-For-GitHub" target="_blank">/bcgov/BC-Policy-Framework-For-GitHub</a> - Policy information for BC Government employees using GitHub
|
|
||||||
* <a href="https://github.com/bcgov/design-system" target="_blank">/bcgov/design-system</a> - British Columbia Government Design System for Digital Services
|
|
||||||
|
|
||||||
### BCGov - VON [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/TheOrgBook" target="_blank">/bcgov/TheOrgBook</a> - A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
|
||||||
* <a href="https://github.com/bcgov/von" target="_blank">/bcgov/von</a> - Verifiable Organizations Network
|
|
||||||
* <a href="https://github.com/bcgov/von-connector" target="_blank">/bcgov/von-connector</a> - Verifiable Organization Network Connector
|
|
||||||
* <a href="https://github.com/bcgov/von-network" target="_blank">/bcgov/von-network</a> - A portable development level Indy Node network.
|
|
||||||
* <a href="https://github.com/bcgov/von-ledger-explorer" target="_blank">/bcgov/von-ledger-explorer</a> - The VON Ledger Explorer
|
|
||||||
* <a href="https://github.com/bcgov/dFlow" target="_blank">/bcgov/dFlow</a> - A demonstration of the verifiable organization network showing a new restaurant gathering the permits necessary to open.
|
|
||||||
|
|
||||||
#### VON - Indy [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/indy-catalyst" target="_blank">/bcgov/indy-catalyst</a> - Hyperledger Indy Catalyst is a set of application level software components designed to accelerate the adoption of trustworthy entity to entity communications.
|
|
||||||
* <a href="https://github.com/bcgov/indy-sdk-postgres-storage" target="_blank">/bcgov/indy-sdk-postgres-storage</a> - PostgreSQL plug-in for use with the indy-sdk
|
|
||||||
|
|
||||||
#### VON - Agents [**^**](#contents)
|
|
||||||
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/von-personal-agent" target="_blank">/bcgov/von-personal-agent</a> - A personal agent for the von network.
|
|
||||||
* <a href="https://github.com/bcgov/VON-ESB-DRS-Agent" target="_blank">/bcgov/VON-ESB-DRS-Agent</a> - Piloting the Dispute Resolution Suite with connections to the OrgBook
|
|
||||||
* <a href="https://github.com/bcgov/von-agent-template" target="_blank">/bcgov/von-agent-template</a> - Template for a von-x based agent
|
|
||||||
* <a href="https://github.com/bcgov/von-bc-registries-agent" target="_blank">/bcgov/von-bc-registries-agent</a>
|
|
||||||
* <a href="https://github.com/bcgov/von_agent" target="_blank">/bcgov/von_agent</a> Forked from PSPC-SPAC-buyandsell/von_agent - VON agents using indy-sdk
|
|
||||||
|
|
||||||
|
|
||||||
### BCGov - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-extension" target="_blank">/bcgov/did-auth-extension</a> - DID Auth browser extension.
|
|
||||||
* <a href="https://github.com/bcgov/http-did-auth-proxy" target="_blank">/bcgov/http-did-auth-proxy</a> - DID Auth HTTP proxy.
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-relying-party" target="_blank">/bcgov/did-auth-relying-party</a> - DID Auth relying party.
|
|
||||||
|
|
||||||
### /PSPC-SPAC-buyandsell [**^**](#contents)
|
|
||||||
**Public Services and Procurement Canada: buyandsell.gc.ca --- Services publics et Approvisionnement Canada : Achatsetventes.gc.ca**
|
|
||||||
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_tails" target="_blank">/PSPC-SPAC-buyandsell/von_tails</a> - Tails file server for von_anchor issuer and holder-prover anchors
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_base" target="_blank">/PSPC-SPAC-buyandsell/von_base</a>
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_anchor" target="_blank">/PSPC-SPAC-buyandsell/von_anchor</a> - VON anchor classes for interaction with sovrin/indy ledger via indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-image" target="_blank">/PSPC-SPAC-buyandsell/von-image</a> - Standard docker images for building VON components
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-x" target="_blank">/PSPC-SPAC-buyandsell/von-x</a> - VON-X is a Python library enabling rapid deployment of Hyperledger Indy credential issuer, holder, and verifier services, particularly for integration with TheOrgBook.
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/didauth" target="_blank">/PSPC-SPAC-buyandsell/didauth</a> - DID authentication by way of HTTP Signatures for Hyperledger Indy agents
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_agent" target="_blank">/PSPC-SPAC-buyandsell/von_agent</a> - VON agents using indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_connector" target="_blank">/PSPC-SPAC-buyandsell/von_connector</a> - service wrapper API per agent, via django application
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/ReferenceVonActuator" target="_blank">/PSPC-SPAC-buyandsell/ReferenceVonActuator</a> - Java implementation of actuator of reference von_connector implementation
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_conx" target="_blank">/PSPC-SPAC-buyandsell/von_conx</a> - Reference implementation (sample) for a VON Connector using tools of VON_X
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/demo-agent" target="_blank">/PSPC-SPAC-buyandsell/demo-agent</a> - agent and api wrapper code base
|
|
||||||
|
|
||||||
## Selfkey Foundation [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkeyfoundation.github.io" target="_blank">/SelfKeyFoundation/selfkeyfoundation.github.io</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-developers" target="_blank">/SelfKeyFoundation/selfkey-developers</a> - SelfKey Developer Site
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-developer-portal" target="_blank">/SelfKeyFoundation/selfkey-developer-portal</a> - Developer Resources for SelfKey SDK's
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-platform" target="_blank">/SelfKeyFoundation/selfkey-platform</a> - Temporarily hosted here until ready for public consumption.
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-download-portal" target="_blank">/SelfKeyFoundation/selfkey-download-portal</a> - Download links and information for SelfKey software releases
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-net" target="_blank">/SelfKeyFoundation/selfkey-net</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/Identity-Wallet" target="_blank">/SelfKeyFoundation/Identity-Wallet</a> - Code for the SelfKey Identity Wallet
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-ui" target="_blank">/SelfKeyFoundation/selfkey-ui</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-simulation" target="_blank">/SelfKeyFoundation/selfkey-simulation</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-payments" target="_blank">/SelfKeyFoundation/selfkey-payments</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-lib" target="_blank">/SelfKeyFoundation/selfkey-lib</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-network-demo" target="_blank">/SelfKeyFoundation/selfkey-network-demo</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-extension" target="_blank">/SelfKeyFoundation/selfkey-extension</a> - SelfKey Extension
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-service" target="_blank">/SelfKeyFoundation/selfkey-service</a> - SelfKey Service
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-aspnetcore-demo" target="_blank">/SelfKeyFoundation/selfkey-aspnetcore-demo</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/face-rec" target="_blank">/SelfKeyFoundation/face-rec</a> - Selfkey Face Recognition API
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/passport-selfkey" target="_blank">/SelfKeyFoundation/passport-selfkey</a>
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-login" target="_blank">/SelfKeyFoundation/selfkey-login</a> - Components for external "log-in with selfkey"
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/matomo" target="_blank">/SelfKeyFoundation/matomo</a> - SelfKey Foundation Matomo server
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/Marketplaces" target="_blank">/SelfKeyFoundation/Marketplaces</a> - Marketplace Applications
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/identity-wallet-mobile" target="_blank">/SelfKeyFoundation/identity-wallet-mobile</a> - The React Native mobile application for SelfKey.
|
|
||||||
|
|
||||||
### Selfkey DID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-did" target="_blank">/SelfKeyFoundation/selfkey-did</a> - Library for DID managemente and issuance and verification of verifiable credentials
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-claim-registry" target="_blank">/SelfKeyFoundation/selfkey-claim-registry</a> - Public claim registry for Selfkey DIDs
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-did-resolver" target="_blank">/SelfKeyFoundation/selfkey-did-resolver</a> - Library for resolving DIDs in SelfKey method space
|
|
||||||
|
|
||||||
### Selfkey SmartContracts [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-commerce" target="_blank">/SelfKeyFoundation/selfkey-commerce</a> - Payment, Escrow and Affiliate Smart Contract Development
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-token" target="_blank">/SelfKeyFoundation/selfkey-token</a> - Crowdsale Smart Contract
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-identity" target="_blank">/SelfKeyFoundation/selfkey-identity</a> - Smart contracts supporting SelfKey identity platform
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-staking" target="_blank">/SelfKeyFoundation/selfkey-staking</a> - Contracts that implement staking and marketplace deposit functionality for SelfKey
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/identity-contracts" target="_blank">/SelfKeyFoundation/identity-contracts</a> - Development on self-sovereign identity and verifiable claims
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-name-registry" target="_blank">/SelfKeyFoundation/selfkey-name-registry</a> - Smart contract for registering names
|
|
||||||
|
|
||||||
### Selfkey Javascript [**^**](#contents)
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/keythereum" target="_blank">/SelfKeyFoundation/keythereum</a> - Forked from ethereumjs/keythereum - Create, import and export Ethereum keys
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-js-client" target="_blank">/SelfKeyFoundation/selfkey-js-client</a> - JavaScript Client Library for integrating Login with SelfKey
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/selfkey-nodejs-demo" target="_blank">/SelfKeyFoundation/selfkey-nodejs-demo</a> - Demo Site For Testing SelfKey Marketplace and LWS Integrations
|
|
||||||
|
|
||||||
### Selfkey Assorted [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/trezor-wallet-provider" target="_blank">/SelfKeyFoundation/trezor-wallet-provider</a> - Forked from HartgerV/trezor-wallet-provider - Trezor wallet provider for the Web3 ProviderEngine
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/lws-app" target="_blank">/SelfKeyFoundation/lws-app</a> - lws-app react app prototype
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/airtable-proxy" target="_blank">/SelfKeyFoundation/airtable-proxy</a> - A proxy service for airtable
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/react-jsonschema-form-material-theme" target="_blank">/SelfKeyFoundation/react-jsonschema-form-material-theme</a> - Widgets and templates using material-ui
|
|
||||||
* <a href="https://github.com/SelfKeyFoundation/react-jsonschema-form" target="_blank">react-jsonschema-form</a> - Forked from rodrigopavezi/react-jsonschema-form
|
|
||||||
A React component for building Web forms from JSON Schema.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Ockam Network [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ockam-network/ockam" target="_blank">/ockam-network/ockam</a> - Tools for building identity, trust and interoperability into connected devices.
|
|
||||||
* <a href="https://github.com/ockam-network/did" target="_blank">/ockam-network/did</a> - A golang package to work with Decentralized Identifiers (DIDs)
|
|
||||||
* <a href="https://github.com/ockam-network/did-method-spec" target="_blank">/ockam-network/did-method-spec</a> - Ockam DID Method Specification
|
|
||||||
|
|
||||||
## Ontology [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/ontio/ontology" target="_blank">/ontio/ontology</a> - Official Go implementation of the Ontology protocol. https://dev-docs.ont.io/#/
|
|
||||||
* <a href="https://github.com/ontio/documentation" target="_blank">/ontio/documentation</a> - Ontology Documents https://ont.io
|
|
||||||
* <a href="https://github.com/ontio/ontology-DID" target="_blank">/ontio/ontology-DID</a> - Ontology decentralized identification protocol based on W3C DID specifications.
|
|
||||||
* <a href="https://github.com/ontio/ontology-crypto" target="_blank">/ontio/ontology-crypto</a>
|
|
||||||
* <a href="https://github.com/ontio/OWallet" target="_blank">/ontio/OWallet</a> - a comprehensive Ontology desktop wallet
|
|
||||||
* <a href="https://github.com/ontio/ontology-dapi" target="_blank">/ontio/ontology-dapi</a> - A lightweight Javascript library for interacting with Ontology node and Ontology wallets
|
|
||||||
* <a href="https://github.com/ontio/ontology-ddxf" target="_blank">/ontio/ontology-ddxf</a> - Distributed data eXchange Framework,which allows to build data marketplaces .
|
|
||||||
|
|
||||||
## TangleID [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/TangleID/TangleID/" target="_blank">/TangleID/TangleID/</a> - Secure self-sovereign identity built on IOTA/Tangle
|
|
||||||
identity
|
|
||||||
* <a href="https://github.com/TangleID/api-examples/" target="_blank">/TangleID/api-examples/</a> - API examples for TangleID
|
|
||||||
* <a href="https://github.com/TangleID/TangleID.github.io/" target="_blank">/TangleID/TangleID.github.io/</a> - TangleID Landing Page
|
|
||||||
* <a href="https://github.com/TangleID/tangleid-client/" target="_blank">/TangleID/tangleid-client/</a> - TangleID Client/Mobile application
|
|
||||||
* <a href="https://github.com/TangleID/demo-site/" target="_blank">/TangleID/demo-site/</a> - A sample web illustrating how to issue claims to the participants with TangleID
|
|
||||||
* <a href="https://github.com/TangleID/docs" target="_blank">/TangleID/docs</a> - TangleID API Documentation
|
|
||||||
- Forked from lord/slate
|
|
||||||
* <a href="https://github.com/TangleID/sample-issuer/" target="_blank">/TangleID/sample-issuer/</a> - TangleID Sample Issuer
|
|
||||||
|
|
||||||
## Simbol [**^**](#contents)
|
|
||||||
|
|
||||||
AR\VR\Mixed
|
|
||||||
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-design" target="_blank">/wearesimbol/simbol-design</a>
|
|
||||||
* <a href="https://github.com/wearesimbol/a-simbol" target="_blank">/wearesimbol/a-simbol</a> - A-Frame component for Simbol
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol" target="_blank">/wearesimbol/simbol</a> - Social and Communications platform WebXR sites with a self-sovereign identity
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-server" target="_blank">/wearesimbol/simbol-server</a> - Simple Web and WebSocket server, specially for sites that use Simbol
|
|
||||||
* <a href="https://github.com/wearesimbol/simbol-demo" target="_blank">/wearesimbol/simbol-demo</a> - Create a fullstack Simbol virtual world very easily
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Assorted [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://github.com/bnelson777/id.ly" target="_blank">/bnelson777/id.ly</a> - Cross-platform self-sovereign identity business card and messaging app
|
|
||||||
|
|
||||||
|
|
||||||
## /peacekeeper/blockchain-identity [**^**](#contents)
|
|
||||||
|
|
||||||
>Projects/companies working on blockchain and identity
|
|
||||||
|
|
||||||
* [/peacekeeper/blockchain-identity](https://github.com/peacekeeper/blockchain-identity) - The Original list of Blockchain Identity Initiatives.
|
|
||||||
|
|
||||||
Maintained by, [Markus Sabadello (Peacekeeper)](https://medium.com/@markus.sabadello)
|
|
||||||
|
|
||||||
## /decentralized-id/decentralized-id.github.io [**^**](#contents)
|
|
||||||
You can join in on the research, and help build this educational resource.
|
|
||||||
|
|
||||||
* [/awesome-decentralized-id](https://github.com/infominer33/awesome-decentralized-id) is becoming
|
|
||||||
* [decentralized-id.com](https://github.com/decentralized-id/decentralized-id.github.io)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
Cover Image Source:
|
|
||||||
|
|
||||||
<a href="https://github.myshopify.com/products/die-cut-github-stickers" target="_blank"><img src="http://i.imgur.com/RhbNQXF.png"/></a><br/>
|
|
||||||
<a href="https://github.myshopify.com/products/die-cut-github-stickers" target="_blank">https://github.myshopify.com/products/die-cut-github-stickers</a>
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id)
|
|
303
docs/index.md
303
docs/index.md
@ -1,303 +0,0 @@
|
|||||||
# Awesome Decentralized Identity [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)
|
|
||||||
*Self-Sovereign, Blockchain and Decentralized Identity Resources*
|
|
||||||
|
|
||||||
>A good self‐sovereign identity system will allow individuals to directly influence how companies, governments, and others correlate our interactions across different services and locations by default. It won’t fix all identity problems nor preclude alternative identity approaches, but it will put the individual in control of most uses of identity and give organizations a simpler, easier, more ethical way to use identity to improve how they provide services and products. When successful, it will not only enable individuals to exercise greater control over how companies and governments keep track of us, it will also illuminate those situations where self‐sovereign identity is restricted, facilitating a conversation about when and where such limits are appropriate. [Joe Andrieu -A Technology‐Free Definition of Self‐Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/blob/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)
|
|
||||||
|
|
||||||
**Note: becoming [decentralized-id.com](https://decentralized-id.com)**
|
|
||||||
>See [/decentralized-id/decentralized-id.github.io](https://github.com/decentralized-id/decentralized-id.github.io)
|
|
||||||
|
|
||||||
For now, this is still home and best maintained.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
[[**T**](#contents)]witter • [[**G**](#contents)]ithub • [[**B**](#contents)]log • [[**wp**](#contents)] whitepaper • [[**D**](#contents)]ocumentation • [[**F**](#contents)]orums • [[**C**](#contents)]hat • [[**tele**](#contents)]gram • [[**web**](#contents)]site
|
|
||||||
• [[**ϟ**](#contents)] related resource • [[**>**](#contents)] related section • [[**^**](#contents)] back to the contents.
|
|
||||||
|
|
||||||
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align=right width="170" height="170"/>
|
|
||||||
|
|
||||||
* [Link Shorthand](#link-shorthand)
|
|
||||||
* [What is Decentralized ID?](#what-is-decentralized-id-)
|
|
||||||
* [What is Self Sovereign Identity?](#self-sovereign-identity-)
|
|
||||||
* [DID Related Web Standards](did-related-web-standards-)
|
|
||||||
* [W3C](#w3c-)
|
|
||||||
* [DID the Decentralized Identifier](#did-the-decentralized-identifier-)
|
|
||||||
* [Verifiable Claims](#verifiable-claims-)
|
|
||||||
* [Decentralized Key Managment DKMS](#decentralized-key-management-dkms-)
|
|
||||||
* [DID Auth](#did-auth-)
|
|
||||||
* [Blockcerts](#blockcerts-)
|
|
||||||
* [Schema](#schema-)
|
|
||||||
* [DID Adoption](#did-adoption-)
|
|
||||||
* [Directory](#directory)
|
|
||||||
* [SSI\DID History](history.md)
|
|
||||||
* [Self Sovereign Identity](self-sovereign-identity)
|
|
||||||
* [GDPR](gdpr)
|
|
||||||
* [Humanitarian](humanitarian.md)
|
|
||||||
* [Identity Related GitHub Repositories](identity-github.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Rebooting Web of Trust](rebooting-web-of-trust.md)
|
|
||||||
* [Media](media.md) - Video, Podcasts and Slideshare
|
|
||||||
* [Decentralized Identity Foundation—DIF](identity-foundation.md)
|
|
||||||
* [Bitcoin](bitcoin.md)
|
|
||||||
* [Spidchain](bitcoin.md#spidchain-)
|
|
||||||
* [Ethereum](ethereum.md)
|
|
||||||
* [ERC-EIP](ethereum.md#erc-eip-)
|
|
||||||
* [uPort](ethereum.md#uport-)
|
|
||||||
* [Jolocom](ethereum.md#jolocom-)
|
|
||||||
* [Spidchain](ethereum.md#spidchain-)
|
|
||||||
* [Indy Ecosystem](indy-ecosystem/)
|
|
||||||
* [Adoption](indy-ecosystem/adoption.md)
|
|
||||||
* [Indy Github](indy-ecosystem/indy-github.md)
|
|
||||||
* [Literature](indy-ecosystem/literature.md)
|
|
||||||
* [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md)
|
|
||||||
* [VON](indy-ecosystem/VON.md)
|
|
||||||
* [Hyperledger Global Forum](hgf-2018/)
|
|
||||||
* [State Sponsored](state-sponsored.md)
|
|
||||||
* [Microsoft](microsoft.md)
|
|
||||||
* [IBM](ibm.md)
|
|
||||||
* [Sources](#sources-)
|
|
||||||
|
|
||||||
|
|
||||||
*Pull Requests Welcome*
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
![](https://i.imgur.com/9KpJRDr.png)
|
|
||||||
|
|
||||||
|
|
||||||
## What is Decentralized ID? [**^**](#contents)
|
|
||||||
|
|
||||||
That's a big question, and what follows are just some notes, until I work out a more thoughtful answer.
|
|
||||||
|
|
||||||
The essence of Decentralized-ID is in creating open standards for a privacy preserving internet-wide identity layer — not owned by any one particular organization, but interoperable between all.
|
|
||||||
|
|
||||||
It's impossible to have a conversation about decentralized-id without discussing blockchain and self sovereign identity:
|
|
||||||
* Self Sovereign Identity principles (with some help from the GDPR) have helped to shape the narrative around putting the identity owner in control over their personal information.
|
|
||||||
* Blockchain fueled longstanding efforts to create a privacy preserving internet-wide identity protocol, and inspired development of decentralized networks for online identification.
|
|
||||||
* The United Nations Sustainable Development Goals (SDGs) have also helped to fueled efforts for a global and widely accessible identity solution.
|
|
||||||
|
|
||||||
—[infominer.id](https://infominer.id)
|
|
||||||
|
|
||||||
## DID-SSI History
|
|
||||||
|
|
||||||
* [The Augmented Social Network and the IDCommons](/history.md#the-augmented-social-network-and-the-idcommons-)
|
|
||||||
* [Internet Identity Workshop—IIW](/history.md#internet-identity-workshop-)
|
|
||||||
* [Bitnation and the United Nations](/history.md#bitnation-and-the-united-nations-)
|
|
||||||
* [#Rebooting-Web-of-Trust (RWoT)](/history.md#rebooting-the-web-of-trust-)
|
|
||||||
* [ID2020 and the GDPR](/history.md#id2020-and-the-gdpr-)
|
|
||||||
* [Additional IID Standards History](/history.md#additional-iid-standards-history-)
|
|
||||||
|
|
||||||
## Self Sovereign Identity [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/3zz62kpl.png)
|
|
||||||
|
|
||||||
|
|
||||||
* [Christopher Allen](http://www.lifewithalacrity.com/)[[**info**](https://christophera.info/)] details the overarching history of internet idenitity standards and outlines [10 Principles of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md) in his seminal work [The Path to Self-Soverereign Identity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html)[[**ϟ**](https://www.coindesk.com/path-self-sovereign-identity/amp/)]
|
|
||||||
* <a href="https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf"><u>A Technlogy-Free Definition of Self-Sovereign Identity</u></a> is a continuation of the discussion started by Allen, offering 3 "Core Characteristics of Sovereign Identity".
|
|
||||||
* [7 Myths of Self Sovereign Identity](https://medium.com/evernym/7-myths-of-self-sovereign-identity-67aea7416b1)
|
|
||||||
* [Inevitable Rise of Self-Sovereign Identity](https://sovrin.org/wp-content/uploads/2018/03/The-Inevitable-Rise-of-Self-Sovereign-Identity.pdf)
|
|
||||||
* [SSIMeetup](http://ssimeetup.org/) [[**S**](https://www.slideshare.net/SSIMeetup/presentations)] [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)] [[**tele**](https://t.me/SSIMeetup)]
|
|
||||||
\- SSI Meetup is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards.
|
|
||||||
* [SSI: A Roadmap for Adoption](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md)
|
|
||||||
* **[/awesome-decentralized-id/self-sovereign-identity](https://github.com/infominer33/awesome-decentralized-id/tree/master/self-sovereign-identity)** SSI documentation is still under development. This directory is to organize existing thought on SSI in one place for ease of study, and the development of new documentation.
|
|
||||||
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
|
|
||||||
|
|
||||||
|
|
||||||
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">0/ “Self-Sovereign Identity: A Progress Report”…</p>— Christopher Allen (@ChristopherA) <a href="https://twitter.com/ChristopherA/status/989120215702261761?ref_src=twsrc%5Etfw">April 25, 2018</a></blockquote>
|
|
||||||
|
|
||||||
|
|
||||||
## DID Related Web Standards [**^**](#contents)
|
|
||||||
|
|
||||||
### W3C [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/Lz6RTysl.png)
|
|
||||||
|
|
||||||
* [World Wide Web Consortium(W3C)](https://www.w3.org/) [[**T**](https://twitter.com/w3c)] [[**G**](https://github.com/w3c)]
|
|
||||||
>The [World Wide Web Consortium (W3C)](https://www.w3.org/Consortium/) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. Led by Web inventor and Director Tim Berners-Lee and CEO Jeffrey Jaffe, W3C's mission is to lead the Web to its full potential.
|
|
||||||
* <a href="https://lists.w3.org/Archives/Public/public-vc-wg/" target="_blank">Verifiable Claims WG - Mailing List</a> (and archives)
|
|
||||||
* [Credentials Community Group](https://www.w3.org/community/credentials/)[[**B**](https://w3c-ccg.github.io/)]
|
|
||||||
* <a href="http://lists.w3.org/Archives/Public/public-credentials/" target="_blank">Public mailing list for the Credentials Community Group</a> (and archives) - Anyone may read or write to this list.
|
|
||||||
* <a href="https://github.com/opencreds/website" target="_blank">/opencreds/website</a>
|
|
||||||
* [opencreds.org — Identity Credentials 1.0](https://opencreds.org/specs/source/identity-credentials/)
|
|
||||||
* <a href="https://sea-region.github.com/w3c-dvcg/w3c-dvcg.github.io" target="_blank">/w3c-dvcg/w3c-dvcg.github.io</a> - Landing site for W3C Digital Verification Community Group. [<a href="https://www.w3.org/community/digital-verification/">**W**</a>]
|
|
||||||
* [JSON-LD 1.0, W3C Recommendation](https://www.w3.org/TR/json-ld/)
|
|
||||||
|
|
||||||
![](https://imgur.com/6MLNgXal.png)\
|
|
||||||
<sup><a href="https://www.youtube.com/watch?v=RllH91rcFdE">The Story of Open SSI Standards - Drummond Reed/Evernym SSIMeetup.org</a>[<b><a href="https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed">ϟ</a></b>]</sup>
|
|
||||||
|
|
||||||
#### DID the Decentralized Identifier [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/7NRcJbq.png"/></a>
|
|
||||||
|
|
||||||
* [A Universally Unique IDentifier (UUID) URN Namespace](https://www.ietf.org/rfc/rfc4122.txt) <-DID's modeled after
|
|
||||||
* [All you need to know about sequential UUID generators](https://blog.2ndquadrant.com/sequential-uuid-generators/)
|
|
||||||
* [w3c- Decentralized Identifiers (DIDs) v0.11](https://w3c-ccg.github.io/did-spec/)
|
|
||||||
* Authors:
|
|
||||||
* [Drummond Reed](https://equalsdrummond.name/) [[**T**](https://twitter.com/drummondreed)] ([Evernym](https://www.evernym.com/))
|
|
||||||
* [Manu Sporney](http://manu.sporny.org/)[[**T**](https://twitter.com/manusporny)] ([Digital Bazaar](https://digitalbazaar.com))
|
|
||||||
* Dave Longley ([Digital Bazaar](https://digitalbazaar.com))
|
|
||||||
* [Christopher Allen](http://www.lifewithalacrity.com/) [[**info**](https://github.com/ChristopherA/info)] ([Blockstream](https://blockstream.com/))
|
|
||||||
* Ryan Grant
|
|
||||||
* [Markus Sabadello (Peacekeeper)](http://mydata2016.org/speaker/markus-sabadello/) [[**T**](https://twitter.com/peacekeeper)] [[**G**](https://github.com/peacekeeper)] [[**B**](https://medium.com/@markus.sabadello)] ([Danube Tech](https://github.com/projectdanube))
|
|
||||||
* [Understanding Decentralized IDs (DIDs)](https://medium.com/@adam_14796/understanding-decentralized-ids-dids-839798b91809)
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/draft-documents/did-primer.md) [[**ϟ**](https://github.com/WebOfTrustInfo/rwot7-fall2018/blob/master/topics-and-advance-readings/did-primer-extended.md)]
|
|
||||||
* [Decentralized IDentifers (DIDs)](https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf)
|
|
||||||
* [Requirements for DIDs](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/requirements-for-dids.pdf)
|
|
||||||
* [DIDs in DPKI](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md)
|
|
||||||
* [What is a DID?](https://docs.google.com/document/d/1Ym85y_bDVN9xkRZ-oD-zlUUIeZjVGWNihfZBk2GQidk/edit)
|
|
||||||
* [The Path from an id (DID) to a Real-Life Something](https://hyperonomy.com/2019/01/04/the-path-from-a-id-did-to-a-real-life-something)
|
|
||||||
|
|
||||||
<a href="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png"><img src="https://hyperonomy.files.wordpress.com/2019/01/path-id-did-real-life-somethings-v0.2-1.png?w=500"/></a>
|
|
||||||
|
|
||||||
#### Verifiable Claims [**^**](#contents)
|
|
||||||
|
|
||||||
<a href="https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf"><img src="https://i.imgur.com/nsZ0X7r.png"/></a>
|
|
||||||
|
|
||||||
|
|
||||||
* [Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) [[**D**](https://www.w3.org/2017/vc/charter.html)]
|
|
||||||
* [Verifiable Claims Data Model 1.0](https://w3c.github.io/vc-data-model/) [[**G**](https://github.com/w3c/vc-data-model)] [[**D**](https://w3c.github.io/vc-use-cases/)]
|
|
||||||
* [Verifiable Credentials 101 for SSI – Tyler Ruff – Webinar 11](http://ssimeetup.org/verifiable-credentials-101-ssi-tyler-ruff-webinar-11/)
|
|
||||||
|
|
||||||
|
|
||||||
### DID Auth [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://imgur.com/XMaq5cil.png)
|
|
||||||
|
|
||||||
|
|
||||||
* [DID Auth and the Little I-am-Me](https://medium.com/@markus.sabadello/did-auth-and-the-little-i-am-me-ec14d757ff09)
|
|
||||||
* [Introduction to DID Auth](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md) [[**ϟ**](http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/)]
|
|
||||||
|
|
||||||
<a href="http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10/"><img src="https://i.imgur.com/YNlk8RY.png"/></a>\
|
|
||||||
http://ssimeetup.org/introduction-did-auth-markus-sabadello-webinar-10
|
|
||||||
|
|
||||||
|
|
||||||
### Decentralized Key Management-Agents [**^**](#Contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/0SLcjUv.png"/>
|
|
||||||
|
|
||||||
* [Decentralized Key Management (DKMS): An Essential Missing Piece of the SSI Puzzle - Drummond Reed](https://www.slideshare.net/SSIMeetup/decentralized-key-management-dkms-an-essential-missing-piece-of-the-ssi-puzzle-drummond-reed)
|
|
||||||
* [Recommendations for Decentralized Key Management Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/dkms-recommendations.md)
|
|
||||||
* [Agent to Agent Communication](https://drive.google.com/file/d/1PHAy8dMefZG9JNg87Zi33SfKkZvUvXvx/view): Daniel Hardman explains the goals of agent to agent communication
|
|
||||||
|
|
||||||
|
|
||||||
![](https://i.imgur.com/5qc1qrG.png)\
|
|
||||||
<sup><a href="http://ssimeetup.org/decentralized-key-management-dkms-essential-missing-piece-ssi-puzzle-drummond-reed-webinar-8/">DKMS - An Essential Missing Piece of the SSI Puzzle. Drummond Reed. SSIMeetup.org</a></sup>
|
|
||||||
|
|
||||||
* <a href="https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2DjfY" target="_blank">Microsoft- Decentralized Identity — Own and Control Your Identity.</a>
|
|
||||||
![](https://i.imgur.com/ozOLCuW.png)
|
|
||||||
|
|
||||||
|
|
||||||
### Blockcerts [**^**](#contents)
|
|
||||||
* [Learning Machine](https://www.learningmachine.com/)
|
|
||||||
* [Academic Credentialing and the Blockchain](https://www.learningmachine.com/academic-credentialing-blockchain/)
|
|
||||||
* [Blockcerts](https://www.blockcerts.org), developed by learning machine is an open standard for issuing and verifying blockchain-based official records; The project offers open-source libraries, tools, and mobile apps. MIT has [issued](https://www.insidehighered.com/news/2017/10/19/mit-introduces-digital-diplomas) digital certificates based on this standard.
|
|
||||||
* [CXC (Carribean) Pilots E-Certificates on the Blockchain](https://www.cxc.org/cxc-pilots-e-certificates-on-the-blockchain/)
|
|
||||||
* [A Decentralized Approach to Blockcerts Credential Revocation](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/blockcerts-revocation.md)
|
|
||||||
|
|
||||||
|
|
||||||
### Schema [**^**](#contents)
|
|
||||||
* [Schema](https://schema.org) — a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet. Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences."
|
|
||||||
|
|
||||||
|
|
||||||
## DID Adoption [**^**](#contents)
|
|
||||||
|
|
||||||
**[DID Method Registry](https://w3c-ccg.github.io/did-method-registry/#the-registry)**
|
|
||||||
* did:example: - [DID Specification](https://w3c-ccg.github.io/did-spec/)
|
|
||||||
* did:btcr: - [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/)
|
|
||||||
* The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
|
|
||||||
* [btcr tx conversion playground](https://weboftrustinfo.github.io/btcr-tx-playground.github.io/)
|
|
||||||
* did:stack: - [Blockstack DID Method](https://github.com/blockstack/blockstack-core/blob/master/docs/blockstack-did-spec.md) [[**ϟ**](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287/9)]
|
|
||||||
- Blockstack is a network for decentralized applications where users own their identities and data. Blockstack utilizes a public blockchain to implement a decentralized naming layer, which binds a user's human-readable username to their current public key and a pointer to their data storage buckets.
|
|
||||||
* did:cnsnt: - Consent
|
|
||||||
* did:erc725: - [erc725 DID Method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Method-erc725.md)
|
|
||||||
* did:ipid: - [IPID DID method](https://did-ipid.github.io/ipid-did-method/)
|
|
||||||
- Implementation of the DID spec over IPFS (Interplanetary File System)
|
|
||||||
* did:life: - [lifeID DID Method](https://lifeid.github.io/did-method-spec/)
|
|
||||||
* did:sov: - [Sovrin DID Method](https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html)
|
|
||||||
* did:uport: - uPort
|
|
||||||
* did:v1: - [Veres One DID Method](https://w3c-ccg.github.io/didm-veres-one/)
|
|
||||||
* [**veres.one**](https://veres.one) — a permissionless public ledger designed specifically for the creation and management of decentralized identifiers (DIDs)
|
|
||||||
* did:dom: - Dominode
|
|
||||||
* did:ont: - [Ontology DID Method](https://github.com/ontio/ontology-DID/blob/master/docs/en/DID-ONT-method.md)
|
|
||||||
* did:vvo: - [Vivvo DID Method](https://vivvo.github.io/vivvo-did-scheme/spec/did-method-spec-template.html)
|
|
||||||
* did:icon: - [ICON DID Method](https://github.com/icon-project/icon-DID/blob/master/docs/ICON-DID-method.md)
|
|
||||||
* did:iwt: - [InfoWallet DID Method](https://github.com/infowallet/did_method/blob/master/did_method.md)
|
|
||||||
* did:ockam: - [Ockam DID Method](https://github.com/ockam-network/did-method-spec/blob/master/README.md)
|
|
||||||
* [did:ockam:](https://medium.com/ockam/an-introduction-to-did-ockam-8626d5aecc53) [[**ϟ**](https://twitter.com/Ockam_io/status/1064589363269365763)]
|
|
||||||
* did:ala: - [Alastria DID Method](https://github.com/alastria/alastria-identity/wiki/Alastria-DID-Method-Specification-(Quorum-version))
|
|
||||||
* did:op: - [Ocean Protocol DID Method](https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md)
|
|
||||||
* did:jlinc: - [JLINC Protocol DID Method](https://did-spec.jlinc.org/)
|
|
||||||
* did:ion: - [ION DID Method](https://github.com/decentralized-identity/ion-did-method)
|
|
||||||
* did:jolo: - Jolocom
|
|
||||||
* did:ethr: - [ETHR DID Method](https://github.com/uport-project/ethr-did-resolver/blob/develop/doc/did-method-spec.md)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
* [Peer DID Method Spec](https://dhh1128.github.io/peer-did-method-spec/index.html)
|
|
||||||
* [@ChristopherA on DID adoption](https://twitter.com/ChristopherA/status/989122017348784130)
|
|
||||||
> "22/ Over a dozen companies and organizations, using multiple blockchains (Bitcoin, Ethereum, Hyperledger, etc.), have committed to deploying DIDs, including IBM, Microsoft, Digital Bazaar, Consensys, Evernym, Learning Machine, British Columbia, and more:" —[How blockchain could solve the internet privacy problem](https://www.computerworld.com/article/3267930/blockchain/how-blockchain-could-solve-the-internet-privacy-problem.html)
|
|
||||||
|
|
||||||
![](https://oneworldidentity.com/wp-content/uploads/2018/10/companies.png)
|
|
||||||
|
|
||||||
2018 Identity Landsacpe brought to you by: [One World Identity](https://oneworldidentity.com/) — independent advisory and digital strategy consultancy focused on trust and the data economy.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Directory [**^**](#contents)
|
|
||||||
Other files and folders within this repository:
|
|
||||||
|
|
||||||
* [SSI\DID History](history.md)
|
|
||||||
* [Self Sovereign Identity](self-sovereign-identity)
|
|
||||||
* [Identity Related GitHub Repositories](identity-github.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Rebooting Web of Trust](rebooting-web-of-trust.md)
|
|
||||||
* [Media](assorted-media.md) - Video, Podcasts and Slideshare
|
|
||||||
* [GDPR](gdpr)
|
|
||||||
* [Humanitarian](humanitarian.md)
|
|
||||||
* [Decentralized Identity Foundation—DIF](identity-foundation.md)
|
|
||||||
* [Bitcoin](bitcoin.md)
|
|
||||||
* [Spidchain](bitcoin.md#spidchain-)
|
|
||||||
* [Ethereum](ethereum.md)
|
|
||||||
* [uPort](ethereum.md#uport-)
|
|
||||||
* [Jolocom](ethereum.md#jolocom-)
|
|
||||||
* [Spidchain](ethereum.md#spidchain-)
|
|
||||||
* [Indy Ecosystem](indy-ecosystem/)
|
|
||||||
* [Adoption](indy-ecosystem/adoption.md)
|
|
||||||
* [Indy Github](indy-ecosystem/indy-github.md)
|
|
||||||
* [Literature](indy-ecosystem/literature.md)
|
|
||||||
* [Sovrin Foundation](indy-ecosystem/sovrin.foundation.md)
|
|
||||||
* [VON](indy-ecosystem/VON.md)
|
|
||||||
* [Hyperledger Global Forum](hgf-2018/)
|
|
||||||
* [State Sponsored](state-sponsored.md)
|
|
||||||
* [IBM](ibm.md)
|
|
||||||
* [Microsoft](microsoft.md)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Sources [**^**](#contents)
|
|
||||||
* [SSI Meetup](http://ssimeetup.org/) [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)][[**ϟ**](https://www.slideshare.net/SSIMeetup/presentations/)]
|
|
||||||
* [IIW-Wiki](https://iiw.idcommons.net/Main_Page)
|
|
||||||
* [wiki.idcommons.net](http://wiki.idcommons.net/Main_Page)
|
|
||||||
* [/WebOfTrustInfo](https://github.com/WebOfTrustInfo/)
|
|
||||||
* [/peacekeeper/blockchain-identity](https://github.com/peacekeeper/blockchain-identity)
|
|
||||||
* [identitywoman.net](https://identitywoman.net/)
|
|
||||||
* [windley.com/tags/identity](http://www.windley.com/tags/identity.shtml)
|
|
||||||
* [Kim Camerons Identity Blog](https://identityblog.com)
|
|
||||||
* [/indy-sovrin-evernym](https://github.com/infominer33/awesome-decentralized-id/blob/master/indy-sovrin-evernym/)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id) ([**^**](#contents))
|
|
||||||
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align="right" width="170" height="170"/></a>
|
|
||||||
|
|
||||||
**Tips Jar**
|
|
||||||
|
|
||||||
BTC— 1GvkjHtiy9LUjVkStnEAXxjhcoS56aCokY
|
|
||||||
|
|
||||||
![](https://imgur.com/yXLLm9Bl.png)
|
|
||||||
|
|
||||||
DOGE— DSzMxfABB8EwKiumzV7YHhS7HTvWAyM7QF
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0zBLoUP.png)
|
|
@ -1,89 +0,0 @@
|
|||||||
# BCGov's Verifiable Organizations Network
|
|
||||||
|
|
||||||
>VON's founding members are governments who are, by law, trusted issuers of data about organizations. The Province of British Columbia, Province of Ontario and the Government of Canada have come together to create the initial services needed to establish VON.
|
|
||||||
>
|
|
||||||
>VON's founders have delivered new Indy-based open source components which form VON's backbone. TheOrgBook is a publicly accessible repository of verifiable claims about organizations. VON-X enables services to verify and issue credentials. - [A Production Government Deployment of Hyperledger Indy- John Jordan, Stephen Curran.](https://hgf18.sched.com/event/G8rm/verifiable-organizations-network-a-production-government-deployment-of-hyperledger-indy-john-jordan-province-of-british-columbia-stephen-curran-cloudcompass-computing-inc)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [VON](#von)
|
|
||||||
* [BCGov Github](#bcgov-github-)
|
|
||||||
* [BCGov - VON](#bcgov---von-)
|
|
||||||
* [VON - Agents](#von-agents-)
|
|
||||||
* [BCGov - DID-Auth](#bcgov---did-auth-)
|
|
||||||
* [PSPC-SPAC-buyandsell](#pspc-spac-buyandsell-) - Public Services and Procurement Canada
|
|
||||||
* [History](#history-)
|
|
||||||
|
|
||||||
|
|
||||||
## VON
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0Mr3YMn.pnghttps://i.imgur.com/CvQnRZ2.png)
|
|
||||||
|
|
||||||
* [Verified Organization Network](https://vonx.io/) [[**G**](https://github.com/bcgov/von)] [[**D**](https://vonx.io/getting_started/von-overview/)] [[**ϟ**](https://www.iaca.org/wp-content/uploads/VON-Using-Blockchain-Technology.pdf)] [[**>**](#Canada)]
|
|
||||||
* "an initiative by the government of British Columbia to create a trusted network of organizational data. It allows organizations to claim credentials that are part of their own digital identity, using a component called [TheOrgBook](https://theorgbook.pathfinder.gov.bc.ca/en/home)[[**G**](https://github.com/bcgov/theorgbook)] that lists entities with their associated public verifiable claims.
|
|
||||||
* [Pan-Canadian Trust Framework](https://github.com/canada-ca/PCTF-CCP)
|
|
||||||
* [Demonstrating the Verifiable Organizations Network (VON)](https://docs.google.com/document/d/1wNnXdQKUtWnx--xw3VQ9Fr2TDa0kUNIBSMmFGR4uoMg/edit#heading=h.kphtj2c176xb)
|
|
||||||
* [BC.gov Verifiable Organizations Network Demo](https://drive.google.com/open?id=1Ms2vKqTe-jVDpz5eWtQIqIz8Jl6TLbSE) (video)
|
|
||||||
* [VON’s Blockchain Basis](https://vonx.io/getting_started/vons-blockchain-basis/)
|
|
||||||
* [Getting Started with Hyperledger Indy](https://cdn.oreillystatic.com/en/assets/1/event/274/Getting%20started%20with%20Hyperledger%20Indy%20Presentation.pdf)
|
|
||||||
* [BCGov Verifiable Organization Network – Impressive Client Demo](https://www.continuumloop.com/bcgov-verifiable-organization-network/)
|
|
||||||
* [bcdevexchange.org/opportunities](https://bcdevexchange.org/opportunities)
|
|
||||||
* [BCovrin](http://138.197.138.255/) - Indy TestNet
|
|
||||||
* [ssimeetup- Overview of Proposed Pan Canadian Trust Framework](https://ssimeetup.org/overview-proposed-pan-canadian-trust-framework-ssi-tim-bouma-webinar-19/) 1\19
|
|
||||||
>The Government of British Columbia and the Government of Ontario have already rolled out a production system using the Sovrin Network for business registration and licensing; together they've issued over 6 million credentials, according to Windley. - [How Blockchain may Kill the Password](https://www.computerworld.com/article/3329962/blockchain/how-blockchain-may-kill-the-password.amp.html)
|
|
||||||
|
|
||||||
## BCGov Github [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/BC-Policy-Framework-For-GitHub" target="_blank">/bcgov/BC-Policy-Framework-For-GitHub</a> - Policy information for BC Government employees using GitHub
|
|
||||||
* <a href="https://github.com/bcgov/design-system" target="_blank">/bcgov/design-system</a> - British Columbia Government Design System for Digital Services
|
|
||||||
|
|
||||||
### BCGov - VON [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/TheOrgBook" target="_blank">/bcgov/TheOrgBook</a> - A public repository of verifiable claims about organizations. A key component of the Verifiable Organization Network.
|
|
||||||
* <a href="https://github.com/bcgov/von" target="_blank">/bcgov/von</a> - Verifiable Organizations Network
|
|
||||||
* <a href="https://github.com/bcgov/von-connector" target="_blank">/bcgov/von-connector</a> - Verifiable Organization Network Connector
|
|
||||||
* <a href="https://github.com/bcgov/von-network" target="_blank">/bcgov/von-network</a> - A portable development level Indy Node network.
|
|
||||||
* <a href="https://github.com/bcgov/von-ledger-explorer" target="_blank">/bcgov/von-ledger-explorer</a> - The VON Ledger Explorer
|
|
||||||
* <a href="https://github.com/bcgov/dFlow" target="_blank">/bcgov/dFlow</a> - A demonstration of the verifiable organization network showing a new restaurant gathering the permits necessary to open.
|
|
||||||
|
|
||||||
### VON - Indy [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/indy-catalyst" target="_blank">/bcgov/indy-catalyst</a> - Hyperledger Indy Catalyst is a set of application level software components designed to accelerate the adoption of trustworthy entity to entity communications.
|
|
||||||
* <a href="https://github.com/bcgov/indy-sdk-postgres-storage" target="_blank">/bcgov/indy-sdk-postgres-storage</a> - PostgreSQL plug-in for use with the indy-sdk
|
|
||||||
|
|
||||||
### VON - Agents [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/bcgov/von-personal-agent" target="_blank">/bcgov/von-personal-agent</a> - A personal agent for the von network.
|
|
||||||
* <a href="https://github.com/bcgov/VON-ESB-DRS-Agent" target="_blank">/bcgov/VON-ESB-DRS-Agent</a> - Piloting the Dispute Resolution Suite with connections to the OrgBook
|
|
||||||
* <a href="https://github.com/bcgov/von-agent-template" target="_blank">/bcgov/von-agent-template</a> - Template for a von-x based agent
|
|
||||||
* <a href="https://github.com/bcgov/von-bc-registries-agent" target="_blank">/bcgov/von-bc-registries-agent</a>
|
|
||||||
* <a href="https://github.com/bcgov/von_agent" target="_blank">/bcgov/von_agent</a> Forked from PSPC-SPAC-buyandsell/von_agent - VON agents using indy-sdk
|
|
||||||
|
|
||||||
|
|
||||||
### BCGov - DID-Auth [**^**](#contents)
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-extension" target="_blank">/bcgov/did-auth-extension</a> - DID Auth browser extension.
|
|
||||||
* <a href="https://github.com/bcgov/http-did-auth-proxy" target="_blank">/bcgov/http-did-auth-proxy</a> - DID Auth HTTP proxy.
|
|
||||||
* <a href="https://github.com/bcgov/did-auth-relying-party" target="_blank">/bcgov/did-auth-relying-party</a> - DID Auth relying party.
|
|
||||||
|
|
||||||
### /PSPC-SPAC-buyandsell [**^**](#contents)
|
|
||||||
Public Services and Procurement Canada: buyandsell.gc.ca --- Services publics et Approvisionnement Canada : Achatsetventes.gc.ca
|
|
||||||
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_tails" target="_blank">/PSPC-SPAC-buyandsell/von_tails</a> - Tails file server for von_anchor issuer and holder-prover anchors
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_base" target="_blank">/PSPC-SPAC-buyandsell/von_base</a>
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_anchor" target="_blank">/PSPC-SPAC-buyandsell/von_anchor</a> - VON anchor classes for interaction with sovrin/indy ledger via indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-image" target="_blank">/PSPC-SPAC-buyandsell/von-image</a> - Standard docker images for building VON components
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von-x" target="_blank">/PSPC-SPAC-buyandsell/von-x</a> - VON-X is a Python library enabling rapid deployment of Hyperledger Indy credential issuer, holder, and verifier services, particularly for integration with TheOrgBook.
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/didauth" target="_blank">/PSPC-SPAC-buyandsell/didauth</a> - DID authentication by way of HTTP Signatures for Hyperledger Indy agents
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_agent" target="_blank">/PSPC-SPAC-buyandsell/von_agent</a> - VON agents using indy-sdk
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_connector" target="_blank">/PSPC-SPAC-buyandsell/von_connector</a> - service wrapper API per agent, via django application
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/ReferenceVonActuator" target="_blank">/PSPC-SPAC-buyandsell/ReferenceVonActuator</a> - Java implementation of actuator of reference von_connector implementation
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/von_conx" target="_blank">/PSPC-SPAC-buyandsell/von_conx</a> - Reference implementation (sample) for a VON Connector using tools of VON_X
|
|
||||||
* <a href="https://github.com/PSPC-SPAC-buyandsell/demo-agent" target="_blank">/PSPC-SPAC-buyandsell/demo-agent</a> - agent and api wrapper code base
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## History [**^**](#contents)
|
|
||||||
|
|
||||||
[![](https://i.imgur.com/Pd6Z2Cf.png)](https://docs.google.com/presentation/d/189DxjNv7EE7KtjkidB6EpwuvO2lIy7kEL-3DWtMAiQg/edit)
|
|
||||||
[Treasury Board Identity Management Policy and Pan-Canadian Trust Framework — Identity Management Policy Workshop](https://docs.google.com/presentation/d/189DxjNv7EE7KtjkidB6EpwuvO2lIy7kEL-3DWtMAiQg/edit)
|
|
||||||
|
|
||||||
* [Pan Canadian Trust Framework](https://diacc.ca/2016/08/11/pctf-overview/) - 2016
|
|
@ -1,32 +0,0 @@
|
|||||||
# Evernym-Sovrin-Indy Adoption
|
|
||||||
|
|
||||||
![](https://i.imgur.com/3sfiarQ.png)
|
|
||||||
|
|
||||||
* [Tykn *The Future of Resilient Identity*](https://tykn.tech/) [[**T**](https://twitter.com/Tykn_tech)][[**G**](https://github.com/tykntech)][[**D**](https://docs.google.com/document/d/1pNRO6aOb5eK4s8PVv7yS4x9TkqrGglCJ4jebU1F3Yzo/edit#)] (Indy\Sovrin)
|
|
||||||
* [Why we use Sovrin](https://blog.tykn.tech/why-we-use-sovrin-ee31dd146a47)
|
|
||||||
* [Illinois Blockchain Initiative](https://illinoisblockchain.tech/) — [partners with Evernym to launch birth registration pilot](https://illinoisblockchain.tech/illinois-partners-with-evernym-to-launch-birth-registration-pilot-f2668664f67c)
|
|
||||||
* [News Release: DHS S&T Awards $749K to Evernym for Decentralized Key Management Research and Development](https://www.dhs.gov/science-and-technology/news/2017/07/20/news-release-dhs-st-awards-749k-evernym-decentralized-key) (Department of Homeland Security)
|
|
||||||
* [Cordenity: Evernym and R3 Partner to make Corda compatible with Indy](http://www.paymentsjournal.com/evernym-r3-partner-apply-self-sovereign-identity-financial-services/) [[**G**](https://github.com/Luxoft/cordentity)][[**D**](https://schd.ws/hosted_files/hgf18/0e/Indy%20Identity%20on%20R3s%20Corda.pdf)]
|
|
||||||
* [Sovrin Foundation, Ontology and Evernym Collaborate on Interoperable Decentralized Identity Networks](https://medium.com/ontologynetwork/blockchain-identity-experts-ontology-evernym-and-the-sovrin-foundation-reach-an-agreement-on-68974ae50bb2)[[**ϟ**](https://globenewswire.com/news-release/2018/10/23/1625715/0/en/Sovrin-Foundation-Ontology-and-Evernym-Collaborate-on-Interoperable-Decentralized-Identity-Networks.html)]
|
|
||||||
* [SecureKey Technologies to explore interoperability between Verified.Me and Hyperledger Indy](https://securekey.com/press-releases/hyperledger-indy/)
|
|
||||||
* [Evernym rolls with auto industry association MOBI to promote SSI in automotive and IoT](https://globenewswire.com/news-release/2018/10/05/1617425/0/en/Evernym-rolls-with-auto-industry-association-MOBI-to-promote-SSI-in-automotive-and-IoT.html)
|
|
||||||
* [15 Industry Leaders Join Evernym’s Global Accelerator to Build the Future of Digital Identity.](https://globenewswire.com/news-release/2018/11/07/1647044/0/en/15-Industry-Leaders-Join-Evernym-s-Global-Accelerator-to-Build-the-Future-of-Digital-Identity.html)
|
|
||||||
> Founding members of the Accelerator include industry leading organizations ATB Financial, IAG, Irish Life, the International Federation of Red Cross, Spark New Zealand, Truu and three provincial and state governments. Collectively, these organizations represent the interests of 100's of millions of individuals worldwide.
|
|
||||||
* [IOTA and Evernym Launch Collaboration Aimed at Making the Internet of Things More Secure](https://globenewswire.com/news-release/2017/08/31/1106292/0/en/IOTA-and-Evernym-Launch-Collaboration-Aimed-at-Making-the-Internet-of-Things-More-Secure.html)
|
|
||||||
* [Digital Identity Innovator Helps Non-Profits Get on the Identity Blockchain](https://globenewswire.com/news-release/2018/09/25/1575928/0/en/Digital-Identity-Innovator-Helps-Non-Profits-Get-on-the-Identity-Blockchain.html)
|
|
||||||
>Evernym is opening its Accelerator program to Non Profit Organization (NPOs) applications. Evernym will waive the $50,000 membership fee it normally charges to participate in the program. A panel of judges will select the successful applicants. The first group of awards will be announced before December 2018 and will include 5 organizations. Further NPO cohorts are already planned for 2019.\
|
|
||||||
>The World Bank estimates over 1 billion persons, usually the most vulnerable, are without formal identity.
|
|
||||||
* [The Sovrin Foundation Names Cisco Founding Steward](https://globenewswire.com/news-release/2018/06/21/1527830/0/en/The-Sovrin-Foundation-Names-Cisco-Founding-Steward.html)
|
|
||||||
* [CULedger partners with decentralized identity innovator Evernym to create MyCUID](https://www.cuinsight.com/press-release/culedger-partners-decentralized-identity-innovator-evernym-create-mycuid)
|
|
||||||
* [Self Sovereign Identity and MyData](https://medium.com/@apoikola/self-sovereign-identity-and-mydata-e1f996a9451)
|
|
||||||
* [Mydata](http://mydata.org/) [[**T**](https://twitter.com/mydataorg)] [[**D**](https://mydata.org/papers/)] [[**D**](https://mydata.org/declaration/)]
|
|
||||||
* goal: to empower individuals with their personal data, thus helping them and their communities develop knowledge, make informed decisions, and interact more consciously and efficiently with each other as well as with organisations."
|
|
||||||
* [Consent](http://www.consent.global/)[[**ϟ**](https://sovrin.org/steward/global-consent/)] — "platform for trusted personal data applications and services, using Ethereum smart contracts to implement decentralized identifiers, verified credentials, consent receipts, a web of trust, and exchange of assets and value."
|
|
||||||
* [Legal Entity Identifier blockchained by a Hyperledger Indy implementation of GraphChain](http://www.graphchain.io/MTSR2018.pdf)
|
|
||||||
>The main idea behind GraphChain is to use blockchain mechanisms on top of an abstract RDF graphs. This paper presents an implementation of GraphChain in the Hyperledger Indy framework. The whole setting is shown to be applied to the RDF graphs containing information about Legal Entity Identifiers (LEIs).
|
|
||||||
* [What the EEA and Hyperledger Collaboration Means for Enterprise Blockchain Development](https://media.consensys.net/what-the-eea-and-hyperledger-collaboration-means-for-enterprise-blockchain-development-31580012cb2)
|
|
||||||
* [IXO World](https://ixo.world/) - Guided by the UN framework of 17 Global Goals to end poverty, protect the planet and ensure prosperity for all, by the year 2030. [[**ϟ**](https://twitter.com/phillipgibb/status/1073247433067556865)]
|
|
||||||
>"Achieving the Sustainable Development Goals demands embracing the data revolution " UN Secretary - General (2014)
|
|
||||||
* <a href="https://twitter.com/Hyperledger/status/1072892591157510148"><img src="https://i.imgur.com/pjs9aPf.png"/></a>
|
|
||||||
* <a href="https://twitter.com/techkuz/status/1074492556434698241"><img src="https://i.imgur.com/txTBlSU.png"/></a>
|
|
||||||
* <a href="https://twitter.com/ByteSizeCapital/status/1046067509869367307"><img src="https://i.imgur.com/WeLDs34.png"/></a>
|
|
@ -1,180 +0,0 @@
|
|||||||
# Awesome Hyperledger Indy Resources [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/images/infominer.png" align="right" width="150" height="140"></a>
|
|
||||||
**Protocol, Governance, Education, Ecosystem**
|
|
||||||
|
|
||||||
This page contains a growing collection of educational resources related to Evernym, the Sovrin Foundation, and Hyperledger Indy. It was born from [/awesome-decentralized-id](../README.md) and contains some of the same material, but is quite exhaustive. As a result, I decided to split this list off to focus on learning about Hyperedger Indy, the Sovrin Foundation, adn Evernym. Its an index for training, developers, students, end users, investors, and enterprise to more easily navigate the digital identity landscape enabled by Hyperledger Indy.
|
|
||||||
|
|
||||||
Since the information is all inter-related, there is some overlapp. Skipping back and forth may be required, depending on your particular interests.
|
|
||||||
|
|
||||||
**[Pull Requests](https://github.com/infominer33/awesome-decentralized-id/blob/master/contributing.md) and\or [Contributions](#brought-to-you-by-the-crypto-librarysuper-source) Welcome**
|
|
||||||
|
|
||||||
|
|
||||||
![](https://i.imgur.com/KFmYHQ6.png)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Introduction](#introduction-)
|
|
||||||
* [Link Shorthand](#link-shorthand-)
|
|
||||||
* [Self Sovereign Identity—SSI](#self-sovereign-identity-)
|
|
||||||
* [Hyperledger Indy](#hyperledger-indy-)
|
|
||||||
* [Additional Indy Related](#additional-indy-related-)
|
|
||||||
* [Wallets](#wallets-)
|
|
||||||
* [Zero Knowledge Proof in Indy](#zero-knowledge-proofs-in-indy-)
|
|
||||||
* [Videos](#video-)
|
|
||||||
* [Podcasts](#podcasts-)
|
|
||||||
* [Directory](#directory-)
|
|
||||||
* [Indy GitHub Repos](indy-github.md)
|
|
||||||
* [Adoption](adoption.md)
|
|
||||||
* [VON.md](VON.md)
|
|
||||||
* [VerifiableOrganizationsNetwork-HGF.md](../hgf-2018/VerifiableOrganizationsNetwork-HGF.md)
|
|
||||||
* [Microledgers-Edgechains-Hardman-HGF.md](../hgf-2018/Microledgers-Edgechains-Hardman-HGF.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Selected Articles Windley.com](literature.md#selected-articles-windleycom-)
|
|
||||||
* [EU General Data Protection Regulation Act](literature.md#eu-general-data-protection-regulation-act-)
|
|
||||||
* [Research Papers](literature.md#research-papers-)
|
|
||||||
* [Reports](literature.md#reports)
|
|
||||||
* [Sources](#sources-)
|
|
||||||
* [<< /awesome-decentralized-id](../README.md)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
|
|
||||||
## Link Shorthand [**^**](#Contents)
|
|
||||||
[[**T**](#Link-Shorthand)]witter • [[**G**](#Link-Shorthand)]ithub • [[**B**](#Link-Shorthand)]log • [[**wp**](#Link-Shorthand)] whitepaper • [[**D**](#Link-Shorthand)]ocumentation • [[**F**](#Link-Shorthand)]orums • [[**C**](#Link-Shorthand)]hat • [[**tele**](Link-Shorthand)]gram • [[**web**](Link-Shorthand)]site
|
|
||||||
• [[**ϟ**](#Link-Shorthand)] related resource • [[**>**](#Link-Shorthand)] related section • [[**>>**]()] related section on awesome-decentralized-id • [[**^**](#Link-Shorthand)] back to the contents.
|
|
||||||
|
|
||||||
![](https://imgur.com/3zz62kpl.png)
|
|
||||||
|
|
||||||
## Introduction [**^**](#Contents)
|
|
||||||
|
|
||||||
Internet Identity Workshop is where the quest for concious, user-centric, identity began. Rebooting Web-of-Trust Workshops sprung from the IIW, focused on creating standards for DPKI. Among the United Nations 'Sustainable Development Goals' is for all the world to have access to a digital identity by 2030. Around 2016, the SDGs, blockchain, and the GDPR converged bringing much energy to the decentralized identity ecosystem.
|
|
||||||
|
|
||||||
**Additional history and related information may be found at [/awesome-decentralized-id](../README.md#Contents)**.
|
|
||||||
|
|
||||||
## Hyperledger Indy [**^**](#Contents)
|
|
||||||
|
|
||||||
![](https://www.osiztechnologies.com/asset/oimages/hyperledger_indy/hyperledger_indy_02.png)
|
|
||||||
|
|
||||||
![](https://imgur.com/2LWlrgvl.png)\
|
|
||||||
<sup><a href="https://www.edx.org/course/blockchain-for-business-an-introduction-to-hyperledger-technologies">Linux Foundation -Blockchain for Business -INDY</a></sup>
|
|
||||||
|
|
||||||
* [Hyperledger Indy - *Distributed Ledger and Utility Library*](https://www.hyperledger.org/projects/hyperledger-indy) [[**T**](https://twitter.com/Hyperledger)] [[**C**](https://chat.hyperledger.org)]
|
|
||||||
* [Indy Documentation Index - wiki.hyperledger.org](https://wiki.hyperledger.org/projects/indy/documentation)
|
|
||||||
* [indy.readthedocs.io](https://indy.readthedocs.io/) (under construction)
|
|
||||||
* [Indy Docs Framwork](https://github.com/hyperledger/indy-hipe/tree/master/text/0025-indy-docs-framework)
|
|
||||||
* [Introduction to Hyperledger Indy](https://github.com/hyperledger/education/blob/master/LFS171x/docs/introduction-to-hyperledger-indy.md) (awesome resource from hyperledger github)
|
|
||||||
* [Hyperledger Indy — the Future of Decentralized Identity](https://www.axiomtech.io/blog-feed/hyperledger-indy-decentralized-identity)
|
|
||||||
* [Hyperledger Welcomes Project Indy](https://www.hyperledger.org/blog/2017/05/02/hyperledger-welcomes-project-indy) - ANN
|
|
||||||
* [The Rise of Self-Sovereign Identity - Hyperledger Indy](https://wso2.com/blog/research/the-rise-of-self-sovereign-identity-hyperledger-indy)
|
|
||||||
* [Ernesto.net - What goes on the Ledger](https://www.ernesto.net/ernesto-net-5-minute-course-on-indy-and-what-goes-on-the-blockchain-ledger/)
|
|
||||||
* [Ernesto.net - Hyperledger Indy Architecture](https://www.ernesto.net/hyperledger-indy-architecture/)
|
|
||||||
* [github.com/IBM-Blockchain-Identity](https://github.com/IBM-Blockchain-Identity) (Docker based tutorial sandbox env)
|
|
||||||
* The Linux Foundation's [Blockchain for Business](https://www.edx.org/professional-certificate/linuxfoundationx-blockchain-for-business) course may be freely audited and has a section about Indy.
|
|
||||||
* [Blockchain development made easy: Getting started with Hyperledger Indy](https://jaxenter.com/hyperledger-indy-interview-hardman-148796.html) - Interview with Daniel Hardman[[**G**](https://github.com/dhh1128)][[**L**](https://www.linkedin.com/in/danielhardman/)][[**T**](https://twitter.com/dhh1128)], Hyperledger Indy maintainer
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/a0dpDtr.png"/>
|
|
||||||
|
|
||||||
|
|
||||||
## Additional Indy Related [**^**](#Contents)
|
|
||||||
* [Hyperledger Identity Working Group-paper](https://docs.google.com/document/d/1ExFNRx-yYoS8FnDIUX1_0UBMha9TvQkfts2kVnDc4KE/edit#heading=h.7noli5fp1i70)
|
|
||||||
* [HyperledgerIndyWGCall_2018-12-06](https://drive.google.com/file/d/1166XpTM8WgZVMN2ca53CRCJapZlAeUhM/view) Discussion of VON and Plenum Docs (w info-graphics)
|
|
||||||
* [A Framework for Designing Cryptographic Key Management Systems](https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-130.pdf)
|
|
||||||
* [An Accumulator Based on Bilinear Maps and Efficient Revocation for Anonymous Credentials](https://eprint.iacr.org/2008/539.pdf)
|
|
||||||
* [An Efficient System for Non-transferable Anonymous Credentials with Optional Anonymity Revocation](https://www.iacr.org/archive/eurocrypt2001/20450093.pdf)
|
|
||||||
* [sovrin-foundation/connector-app](https://github.com/sovrin-foundation/connector-app) - Reference mobile edge agent for use with the Sovrin Network built from Hyperledger Indy.
|
|
||||||
* [Building binaries of LibIndy for Android](https://github.com/hyperledger/indy-sdk/blob/master/doc/android-build.md)
|
|
||||||
* [HIPE 0014-ssi-notation](https://github.com/hyperledger/indy-hipe/tree/master/text/0014-ssi-notation)
|
|
||||||
* [Set up Indy Pool in Local Linux Environment Using Docker](https://medium.com/@smaldeniya/setup-hyperledger-indy-pool-in-local-linux-environment-using-docker-304d13eb86dc)
|
|
||||||
* [Learn how to set up a DEV Environment with Vagrant on Hyperledger Indy!](https://github.com/hyperledger/indy-node/blob/master/environment/vagrant/sandbox/DevelopmentEnvironment/Virtualbox/Vagrantfile)
|
|
||||||
* [Semantics Working Group Shared Docs](https://drive.google.com/drive/u/0/folders/1zkXr--0DG7I1k62vaFuotEzIaTIUH0ou?ogsrc=32)
|
|
||||||
* [Verifiable Credentials, Schema and Overlays- Overview Decks](https://drive.google.com/drive/u/0/folders/1UxLLugRQKuV8Mdvv_X9Y6ty4szSi5ZNU?ogsrc=32)
|
|
||||||
* [Indy August Update](https://wiki.hyperledger.org/groups/tsc/project-updates/indy-2018-aug) - Most recent report from the Hyperledger Indy team.
|
|
||||||
|
|
||||||
|
|
||||||
### Wallets [**^**](#Contents)
|
|
||||||
|
|
||||||
* [How to build a Self Sovereign Identity Wallet](https://www.devteam.space/blog/how-to-build-a-self-sovereign-identity-wallet/)
|
|
||||||
* https://github.com/streetcred-id/indy-sdk-storage
|
|
||||||
|
|
||||||
### Zero Knowledge Proofs in Indy [**^**](#Contents)
|
|
||||||
<a href="https://www.slideshare.net/eralcnoslen/privacypreserving-authentication-another-reason-to-care-about-zeroknowledge-proofs"><img src="https://i.imgur.com/LAUkkbN.png"/><br/><sup>Privacy Preserving Authentication—Another reason to care about ZKP</sup></a>
|
|
||||||
|
|
||||||
* [The Sovrin Network and Zero Knowledge Proof](https://sovrin.org/the-sovrin-network-and-zero-knowledge-proofs/) - high level walk through
|
|
||||||
* [AnonCreds: Anonymous credentials protocol implementation in python](https://github.com/hyperledger/indy-anoncreds) [[**ϟ**](https://github.com/hyperledger/indy-anoncreds/blob/master/docs/anoncred-usecase1.pdf)]
|
|
||||||
* [Relationship Diagram](https://github.com/hyperledger/indy-node/blob/master/docs/relationship-diagram.png)
|
|
||||||
* [Zero-Knowledge Proofs: Privacy-Preserving Digital Identity with Clare Nelson](https://www.slideshare.net/SSIMeetup/zeroknowledge-proofs-privacypreserving-digital-identity-with-clare-nelson)
|
|
||||||
* [Anonymous Credentials: Claims and Proofs in a Developer-friendly Format](https://docs.google.com/document/d/1XEfaOinOTIU9RgtP-GlXQAbOoW8z-oR5aWJDoQdftZ4/edit#heading=h.vor6nerodxkn) - Mike Lodder
|
|
||||||
|
|
||||||
|
|
||||||
>Our zero-knowledge proofs are part of the [Idemix protocol](http://domino.research.ibm.com/library/cyberdig.nsf/papers/EEB54FF3B91C1D648525759B004FBBB1/%24File/rz3730_revised.pdf), where they are used to prove the possession of [Camenisch-Lysyanskaya credentials](https://eprint.iacr.org/2001/019.pdf). We also use zero-knowledge proofs in the revocation protocol, which is based on [cryptographic accumulators](https://eprint.iacr.org/2008/539.pdf). —*[What Zero Knowledge Poof Algorithm is used in Sovrin?](https://forum.sovrin.org/t/what-zero-knowledge-proof-algorithm-is-used-in-sovrin/71/2)*
|
|
||||||
|
|
||||||
>Identity Mixer is not directly (re)implemented by Sovrin, but its cryptographic foundations are very similar, and Sovrin’s implementation includes most of its extended features (predicates, multi-credential, revocation, advanced issuance…). One of the researchers who helped to create Identity Mixer is on Sovrin’s Technical Governance Board and has offered insight to keep the implementations aligned on goals and methods.
|
|
||||||
>—*[How is IDEMix Implemented?](https://forum.sovrin.org/t/how-idemex-is-implemented-in-sovrin-indy/)*
|
|
||||||
|
|
||||||
* [IBM Identity Mixer](https://www.zurich.ibm.com/identity_mixer/) [[**B**](https://idemix.wordpress.com/)]
|
|
||||||
* [idemix in Hyperledger Fabric](https://hyperledger-fabric.readthedocs.io/en/release-1.3/idemix.html)
|
|
||||||
* [ABC4Trust—Attribute-based Credentials for Trust](https://abc4trust.eu/)
|
|
||||||
* [Concepts and Features of Privacy-Preserving Attribute-Based Credentials](https://github.com/p2abcengine/p2abcengine/wiki/Concepts-and-features)
|
|
||||||
* [Concepts and Languages for Privacy-Preserving Attribute-Based Authentication](http://dl.ifip.org/db/conf/idman/idman2013/CamenischDLNPP13.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Video [**^**](#Contents)
|
|
||||||
* [Meet the Sovrin Foundation](https://vimeo.com/299487829)
|
|
||||||
* [Hyperledger Indy Explainer Video](https://www.youtube.com/watch?v=MnO2L6WoqD0)
|
|
||||||
* [Phil Windley on the Sovrin Network](https://www.youtube.com/watch?v=IxQUL2ztFi8)
|
|
||||||
* [Self-Sovereign Identity with Hyperledger Indy\Sovrin- Calvin Cheng - FOSSASIA 2018](https://www.youtube.com/watch?v=hfyIZu3_fw8)
|
|
||||||
* [Hyperledger Indy introduction with Indy Agents Demo](https://www.youtube.com/watch?v=llwfb5Ut5sg)
|
|
||||||
* [Hyperledger Indy Demo Screencast](https://www.youtube.com/watch?v=9WZxlrGMA3s&t=93s)
|
|
||||||
* [Architectural Overview of Indy Wallets](https://www.youtube.com/watch?v=Km4IoUdb3Lc)
|
|
||||||
* [Indy Demo by IBM](https://www.youtube.com/watch?v=cz-6BldajiA)
|
|
||||||
* [Behind the Cloud Episode 6: Blockchain and Self-Sovereign Identity in the Enterprise](https://www.youtube.com/watch?v=wSdm2-18Z2g)
|
|
||||||
* [Evernym's contributions to Hyperledger Indy](https://www.youtube.com/playlist?list=PLRp0viTDxBWGLdZk0aamtahB9cpJGV7ZF)
|
|
||||||
* [Introduction to Indy Plenum Architecture](https://www.youtube.com/watch?v=WZin717AT_A)
|
|
||||||
* [Hyperledger Indy Working Group Calls](https://drive.google.com/drive/u/0/folders/1AwHWN95KmSEi5fijraID0tFFMzYHoMwt?ogsrc=32)
|
|
||||||
* [Sovrin: Public, Permissioned and Still Decentralized - Nathan George](https://www.youtube.com/watch?v=lVHJiUrHv2A&app=desktop)
|
|
||||||
* [Hyperledger Global Forum - Video](https://www.youtube.com/playlist?list=PL0MZ85B_96CGkWnEvdPy5sB4VRcH2XWuP)
|
|
||||||
|
|
||||||
|
|
||||||
### Podcasts [**^**](#contents)
|
|
||||||
* [MyData Podcast](https://mydata.org/podcast/)
|
|
||||||
|
|
||||||
### Directory [**^**](#contents)
|
|
||||||
* [Indy GitHub Repos](indy-github.md)
|
|
||||||
* [Adoption](adoption.md)
|
|
||||||
* [VON.md](VON.md)
|
|
||||||
* [VerifiableOrganizationsNetwork-HGF.md](../hgf-2018/VerifiableOrganizationsNetwork-HGF.md)
|
|
||||||
* [Microledgers-Edgechains-Hardman-HGF.md](../hgf-2018/Microledgers-Edgechains-Hardman-HGF.md)
|
|
||||||
* [Literature](literature.md)
|
|
||||||
* [Selected Articles Windley.com](literature.md#selected-articles-windleycom-)
|
|
||||||
* [EU General Data Protection Regulation Act](literature.md#eu-general-data-protection-regulation-act-)
|
|
||||||
* [Research Papers](literature.md#research-papers-)
|
|
||||||
* [Reports](literature.md#reports)
|
|
||||||
|
|
||||||
### Sources [**^**](#contents)
|
|
||||||
* [Evernym](https://www.evernym.com/)
|
|
||||||
* [Sovrin Foundation](https://sovrin.org/)
|
|
||||||
* [wiki.hyperledger.org—Indy](https://wiki.hyperledger.org/display/indy)
|
|
||||||
* [indy.readthedocs.io](https://indy.readthedocs.io)
|
|
||||||
* [SSI Meetup](http://ssimeetup.org/) [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)][[**SS**](https://www.slideshare.net/SSIMeetup/presentations/)]
|
|
||||||
* [windley.com/tags/sovrin](http://www.windley.com/tags/sovrin)
|
|
||||||
* [/WebOfTrustInfo](https://github.com/WebOfTrustInfo/)
|
|
||||||
* [/peacekeeper/blockchain-identity](https://github.com/peacekeeper/blockchain-identity)
|
|
||||||
* [/awesome-decentralized-id](/README.md)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id) ([**^**](#contents))
|
|
||||||
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align="right" width="170" height="170"/></a>
|
|
||||||
|
|
||||||
**Tips Jar**
|
|
||||||
|
|
||||||
BTC— 1GvkjHtiy9LUjVkStnEAXxjhcoS56aCokY
|
|
||||||
|
|
||||||
![](https://imgur.com/yXLLm9Bl.png)
|
|
||||||
|
|
||||||
DOGE— DSzMxfABB8EwKiumzV7YHhS7HTvWAyM7QF
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0zBLoUP.png)
|
|
@ -1,18 +0,0 @@
|
|||||||
# Indy Github Repositories
|
|
||||||
|
|
||||||
* [/indy-plenum](https://github.com/hyperledger/indy-plenum) - Byzantine Fault Tolerant Protocol [[**wiki**](https://github.com/hyperledger/indy-plenum/wiki)]
|
|
||||||
> "Byzantine fault tolerance is a sub-field of fault tolerance research inspired by the Byzantine Generals' Problem, which is a generalized version of the Two Generals' Problem."
|
|
||||||
* [Storage components](https://github.com/hyperledger/indy-plenum/blob/master/docs/storage.md) - As of now, RocksDB is used as a key-value database for all Storages.
|
|
||||||
* [/indy-sdk](https://github.com/hyperledger/indy-sdk) - Everything needed to build applications that interact with an Indy distributed identity ledger.
|
|
||||||
* [MAINTAINERS.md](https://github.com/hyperledger/indy-sdk/blob/master/MAINTAINERS.md)
|
|
||||||
* [/indy-node](https://github.com/hyperledger/indy-node) - The server portion of a distributed ledger purpose-built for decentralized identity.
|
|
||||||
* [/indy-anoncreds](https://github.com/hyperledger/indy-anoncreds) - Anonymous credentials protocol implementation in python
|
|
||||||
* [/indy-agent](https://github.com/hyperledger/indy-agent) - reference agents and associated tools.
|
|
||||||
* [/indy-test-automation](https://github.com/hyperledger/indy-test-automation) - Automation tools for testing of Indy Project components.
|
|
||||||
* [/indy-post-install-automation](https://github.com/hyperledger/indy-post-install-automation)
|
|
||||||
* [/indy-hipe](https://github.com/hyperledger/indy-hipe) -
|
|
||||||
Hyperledger Indy Project Enhancements
|
|
||||||
* https://indy.readthedocs.io/projects/hipe/en/latest/
|
|
||||||
* [/indy-crypto](https://github.com/hyperledger/indy-crypto) - shared crypto library for Hyperledger Indy components. To be:
|
|
||||||
* [/ursa](https://github.com/hyperledger/ursa) [[**ϟ**](https://www.hyperledger.org/blog/2018/12/04/welcome-hyperledger-ursa)][[**ϟ**](https://www.coindesk.com/hyperledger-launches-cryptography-toolbox-for-blockchain-developers)] "includes the Hyperledger Indy-Crypto code base that is the building block for anonymous credentials, the verifiable credentials protocol, in indy-sdk used by the Sovrin Network. [...] We are hopeful the shared library will help other platforms better incorporate and use ZKP-based credentials and leverage Sovrin for their identity component." (From Nathan George on Sovrin Telegram) [[**wiki**](https://wiki.hyperledger.org/projects/ursa)]
|
|
||||||
|
|
@ -1,47 +0,0 @@
|
|||||||
# Sovrin Related Literature and Media
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Selected articles from Windley.com](#selected-articles-windleycom-)
|
|
||||||
* [EU General Data Protection Regulation Act](#eu-general-data-protection-regulation-act-)
|
|
||||||
* [Research Papers](#research-papers-)
|
|
||||||
* [Reports](#reports)
|
|
||||||
* [/indy-ecosystem/README.md](README.md)
|
|
||||||
* [<< /awesome-decentralized-id](../README.md)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
|
|
||||||
## Selected articles Windley.com [**^**](#Contents)
|
|
||||||
|
|
||||||
* [windley.com/tags/sovrin](http://www.windley.com/tags/sovrin)
|
|
||||||
* [An Internet for Identity](http://www.windley.com/archives/2016/08/an_internet_for_identity.shtml)
|
|
||||||
* [A Universal Trust Framework](http://www.windley.com/archives/2017/01/a_universal_trust_framework.shtml)
|
|
||||||
* [Building Your Business on Sovrin: Domain-Specific Trust Frameworks](http://www.windley.com/archives/2018/03/building_your_business_on_sovrin_domain-specific_trust_frameworks.shtml)
|
|
||||||
* [The Sovrin Foundation](http://www.windley.com/archives/2018/07/the_sovrin_foundation.shtml)
|
|
||||||
* [Decentralization in Sovrin](http://www.windley.com/archives/2018/10/decentralization_in_sovrin.shtml)
|
|
||||||
* [Self-Sovereign Identity and the Legitimacy of Permissioned Ledgers](http://www.windley.com/archives/2016/09/self-sovereign_identity_and_the_legitimacy_of_permissioned_ledgers.shtml)
|
|
||||||
* [The Sovrin Ecosystem](http://www.windley.com/archives/2018/11/the_sovrin_ecosystem.shtml) (Disambiguating between Evernym, Sovrin, and Indy)
|
|
||||||
|
|
||||||
|
|
||||||
## EU General Data Protection Regulation Act [**^**](#Contents)
|
|
||||||
|
|
||||||
* [Digital Identity Management in the Context of GDPR & Sovrin —Why Data Privacy Matters & How to Protect It](https://blog.tykn.tech/digital-identity-management-in-the-context-of-gdpr-sovrin-43028247378b)
|
|
||||||
* [Implementing Privacy by Design in Hyperledger Indy](https://www.infoq.com/news/2018/09/Hyperledger-Indy-Privacy)
|
|
||||||
* [Self-Sovereign Privacy By Design](https://github.com/sovrin-foundation/protocol/blob/master/self_sovereign_privacy_by_design_v1.md)
|
|
||||||
* [Privacy by Design The 7 Foundational Principles](https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf)
|
|
||||||
* [When GDPR Becomes Real, and Blockchain is no longer fairydust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/gdpr.md)
|
|
||||||
* [Is Self-Sovereign Identity the ultimate GDPR compliance tool? [1\3]](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-9d8110752f89) [[**2**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-40db94c1c437)] [[**3**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-7296a3b07769)]
|
|
||||||
* [Privacy by Design in Hyperledger Indy](https://www.hyperledger.org/blog/2018/09/12/privacy-by-design-in-hyperledger-indy)
|
|
||||||
|
|
||||||
## Research Papers [**^**](#Contents)
|
|
||||||
* [A Conceptual Analysis on Sovrin](https://www.researchgate.net/publication/323144927_A_Conceptual_Analysis_on_Sovrin)
|
|
||||||
* [Evernym Research Collection *2016 Archive*](https://web.archive.org/web/20170206161655/http://www.evernym.com/our-research/)
|
|
||||||
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
|
|
||||||
* [A First Look at Identity Management Schemes on the Blockchain](https://arxiv.org/pdf/1801.03294.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
## Reports [**^**](#Contents)
|
|
||||||
* [A Comprehensive Evaluation of the Identity Management Utility Sovrin](https://dutchblockchaincoalition.org/uploads/pdf/Blockchain-Sovrin-rapport.pdf)
|
|
||||||
* [White Paper: Canada’s Digital ID Future - A Federated Approach](https://www.cba.ca/embracing-digital-id-in-canada)
|
|
||||||
* [IDENTITY MATTERS](https://cboxxtest.files.wordpress.com/2017/09/cboxxidentitymatters04.pdf)
|
|
||||||
* [A position paper on blockchain enabled identity and the road ahead—Identity Working Group of the German Blockchain Association](https://www.bundesblock.de/wp-content/uploads/2018/10/ssi-paper.pdf)
|
|
@ -1,160 +0,0 @@
|
|||||||
# The Sovrin Foundation
|
|
||||||
|
|
||||||
![](https://www.evernym.com/wp-content/uploads/2017/04/logo-large.png)
|
|
||||||
|
|
||||||
* [[**F**](https://forum.sovrin.org/)]orum • [[**C**](https://chat.sovrin.org/)]hat • [[**T**](https://twitter.com/SovrinID)]witter • [[**G**](https://github.com/sovrin-foundation/sovrin)]ithub • [[**tele**](https://t.me/sovrin_foundation)]gram • [[**web**](https://sovrin.org/)]site
|
|
||||||
* [Founded](http://www.windley.com/archives/2016/09/announcing_the_sovrin_foundation.shtml) in [September](https://www.prnewswire.com/news-releases/sovrin-foundation-launches-first-dedicated-self-sovereign-identity-network-300336702.html) 2016, The [Sovrin](https://sovrin.org/)
|
|
||||||
Foundation is creating a public instance of the Sovrin\Indy codebase; initially developed by [Evernym](#Evernym)
|
|
||||||
* [Sovrin Library](https://sovrin.org/library/)
|
|
||||||
* [Getting Started with Sovrin](https://sovrin.org/library/getting-started-with-sovrin/)
|
|
||||||
* [Sovrin: A Protocol and Token for Self-Sovereign Identity and Decentralized Trust](https://sovrin.org/wp-content/uploads/Sovrin-Protocol-and-Token-White-Paper.pdf)
|
|
||||||
* [Sovrin Network: What Goes on the Ledger?](https://sovrin.org/wp-content/uploads/2018/10/What-Goes-On-The-Ledger.pdf)
|
|
||||||
* [Sovrin Governance Framework](https://sovrin.org/library/sovrin-governance-framework/)
|
|
||||||
* [How Sovrin Works: A Technical Guide from the Sovrin Foundation](https://sovrin.org/wp-content/uploads/2018/03/How-Sovrin-Works.pdf) [[**ϟ**](https://sovrin.org/wp-content/uploads/AnonCred-RWC.pdf)]
|
|
||||||
* [Sovrin Test Network Trust Anchor Registration](https://s3.us-east-2.amazonaws.com/evernym-cs/sovrin-STNnetwork/www/trust-anchor.html)[[**F**](https://forum.sovrin.org/t/testing-on-the-sovrin-test-network-stn/643/17)]
|
|
||||||
* [Sovrin Main Net Outage, December 2018](https://forum.sovrin.org/t/sovrin-main-net-outage-december-2018/1010)
|
|
||||||
> The Sovrin Main Network experienced an outage lasting from Saturday 2018-12-08 until Tuesday 2018-12-11. This was our first significant outage of the network. This post describes the incident, how it was addressed, and what we are doing to prevent future incidents and improve our responses.
|
|
||||||
* [Sovrin Status Twitter](https://twitter.com/sovrin_status)
|
|
||||||
|
|
||||||
|
|
||||||
## Sovrin Stewards
|
|
||||||
|
|
||||||
The Sovrin ledger is operated by Stewards, trusted organizations within the ecosystem who have agreed to abide by the requirements in the [Sovrin Trust Framework](https://sovrin.org/library/sovrin-governance-framework/) and are responsible for operation the nodes that maintain the Sovrin distributed ledger.
|
|
||||||
|
|
||||||
Stewards also, as a group, accept or reject any changes to the ledger-specific portions of the Sovrin open source code by virtue of that role. They thus provide a counterbalance to the Sovrin architects who maintain the Indy code base.
|
|
||||||
|
|
||||||
### Aalto University
|
|
||||||
|
|
||||||
[Aalto University](http://www.aalto.fi/en/)
|
|
||||||
|
|
||||||
### Absa Group Limited
|
|
||||||
[Absa Group Limited](https://www.absa.africa/absaafrica/)
|
|
||||||
|
|
||||||
### Amihan Global Strategies
|
|
||||||
• [Amihan Global Strategies](https://amihan.net/)
|
|
||||||
|
|
||||||
### ARTiFACTS
|
|
||||||
• [ARTiFACTS](https://artifacts.ai/)
|
|
||||||
|
|
||||||
### Attinad Software
|
|
||||||
• [Attinad Software](http://attinadsoftware.com/)
|
|
||||||
|
|
||||||
### ATB Financial
|
|
||||||
• [ATB Financial](http://www.atb.com/Pages/default.aspx)
|
|
||||||
|
|
||||||
### Best Innovation Group
|
|
||||||
• [Best Innovation Group](http://www.big-fintech.com/)
|
|
||||||
|
|
||||||
### BakerHostetler
|
|
||||||
• [BakerHostetler](https://www.bakerlaw.com/)
|
|
||||||
|
|
||||||
### Cisco
|
|
||||||
• [Cisco](https://www.cisco.com/)
|
|
||||||
|
|
||||||
### Certisign
|
|
||||||
• [Certisign](http://www.certisign.com.br/)
|
|
||||||
|
|
||||||
### Crypto Valley Association
|
|
||||||
• [Crypto Valley Association](https://cryptovalley.swiss/)
|
|
||||||
|
|
||||||
### CULedger
|
|
||||||
• [CULedger](http://culedger.com/)
|
|
||||||
|
|
||||||
### Danube Tech
|
|
||||||
• [Danube Tech](https://danubetech.com/)
|
|
||||||
|
|
||||||
### Datum
|
|
||||||
• [Datum](https://datum.org/)
|
|
||||||
|
|
||||||
### Desert Financial Credit Union
|
|
||||||
• [Desert Financial Credit Union](https://www.desertschools.org/business)
|
|
||||||
|
|
||||||
### Digicert
|
|
||||||
• [Digicert](https://www.digicert.com/)
|
|
||||||
|
|
||||||
### Digital Bazaar
|
|
||||||
• [Digital Bazaar](https://digitalbazaar.com/)
|
|
||||||
|
|
||||||
### estatus AG
|
|
||||||
• [estatus AG](https://www.esatus.com/)
|
|
||||||
|
|
||||||
### Evernym
|
|
||||||
• [Evernym](https://www.evernym.com/)
|
|
||||||
|
|
||||||
### European Business Process Institute
|
|
||||||
• [European Business Process Institute](https://ebpi.nl/en/home/)
|
|
||||||
|
|
||||||
### Finicity
|
|
||||||
• [Finicity](https://www.finicity.com/)
|
|
||||||
|
|
||||||
### First Education Credit Union
|
|
||||||
• [First Education Credit Union](https://www.firstedfcu.com/)
|
|
||||||
|
|
||||||
### Consent.Global
|
|
||||||
• [Global Consent](http://www.consent.global/)
|
|
||||||
* [Consent](http://www.consent.global/)[[**ϟ**](https://sovrin.org/steward/global-consent/)] — "platform for trusted personal data applications and services, using Ethereum smart contracts to implement decentralized identifiers, verified credentials, consent receipts, a web of trust, and exchange of assets and value."
|
|
||||||
|
|
||||||
### IBM
|
|
||||||
|
|
||||||
• [IBM](https://www.ibm.com/blogs/blockchain/2018/08/ibm-blockchain-trusted-identity-sovrin-steward-closed-beta-offering/)
|
|
||||||
|
|
||||||
### InfoCert
|
|
||||||
• [InfoCert](https://infocert.digital/)
|
|
||||||
|
|
||||||
### iRespond
|
|
||||||
• [iRespond](https://irespond.org/)
|
|
||||||
|
|
||||||
### KYC Chain
|
|
||||||
• [KYC Chain](https://kyc-chain.com/)
|
|
||||||
|
|
||||||
### lab10 collective
|
|
||||||
• [lab10 collective](https://lab10.coop/en/)
|
|
||||||
|
|
||||||
### OAS Staff Federal Credit Union
|
|
||||||
• [OAS Staff Federal Credit Union](https://www.oasfcu.org/en/default.asp)
|
|
||||||
|
|
||||||
### Perkins Cole
|
|
||||||
• [Perkins Cole](https://www.perkinscoie.com/)
|
|
||||||
|
|
||||||
### ProSapien
|
|
||||||
• [ProSapien](https://www.prosapien.com/)
|
|
||||||
|
|
||||||
### Qiy Foundation
|
|
||||||
• [Qiy Foundation](https://www.qiyfoundation.org/)
|
|
||||||
|
|
||||||
### Royal Credit Union
|
|
||||||
• [Royal Credit Union](https://www.rcu.org/)
|
|
||||||
|
|
||||||
### SICPA
|
|
||||||
• [SICPA](https://www.sicpa.com/)
|
|
||||||
|
|
||||||
### SITA
|
|
||||||
• [SITA](https://www.sita.aero/)
|
|
||||||
|
|
||||||
### Spark New Zealand
|
|
||||||
• [Spark New Zealand](http://www.sparknz.co.nz/)
|
|
||||||
|
|
||||||
### Swisscom Blockchain
|
|
||||||
• [Swisscom Blockchain](https://blockchain.swisscom.com/)
|
|
||||||
|
|
||||||
### T-Labs
|
|
||||||
• [T-Labs](https://laboratories.telekom.com/)
|
|
||||||
|
|
||||||
### The City of Osmio
|
|
||||||
• [The City of Osmio](https://osmio.ch/)
|
|
||||||
|
|
||||||
### TNO
|
|
||||||
• [TNO](https://www.tno.nl/en/)
|
|
||||||
|
|
||||||
### Truu
|
|
||||||
• [Truu](https://www.truu.id/)
|
|
||||||
|
|
||||||
### TwinPeek
|
|
||||||
• [TwinPeek](https://twinpeek.net/)
|
|
||||||
|
|
||||||
### Tykn
|
|
||||||
• [Tykn](https://tykn.tech/)
|
|
||||||
|
|
||||||
### Veridium
|
|
||||||
• [Veridium](https://veridiumid.com/)
|
|
||||||
|
|
@ -1,89 +0,0 @@
|
|||||||
# Identity Articles, Research and Literature
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Literature](#literature-)
|
|
||||||
* [Reports](#reports)
|
|
||||||
* [Decentralized Public Key Infrastructure DPKI](#decentralized-public-key-infrastructure-dpki-)
|
|
||||||
* [Rebooting Web of Trust -Directory](#rebooting-web-of-trust-)
|
|
||||||
* [Assorted Thought Around Identity](#assorted-thought-around-identity)
|
|
||||||
* [>> Sovrin Related Literature](indy-ecosystem/literature.md)
|
|
||||||
* [<< /awesome-decentralized-id](README.md)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
## Literature [**^**](#contents)
|
|
||||||
|
|
||||||
* [Security without Identification: Transaction Systems to make Big Brother Obsolete](https://www.cs.ru.nl/~jhh/pub/secsem/chaum1985bigbrother.pdf) - David Chaum 1985
|
|
||||||
* [Establishing Identity Without Certification Authorities](https://irl.cs.ucla.edu/~yingdi/pub/papers/Ellison-OldFriend-USENIX-Security-1996.pdf)
|
|
||||||
* [A First Look at Identity Management Schemes on the Blockchain](https://arxiv.org/pdf/1801.03294.pdf)
|
|
||||||
* [ChainAnchor — Anonymous Identities for Permissioned Blokchains](http://connection.mit.edu/wp-content/uploads/sites/29/2014/12/Anonymous-Identities-for-Permissioned-Blockchains2.pdf)
|
|
||||||
* [Decentralizing Privacy: Using Blockchain to Protect Personal Data](http://web.media.mit.edu/~guyzys/data/ZNP15.pdf)
|
|
||||||
* [Towards Self-Sovereign Identity using Blockchain Technology](https://essay.utwente.nl/71274/1/Baars_MA_BMS.pdf)
|
|
||||||
* [Self-sovereign Identity – Opportunities and Challenges for the Digital Revolution](https://arxiv.org/pdf/1712.01767.pdf)
|
|
||||||
* [The Knowledge Complexity Of Interactive Proofs](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.419.8132&)
|
|
||||||
* [A Conceptual Analysis on Sovrin](https://www.researchgate.net/publication/323144927_A_Conceptual_Analysis_on_Sovrin)
|
|
||||||
* [Blockchain for Identity Management](https://www.cs.bgu.ac.il/~frankel/TechnicalReports/2016/16-02.pdf) - Details early efforts towards Blockchain-ID
|
|
||||||
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
|
|
||||||
|
|
||||||
## Reports [**^**](#contents)
|
|
||||||
* [EU BLOCKCHAIN OBSERVATORY AND FORUM — Workshop Report — e-Identity, Brussels, November 7, 2018](https://www.eublockchainforum.eu/sites/default/files/reports/workshop_5_report_-_e-identity.pdf)
|
|
||||||
* [A Comprehensive Evaluation of the Identity Management Utility Sovrin](https://dutchblockchaincoalition.org/uploads/pdf/Blockchain-Sovrin-rapport.pdf)
|
|
||||||
* [How Blockchain Revolutionizes Identity Management](https://www.accenture-insights.nl/en-us/articles/how-blockchain-will-revolutionize-identity-management)
|
|
||||||
* [Digital Identity: the current state of affairs](https://www.bbvaresearch.com/wp-content/uploads/2018/02/Digital-Identity_the-current-state-of-affairs.pdf)
|
|
||||||
* [Blockchain: Evolving Decentralized Identity Design](https://www.gartner.com/doc/3834863/blockchain-evolving-decentralized-identity-design)
|
|
||||||
* [IDENTITY MATTERS](https://cboxxtest.files.wordpress.com/2017/09/cboxxidentitymatters04.pdf)
|
|
||||||
* [Accenture: ID2020: DIGITAL IDENTITY with Blockchain and Biometrics](https://www.accenture.com/us-en/insight-blockchain-id2020)
|
|
||||||
* [Privacy-Preserving Authentication, Another Reason to Care about Zero-Knowledge Proofs —slideshare](https://www.slideshare.net/eralcnoslen/privacypreserving-authentication-another-reason-to-care-about-zeroknowledge-proofs)
|
|
||||||
* [r3- Identity in Depth](https://www.r3.com/wp-content/uploads/2017/06/Identity_indepth_r3.pdf)
|
|
||||||
* [Global Blockchain Identity Management Market 2018-2022](https://www.technavio.com/report/global-blockchain-identity-management-market-analysis-share-2018)
|
|
||||||
* [A Comprehensive Guide to Self Sovereign Identity](https://ssiscoop.com/) - by Kaliya ['Identity Woman'](https://twitter.com/IdentityWoman) Young and [Heather Vescent](https://twitter.com/heathervescent) [[**ϟ**](https://www.thepaypers.com/expert-opinion/10-things-you-need-to-know-about-self-sovereign-identity-part-1/774556)]
|
|
||||||
* [Report launch: ‘Identity at the Margins — identification systems for refugees”](https://medium.com/caribou-digital/report-launch-identity-at-the-margins-identification-systems-for-refugees-69466244fa62)
|
|
||||||
* [WEF: Identity in a Digital World A new chapter in the social contract](http://www3.weforum.org/docs/WEF_INSIGHT_REPORT_Digital%20Identity.pdf)
|
|
||||||
* [A position paper on blockchain enabled identity and the road ahead](https://www.bundesblock.de/wp-content/uploads/2018/10/ssi-paper.pdf)—Identity Working Group of the German Blockchain Association [[**ϟ**](https://www.bundesblock.de/2018/10/23/position-paper-self-sovereign-identity/)]
|
|
||||||
|
|
||||||
## Decentralized Public Key Infrastructure DPKI [**^**](#contents)
|
|
||||||
* RWoT—[Decentralized Public Key Infrastructure](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/dpki.pdf)
|
|
||||||
* [SCPKI: A Smart Contract-based PKI and Identity System](http://www0.cs.ucl.ac.uk/staff/M.AlBassam/publications/scpki-bcc17.pdf)
|
|
||||||
* [KeyChains: A Decentralized Public-Key Infrastructure](https://drum.lib.umd.edu/bitstream/handle/1903/3332/0.pdf?sequence=1&isAllowed=y)
|
|
||||||
* [ClaimChain: Decentralized Public Key Infrastructure](https://www.researchgate.net/publication/318584251_ClaimChain_Decentralized_Public_Key_Infrastructure)
|
|
||||||
* [A Decentralized Public Key Infrastructure with Identity Retention](https://eprint.iacr.org/2014/803.pdf)
|
|
||||||
* [Privacy based decentralized Public Key Infrastructure
|
|
||||||
(PKI) implementation using Smart contract in
|
|
||||||
Blockchain](https://isrdc.iitb.ac.in/blockchain/workshops/2017-iitb/papers/paper-11%20-%20Decentralized%20PKI%20in%20blockchain%20and%20Smart%20contract.pdf)
|
|
||||||
|
|
||||||
### Rebooting Web of Trust [**^**](#contents)
|
|
||||||
|
|
||||||
[**>> Rebooting Web of Trust - "complete" Papers, Topics and Advance Readings >>**](rebooting-web-of-trust.md)
|
|
||||||
* [Selected RWoT Whitepapers](rebooting-web-of-trust.md#selected-rebooting-web-of-trust-whitepapers-)
|
|
||||||
* [Primers](rebooting-web-of-trust.md#primers)
|
|
||||||
* [RWoT Workshop Related](rebooting-web-of-trust.md#rwot-workshop-related-)
|
|
||||||
* [Use Cases](rebooting-web-of-trust.md#use-cases-)
|
|
||||||
* [Completed Papers](rebooting-web-of-trust.md#completed-papers-)
|
|
||||||
* [Rebooting the Web of Trust I](rebooting-web-of-trust.md#rebooting-the-web-of-trust-i-)
|
|
||||||
* [Rebooting the Web of Trust II - ID2020](rebooting-web-of-trust.md#rebooting-the-web-of-trust-ii---id2020-)
|
|
||||||
* [Rebooting the Web of Trust III](rebooting-web-of-trust.md#rebooting-the-web-of-trust-iii-)
|
|
||||||
* [Rebooting the Web of Trust IV](rebooting-web-of-trust.md#rebooting-the-web-of-trust-iv-)
|
|
||||||
* [Rebooting the Web of Trust V](rebooting-web-of-trust.md#rebooting-the-web-of-trust-v-)
|
|
||||||
* [Rebooting the Web of Trust VI](rebooting-web-of-trust.md#rebooting-the-web-of-trust-vi-)
|
|
||||||
* [Rebooting the Web of Trust VII](rebooting-web-of-trust.md#rebooting-the-web-of-trust-vii-)
|
|
||||||
* [Topics and Advance Readings](#topics-and-advance-readings-)
|
|
||||||
* [RWoT 1](#rwot-1-)
|
|
||||||
* [RWoT 2](#rwot-id2020-)
|
|
||||||
* [RWoT 3](#rwot-3-)
|
|
||||||
* [RWoT 4](#rwot-4-)
|
|
||||||
* [RWoT 5](#rwot-5-)
|
|
||||||
* [RWoT 6](#rwot-6-)
|
|
||||||
* [RWoT 7](#rwot-7-)
|
|
||||||
|
|
||||||
## Additional Thought around Identity [**^**](#contents)
|
|
||||||
* [Is putting hashed PII on any immutable ledger(blockchain) is a bad Idea](https://identitywoman.net/putting-hashed-pii-immutable-ledgerblockchain-bad-idea/)
|
|
||||||
* [Decentralized Identity Trilemma](http://maciek.blog/decentralized-identity-trilemma/)
|
|
||||||
>There seems to exist a trilemma in decentralized identity analogous to @Zooko's triangle. None of the existing solutions are at the same time: 1) privacy-preserving, 2) Sybil-resistant 3) self-sovereign -[[**T**](https://twitter.com/MaciekLaskus/status/1031859093072424960)]
|
|
||||||
* [Maciek Laskus - BLOCKWALKS](https://www.youtube.com/watch?v=KAgJpQfQXxs) (video)
|
|
||||||
* "I designed an algorithm that mapped out people [working on identity](https://twitter.com/MaciekLaskus/status/1066780557906976768) using Twitter data:" [Identity list](https://docs.google.com/spreadsheets/d/1hBBVA0-jqmRRZ_JFQ8HEck9tFub7crsqRzlBZWf01xg/edit?usp=sharing)
|
|
||||||
* [Proof of Thought (PoT)](https://bitcointalk.org/index.php?topic=4459113.0)
|
|
||||||
* [Queer Privacy](https://leanpub.com/queerprivacy)
|
|
||||||
>Stories about using the Internet as a tool to find out more about yourself, and as a tool to express and empower; about the dangers of Internet censorship and about the practical realities of maintaining multiple distinct digital identities.
|
|
||||||
* [@SarahJamieLewis Twitter thread on Identity](https://twitter.com/SarahJamieLewis/status/1041043532654542848)
|
|
||||||
>Any technology which relies on the existence of, or attempts to create a, global, unique identity is oppressive by design. Stop" innovating" oppressive structures.
|
|
||||||
|
|
@ -1,31 +0,0 @@
|
|||||||
# SSI and DID Related Media
|
|
||||||
|
|
||||||
## Video
|
|
||||||
|
|
||||||
* [SSI Meetup Youtube Channel](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)
|
|
||||||
* [The Story of Open SSI Standards - Drummond Reed](https://www.youtube.com/watch?v=RllH91rcFdE&feature=youtu.be&t=4m30s)
|
|
||||||
* [Is Blockchain the Future of Digital Identity?](https://youtu.be/Aub5dNpj2_k) -CB Insights
|
|
||||||
* [Identity and Blockchain Technology](https://www.youtube.com/watch?v=Aub5dNpj2_k)
|
|
||||||
* [Phil Windley on the Sovrin Network](https://www.youtube.com/watch?v=IxQUL2ztFi8)
|
|
||||||
* [Decentralized Identifiers enable self-sovereign identity - MyData 2018](https://www.youtube.com/watch?v=KsIM0zq37fU)
|
|
||||||
* [eIDAS and Self-Sovereign Identity - MyData 2018](https://www.youtube.com/watch?v=AHa175AEVVs)
|
|
||||||
* [uPort: Self-Sovereign Identity Meets Portable Data](https://www.youtube.com/watch?v=hBIragrwqYc)
|
|
||||||
* [MyData Global Youtube](https://www.youtube.com/channel/UCjBkx-XKa1gOr71fyCrJPfg)
|
|
||||||
* [Phil Windley on Vimeo](https://vimeo.com/windley/videos)
|
|
||||||
* [Internet of Agreements Conference on Identity](https://medium.com/humanizing-the-singularity/identity/home)
|
|
||||||
* [Behind the Cloud Episode 6: Blockchain and Self-Sovereign Identity in the Enterprise](https://www.youtube.com/watch?v=wSdm2-18Z2g)
|
|
||||||
* [Identity and the quest for Self Sovereign Identity - Daniel Hardman](https://www.youtube.com/watch?v=iqmY_h49vPs)
|
|
||||||
|
|
||||||
|
|
||||||
## Slideshare
|
|
||||||
* [Blockchain Based Solutions For Identity Access Management](https://www.slideshare.net/prabathsiriwardena/blockchainbased-solutions-for-identity-access-management)
|
|
||||||
* [Towards Self Sovereign Identity](https://www.slideshare.net/alehors/towards-self-sovereign-identity-20180508) - A great slide-deck by IBM explaining Indy\Sovrin Architecture.
|
|
||||||
* [Identiverse](https://www.slideshare.net/Identiverse/presentations)
|
|
||||||
* [SSI Meetup](https://www.slideshare.net/SSIMeetup/presentations/)
|
|
||||||
* [ChristopherA](https://www.slideshare.net/ChristopherA/presentations)
|
|
||||||
|
|
||||||
## Podcasts
|
|
||||||
* [State of Identity](https://oneworldidentity.com/podcasts/)
|
|
||||||
* [Analytics Neat—Episode 37: What is a Decentralized Identity (DID)?](https://player.fm/series/analytics-neat/episode-37-what-is-a-decentralized-identity-did)
|
|
||||||
* [State Change #41 Unpacking Digital Identity](https://media.consensys.net/state-change-41-unpacking-digital-identity-christian-lundkvist-stephen-wilson-4fb5a75eb6ed)
|
|
||||||
* [MyData Podcast](https://mydata.org/podcast/)
|
|
@ -1,12 +0,0 @@
|
|||||||
# Microsoft Identity
|
|
||||||
|
|
||||||
![](https://i.imgur.com/MEN8iSn.png)
|
|
||||||
|
|
||||||
* [Microsoft Azure Own your identity](https://azure.microsoft.com/en-us/overview/decentralized-identity/) [[**ϟ**](https://www.coindesk.com/microsoft-is-pushing-new-blockchain-id-products-but-theres-pushback-too)]
|
|
||||||
Discover decentralized identity—a new way to take ownership of your personal data.
|
|
||||||
* [didproject.azurewebsites.net](https://didproject.azurewebsites.net/) [[**D**](https://didproject.azurewebsites.net/docs/overview.html)]ocs [[**wp**](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2DjfY)]
|
|
||||||
* [DID Registration](https://didproject.azurewebsites.net/docs/registration.html)
|
|
||||||
* [Mastercard, Microsoft Join Forces to Advance Digital Identity Innovations](https://newsroom.mastercard.com/press-releases/mastercard-microsoft-join-forces-to-advance-digital-identity-innovations/)
|
|
||||||
* [Decentralized digital identities and blockchain: The future as we see it](https://www.microsoft.com/en-us/microsoft-365/blog/2018/02/12/decentralized-digital-identities-and-blockchain-the-future-as-we-see-it/)
|
|
||||||
* [Microsoft Identity Standards Blog](https://techcommunity.microsoft.com/t5/Identity-Standards-Blog/bg-p/IdentityStandards)
|
|
||||||
* [Microsoft working on Project Bali to Give People Control over their data](https://amp.businessinsider.com/microsoft-working-on-project-bali-to-give-people-control-over-data-2019-1)
|
|
@ -1,123 +0,0 @@
|
|||||||
# DID-SSI Organizations
|
|
||||||
|
|
||||||
this page is a work in progress
|
|
||||||
|
|
||||||
## IIW - Internet Identity Workshop
|
|
||||||
|
|
||||||
>The [Internet Identity Workshop](https://internetidentityworkshop.com) has been finding, probing and solving identity issues twice every year since 2005.
|
|
||||||
|
|
||||||
...
|
|
||||||
|
|
||||||
<blockquote>
|
|
||||||
IIW is at its heart a participatory conference. Through dozens of sessions, lunches, and two evening meals (all included in ticket) you’ll have plenty of chances to exchange ideas and make new professional connections.
|
|
||||||
|
|
||||||
This is the time and place that you get to discuss, share your knowledge, work on and learn about anything & everything related to Internet Identity today.
|
|
||||||
|
|
||||||
Spring: April 30, 2019 – May 2, 2019
|
|
||||||
|
|
||||||
Fall: October 01, 2019 – October 03, 2019
|
|
||||||
</blockquote>
|
|
||||||
|
|
||||||
[![](https://i.imgur.com/DRSuywW.png)](https://vimeo.com/173562225)
|
|
||||||
|
|
||||||
## Rebooting Web of Trust
|
|
||||||
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
|
|
||||||
* <a href="http://www.weboftrust.info/next-event-page.html" target="_blank">WebOfTrust.info - Upcoming Events</a>
|
|
||||||
|
|
||||||
## MyData
|
|
||||||
|
|
||||||
* [Mydata](http://mydata.org/) [[**T**](https://twitter.com/mydataorg)] [[**D**](https://mydata.org/papers/)] [[**D**](https://mydata.org/declaration/)]
|
|
||||||
* goal: to empower individuals with their personal data, thus helping them and their communities develop knowledge, make informed decisions, and interact more consciously and efficiently with each other as well as with organisations."
|
|
||||||
|
|
||||||
>When you join the MyData Global, you are helping to create a trustworthy human centered data economy. Read from the [MyData Declaration](https://mydata.org/declaration/) what we mean by this.
|
|
||||||
|
|
||||||
![](https://i.imgur.com/gIbUsDQ.png)
|
|
||||||
|
|
||||||
## Danube
|
|
||||||
|
|
||||||
* [Danube Tech](http://danubetech.com/) — digital identity and personal data, including personal agents, semantic graphs, and blockchain ([**xdi**](https://xdi2.org)) ([**navigator**](https://github.com/projectdanube/xdi2))
|
|
||||||
* Founded by [Markus Sabadello (Peacekeeper)](http://mydata2016.org/speaker/markus-sabadello/) [[**T**](https://twitter.com/peacekeeper)] [[**G**](https://github.com/peacekeeper)] [[**B**](https://medium.com/@markus.sabadello)]
|
|
||||||
|
|
||||||
## Blockstack [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/ZZx8lfR.png)
|
|
||||||
* [Blockstack](https://blockstack.org/) • [[**G**](https://github.com/blockstack)]ithub • [[**F**](https://forum.blockstack.org/)]orum • [[**B**](https://blockstack.org/blog)]log • [[**T**](https://twitter.com/blockstack)]witter • [[**W**](https://blockstack.org/whitepaper.pdf)]hitepaper • [[**bitcoinwiki**](https://en.bitcoinwiki.org/wiki/BlockStack)]
|
|
||||||
* a network of computers that collectively maintain a global registry of domain names, public keys, and cryptographic hashes. With this registry, Blockstack serves as a decentralized domain name system (DNS) and a decentralized public key infrastructure (PKI).
|
|
||||||
* [Extending Existing Blockchains with Virtualchain](https://www.zurich.ibm.com/dccl/papers/nelson_dccl.pdf)
|
|
||||||
* [Onename](https://onename.com/) — "a product built on Blockstack that allows people to register identities"
|
|
||||||
* [Blockstack DID Spec](https://github.com/blockstack/blockstack-core/blob/master/docs/blockstack-did-spec.md)[**[ϟ](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287/9)**]
|
|
||||||
* [App Mining](https://app.co/mining)
|
|
||||||
* [/dantrevino/awesome-blockstack](https://github.com/dantrevino/awesome-blockstack) [[**ϟ**](https://gitlab.com/dantrevino/awesome-blockstack)]
|
|
||||||
|
|
||||||
## Democracy Earth [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/KxbXb1t.png)
|
|
||||||
* [Democracy Earth Foundation](http://democracy.earth/) [[**G**](https://github.com/DemocracyEarth/)][[**B**](https://words.democracy.earth/)][[**T**](https://twitter.com/DemocracyEarth)][[**C**](http://chat.democracy.earth/)] - Crypto Governance
|
|
||||||
* [Sovereign](http://sovereign.software/)[[**G**](https://github.com/DemocracyEarth/sovereign)], a blockchain direct democracy tool using "vote" tokens to grant democratic participation rights to every human. A proof-of-individuality (POI) process based on peer-to-peer validation establishes that a self-sovereign identity is uniquely tied to a single person. Cooperation is happening with other decentralized identity initiatives such as Blockstack and uPort.
|
|
||||||
* [The Social Smart Contract](https://github.com/DemocracyEarth/paper#The_Social_Smart_Contract)[[**ϟ**](https://www.dropbox.com/s/sifogl4zimwkkei/Democracy%20Earth%20-%20Social%20Smart%20Contract%20-%20Paper%20v0.2.pdf?dl=0)] An Initial Rights Offering from Democracy Earth Foundation.
|
|
||||||
* [December App-Mining Results](https://words.democracy.earth/decembers-app-mining-results-are-live-7bd2b4f2390)
|
|
||||||
* [Yellow Jackets on the Sovereign Platform](https://words.democracy.earth/yellow-jackets-on-the-sovereign-platform-bdebe6d62ae1)
|
|
||||||
* [Meet the Dad Who Registered His Daughter’s Birth on the Blockchain](https://www.coindesk.com/meet-the-dad-who-registered-his-daughters-birth-on-the-blockchain) [[**ϟ**](https://www.coindesk.com/humans-on-the-blockchain-why-crypto-is-the-best-defense-against-ai-overlords)]
|
|
||||||
* Token: [Sale](https://token.democracy.earth/) • [Economics](https://www.dropbox.com/s/8q35dvht2hkfvqa/Democracy%20Earth%20-%20Token%20Economics.pdf?dl=0) • [testnet](https://votest.democracy.earth/)
|
|
||||||
>we worked with councils, senates, non profits, student centers, political parties, corporations.. but implementing real digital governance at scale really took off with crypto networks. our partnership with @blockstack is our biggest milestone of 2018. -[Santi](https://twitter.com/santisiri/status/1076259390154592256)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Blockpass [**^**](#contents)
|
|
||||||
<img src="https://imgur.com/mMZ4E2rl.png" />
|
|
||||||
|
|
||||||
* [Blockpass](https://www.blockpass.org/) [[**T**](https://twitter.com/BlockpassOrg)] [[**wp**](https://www.blockpass.org/downloads/BlockpassWhitepaper.v1.3.3.pdf)]
|
|
||||||
* [Edinburgh Identity Lab](https://identity-lab.blockpass.org/) [[**ϟ**](https://www.newsbtc.com/2018/09/28/worlds-first-blockchain-identity-lab-launched-today-in-edinburgh/)]
|
|
||||||
|
|
||||||
|
|
||||||
## Handshake [**^**](#contents)
|
|
||||||
|
|
||||||
<img src="https://i.imgur.com/lhHnC8w.png"/>
|
|
||||||
|
|
||||||
* [Handshake](https://handshake.org) [[**wp**](https://handshake.org/files/handshake.txt)] [[**D**](https://handshake-org.github.io/)] - Handshake is a UTXO-based blockchain protocol which manages the registration, renewal and transfer of DNS top-level domains (TLDs). Our naming protocol differs from its predecessors in that it has no concept of namespacing or subdomains at the consensus layer. Its purpose is not to replace DNS, but to replace the root zone file and the root servers.
|
|
||||||
|
|
||||||
## Ontology [**^**](#contents)
|
|
||||||
|
|
||||||
* [ONTology](https://ont.io/) [[**G**](https://github.com/ontio/ontology-DID)]— "a "Distributed Trust Network" which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules. It also includes an Ontology Crypto Package (OCP) and an Ontology Marketplace (OM)."
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## SSI-Meetup
|
|
||||||
|
|
||||||
>[SSI Meetup](https://ssimeetup.org) is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards. Our main mission is to help you connect with other SSI enthusiasts and create a dynamic, local, yet globally connected community.
|
|
||||||
|
|
||||||
...[Monthly webinars](https://ssimeetup.org/blog/), the slideshares of which provide a ton of value.
|
|
||||||
|
|
||||||
Who can join?
|
|
||||||
Anyone deals with or who wants to deal with Self-Sovereign Identity. This includes: SSI companies, SSI loving organizations, and any SSI evangelist wanting to use community SSI tools or who is otherwise interested in contributing.
|
|
||||||
|
|
||||||
Our Principles
|
|
||||||
What can I/we do?
|
|
||||||
Anything to support the cause – please get in touch and we will try to find a way to make it happen as we build the community.
|
|
||||||
|
|
||||||
## Assorted
|
|
||||||
|
|
||||||
* [Identity at Coinbase: Welcoming the Distributed Systems team](https://blog.coinbase.com/identity-at-coinbase-welcoming-the-distributed-systems-team-d929dd64de2e) [[**ϟ**](https://www.wired.com/story/coinbase-distributed-systems-acquisition/)]
|
|
||||||
* [Shocard](https://shocard.com/) — "Blockchain-Based Mobile Identity Platform" [[**ϟ**](https://medium.com/shocard/why-shocard-is-the-premier-blockchain-based-mobile-identity-platform-6fad15410106)]
|
|
||||||
* [Authenteq](http://authenteq.com/) [[**T**](https://twitter.com/authenteq)] [[**G**](https://github.com/authenteq)]
|
|
||||||
* enables users to create their own sovereign digital IDs which are stored encrypted on [BigChainDB](http://docs.bigchaindb.com)
|
|
||||||
* [JLinc](https://www.jlinc.com/) — registers cryptographic public keys on the Stellar blockchain.
|
|
||||||
> "The founders have been at the center of a community of developers working on “user-centric digital identity for almost two decades."
|
|
||||||
* [Civic](https://www.civic.com/) launches: [identity.com](https://identity.com)[[**G**](https://github.com/identity-com/)][[**B**](https://www.civic.com/blog/identity-com-first-open-source-update/)][[**wp**](https://tokensale.civic.com/CivicTokenSaleWhitePaper.pdf)][[**ϟ**](https://www.theblockcrypto.com/2018/12/21/civics-token-illustrates-why-companies-masquerading-tokens-will-fail/)]
|
|
||||||
* [Dapp Framework Melo One to use Civic](https://www.cryptoninjas.net/2018/08/30/dapp-framework-menlo-one-to-use-civic-for-blockchain-identity-verification/)
|
|
||||||
* [Brave Civic Partnership](https://brave.com/brave-civic-partnership/)
|
|
||||||
* [I/O Digital Foundation](https://iodigital.io/) [**[**wp**](https://simplebooklet.com/iocoinwhitepaper#page=0)**]
|
|
||||||
* "offers a Proof-of-Stake blockchain called Decentralised Input Output Name Server (DIONS). It will enable applications such as identity and alias registration, storage of legal documents, key exchange, and encrypted messaging."
|
|
||||||
* [Gemalto and R3 pilot blockchain for SSID](https://www.cryptoninjas.net/2018/09/18/gemalto-and-r3-pilot-blockchain-technology-for-self-sovereign-digital-id-network/#.W6drpckvGLU.twitter)
|
|
||||||
* [Datum](https://datum.org) [[**wp**](https://datum.org/assets/Datum-WhitePaper.pdf)]
|
|
||||||
* "network allows anyone to store structured data on a smart contract blockchain. Data can optionally be bought and sold on a marketplace using the DAT token. Datum leverages BigchainDB and IPFS as data storage backends. All data is encrypted and protected using AES256-GCM.
|
|
||||||
* [Pro-civis](https://procivis.ch) — "e-government as a service" platform called "eID+". It enables citizens to get an official, electronic Citizen-ID on a mobile app.
|
|
||||||
* The platform includes the [Vetri](https://vetri.global/) wallet and marketplace. 'Earn extra income and rewards by joining the data economy.'"
|
|
||||||
* [We can do better than selling our data](http://blogs.harvard.edu/doc/2018/09/18/data/)-Doc Searls(*IIW*)
|
|
||||||
|
|
@ -1,717 +0,0 @@
|
|||||||
---
|
|
||||||
title: "A \"complete\" listing of #RebootingWebOfTrust Papers, Topics, and Advance Readings"
|
|
||||||
description: Lets make this awesome collaborative work easier to explore!
|
|
||||||
image: "https://i.imgur.com/Nmxk4fE.png"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Rebooting Web Of Trust - Papers and Advance Readings Index
|
|
||||||
|
|
||||||
I wanted a list of all RWoT papers in one place, rather than having to directory hop to look for what I need. I'll be adding a short exerpt to each advance reading and then turning this into a database, so that it's easily searchable.+
|
|
||||||
|
|
||||||
See the [WebofTrust.Info](http://www.weboftrust.info/) or [github.com/WebOfTrustInfo](https://github.com/WebOfTrustInfo/) for more information.
|
|
||||||
|
|
||||||
> '[Web of Trust](https://en.wikipedia.org/wiki/Web_of_trust)' is a network of relationships that attest to our identity claims. *Each party attesting to your identity information becomes a strand in your web of trust.*
|
|
||||||
|
|
||||||
![](https://i.imgur.com/Nmxk4fE.png)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Selected RWoT Whitepapers](#selected-rebooting-web-of-trust-whitepapers-)
|
|
||||||
* [Primers](#primers)
|
|
||||||
* [RWoT Workshop Related](#rwot-workshop-related-)
|
|
||||||
* [Use Cases](#use-cases-)
|
|
||||||
* [Completed Papers](#completed-papers-)
|
|
||||||
* [Rebooting the Web of Trust I](#rebooting-the-web-of-trust-i-)
|
|
||||||
* [Rebooting the Web of Trust II - ID2020](#rebooting-the-web-of-trust-ii---id2020-)
|
|
||||||
* [Rebooting the Web of Trust III](#rebooting-the-web-of-trust-iii-)
|
|
||||||
* [Rebooting the Web of Trust IV](#rebooting-the-web-of-trust-iv-)
|
|
||||||
* [Rebooting the Web of Trust V](#rebooting-the-web-of-trust-v-)
|
|
||||||
* [Rebooting the Web of Trust VI](#rebooting-the-web-of-trust-vi-)
|
|
||||||
* [Rebooting the Web of Trust VII](#rebooting-the-web-of-trust-vii-)
|
|
||||||
* [Topics and Advance Readings](#topics-and-advance-readings-)
|
|
||||||
* [RWoT 1](#rwot-1-)
|
|
||||||
* [RWoT 2](#rwot-id2020-)
|
|
||||||
* [RWoT 3](#rwot-3-)
|
|
||||||
* [RWoT 4](#rwot-4-)
|
|
||||||
* [RWoT 5](#rwot-5-)
|
|
||||||
* [RWoT 6](#rwot-6-)
|
|
||||||
* [RWoT 7](#rwot-7-)
|
|
||||||
* [RWoT GitHub Listing](#rwot-github-listing-)
|
|
||||||
* [>> Identity Research and Literature](literature.md)
|
|
||||||
* [>> Sovrin Related Literature](indy-ecosystem/literature.md)
|
|
||||||
* [<< /awesome-decentralized-id](README.md)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
## Selected 'Rebooting Web of Trust' Whitepapers [**^**](#contents)
|
|
||||||
|
|
||||||
### Primers
|
|
||||||
|
|
||||||
* [A Primer on Functional Identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/functional-identity-primer.md) by Joe Andrieu
|
|
||||||
* [A Primer on Self-Sovereign identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/self-sovereign-identity-primer.md) by Christopher Allen & Shannon Appelcline
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/did-primer.md) by Drummond Reed & Manu Sporny
|
|
||||||
* [A Verifiable Claims Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/verifiable-claims-primer.md) by Manu Sporny
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md)
|
|
||||||
|
|
||||||
### RWoT Workshop Related [**^**](#contents)
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* [Rebranding the Web of Trust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/rebranding-web-of-trust.pdf) Original RWoT whitepaper
|
|
||||||
* [WebofTrust.info/papers.html](https://www.weboftrust.info/papers.html)
|
|
||||||
|
|
||||||
### Use Cases [**^**](#contents)
|
|
||||||
* [Amira 1.0](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/amira.md)
|
|
||||||
* [Re-Imagining What Users Really Want](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2017/blob/master/final-documents/what-users-really-want.md)
|
|
||||||
* [Joram 1.0.0](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016/blob/master/final-documents/joram-engagement-model.pdf)
|
|
||||||
* [Powering the Physician-Patient Relationship with HIE of One Blockchain Health IT](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/physician-patient-relationship.pdf)
|
|
||||||
* [Protecting Digital Identities in Developing Countries](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/protecting-digital-identities-in-developing-countries.pdf)
|
|
||||||
* [Opportunities Created by the Web of Trust for Controlling and Leveraging Personal Data](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/satisfying-real-world-use-cases.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Completed Papers [**^**](#contents)
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust I [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/pes1Vm8.png)
|
|
||||||
|
|
||||||
The first Rebooting the Web of Trust design workshop, held in San Francisco, CA - November 3rd & 4th, 2015.
|
|
||||||
|
|
||||||
* **[Rebranding the Web of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/rebranding-web-of-trust.pdf)**
|
|
||||||
* A history of the Web of Trust and a look at what the term could mean for the future.
|
|
||||||
* Shannon Appelcline, Dave Crocker, Randall Farmer, and Justin Newton
|
|
||||||
>The Web of Trust is a buzzword for a new model of decentralized self-sovereign identity. It’s a phrase that dates back almost twenty-five years, the classic definition derives from PGP [...] the vibrant blockchain community is also drawing new attention to the concept we aim to reboot it.
|
|
||||||
* **[Opportunities Created by the Web of Trust for Controlling and Leveraging Personal Data](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/satisfying-real-world-use-cases.pdf)**
|
|
||||||
* Five use cases, from two relatively simple cases of managing selective disclosure to the most extreme case of establishing government-verifiable credentials from nothing for a stateless refugee.
|
|
||||||
* du5t, Kaliya "Identity Woman" Young (@identitywoman), John Edge, Drummond Reed, and Noah Thorp
|
|
||||||
* **[Decentralized Public Key Infrastructure](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf)**
|
|
||||||
* A massive overview of a decentralized public-key infrastructure (DPKI).
|
|
||||||
* Christopher Allen, Arthur Brock, Vitalik Buterin, Jon Callas, Duke Dorje, Christian Lundkvist, Pavel Kravchenko, Jude Nelson, Drummond Reed, Markus Sabadello, Greg Slepak, Noah Thorp, and Harlan T Wood
|
|
||||||
* **[Smart Signatures](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/smart-signatures.pdf)**
|
|
||||||
* A system to explicitly outline and fully program conditions for verification, inspired by Bitcoin Script.
|
|
||||||
* Christopher Allen, Greg Maxwell, Peter Todd, Ryan Shea, Pieter Wuille, Joseph Bonneau, Joseph Poon, and Tyler Close
|
|
||||||
* **[Creating the New World of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/whats-the-next-step.pdf)**
|
|
||||||
* A summary of the next step for the Rebooting the Web of Trust group.
|
|
||||||
* Shannon Appelcline
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust II - ID2020 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/cn5CQEI.png)
|
|
||||||
|
|
||||||
The second Rebooting the Web of Trust design workshop, in San Francisco, CA, on May 21st & 22nd, 2016. It was run in conjunction with the UN ID2020 Summit on Identity, which occurred at the UN in New York on May 20th, 2016.
|
|
||||||
|
|
||||||
* [**Identity Crisis: Clearer Identity Through Correlation**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/identity-crisis.pdf)
|
|
||||||
* A new way to look at identity, as correlation over time.
|
|
||||||
* Joe Andrieu, Kevin Gannon, Igor Kruiper, Ajit Tripathi, and Gary Zimmerman
|
|
||||||
* [**Powering the Physician-Patient Relationship with HIE of One Blockchain Health IT**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/physician-patient-relationship.pdf)
|
|
||||||
* Using Blockchains and DIDs for physician-patient interactions.
|
|
||||||
* Adrian Gropper, MD
|
|
||||||
* [**Protecting Digital Identities in Developing Countries**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/protecting-digital-identities-in-developing-countries.pdf)
|
|
||||||
* A real-world use case, describing issues of identity in the developing world.
|
|
||||||
* Wayne Hennessy-Barrett
|
|
||||||
* [**Requirements for DIDs (Decentralized Identifiers)**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/requirements-for-dids.pdf)
|
|
||||||
* The first of a series of papers abou tproducing a concrete DID system.
|
|
||||||
* Drummond Reed and Les Chasen
|
|
||||||
* [**Smarter Signatures: Experiments in Verifications**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/smarter-signatures.pdf)
|
|
||||||
* A look at uses and requirements of next-generation smart signature systems.
|
|
||||||
* Christopher Allen and Shannon Appelcline
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust III [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/37wRZ9B.png)
|
|
||||||
|
|
||||||
The design workshop exceeded its mandate by producing seven papers:
|
|
||||||
|
|
||||||
* [**DID (Decentralized Identifier) Data Model and Generic Syntax 1.0 Implementer’s Draft 01**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/did-implementer-draft-10.pdf)
|
|
||||||
- The complete draft of the Decentralized IDentifier (DID) model and syntac, a project that has run through the RWOT workshops to date.
|
|
||||||
- Drummond Reed, Les Chasen, Christopher Allen, and Ryan Grant
|
|
||||||
* [**Digital Verification Advancements at RWoT III**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/digital-verification-advancements.pdf)
|
|
||||||
- A short overview of enhancements to Digital Verification that came out of RWOT III.
|
|
||||||
- Manu Sporny with Christopher Allen, Harlan Wood, and Jason Law
|
|
||||||
* [**Embedding Human Wisdom in Our Digital Tomorrow**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/WisdomEmbedding-Human-Wisdom-in-Our-Digital-Tomorrow.pdf)
|
|
||||||
- A discussion of the dangers of transferring wisdom into the digital world, seen through the lenses of vulnerability, shadows, healing, tensions, complexity and gestalt, and organizational choices.
|
|
||||||
- Daniel Hardman, Kaliya “Identity Woman” Young, and Matthew Schutte
|
|
||||||
* [**Hubs**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/hubs.pdf)
|
|
||||||
- An overview of the hubs datastore system.
|
|
||||||
- Daniel Buchner, Wayne Vaughan, and Ryan Shea
|
|
||||||
* [**Joram 1.0.0**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/joram-engagement-model.pdf)
|
|
||||||
- An Information Lifecycle Engagement Model that offers a use case for a Syrian refugee.
|
|
||||||
- Joe Andrieu and Bob Clint
|
|
||||||
* [**Portable Reputation Toolkit Use Cases**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/reputation-toolkit.pdf)
|
|
||||||
- A model and proof-of-concept implementation for decentralized verification.
|
|
||||||
- Christopher Allen, Tim Daubenschütz, Manu Sporny, Noah Thorp, Harlan Wood, Glenn Willen, and Alessandro Voto
|
|
||||||
* [**Smart Consent Protocol**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/smart-consent-protocol.pdf)
|
|
||||||
- Bringing together COALA IP and Consent to deal with digital intellectual property.
|
|
||||||
- Dr. Shaun Conway, Lohan Spies, Jonathan Endersby, and Tim Daubenschütz
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust IV [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/ZtP6Dny.png)
|
|
||||||
|
|
||||||
The fourth Rebooting the Web of Trust design workshop ran in Paris, France, on April 19th-21st, 2017.
|
|
||||||
|
|
||||||
* [*Design Considerations for Decentralized Reputation Systems*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/reputation-design.md)
|
|
||||||
- Angus Champion de Crespigny, Dmitry Khovratovich, Florent Blondeau, Klara Sok, Philippe Honigman, Nikolaos Alexopoulos, Fabien Petitcolas, and Shaun Conway
|
|
||||||
* [*LD Signature Format Alignment*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/ld-signatures.md) - Bringing JSON-LD signatures into alignment with JOSE JSON Web Signature (JWS) standards.
|
|
||||||
- Kim Hamilton Duffy, Rodolphe Marques, Markus Sabadello, and Manu Sporny
|
|
||||||
* [*Re-Imagining What Users Really Want*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/what-users-really-want.md) - Five people, five opportunities for self-sovereign identity.
|
|
||||||
- Joe Andrieu, Frederic Engel, Adam Lake, Moses Ma, Olivier Maas, and Mark van der Waal.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust V [**^**](#contents)
|
|
||||||
![](http://i.imgur.com/H7i3KFD.png)
|
|
||||||
|
|
||||||
* [**ActivityPub: From Decentralized to Distributed Social Networks**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/activitypub-decentralized-distributed.md)
|
|
||||||
- Christopher Lemmer Webber & Manu Sporny
|
|
||||||
- An overview of the W3C ActivityPub protocol.
|
|
||||||
* [**Amira 1.0.0**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/amira.md)
|
|
||||||
- Joe Andrieu & Team
|
|
||||||
- This paper [...] presents a human-centric illustration of an individual’s experience in a self-sovereign, decentralized realization of the Web of Trust as originally conceived by Phil Zimmerman for PGP.
|
|
||||||
* [**The DCS Theorem**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/dcs-theorem/The-DCS-Theorem.pdf)
|
|
||||||
- Greg Slepak & Anya Petrova
|
|
||||||
- A probability proof of the DCS Triangle. Why can't decentralized consensus systems have all three of decentralization, consensus, and scale? Plus, two methods for getting around these limitations.
|
|
||||||
* [**A Decentralized Approach to Blockcerts Credential Revocation**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/blockcerts-revocation.md)
|
|
||||||
- João Santos & Kim Hamilton Duffy
|
|
||||||
- Blockcerts are blockchain-anchored credentials with a verification process designed to be decentralized and trustless. This proposal describes an alternate method of issuing Blockcerts using Ethereum, which allows for a new form of revocation by either the issuer or the recipient.
|
|
||||||
* [**Engineering Privacy for Verified Credentials: In Which We Describe Data Minimization, Selective Disclosure, and Progressive Trust**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/data-minimization-sd.md)
|
|
||||||
- Lionel Wolberger, Brent Zundel, Zachary Larson, Irene Hernandez & Katryna Dow
|
|
||||||
- we have identified three related but distinct privacy enhancing strategies: "data minimization," "selective disclosure," and "progressive trust." These enhancements are enabled with cryptography. The goal of this paper is to enable decision makers, particularly non-technical ones, to gain a nuanced grasp of these enhancements along with some idea of how their enablers work.
|
|
||||||
* [**Identity Hubs Capabilities Perspective**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/identity-hubs-capabilities-perspective.md)
|
|
||||||
- by Adrian Gropper, Drummond Reed & Mark S. Miller
|
|
||||||
> Identity Hubs as currently proposed in the Decentralized Identity Foundation (DIF) are a subset of a general Decentralized Identifier (DID) based user-controlled agent, based on ACLs rather than an object-capabilities (ocap) architecture. Transitioning the Hubs design to an ocap model can be achieved by introducing an UMA authorization server as the control endpoint.
|
|
||||||
* [**Linked Data Capabilities**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/lds-ocap.md)
|
|
||||||
- Christopher Lemmer Webber & Mark S. Miller
|
|
||||||
> Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems.
|
|
||||||
* [**Veres One DID Method**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/did-method-veres-one.md)
|
|
||||||
- Manu Sporny & Dave Longley
|
|
||||||
> The Veres One Ledger is a permissionless public ledger designed specifically for the creation and management of decentralized identifiers (DIDs). This specification defines how a developer may create and update DIDs in the Veres One Ledger.
|
|
||||||
* [**When GDPR becomes real, and Blockchain is no longer Fairy Dust**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/gdpr.md)
|
|
||||||
- Marta Piekarska, Michael Lodder, Zachary Larson & Kaliya Young (Identity Woman)
|
|
||||||
> This document describes the GDPR requirements and the different approaches to digital identity solutions and finally explains why distributed ledger technology may offer an opportunity for enterprises to simplify data management solutions that are GDPR compliant.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust VI [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/9yhGv6a.png)
|
|
||||||
|
|
||||||
The sixth Rebooting the Web of Trust design workshop ran in Santa Barbara, California, on March 6th to 8th, 2018.
|
|
||||||
|
|
||||||
* [**BTCR DID Resolver Specification**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/btcr-resolver.md)
|
|
||||||
- Kim Hamilton Duffy, Christopher Allen, Ryan Grant, and Dan Pape
|
|
||||||
> This describes the process of resolving a BTCR DID into a DID Document. The draft reference implementation is available at https://github.com/WebOfTrustInfo/btcr-did-tools-js (see didFormatter.js). Note that not all steps described in this document are implemented yet.
|
|
||||||
* [**Decentralized Autonomic Data (DAD) and the three R's of Key Management**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/DecentralizedAutonomicData.md)
|
|
||||||
- by Samuel M. Smith Ph.D. with Vishal Gupta
|
|
||||||
> This paper proposes a new class of data called decentralized autonomic data (DAD). The term decentralized means that the governance of the data may not reside with a single party. A related concept is that the trust in the data provenance is diffuse in nature. Central to the approach is leveraging the emerging DID (decentralized identifier) standard. The term autonomic means self-managing or self-regulating. In the context of data, we crystalize the meaning of self-managing to include cryptographic techniques for maintaining data provenance that make the data self-identifying, self-certifying, and self-securing. Implied thereby is the use of cryptographic keys and signatures to provide a root of trust for data integrity and to maintain that trust over transformation of that data, e.g. provenance. Thus key management must be a first order property of DADs. This includes key reproduction, rotation, and recovery. The pre-rotation and hybrid recovery methods presented herein are somewhat novel.
|
|
||||||
|
|
||||||
* [**Decentralized Identifiers v1.0**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-spec-1.0.md)
|
|
||||||
- A Status Note
|
|
||||||
|
|
||||||
> The Decentralized Identifiers specification editors and implementers spent some time at Rebooting the Web of Trust 6 processing the remaining issues in the issue tracker. This document summarizes the proposed resolutions that the group has put forward to resolve all of the DID specification issues that were submitted before 2018-03-05.
|
|
||||||
|
|
||||||
* [*Exploring Sustainable Technology Commons using Appreciative Inquiry*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/sustainable-commons.md)
|
|
||||||
- by Heather Vescent, Kaliya “Identity Woman” Young, Adrian Gropper, and Juan Caballero
|
|
||||||
|
|
||||||
> Technology commons come in a variety of flavors and have achieved varying levels of financial success. For-profit corporate activities have in few historical cases been set up with a financial feedback mechanism to support the commons upon which they depend and capitalize. Why do the commons and the technology sectors’ available forms of capitalism act as incompatible as oil and water, even though they support each other’s aims? When capitalist benefactors support the technology commons that they utilize, it creates a sustainable and thriving commons which enables and supports additional capitalistic technology innovation. Having worked on both sides of the equation, the authors of this piece propose a vocabulary to nourish these interactions between the two sides; identified characteristics of a sustainable technology commons; identified commons models and variations; applied Appreciative Inquiry principles to one commons model; and identified future research areas.
|
|
||||||
|
|
||||||
* [*Identity Hub Attestation Flows and Components*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/identity-hub-attestations.md)
|
|
||||||
- by Daniel Buchner, Cherie Duncan, John Toohey, Ron Kreutzer, and Stephen Curran
|
|
||||||
|
|
||||||
> In this document, we define a set of user flows and describe the associated Action Objects that support a Hub-centric approach to the request, issuance, presentation, verification, and revocation of interoperable attestations. This document extends the [Identity Hub Explainer](https://github.com/decentralized-identity/hubs/blob/master/explainer.md).
|
|
||||||
|
|
||||||
* [*Introduction to DID Auth*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md)
|
|
||||||
- by Markus Sabadello, Kyle Den Hartog, Christian Lundkvist, Cedric Franz, Alberto Elias, Andrew Hughes, John Jordan & Dmitri Zagidulin
|
|
||||||
|
|
||||||
> The term DID Auth has been used in different ways and is currently not well-defined. We define DID Auth as a ceremony where an identity owner, with the help of various components such as web browsers, mobile devices, and other agents, proves to a relying party that they are in control of a DID. This means demonstrating control of the DID using the mechanism specified in the DID Document's "authentication" object. This could take place using a number of different data formats, protocols, and flows. DID Auth includes the ability to establish mutually authenticated communication channels and to authenticate to web sites and applications. Authorization, Verifiable Credentials, and Capabilities are built on top of DID Auth and are out of scope for this document. This paper gives on overview of the scope of DID Auth, supported protocols and flows, and the use of components of the DID Documents that are relevant to authentication, as well as formats for challenges and responses.
|
|
||||||
|
|
||||||
* [*Open Badges are Verifiable Credentials*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.md)
|
|
||||||
- By Nate Otto & Kim Hamilton Duffy
|
|
||||||
|
|
||||||
> We identify use cases and requirements that connect threads of work happening in the Rebooting Web of Trust community around: educational achievement claims (particularly using the Open Badges vocabulary); use of decentralized identifiers (DIDs) within web services where educational claims circulate; and integrating blockchain-reliant verification layers. We illustrate each of these cases with a set of example documents and describe user stories for Open Badges ecosystem software in the roles of Issuer, Host/Backpack, Displayer, and Verifier that need to be implemented in order to enable the capabilities described.
|
|
||||||
|
|
||||||
* [*SSI: A Roadmap for Adoption*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md)
|
|
||||||
- By Moses Ma, Claire Rumore, Dan Gisolfi, Wes Kussmaul & Dan Greening (Senex Rex)
|
|
||||||
|
|
||||||
> This document proposes the formation of a short-term team to develop consistent messaging for the Self-Sovereign Identity (SSI) market. It will target key stakeholders who would actively promote SSI adoption. The goal is to create an SSI market roadmap. This roadmap will help SSI leaders, standards bodies, developers, academics, media, and investors coordinate and clarify their messaging for the market, to accelerate the SSI adoption.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust VII [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/tHcfNsK.png)
|
|
||||||
|
|
||||||
The seventh Rebooting the Web of Trust design workshop, ran near Toronto, Canada, on September 26th to 28th, 2018.
|
|
||||||
|
|
||||||
* [*BTCR v0.1 Decisions*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.md)
|
|
||||||
- Kim Hamilton Duffy, Christopher Allen, and Dan Pape
|
|
||||||
|
|
||||||
> The Bitcoin Reference (BTCR) DID method supports DIDs using the Bitcoin blockchain. This method has been under development through Rebooting Web of Trust events and hackathons over the past year. The BTCR method's reliance on the Bitcoin blockchain presents both advantages and design challenges. During RWOT7, the authors made a number of design and implementation decisions -- largely scope-cutting in nature -- in order to lock down a Minimum Viable Product (MVP) version, which we'll refer to as v0.1. This paper documents those decisions, which will apply to the upcoming v0.1 BTCR method specification and associated v0.1 BTCR reference implementation.
|
|
||||||
|
|
||||||
* [*A DID for Everything*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/A_DID_for_everything.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/A_DID_for_everything.md)
|
|
||||||
- Shaun Conway, Andrew Hughes, Moses Ma, Jack Poole, Martin Riedel, Samuel M. Smith Ph.D., and Carsten Stöcker
|
|
||||||
|
|
||||||
> The decentralized identifier (DID) is a new and open standard type of globally unique identifier that offers a model for lifetime-scope portable digital identity that does not depend on any centralized authority and that can never be taken away by third-parties. DIDs are supported by the W3C community and the Decentralized Identity Foundation (DIF). They are the "atomic units" of a new layer of decentralized identity infrastructure. However, DIDs can be extended from identifiers for people to any entity, thus identifying everything. We can use DIDs to help us identify and manage objects, machines, or agents through their digital twins; we can expand them to locations, to events, and even to pure data objects, which we refer to as decentralized autonomic data (DAD) items.
|
|
||||||
|
|
||||||
> The paper will present novel use-cases for DIDs and DADs and propose a new cryptographic data structure that is a self-contained blockchain of DADs. This enables the verification of the provenance of a given data flow. It builds on a prior paper and an associated reading.
|
|
||||||
|
|
||||||
* [*How to Convince Dad\* of the Importance of Self-Sovereign Identity*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.md)
|
|
||||||
- Shannon Appelcline, Kenneth Bok, Lucas Parker, Peter Scott, and Matthew Wong
|
|
||||||
|
|
||||||
> One of the major problems with bootstrapping self-sovereign identity is that it requires adoption by a large number of people. Pushing self-sovereign identity from the top-down is most likely to result in a technology that’s not actually used, but instead encouraging the average person to demand self-sovereign identity from the bottom-up will result in the organic development of a vibrant, well-utilized decentralized web-of-trust ecosystem.
|
|
||||||
|
|
||||||
> This paper addresses that need by offering arguments to a variety of people who might be reluctant to use self-sovereign identity, uninterested in its possibilities, or oblivious to the dangers of centralization. By focusing on the needs of real people, we hope to also encourage developers, engineers, and software business owners to create the apps that will address their reluctance and fulfill their needs, making self-sovereign identity a reality.
|
|
||||||
|
|
||||||
* [*IPLD as a general pattern for DID documents and Verifiable Claims*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/ipld-did.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/ipld-did.md)
|
|
||||||
- jonnycrunch, Anthony Ronning, Kim Duffy, Christian Lundkvist
|
|
||||||
|
|
||||||
> Since the emergence of the Decentralized Identifier (DID) specification at the Fall 2016 Rebooting the Web of Trust [1], numerous DID method specifications have appeared. Each DID method specification defines how to resolve a cryptographically-tied DID document given a method-specific identifier. In this paper, we describe a way to represent the DID document as a content-addressed Merkle Directed Acyclic Graph (DAG) using Interplanetary Linked Data (IPLD). This technique enables more cost-efficient, scaleable creation of DIDs and can be applied across different DID method specifications.
|
|
||||||
|
|
||||||
* [*Peer to Peer Degrees of Trust*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/peer-to-peer-degrees-of-trust.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/peer-to-peer-degrees-of-trust.md)
|
|
||||||
- Harrison Stahl, Titus Capilnean, Peter Snyder, and Tyler Yasaka
|
|
||||||
|
|
||||||
> Aunthenticity is a challenge for any identity solution. In the physical world, at least in America, it is not difficult to change one's identity. In the digital world, there is the problem of bots. The botnet detection market is expected to be worth over one billion USD by 2023, in a landscape where most digital activity is still heavily centralized. These centralized digital solutions have the advantage of being able to track IP addresses, request phone verification, and present CAPTCHAs to users in order to authenticate them. If this problem is so difficult to solve in the centralized world, how much more challenging will it be in the decentralized world, where none of these techniques are available?
|
|
||||||
|
|
||||||
> In this paper, we explore the idea of using a web of trust as a tool to add authenticity to decentralized identifiers (DIDs). We define a framework for deriving relative trust degrees using a given trust metric: a "trustworthiness" score for a given identity from the perspective of another identity. It is our intent that this framework may be used as a starting point for an ongoing exploration of graph-based, decentralized trust. We believe this approach may ultimately be used as a foundation for decentralized reputation.
|
|
||||||
|
|
||||||
* [*Resource Integrity Proofs*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/resource-integrity-proofs.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/resource-integrity-proofs.md)
|
|
||||||
- Ganesh Annan and Kim Hamilton Duffy
|
|
||||||
|
|
||||||
> Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?
|
|
||||||
|
|
||||||
> This paper proposes a linking solution that decouples integrity information from link and resource syntaxes, enabling verification of any representation of a resource from any type of link. We call this approach Resource Integrity Proofs (RIPs). RIPs provide a succinct way to link to resources with cryptographically verifiable content integrity. RIPs can be combined with blockchain technology to create discoverable proofs of existence to off-chain resources.
|
|
||||||
|
|
||||||
* [*Use Cases and Proposed Solutions for Verifiable Offline Credentials*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/offline-use-cases.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/offline-use-cases.md)
|
|
||||||
- Michael Lodder, Samantha Mathews Chase, and Wolf McNally
|
|
||||||
|
|
||||||
> In this paper we cover various scenarios where some or all parties have intermittent, unreliable, untrusted, insecure, or no network access, but require cryptographic verification (message protection and/or proofs). Furthermore, communications between the parties may be only via legacy voice channels. Applicable situations include marine, subterranean, remote expeditions, disaster areas, refugee camps, and high-security installations. This paper then recommends solutions for addressing offline deployments.
|
|
||||||
|
|
||||||
![](https://i.imgur.com/TpsPXoa.png)
|
|
||||||
|
|
||||||
|
|
||||||
## Topics and Advance Readings [**^**](#contents)
|
|
||||||
|
|
||||||
In advance of the design workshop, all participants are requested to produce a one-or-two page topic paper to be shared with the other attendees on either:
|
|
||||||
|
|
||||||
* A specific problem that they wanted to solve with a web-of-trust solution, and why current solutions (PGP or CA-based PKI) can't address the problem?
|
|
||||||
* A specific solution related to the web-of-trust that you'd like others to use or contribute to?
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 1 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/Hv2rPVy.png)
|
|
||||||
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* [Advanced Web-of-Trust Concepts](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/advanced-web-of-trust-concepts.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Attempts at common terminology for digital identity systems](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/shared_terminology_for_digital_identity_systems.md)
|
|
||||||
- Christian Lundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Authorities vs. Peers: Pain Points in Security](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/authorities-vs-peers--pain-points-in-security.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [Avoiding Confused Deputy Attack Using Capabilities](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/AvoidingConfusedDeputyAttackUsingCapabilities.md)
|
|
||||||
- Tyler Close *\<tyler.close@gmail.com\>*
|
|
||||||
* [Binding Identity in a Decentralized System](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/binding-identity-in-decentralized-system.md)
|
|
||||||
- Wayne Thayer *[@WThayer](https://twitter.com/wthayer) \<wthayer@gmail.com\>*
|
|
||||||
* [Blockchain-based Trust for Software Components](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/code-and-file-signing.adoc)
|
|
||||||
- Sean Gilligan *[@msgilligan](https://twitter.com/msgilligan) \<sean@msgilligan.com\>*
|
|
||||||
* [Blockchain Tech Opportunities in the Web-of-Trust](blockchain-opportunities.txt)
|
|
||||||
- Peter Todd *[@PeterToddBTC](https://twitter.com/PeterToddBTC) \<pete@petertodd.org\>*
|
|
||||||
* [Building a Web of Trust for E-commerce](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/decentralized_e-commerce.md)
|
|
||||||
- Michael Folkson *[@michaelfolkson](https://twitter.com/michaelfolkson) \<michaelfolkson@gmail.com\>*
|
|
||||||
* [Cool hack with XDI graphs, blockstore, link contracts, and cryptographic identifiers](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/cool-hack-xdi-blockstore-bip32.md)
|
|
||||||
- Markus Sabadello *[@Peacekeeper](https://twitter.com/Peacekeeper) \<markus@projectdanube.org\>*
|
|
||||||
* [Dealing with key loss in digital identity systems](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/dealing_with_key_loss_in_digital_identity.md)
|
|
||||||
- Christian Lundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Decentralized Authentication with Blockchain Auth](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Decentralized-Authentication-with-Blockchain-Auth.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Decentralized Cooperation Needs Decentralized Reputation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/DecentralizedCooperationNeedsDecentralizedReputation.md)
|
|
||||||
- Noah Thorp *[@noahthorp](https://twitter.com/noahthorp) \<noah@citizencode.io\>*
|
|
||||||
* [Different Models for Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/different-models-for-trust.md)
|
|
||||||
- Kaliya Hamlin *[@IdentityWoman](https://twitter.com/identitywoman) \<kaliya@identitywoman.net\>*
|
|
||||||
* [Distributed multi-ledger model for financial industry](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/DistributedMulti-ledgerModelForFinancialIndustry.md)
|
|
||||||
- Pavel Kravchenko *[@kravchenkopo](https://twitter.com/kravchenkopo) \<kravchenkopo@gmail.com\>*
|
|
||||||
* [Distributed Receptor-Based Computing](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Distributed_Receptor-Based_Computing.md)
|
|
||||||
- Arthur Brock - *[@ArtBrock](https://twitter.com/artbrock) \<artbrock@gmail.com>*
|
|
||||||
* [Distributed Trust Systems and the Kenyesian Beauty Contest](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Distributed-Trust-Systems-and-the-Kenyesian-Beauty-Contest.md)
|
|
||||||
- Joel Dietz *[@fractastical](https://twitter.com/fractastical) \<jdietz@gmail.com\>*
|
|
||||||
* [First Encounters with PGP](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/FirstEncountersWithPGP.md)
|
|
||||||
- Kiara Robles *[@anarchoass](https://twitter.com/anarchoass) \<kiara.robles@gmail.com\>*
|
|
||||||
* [Hierarchical Deterministic Keys: BIP32 & Beyond](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/hierarchical-deterministic-keys--bip32-and-beyond.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [How not to build an Orwellian reputation system](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/How-not-to-build-an-orwellian-reputation-system)
|
|
||||||
- Juan S. Galt *[@juansgalt](https://twitter.com/juansgalt) \<juans.galt@tuta.io\>*
|
|
||||||
* [Identity, Guidance and Situational Awareness](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Identity_Guidance_and_Situational_Awareness.md)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [Identity, Property and Simulation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Identity-Property-Simulation.md)
|
|
||||||
- Patrick Deegan \<pdeegan@gmail.com\>
|
|
||||||
* [Key revocation of lost and stolen keys](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Key-revokation-of-lost-and-stolen-keys.md)
|
|
||||||
- Martin Koeppelmann *[@koeppelmann](https://twitter.com/koeppelmann) \<martin.koeppelmann@consensys.net \>*
|
|
||||||
* [Key Transparency for End Users](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/key-transparency-for-end-users.md)
|
|
||||||
- Joseph Bonneau *[@JosephBonneau](https://twitter.com/josephbonneau) \<jbonneau@cs.stanford.edu\>*
|
|
||||||
* [Knowing When Your Digital Identity Has Been Compromised](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/knowing-when-your-identity-has-been-compromised.md)
|
|
||||||
- Justin Newton *[@JustinwNewton](https://twitter.com/justinwnewton) \<justin@netki.com\>*
|
|
||||||
* [Lightning Network and Web of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/lightning-network-and-web-of-trust.md)
|
|
||||||
- Joseph Poon *\<joseph@lightning.network\>*
|
|
||||||
* [Linked Local Names](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/linked-local-names.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Modern PKI: Identity Assertions Forming Trust Networks](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/modern-pki-identity-assertions.md)
|
|
||||||
- Duke Dorje *[@dukedorje](https://twitter.com/dukedorje) \<duke@citizencode.io\>*
|
|
||||||
* [PGP Paradigm](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/PGP-Paradigm.pdf)
|
|
||||||
- Jon Callas - *[@JonCallas](https://twitter.com/joncallas) \<jon@crypto.expert>* & Phil Zimmerman - *\<prz@mit.edu\>*
|
|
||||||
* [PKI Tools in EVM-based blockchains](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/pki_tools_in_evm_blockchains.md)
|
|
||||||
- ChristianLundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Progressive Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/progressive-trust.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Real life application of WoT: Refugee Use Case](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/refugee-use-case.md)
|
|
||||||
- Alicia Carmona *\<alicia.carmona@id2020.org\>*
|
|
||||||
* [Reputation and the Real World](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/ReputationAndTheRealWorld.md)
|
|
||||||
- Randy Farmer *[@FRandallFarmer](https://twitter.com/FRandallFarmer) \<randy.farmer@pobox.com\>*
|
|
||||||
* [Schnorr Signatures: An Overview](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Schnorr-Signatures--An-Overview.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [Secret Handshake: Key Exchange as a Capability System](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/key-exchange-as-capability-system.md)
|
|
||||||
- Dominic Tarr *[@DominicTarr](https://twitter.com/DominicTarr) \<dominic.tarr@gmail.com\>*
|
|
||||||
* [Secure Naming on the Blockchain](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Secure-Naming-on-the-Blockchain.md)
|
|
||||||
- Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@onename.com\>* and Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Selective Disclosure of Identity with Hierarchical Deterministic Keys and JSON Web Tokens](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Selective-Disclosure-of-Identity.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Tensions related to identity and community regulation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/tensions-related-to-identity-and-community-regulation.md)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [The Naming of Things](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/The-Naming-of-Things.txt)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [Thin Clients](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/thin-clients.md)
|
|
||||||
- Greg Slepak *[@TaoEffect](https://twitter.com/TaoEffect) \<hi@okturtles.com\>*
|
|
||||||
* [Trust Exchange: An Architecture for a Permanent Open Trust Network](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Trust-Exchange-An-Architecture-for-a-Permanent-Open-Trust-Network.md)
|
|
||||||
- Harlan T. Wood *[@HarlanTWood](https://twitter.com/harlantwood) \<h@rlan.me \>*
|
|
||||||
* [Web of Trust with Blockchain IDs](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Web-of-Trust-with-Blockchain-IDs.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [XDI Link Contracts: An Overview](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/xdi-link-contracts.md)
|
|
||||||
- Drummond Reed *[@DrummondReed](https://twitter.com/DrummondReed) \<drummond@respect.network\>*
|
|
||||||
* [How Not to build and Orwellian reputation system](How-Not-to-build-an-Orwellian-reputation-system.md)
|
|
||||||
- [Juan S. Galt](http://twitter.com/juansgalt)
|
|
||||||
* [Notes on the IPFS Keychain (or the Web Keychain)](ipfs-keychain.md)
|
|
||||||
* [IPFS - The Permanent Web](ipfs-links.md)
|
|
||||||
* [multiplexed: a 'slightly radical' framing of identity](multiplexed--a-slightly-radical-framing-of-identity.md)
|
|
||||||
- \<[du5t@multiplexed.be](mailto:du5t@multiplexed.be)\>
|
|
||||||
* [RLPx: Cryptographic Network & Transport Protocol - Version 0.3](rlpx.md)
|
|
||||||
- Alex Leverington
|
|
||||||
* [Self-certifying File System](sfs.md)
|
|
||||||
* [Trust Models, Accountability, LIfeCycle and Social Context](Trust%20Models%2C%20Accountability%2C%20LIfeCycle%20and%20Social%20Context.md)
|
|
||||||
- by Kaliya "[Identity Woman](http://www.identitywoman.net/)" Young (formerly Hamlin)
|
|
||||||
|
|
||||||
### RWoT ID2020 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/ZG5msLT.png)
|
|
||||||
|
|
||||||
* [A Double Edge Sword of Having an Identity](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/double_edged_identity.md)
|
|
||||||
- Marta Piekarska \<marta@blockstream.io\>
|
|
||||||
* [A Self-Sovereign Identity Architecture](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/a-self-sovereign-identity-architecture.pdf)
|
|
||||||
- Manu Sporny *[@msporny](https://twitter.com/manusporny?lang=en)* and David Longley
|
|
||||||
* [Blockstack: Design and Implementation of a Global Naming System with Blockchains](https://blockstack.org/blockstack.pdf)
|
|
||||||
- by Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@blockstack.com\>* and Jude Nelson *[@judecnelson](https://twitter.com/judecnelson) \<jude@blockstack.com\>* and Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@blockstack.com\>*
|
|
||||||
* [From Identity to Refugee Status Determination](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/identity_to_refugee_status_determination.md)
|
|
||||||
- Susan R. Ramonat \<SRamonat@seic.com\>
|
|
||||||
* [Peer Attestation of Identity in the Real World](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/PeerAttestationofIdentity.pdf)
|
|
||||||
- Dr Shaun Conway & Lohan Spies
|
|
||||||
* [Sovereign Identity Namespaces](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/SovereignIdentityNamespaces.pdf)
|
|
||||||
- Drummond Reed [@DrummondReed](https://twitter.com/drummondreed?lang=en) \<drummond@respectnetwork.com\>
|
|
||||||
* [Identity System Essentials](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/Identity-System-Essentials.pdf)
|
|
||||||
- Samuel Smith and Dmitry Khovratovich
|
|
||||||
* [Decentralized Identifiers (DIDs) and Decentralized Identity Management (DIDM)](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/DID-Whitepaper.md)
|
|
||||||
- Les Chasen
|
|
||||||
* [“Immutable Me” - A Discussion Paper Exploring Data Provenance To Enable New Value Chains](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/immutable-me.pdf)
|
|
||||||
- *George Samman [@sammantic](https://twitter.com/sammantic) \<[George.Samman@meeco.me](mailto:George.Samman@meeco.me)\> and Katryna Dow [@katrynadow](https://twitter.com/katrynadow) \<[Katryna.Dow@meeco.me](mailto:Katryna.Dow@meeco.me)\>*
|
|
||||||
* [No Secure Protocol = No Sovereign Identity](/topics-and-advance-readings/no-secure-protocol-equals-no-sovereign-identity.md)
|
|
||||||
- Greg Slepak *[@taoeffect](https://twitter.com/taoeffect) \<hi@okturtles.com\>*
|
|
||||||
* [Questions around key management for digital ID systems](/topics-and-advance-readings/questions_around_key_management.md)
|
|
||||||
- by Christian Lundkvist *[@chrislundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net\>* and Rouven Heck *[@rh7](https://twitter.com/rh7) \<rouven.heck@consensys.net\>*
|
|
||||||
* [The Path to Self-Sovereign Identity](/topics-and-advance-readings/the-path-to-self-sovereign-identity.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Distibuted Identity Management - Verifiable Claims Exchange Via Agents](/topics-and-advance-readings/DistibutedIdentityManagement-VerifiableClaimsExchangeViaAgents.pdf)
|
|
||||||
- Gary Zimmerman
|
|
||||||
* [Blockstack Rules and Support for Multiple Blockchains](/topics-and-advance-readings/blockstack-rules-and-multiple-blockchains.md)
|
|
||||||
- Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@blockstack.com\>
|
|
||||||
* [Plurality of Provenance in Distributed Identity](/topics-and-advance-readings/Plurality%20of%20Provenance%20in%20Distributed%20Identity.Andrieu.2016.pdf)
|
|
||||||
- Joe Andrieu \<[joe@joeandrieu.com](mailto:joe@joeandrieu.com)\>
|
|
||||||
* [Identity is a Phenomenon, Not a Property](/topics-and-advance-readings/Identity%20is%20a%20Phenomenon%20Not%20a%20Property.Andrieu.2016.pdf)
|
|
||||||
- Joe Andrieu \<[joe@joeandrieu.com](mailto:joe@joeandrieu.com)\>
|
|
||||||
* [Dex: Deterministic Predicate Expressions for Smarter Signatures](/topics-and-advance-readings/DexPredicatesForSmarterSigs.md)
|
|
||||||
- Peter Todd
|
|
||||||
* [Scaling a BFT Consensus Protocol for Identity](/topics-and-advance-readings/scaling-a-bft-consensus-protocol-for-identity.md)
|
|
||||||
- Jason Law & Lovesh Harchandani
|
|
||||||
* [XDI Graphs in IPFS](/topics-and-advance-readings/XDI-Graphs-in-IPFS.md)
|
|
||||||
- Markus Sabadello
|
|
||||||
* [Replace Blockchain with DLT (Distributed Ledger Technology)](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/Erik%20Anderson-USE%20CASE%20story.md)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Blockchain For Capital Markets](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Blockchain_for_capital_markets.pdf)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Identity Management IdSec](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/PM_15_026_FIN2_IdSEC_160513.pdf)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Trust-i-ness](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Trust-i-ness.md)
|
|
||||||
- by Kaliya "Identity Woman"
|
|
||||||
* [ID2020 - Self-Sovereign Identity](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Rebooting%20Web%20of%20Trust%20Position%20MindMap%20-%20pre-reading%20DRAFT%20ID2020%20Summit%202016.pdf)
|
|
||||||
- Patrick Deegan
|
|
||||||
* [Identity and decentralised Communication](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Identity%20and%20decentralised%20communications.md)
|
|
||||||
- By Harsh Patel
|
|
||||||
* [Chime National Patent ID Challenge](/topics-and-advance-readings/CHIMENationalPatientIDChallenge.pdf)
|
|
||||||
* [Usability and Multiplicity in Global Identity Management](/topics-and-advance-readings/Crocker-ID-Usability-Multiplicity.md) — by D. Crocker ~ \<[dcrocker@bbiw.net](mailto:dcrocker@bbiw.net)\>
|
|
||||||
* [Decentralized Identity Satoshi Style](/topics-and-advance-readings/Decentralized-Identity-Satoshi-Style) - by Darrell Duane - \<[darrell@idi.io](mailto:darrell@idi.io)\>
|
|
||||||
* [Declaration of Identity - Printed.pdf](https://github.com/infominer33/rwot2-id2020/blob/master/topics-and-advance-readings/Declaration%20of%20Identity%20-%20Printed.pdf)
|
|
||||||
* [Identities for Moving Things](/topics-and-advance-readings/IdentitiesForMovingThings.md) - by Daniel Ford - \<[dan@keoja.com](mailto:dan@keoja.com)\>
|
|
||||||
* [Legalizing Identity Protocols for the United Nations 16.9](/topics-and-advance-readings/Legalizing-Identity-Protocols-United-Nations.md)
|
|
||||||
* [Personal Levels of Assurance (PLOA)](/topics-and-advance-readings/PLOA%20White%20Paper%20-%20v1.01.pdf) — by J. Oliver Glasgow and Jeff Dogen, Kennie Kwong, David Chen, Johannes Jaskolski, Kevin Castellow, Dan Druta — An AT&T Whitepaper on Assurance
|
|
||||||
* [Clues](/topics-and-advance-readings/clues.md) — by Nicola Greco
|
|
||||||
— something that serves to guide or direct in the solution of a problem or mystery.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 3 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/05aTksa.png)
|
|
||||||
|
|
||||||
* [Identity as Linked Data on Immutable Ledgers](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md)
|
|
||||||
- Tim Daubenschuetz and Trent McConaghy
|
|
||||||
* [EU General Data Protection Regulation & Self-Sovereign Identifier(s)](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/EU%20General%20Data%20Protection%20Regulation%20%26%20Self-Sovereign%20Identifier(s))
|
|
||||||
- David Robert
|
|
||||||
* [Identity Forking and Federated Reputation](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-forking-and-federated-reputation.md)
|
|
||||||
- Christopher Malon
|
|
||||||
* [OpenTimestamps: Scalable, Trustless, Distributed Timestamping with Bitcoin](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/opentimestamps.md)
|
|
||||||
- Peter Todd
|
|
||||||
* [Distributed Identity, Distributed Self](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/DistributedIdentityDistributedSelf.md)
|
|
||||||
- Natalie Smolenski
|
|
||||||
* [Blockchain Extensions for Linked Data Signatures](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md)
|
|
||||||
- the Signature Super Friends (Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley)
|
|
||||||
* [Fit for Purpose Blockchains](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/fit-for-purpose-blockchains.md)
|
|
||||||
- Digital Bazaar (Manu Sporny, Dave Longley, Dave Lehn, and Adam Lake)
|
|
||||||
* [Taxonomy of Identity Interaction Types](https://github.com/Identitywoman/Writing/blob/master/Taxonomy-of-Identity-Interaction-Types.md)
|
|
||||||
- Kaliya Young
|
|
||||||
* [Privacy Preserving Identity Architectures](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/privacy-preserving-identity-architectures.md)
|
|
||||||
- Anonymous (no, not that Anonymous, the other one)
|
|
||||||
* [A Technlogy-Free Definition of Self-Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)
|
|
||||||
- Joe Andrieu
|
|
||||||
* [Architecture of Proof-of-Stake Blockchain that Doesn’t Have Native Coin and its Applicability to Decentralized Trading](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/Proof-of-stake-without-native-coin.md)
|
|
||||||
- Pavel Kravchenko
|
|
||||||
* [JXD Examples](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/JXD-Examples.md)
|
|
||||||
- Markus Sabadello
|
|
||||||
* [Anonymous Credentials in Sovrin](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/anonymous-credentials-in-sovrin.md)
|
|
||||||
- Jason Law and Daniel Hardman
|
|
||||||
* [Portable Reputation Toolkit](/topics-and-advance-readings/portable-reputation-toolkit.md)
|
|
||||||
- Noah Thorp and Harlan Wood
|
|
||||||
* [Blockchain Attestation Taxonomies](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/attestation-taxonomies.md)
|
|
||||||
- Christian Lundkvist
|
|
||||||
* [Slepak's Triangle: The fundamental user limit of decentralized consensus systems](topics-and-advance-readings/Slepaks-Triangle.pdf)
|
|
||||||
- Greg Slepak (@taoeffect)
|
|
||||||
* [Sovereign Identity Model for Digital Ecologies](topics-and-advance-readings/Sovereign-Identity-Model-for-Digital-Ecologies.md)
|
|
||||||
- Patrick Deegan
|
|
||||||
* [Alternative Futures: Framework for Identity Scenarios](topics-and-advance-readings/alternative-futures-frameworks.md)
|
|
||||||
- Alessandro Voto
|
|
||||||
* [Powering the Physician-Patient Relationship with HIW of One Blockchain Health IT](physician-patient-relationship.pdf)
|
|
||||||
- Adrian Gropper
|
|
||||||
* [Creating a Humanized Internet](https://github.com/vshen2010/rebooting-the-web-of-trust-fall2016/blob/master/topics-and-advance-readings/Creating%20a%20Humanized%20Internet.pdf)
|
|
||||||
- Monique Morrow, et al
|
|
||||||
* [Smart Consent Protocol](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/Consent%20and%20rights%20to%20use%20Personal%20Data.md)
|
|
||||||
- Dr Shaun Conway, Lohan Spies, Jonathan Endersby, Tim Daubenschütz (see [Completed Papers III](#completed-papers-iii-))
|
|
||||||
* [Creating a Humanized Internet](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/Creating%20a%20Humanized%20Internet.pdf)
|
|
||||||
- Akram Alfawakheeri \<[akram.f1_1@gmail.com](mailto:akram.f1_1@gmail.com)\>, Mark Kovarski \<mark@kovarski.org\>, Aron Dutta <\aron_dutta@yahoo.com\>, Monique Morrow \<monique.morrow223@gmail.com\>, Vivien Shen \<vshen670@gmail.com\>
|
|
||||||
* [DIDs and Personal Data Storage for Children](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/DIDsandPersonalDataStorageforChildren.pdf)
|
|
||||||
- Jonathan Endersby, Shaun Conway, Lohan Spies
|
|
||||||
* [BIP32-Ed25519 Hierarchical Deterministic Keys of a Non-Linear Keyspace](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/HDKeys-Ed25519.pdf)
|
|
||||||
- Dmitry Khovratovich, Jason Law
|
|
||||||
* [Sovrin - Digital Identities in the Blockchain Era](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/Sovrin--digital-identities-in-the-blockchain-era.pdf)
|
|
||||||
* [Alternative Futures: Framework for Identity Scenarios](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/alternative-futures-framework.md)
|
|
||||||
- by Alessandro Voto
|
|
||||||
* [Blockchain Technologies Feature Analysis](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/blockchain-technologies-feature-analysis.md)
|
|
||||||
-Copyright 2016 Digital Bazaar, Inc.
|
|
||||||
* [DID (Decentralized Identifier) Specification](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/did-spec-working-draft-03.md)
|
|
||||||
- Editors: Drummond Reed, Les Chasen Contributors: Christopher Allen, Manu Sporny, David Longley, Jason Law, Daniel Hardman, Markus Sabadello (see [Completed Papers III](#completed-papers-iii-))
|
|
||||||
* [Towards a User Interface for Selectively Revealing Fine-Grained Personal Information to Transaction Counterparties](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/rgrant-user-interface-standards-rwot-fall2016.md)
|
|
||||||
* [Recovery strategy for user-controlled keys for self-sovereign identity](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/user-controlled-key-recovery.md)
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 4 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/HcVlTZQ.png)
|
|
||||||
|
|
||||||
* [Aligning Signature Formats](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/SignatureFormatAlignment.md) by Manu Sporny, Christopher Allen, Jason Law, and Ryan Shea
|
|
||||||
* [Beyond Identity Cards](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Beyond-Identity-Cards.pdf) by Joe Andrieu
|
|
||||||
* [Blockcerts and Open Badges Signature Alignment](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/BlockcertsAlignment.md) by Kim Hamilton Duffy
|
|
||||||
* [Booting a Web of Sovereignty with a Decentralized Social App](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Booting-a-Web-of-Sovereignty-with-a-Decentralized-Social-App.md) by Adam Lake
|
|
||||||
* [Certificate Chains for DID-based Self-sovereign Identities](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/certificate_chains_dids.md) by Christian Lundkvist
|
|
||||||
* [Credit-based Reputations for Identity Management with Blockchain and Flow Networks](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Credit-based-Reputations-for-Identity-Management.md) by Tobias Mayer, Obar Hasan, and Lionel Brunie
|
|
||||||
* [DID Auth](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-auth.md) by James Monaghan
|
|
||||||
* [The DID Family of Specifications](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-family-of-specifications.md) by Drummond Reed
|
|
||||||
* [DID Method Specifications / BTCR and PGPR](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-methods-btcr-pgpr.md) by Ryan Grant
|
|
||||||
* [DID Names](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-names.md) by Drummond Reed and James Monaghan
|
|
||||||
* [Distributed Identities as a EU Cross-border Identity Infrastructure](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Levrage_EU_identities.md) by L. Boldrin
|
|
||||||
* [DKMS—Decentralized Key Management System](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/dkms-decentralized-key-mgmt-system.md) by Drummond Reed
|
|
||||||
* [Fostering the Resilience of an Ecosystem of Workers through Regulated Decentralized Reputation](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Fostering-resilience.md) by Philippe Honigman & Klara Sok
|
|
||||||
* [ID-Blockchain: An Initiative towards Privacy-preserving Blockchain-based Identity](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/id-blockchain.md) by Olivier Maas & Florent Poiron
|
|
||||||
* [The IP Blockchain: Enhancing Global Responsiveness to Infectious Disease Outbreaks](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/RWoT_IPblockchain.md) by Moses Ma, Mark van der Waal, and Net Jacobsson
|
|
||||||
* [Project Vouch: A Decentralized Identity Network Based on Public Attestation, Reputation, and Approval of Identity Attributes](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/ProjectVouch_Peer-attestation-and-reputation-based-identity.md) by Angus Champion
|
|
||||||
* [Reputation Proofs](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/rep-proofs.md) by Dmitry Khovratovich
|
|
||||||
* [RWoT Proposals and Modern Portable Secure Hardware](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/RWoT_proposals_and_modern_portable_secure_hardware.md) by Nicolas Bacca
|
|
||||||
* [Self-sovereign Delegated Identity](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/170418_IDEAS_Paper.pdf) by Pierre Noizat
|
|
||||||
* [Towards a User-centered Web of Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Towards-a-user-centered-web-of-trust.md) by Fabien Petitcolas & Paul Dunphy
|
|
||||||
* [Trust for Security and Security for Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/topic_alexopoulos.md) by Nikolaos Alexopoulos
|
|
||||||
* [Verifiable Claims and Web of Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/WoTVerifiableClaims.md) by Manu Sporny, Christopher Allen, Joe Andrieu, Matthew Collier, Dave Longley, and Adam Lake
|
|
||||||
* [XDI Verifiable Claims and Link Contracts](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/xdi-verifiable-claims-link-contracts.md) by Markus Sabadello
|
|
||||||
|
|
||||||
### RWoT 5 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0yF0Ai7.png)
|
|
||||||
|
|
||||||
The following advanced readings have been prepared as primers, intended to give you a foundation in some of the topics that may be discussed at the design workshop:
|
|
||||||
|
|
||||||
* [A Primer on Functional Identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/functional-identity-primer.md) by Joe Andrieu
|
|
||||||
* [A Primer on Self-Sovereign identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/self-sovereign-identity-primer.md) by Christopher Allen & Shannon Appelcline
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/did-primer.md) by Drummond Reed & Manu Sporny
|
|
||||||
* [A Verifiable Claims Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/verifiable-claims-primer.md) by Manu Sporny
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md)
|
|
||||||
|
|
||||||
Here are the rest of the advance readings to date:
|
|
||||||
|
|
||||||
* [#RebootingWebOfTrust User Story & Tech Concept](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/RWOT-User-Story.md) by Christopher Allen
|
|
||||||
* [ActivityPub: from decentralized to distributed social networks](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/activitypub-decentralized-distributed.md) by Christopher Lemmer Webber
|
|
||||||
* [Architectural Layering for Decentralized Identification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Architectural-Layering-for-Decentralized-Identification.md) by Drummond Reed
|
|
||||||
* [BFTKV: Byzantine Fault Tolerant Web of Trust based Key-Value Storage](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/byzantine-fault-tolerant-web-of-trust-based-key-value-storage.md) by Ercan Ozturk
|
|
||||||
* [BFTKV DID Method Specification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/BFTKV-DID-Method-Specification.pdf) by Ercan Ozturk
|
|
||||||
* [Biometric transaction signing on blockchain](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Biometric-transaction-signing-on-blockchain.md) by John Callahan & Virgil Tornoreanu
|
|
||||||
* [Blockchain Based Digital Signatures: Admissibility and Enforceability](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Blockchain-Based-Digital-Signatures--Admissibility-and-Enforceability.md) by Dazza Greenwood
|
|
||||||
* [BTCR DIDs and DDOs](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/btcr-dids-ddos.md) by Kim Hamilton Duffy
|
|
||||||
* [Credential Handler API](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/credential-handler-api.md) by Dave Longley and Manu Sporny
|
|
||||||
* [Data Minimization and Selective Disclosure](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Data-minimization-and-selective-disclosure.md) by Lionel Wolberger
|
|
||||||
* [Decentralized Identifier Tooling](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/credential-handler-api.md) by Dave Longley & Manu Sporny
|
|
||||||
* [DID for the 3D Web](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/did-3d-web.md) by Alberto Elias
|
|
||||||
* [DID Tooling](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/did-tooling.md) by Manu Sporny and Matt Collier
|
|
||||||
* [First XDI Link Contract between "btcr" DID and "sov" DID](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/first-xdi-link-contract-between-btcr-did-and-sov-did.md) by Markus Sabadello
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md) by Kyle Den Hartog
|
|
||||||
* [HIE of One Loop: A Patient-Controlled Independent Health Record](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Loop-white-paper.pdf) by Adrian Gropper
|
|
||||||
* [The Horcrux protocol: Biometric credentials as high-privacy verifiable claims](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Biometric-credentials-as-high-privacy-verifiable-claims.md) by John Callahan & Asem Othman
|
|
||||||
* [Hub Asset Access Control System - Intent](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/DIF-Hub-Permissions-RWOT-Intent.md) by Daniel Buchner
|
|
||||||
* [Hypercerts: Blockcerts Revocation Improvements](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/hypercerts-blockcerts_revocation.md) by João Santos and Kim Hamilton Duffy
|
|
||||||
* [Identifying stakeholders' challenges in the digital economy](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Identifying-challenges-in-the-digital-economy.md) by Irene Hernandez
|
|
||||||
* [Open Badges (and Blockcerts) as Verifiable Claims](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/open-badges-as-verifiable-claims.md) by Kim Hamilton Duffy and Nate Otto
|
|
||||||
* [Owned vs. Unowned Claims and Self-Sovereign Identity](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/owned-vs-unowned-claims-and-ssi.md) by Natalie Smolenski
|
|
||||||
* [Recommendations for Decentralized Key Management Systems](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/dkms-recommendations.md) by Michael Lodder
|
|
||||||
* [Trust Objects: Enabling Advanced Reputation Services on the Web of Trust](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/trust-objects-rough-draft.pdf) by Moses Ma & Dr. Rutu Mulka
|
|
||||||
* [Original Proposal](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/trust-objects-proposal.md) by Moses Ma & Dr. Rutu Mulka
|
|
||||||
* [Veres One DID Method Specification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/veres-one-did-method.md) by Manu Sporny, Dave Longley & Matt Collier
|
|
||||||
* [Verifiable Claims of Impact](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/verifiable-claims-of-impact.md) by Cedric Franz & Dr. Shaun Conway
|
|
||||||
* [Visa? Really?](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Visa-Really.md) by Kaliya Identity Woman
|
|
||||||
* [Data Minimization and Selective Disclosure](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Data-minimization-and-selective-disclosure.md) by Lionel Wolberger
|
|
||||||
* [HIE of One Loop: A Patient-Controlled Independent Health Record](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Loop-white-paper.pdf) by Adrian Gropper, MD and the Loop Project Team
|
|
||||||
|
|
||||||
### RWoT 6 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/LmmFZws.png)
|
|
||||||
|
|
||||||
* [Attribute Based Credentials and Variable Length Data Graphs](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/AttributeBasedCredentials_and_VariableLengthDataGraphs.md) by nage
|
|
||||||
* [Blockchain Timestamps Unnecessary In Proof-of-Work?](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Blockchains-Timestamps-Unnecessary-In-PoW.md) by Greg Slepak
|
|
||||||
* [BTCR DID Resolver](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/btcr_did_resolver.md) by Kim Hamilton Duffy, Christopher Allen, Ryan Grant
|
|
||||||
* [Collegial Certifcation Works for Truly Collegial Communities](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Collegial%20Certification%20Works%20for%20Truly%20Collegial%20Communities.pdf) by Wes Kussmaul
|
|
||||||
* [Credential Providers for Signing Application Requests](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/CredentialProvider_App_Integration.md) by Cedric Franz
|
|
||||||
* [DClaims News - A Fake News Mitigation Platform](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DClaims.md) by João Santos
|
|
||||||
* [Decentralized Attestations Storage - Current Challenges](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/decentralised-attestations-storage-network-challenges.md) by Kulpreet Singh
|
|
||||||
* [Decentralized Identities for the Cannabis Industry](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/cannabis-kyc.md) by Matthew Nguyen & Nicholas Shook
|
|
||||||
* [Decentralized Interfaces and the Request-Responsive World](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/decentralized-interfaces.md) by Vlad Kahoun
|
|
||||||
* [Decentralized Self-certifying Self-Identifing Data](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Self_ID_Data_KeyMgmt.md) by Samuel M. Smith
|
|
||||||
* [A Demonstration of the Veres One Blockchain](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-demo.md) by David I. Lehn, Manu Sporny, David Longley, Matt Collier, and Chris Webber
|
|
||||||
* [DID-Auth Protocol](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Auth%20protocol.md) by Kyle Den Hartog
|
|
||||||
* [DID Auth: Scope, Formats, and Protocols](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID%20Auth:%20Scope%2C%20Formats%2C%20and%20Protocols.md) by Markus Sabadello
|
|
||||||
* [did:erc725 method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Method-erc725.md) by Markus Sabadello, Fabian Vogelsteller, and Peter Kolarov <pkolarov@finid.me>
|
|
||||||
* [Distributed Reputation Systems Using Blockchain Records](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/distributed-reputation-systems-kate-sills.md) by Kate Sills
|
|
||||||
* [Hashed PII Question](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/hashed-PII-Question.md) by Identity Woman
|
|
||||||
* [The Horcrux Protocol: A Method for Decentralized Biometric-based Self-sovereign Identity](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/HorcruxProtocol.pdf) by Asem Othman & John Callahan
|
|
||||||
* [Identity System for Immersive and Ambient Computing](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/identy_immersive_ambient_computing.md) by Alberto Elias
|
|
||||||
* [Integrating Identity Silos via Address Books](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Diam.md) by vishal144
|
|
||||||
* [Open Badges Prototypes and Action Items 2018](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/openbadges-prototypes-action-items-2018.md) by Nate Otto and Kim (Hamilton) Duffy
|
|
||||||
* [Open TLS](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/OpenTLS.md) by Sam Curren
|
|
||||||
* [Open Verifiable Data to Drive the Digital Economy](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/TheOrgBook%20-%20RWoT%20Mar%202018%20-%20Province%20of%20BC.md) by John Jordan
|
|
||||||
* [Petnames for Self Sovereign and Human Readable Identifiers](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/petnames.md) by Christopher Lemmer Webber
|
|
||||||
* [Proposed Collaboration on Open Standards for Data Wallet and Data Service Integration](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/data_wallet_serivce_integration.md) by Ron Kreutzer
|
|
||||||
* [Recent Happenings with Linked Data Capabilities](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md) by Christopher Lemmer Webber
|
|
||||||
* [Self-sovereign Compliance](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/self-sovereign-compliance.md) by Moses Ma
|
|
||||||
* [The Three Primary Roles in the Sovrin Web of Trust Model](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/sovrin-web-of-trust-3-primary-roles.md) by Drummond Reed
|
|
||||||
* [Towards a Sustainable Technology Commons](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/SustainableTechnologyCommons-HeatherVescentv3.md) by Heather Vescent
|
|
||||||
* [Using Blockchain to Store Academic Accreditations](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/documentorum.md) by Luiz Gustavo Ferraz Aoqui and Andrei Moskalev
|
|
||||||
* [Veres One Primer](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-primer.md) by Manu Sporny, et. al.
|
|
||||||
* [The Veres One DID Method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-did-method.md) by Manu Sporny, David Longley, and Chris Webber
|
|
||||||
* [Veres One Demo](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-demo.md) by David I. Lehn, et. al.
|
|
||||||
* [Web of Pragmatics: A Comment on Methodology](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Web-of-Pragmatics.md) by D. Crocker
|
|
||||||
|
|
||||||
### RWoT 7 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/MCjnuJw.png)
|
|
||||||
|
|
||||||
* [Addressing Global/Local Barriers to Adoption of Decentralized Identity Systems](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Adoption.md) by Eric Brown
|
|
||||||
* [Agent to Agent Communication Protocol Overview](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/a2a-comm-protocol-overview.md) by Kyle Den Hartog
|
|
||||||
* [Blockcerts -- Where we are and what's next](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/blockcerts_roadmap.md) by Kim Hamilton Duffy, Anthony Ronning, Lucas Parker, and Peter Scott
|
|
||||||
* [Can Curation Markets Establish a Sustainable Technology Commons](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/CanCurationMarketsEstablishSustainableTechnologyCommons.pdf) by Sam Chase
|
|
||||||
* [CapAuth](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/capauth.md) by Manu Sporny, Dave Longley, Chris Webber, and Ganesh Annan
|
|
||||||
* [A Concept Diagram For RWOT Identity Terms](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/towards-a-terminology-concept-map.md) by Andrew Hughes
|
|
||||||
* [Cryptocurrency Wallets as a Form of Functional Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Cryptocurrency%20wallets%20a%20an%20application%20of%20Functional%20Identity.md) by Mikerah Quintyne-Collins and Abdulwasay Mehar
|
|
||||||
* [Decentralized Error Reporting](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/decentralized-error-reporting.md) by Jack Poole
|
|
||||||
* [Decentralized Identities and eIDAS](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/leveraging-eidas-for-did.md) by Oliver Terbu
|
|
||||||
* [Decentralized Identity: Hub Authentication & Message Encryption](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/did-auth-jwe.md) by Daniel Buchner
|
|
||||||
* [DIDDoc Conventions for Interoperability](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/diddoc-conventions-for-interoperability.md) by Stephen Curran & Olena Mitovska
|
|
||||||
* [DIDs In DPKI](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md) by Greg Slepak
|
|
||||||
* [DID Resolution Topics](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/did-resolution-topics.md) by Markus Sabadello
|
|
||||||
* [Digital Identity for the Homeless](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Digital-Identity-for-the-Homeless.md) by Matthew Wong, T. Tian & CG Chen
|
|
||||||
* [Exploring Browser Web of Trust Use Cases](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/exploring-browser-wot-use.md) by Peter Snyder and Ben Livshits
|
|
||||||
* [Five Mental Models of Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/five-mental-models-of-identity.md) by Joe Andrieu
|
|
||||||
* [Identity Hub Permissions / Authorization](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/identity-hub-permissions.md) by Daniel Buchner
|
|
||||||
* [IPLD as a general pattern for DID Documents](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/ipld_did_documents.md) by Christian Lundkvist
|
|
||||||
* [Is a Decentralized Collective Identity Possible?](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Decentralized-Collective-Identity.md) by Heather Vescent
|
|
||||||
* [Magenc Magnet URIs: Secure Object Permanence for the Web](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/magenc.md) by Christopher Lemmer Webber
|
|
||||||
* [Measuring Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/measuring-trust.md) by Tyler Yasaka
|
|
||||||
* [More Control for Identity Holders](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/more-control-for-identity-holders.md) by Arturo Manzaneda and Ismenia Galvao
|
|
||||||
* [Nobody REALLY Trusts the Blockchain](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Nobody_REALLY_Trusts_the_Blockchain.md) by Daniel Burnett
|
|
||||||
* [Not-a-Bot: A Use Case for Decentralized Identity using Proximity Verification to generate a Web of Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/not-a-bot.md) by Moses Ma & Claire Rumore
|
|
||||||
* [The Political Economy of Naming](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/political-economy-of-naming.md) by Kate Sills
|
|
||||||
* [A Public Web of Trust of Public Identities](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/a-public-web-of-trust-of-public-identities.md) by Ouri Poupko and Ehud Shapiro
|
|
||||||
* [Resource Integrity Proofs](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/resource-integrity-proofs.md) by Ganesh Annan, Manu Sporny, Dave Longley, and David Lehn
|
|
||||||
* [RWoT Tribal Knowledge: Cryptographic and Data Model Requirements](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/crypto-data-model-requirements.md) by Manu Sporny, Dave Longley, and Chris Webber
|
|
||||||
* [The Role of Standards in Accelerating Innovation](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/The_Role_of_Standards_in_Accelerating_Innovation.md) by Michael B. Jones
|
|
||||||
* [Scoped Presentation Request on Verifiable Credentials](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/presentation-request/presentation-request.md) by Martin Riedel
|
|
||||||
* [Secure Crypto-Wallet Introductions](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Secure%20Crypto-Wallet%20Introductions.md) by Wolf McNally, Ryan Grant
|
|
||||||
* [Standards for Agency and Decentralized Information Governance - Early Experience](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/standards-for-governance.md) by Adrian Gropper, MD, Michael Chen, MD, and Lydia Fazzio, MD
|
|
||||||
* [Towards Proof of Person](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/towards-proof-of-person.md) by Peter Watts
|
|
||||||
* [A Trustless Web-of-Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/trustless-web-of-trust.md) by Ouri Poupko
|
|
||||||
* [Verifiable Displays](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/verifiable_displays.md) by Kim Hamilton Duffy, Lucas Parker & Anthony Ronning
|
|
||||||
* [Verifiable Offline Credentials](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/verifiable-offline-credentials.md) by Michael Lodder
|
|
||||||
* [What (and Who) Is In Your Wallet](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/what-and-who-is-in-your-wallet.md) by Darrell O'Donnell
|
|
||||||
* [Digital Identity for the Homeless](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Digital-Identity-for-the-Homeless.md) by Matthew Wong, T. Tian & CG Chen
|
|
||||||
* [Zero Trust Computing with DIDs and DADs](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/ZeroTrustComputingWithDidsAndDads.md) by Samuel M. Smith
|
|
||||||
|
|
||||||
## License [**^**](#contents)
|
|
||||||
|
|
||||||
Unless otherwise noted, all RWoT Completed Papers, Topics and Advance Readings are licensed [Creative Commons CC-BY](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/LICENSE-CC-BY-4.0.md).
|
|
||||||
|
|
||||||
|
|
||||||
## RWoT Github Listing [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/self-sovereign-identity" target="_blank">/WebOfTrustInfo/self-sovereign-identity</a> - Articles and documents associated with designing and implementing identity technology using self-sovereign identity principles
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/website" target="_blank">/WebOfTrustInfo/website</a> - Website for http://www.WebOfTrust.info
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/community-resilience" target="_blank">/WebOfTrustInfo/community-resilience</a> - Rebooting Web of Trust Community Resilience Team
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/satyrn" target="_blank">/WebOfTrustInfo/satyrn</a> - A Markdown-based JavaScript Sandbox
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/sss" target="_blank">/WebOfTrustInfo/sss</a> - Library for the Shamir secret sharing scheme
|
|
||||||
- Forked from dsprenkels/sss
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/verifiable-news" target="_blank">/WebOfTrustInfo/verifiable-news</a> - TBD: W3C Credentials Community Group repository for curbing "social bots" and mitigating the spread of online misinformation and "fake news".
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/portable-reputation-toolkit" target="_blank">/WebOfTrustInfo/portable-reputation-toolkit</a>
|
|
||||||
|
|
||||||
### Workshops [**^**](#contents)
|
|
||||||
|
|
||||||
* [Rebooting the Web of Trust I: San Francisco (November 2015)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust)
|
|
||||||
* [Rebooting the Web of Trust II: ID2020 (May 2016)](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop)
|
|
||||||
* [Rebooting the Web of Trust III: San Francisco (October 2016)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016)
|
|
||||||
* [Rebooting the Web of Trust IV: Paris (April 2017)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2017)
|
|
||||||
* [Rebooting the Web of Trust V: Boston (October 2017)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017)
|
|
||||||
* [Rebooting the Web of Trust VI: Santa Barbara (March 2018)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018)
|
|
||||||
* [Rebooting the Web of Trust VII: Toronto (September 2018)](https://github.com/WebOfTrustInfo/rwot7-fall2018)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1,717 +0,0 @@
|
|||||||
---
|
|
||||||
title: "A \"complete\" listing of #RebootingWebOfTrust Papers, Topics, and Advance Readings"
|
|
||||||
description: Lets make this awesome collaborative work easier to explore!
|
|
||||||
image: "https://i.imgur.com/Nmxk4fE.png"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Rebooting Web Of Trust - Papers and Advance Readings Index
|
|
||||||
|
|
||||||
I wanted a list of all RWoT papers in one place, rather than having to directory hop to look for what I need. I'll be adding a short exerpt to each advance reading and then turning this into a database, so that it's easily searchable.+
|
|
||||||
|
|
||||||
See the [WebofTrust.Info](http://www.weboftrust.info/) or [github.com/WebOfTrustInfo](https://github.com/WebOfTrustInfo/) for more information.
|
|
||||||
|
|
||||||
> '[Web of Trust](https://en.wikipedia.org/wiki/Web_of_trust)' is a network of relationships that attest to our identity claims. *Each party attesting to your identity information becomes a strand in your web of trust.*
|
|
||||||
|
|
||||||
![](https://i.imgur.com/Nmxk4fE.png)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Selected RWoT Whitepapers](#selected-rebooting-web-of-trust-whitepapers-)
|
|
||||||
* [Primers](#primers)
|
|
||||||
* [RWoT Workshop Related](#rwot-workshop-related-)
|
|
||||||
* [Use Cases](#use-cases-)
|
|
||||||
* [Completed Papers](#completed-papers-)
|
|
||||||
* [Rebooting the Web of Trust I](#rebooting-the-web-of-trust-i-)
|
|
||||||
* [Rebooting the Web of Trust II - ID2020](#rebooting-the-web-of-trust-ii---id2020-)
|
|
||||||
* [Rebooting the Web of Trust III](#rebooting-the-web-of-trust-iii-)
|
|
||||||
* [Rebooting the Web of Trust IV](#rebooting-the-web-of-trust-iv-)
|
|
||||||
* [Rebooting the Web of Trust V](#rebooting-the-web-of-trust-v-)
|
|
||||||
* [Rebooting the Web of Trust VI](#rebooting-the-web-of-trust-vi-)
|
|
||||||
* [Rebooting the Web of Trust VII](#rebooting-the-web-of-trust-vii-)
|
|
||||||
* [Topics and Advance Readings](#topics-and-advance-readings-)
|
|
||||||
* [RWoT 1](#rwot-1-)
|
|
||||||
* [RWoT 2](#rwot-id2020-)
|
|
||||||
* [RWoT 3](#rwot-3-)
|
|
||||||
* [RWoT 4](#rwot-4-)
|
|
||||||
* [RWoT 5](#rwot-5-)
|
|
||||||
* [RWoT 6](#rwot-6-)
|
|
||||||
* [RWoT 7](#rwot-7-)
|
|
||||||
* [RWoT GitHub Listing](#rwot-github-listing-)
|
|
||||||
* [>> Identity Research and Literature](literature.md)
|
|
||||||
* [>> Sovrin Related Literature](indy-ecosystem/literature.md)
|
|
||||||
* [<< /awesome-decentralized-id](README.md)
|
|
||||||
* [**infominer.id**](https://infominer.id)
|
|
||||||
|
|
||||||
## Selected 'Rebooting Web of Trust' Whitepapers [**^**](#contents)
|
|
||||||
|
|
||||||
### Primers
|
|
||||||
|
|
||||||
* [A Primer on Functional Identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/functional-identity-primer.md) by Joe Andrieu
|
|
||||||
* [A Primer on Self-Sovereign identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/self-sovereign-identity-primer.md) by Christopher Allen & Shannon Appelcline
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/did-primer.md) by Drummond Reed & Manu Sporny
|
|
||||||
* [A Verifiable Claims Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/verifiable-claims-primer.md) by Manu Sporny
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md)
|
|
||||||
|
|
||||||
### RWoT Workshop Related [**^**](#contents)
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* [Rebranding the Web of Trust](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/rebranding-web-of-trust.pdf) Original RWoT whitepaper
|
|
||||||
* [WebofTrust.info/papers.html](https://www.weboftrust.info/papers.html)
|
|
||||||
|
|
||||||
### Use Cases [**^**](#contents)
|
|
||||||
* [Amira 1.0](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/amira.md)
|
|
||||||
* [Re-Imagining What Users Really Want](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2017/blob/master/final-documents/what-users-really-want.md)
|
|
||||||
* [Joram 1.0.0](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016/blob/master/final-documents/joram-engagement-model.pdf)
|
|
||||||
* [Powering the Physician-Patient Relationship with HIE of One Blockchain Health IT](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/physician-patient-relationship.pdf)
|
|
||||||
* [Protecting Digital Identities in Developing Countries](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/final-documents/protecting-digital-identities-in-developing-countries.pdf)
|
|
||||||
* [Opportunities Created by the Web of Trust for Controlling and Leveraging Personal Data](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/satisfying-real-world-use-cases.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Completed Papers [**^**](#contents)
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust I [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/pes1Vm8.png)
|
|
||||||
|
|
||||||
The first Rebooting the Web of Trust design workshop, held in San Francisco, CA - November 3rd & 4th, 2015.
|
|
||||||
|
|
||||||
* **[Rebranding the Web of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/rebranding-web-of-trust.pdf)**
|
|
||||||
* A history of the Web of Trust and a look at what the term could mean for the future.
|
|
||||||
* Shannon Appelcline, Dave Crocker, Randall Farmer, and Justin Newton
|
|
||||||
>The Web of Trust is a buzzword for a new model of decentralized self-sovereign identity. It’s a phrase that dates back almost twenty-five years, the classic definition derives from PGP [...] the vibrant blockchain community is also drawing new attention to the concept we aim to reboot it.
|
|
||||||
* **[Opportunities Created by the Web of Trust for Controlling and Leveraging Personal Data](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/satisfying-real-world-use-cases.pdf)**
|
|
||||||
* Five use cases, from two relatively simple cases of managing selective disclosure to the most extreme case of establishing government-verifiable credentials from nothing for a stateless refugee.
|
|
||||||
* du5t, Kaliya "Identity Woman" Young (@identitywoman), John Edge, Drummond Reed, and Noah Thorp
|
|
||||||
* **[Decentralized Public Key Infrastructure](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf)**
|
|
||||||
* A massive overview of a decentralized public-key infrastructure (DPKI).
|
|
||||||
* Christopher Allen, Arthur Brock, Vitalik Buterin, Jon Callas, Duke Dorje, Christian Lundkvist, Pavel Kravchenko, Jude Nelson, Drummond Reed, Markus Sabadello, Greg Slepak, Noah Thorp, and Harlan T Wood
|
|
||||||
* **[Smart Signatures](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/smart-signatures.pdf)**
|
|
||||||
* A system to explicitly outline and fully program conditions for verification, inspired by Bitcoin Script.
|
|
||||||
* Christopher Allen, Greg Maxwell, Peter Todd, Ryan Shea, Pieter Wuille, Joseph Bonneau, Joseph Poon, and Tyler Close
|
|
||||||
* **[Creating the New World of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/whats-the-next-step.pdf)**
|
|
||||||
* A summary of the next step for the Rebooting the Web of Trust group.
|
|
||||||
* Shannon Appelcline
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust II - ID2020 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/cn5CQEI.png)
|
|
||||||
|
|
||||||
The second Rebooting the Web of Trust design workshop, in San Francisco, CA, on May 21st & 22nd, 2016. It was run in conjunction with the UN ID2020 Summit on Identity, which occurred at the UN in New York on May 20th, 2016.
|
|
||||||
|
|
||||||
* [**Identity Crisis: Clearer Identity Through Correlation**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/identity-crisis.pdf)
|
|
||||||
* A new way to look at identity, as correlation over time.
|
|
||||||
* Joe Andrieu, Kevin Gannon, Igor Kruiper, Ajit Tripathi, and Gary Zimmerman
|
|
||||||
* [**Powering the Physician-Patient Relationship with HIE of One Blockchain Health IT**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/physician-patient-relationship.pdf)
|
|
||||||
* Using Blockchains and DIDs for physician-patient interactions.
|
|
||||||
* Adrian Gropper, MD
|
|
||||||
* [**Protecting Digital Identities in Developing Countries**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/protecting-digital-identities-in-developing-countries.pdf)
|
|
||||||
* A real-world use case, describing issues of identity in the developing world.
|
|
||||||
* Wayne Hennessy-Barrett
|
|
||||||
* [**Requirements for DIDs (Decentralized Identifiers)**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/requirements-for-dids.pdf)
|
|
||||||
* The first of a series of papers abou tproducing a concrete DID system.
|
|
||||||
* Drummond Reed and Les Chasen
|
|
||||||
* [**Smarter Signatures: Experiments in Verifications**](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/smarter-signatures.pdf)
|
|
||||||
* A look at uses and requirements of next-generation smart signature systems.
|
|
||||||
* Christopher Allen and Shannon Appelcline
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust III [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/37wRZ9B.png)
|
|
||||||
|
|
||||||
The design workshop exceeded its mandate by producing seven papers:
|
|
||||||
|
|
||||||
* [**DID (Decentralized Identifier) Data Model and Generic Syntax 1.0 Implementer’s Draft 01**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/did-implementer-draft-10.pdf)
|
|
||||||
- The complete draft of the Decentralized IDentifier (DID) model and syntac, a project that has run through the RWOT workshops to date.
|
|
||||||
- Drummond Reed, Les Chasen, Christopher Allen, and Ryan Grant
|
|
||||||
* [**Digital Verification Advancements at RWoT III**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/digital-verification-advancements.pdf)
|
|
||||||
- A short overview of enhancements to Digital Verification that came out of RWOT III.
|
|
||||||
- Manu Sporny with Christopher Allen, Harlan Wood, and Jason Law
|
|
||||||
* [**Embedding Human Wisdom in Our Digital Tomorrow**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/WisdomEmbedding-Human-Wisdom-in-Our-Digital-Tomorrow.pdf)
|
|
||||||
- A discussion of the dangers of transferring wisdom into the digital world, seen through the lenses of vulnerability, shadows, healing, tensions, complexity and gestalt, and organizational choices.
|
|
||||||
- Daniel Hardman, Kaliya “Identity Woman” Young, and Matthew Schutte
|
|
||||||
* [**Hubs**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/hubs.pdf)
|
|
||||||
- An overview of the hubs datastore system.
|
|
||||||
- Daniel Buchner, Wayne Vaughan, and Ryan Shea
|
|
||||||
* [**Joram 1.0.0**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/joram-engagement-model.pdf)
|
|
||||||
- An Information Lifecycle Engagement Model that offers a use case for a Syrian refugee.
|
|
||||||
- Joe Andrieu and Bob Clint
|
|
||||||
* [**Portable Reputation Toolkit Use Cases**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/reputation-toolkit.pdf)
|
|
||||||
- A model and proof-of-concept implementation for decentralized verification.
|
|
||||||
- Christopher Allen, Tim Daubenschütz, Manu Sporny, Noah Thorp, Harlan Wood, Glenn Willen, and Alessandro Voto
|
|
||||||
* [**Smart Consent Protocol**](https://github.com/WebOfTrustInfo/rwot3-sf/tree/master/final-documents/smart-consent-protocol.pdf)
|
|
||||||
- Bringing together COALA IP and Consent to deal with digital intellectual property.
|
|
||||||
- Dr. Shaun Conway, Lohan Spies, Jonathan Endersby, and Tim Daubenschütz
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust IV [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/ZtP6Dny.png)
|
|
||||||
|
|
||||||
The fourth Rebooting the Web of Trust design workshop ran in Paris, France, on April 19th-21st, 2017.
|
|
||||||
|
|
||||||
* [*Design Considerations for Decentralized Reputation Systems*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/reputation-design.md)
|
|
||||||
- Angus Champion de Crespigny, Dmitry Khovratovich, Florent Blondeau, Klara Sok, Philippe Honigman, Nikolaos Alexopoulos, Fabien Petitcolas, and Shaun Conway
|
|
||||||
* [*LD Signature Format Alignment*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/ld-signatures.md) - Bringing JSON-LD signatures into alignment with JOSE JSON Web Signature (JWS) standards.
|
|
||||||
- Kim Hamilton Duffy, Rodolphe Marques, Markus Sabadello, and Manu Sporny
|
|
||||||
* [*Re-Imagining What Users Really Want*](https://github.com/WebOfTrustInfo/rwot4-paris/blob/master/final-documents/what-users-really-want.md) - Five people, five opportunities for self-sovereign identity.
|
|
||||||
- Joe Andrieu, Frederic Engel, Adam Lake, Moses Ma, Olivier Maas, and Mark van der Waal.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust V [**^**](#contents)
|
|
||||||
![](http://i.imgur.com/H7i3KFD.png)
|
|
||||||
|
|
||||||
* [**ActivityPub: From Decentralized to Distributed Social Networks**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/activitypub-decentralized-distributed.md)
|
|
||||||
- Christopher Lemmer Webber & Manu Sporny
|
|
||||||
- An overview of the W3C ActivityPub protocol.
|
|
||||||
* [**Amira 1.0.0**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/amira.md)
|
|
||||||
- Joe Andrieu & Team
|
|
||||||
- This paper [...] presents a human-centric illustration of an individual’s experience in a self-sovereign, decentralized realization of the Web of Trust as originally conceived by Phil Zimmerman for PGP.
|
|
||||||
* [**The DCS Theorem**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/dcs-theorem/The-DCS-Theorem.pdf)
|
|
||||||
- Greg Slepak & Anya Petrova
|
|
||||||
- A probability proof of the DCS Triangle. Why can't decentralized consensus systems have all three of decentralization, consensus, and scale? Plus, two methods for getting around these limitations.
|
|
||||||
* [**A Decentralized Approach to Blockcerts Credential Revocation**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/blockcerts-revocation.md)
|
|
||||||
- João Santos & Kim Hamilton Duffy
|
|
||||||
- Blockcerts are blockchain-anchored credentials with a verification process designed to be decentralized and trustless. This proposal describes an alternate method of issuing Blockcerts using Ethereum, which allows for a new form of revocation by either the issuer or the recipient.
|
|
||||||
* [**Engineering Privacy for Verified Credentials: In Which We Describe Data Minimization, Selective Disclosure, and Progressive Trust**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/data-minimization-sd.md)
|
|
||||||
- Lionel Wolberger, Brent Zundel, Zachary Larson, Irene Hernandez & Katryna Dow
|
|
||||||
- we have identified three related but distinct privacy enhancing strategies: "data minimization," "selective disclosure," and "progressive trust." These enhancements are enabled with cryptography. The goal of this paper is to enable decision makers, particularly non-technical ones, to gain a nuanced grasp of these enhancements along with some idea of how their enablers work.
|
|
||||||
* [**Identity Hubs Capabilities Perspective**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/identity-hubs-capabilities-perspective.md)
|
|
||||||
- by Adrian Gropper, Drummond Reed & Mark S. Miller
|
|
||||||
> Identity Hubs as currently proposed in the Decentralized Identity Foundation (DIF) are a subset of a general Decentralized Identifier (DID) based user-controlled agent, based on ACLs rather than an object-capabilities (ocap) architecture. Transitioning the Hubs design to an ocap model can be achieved by introducing an UMA authorization server as the control endpoint.
|
|
||||||
* [**Linked Data Capabilities**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/lds-ocap.md)
|
|
||||||
- Christopher Lemmer Webber & Mark S. Miller
|
|
||||||
> Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems.
|
|
||||||
* [**Veres One DID Method**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/did-method-veres-one.md)
|
|
||||||
- Manu Sporny & Dave Longley
|
|
||||||
> The Veres One Ledger is a permissionless public ledger designed specifically for the creation and management of decentralized identifiers (DIDs). This specification defines how a developer may create and update DIDs in the Veres One Ledger.
|
|
||||||
* [**When GDPR becomes real, and Blockchain is no longer Fairy Dust**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/final-documents/gdpr.md)
|
|
||||||
- Marta Piekarska, Michael Lodder, Zachary Larson & Kaliya Young (Identity Woman)
|
|
||||||
> This document describes the GDPR requirements and the different approaches to digital identity solutions and finally explains why distributed ledger technology may offer an opportunity for enterprises to simplify data management solutions that are GDPR compliant.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust VI [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/9yhGv6a.png)
|
|
||||||
|
|
||||||
The sixth Rebooting the Web of Trust design workshop ran in Santa Barbara, California, on March 6th to 8th, 2018.
|
|
||||||
|
|
||||||
* [**BTCR DID Resolver Specification**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/btcr-resolver.md)
|
|
||||||
- Kim Hamilton Duffy, Christopher Allen, Ryan Grant, and Dan Pape
|
|
||||||
> This describes the process of resolving a BTCR DID into a DID Document. The draft reference implementation is available at https://github.com/WebOfTrustInfo/btcr-did-tools-js (see didFormatter.js). Note that not all steps described in this document are implemented yet.
|
|
||||||
* [**Decentralized Autonomic Data (DAD) and the three R's of Key Management**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/DecentralizedAutonomicData.md)
|
|
||||||
- by Samuel M. Smith Ph.D. with Vishal Gupta
|
|
||||||
> This paper proposes a new class of data called decentralized autonomic data (DAD). The term decentralized means that the governance of the data may not reside with a single party. A related concept is that the trust in the data provenance is diffuse in nature. Central to the approach is leveraging the emerging DID (decentralized identifier) standard. The term autonomic means self-managing or self-regulating. In the context of data, we crystalize the meaning of self-managing to include cryptographic techniques for maintaining data provenance that make the data self-identifying, self-certifying, and self-securing. Implied thereby is the use of cryptographic keys and signatures to provide a root of trust for data integrity and to maintain that trust over transformation of that data, e.g. provenance. Thus key management must be a first order property of DADs. This includes key reproduction, rotation, and recovery. The pre-rotation and hybrid recovery methods presented herein are somewhat novel.
|
|
||||||
|
|
||||||
* [**Decentralized Identifiers v1.0**](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-spec-1.0.md)
|
|
||||||
- A Status Note
|
|
||||||
|
|
||||||
> The Decentralized Identifiers specification editors and implementers spent some time at Rebooting the Web of Trust 6 processing the remaining issues in the issue tracker. This document summarizes the proposed resolutions that the group has put forward to resolve all of the DID specification issues that were submitted before 2018-03-05.
|
|
||||||
|
|
||||||
* [*Exploring Sustainable Technology Commons using Appreciative Inquiry*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/sustainable-commons.md)
|
|
||||||
- by Heather Vescent, Kaliya “Identity Woman” Young, Adrian Gropper, and Juan Caballero
|
|
||||||
|
|
||||||
> Technology commons come in a variety of flavors and have achieved varying levels of financial success. For-profit corporate activities have in few historical cases been set up with a financial feedback mechanism to support the commons upon which they depend and capitalize. Why do the commons and the technology sectors’ available forms of capitalism act as incompatible as oil and water, even though they support each other’s aims? When capitalist benefactors support the technology commons that they utilize, it creates a sustainable and thriving commons which enables and supports additional capitalistic technology innovation. Having worked on both sides of the equation, the authors of this piece propose a vocabulary to nourish these interactions between the two sides; identified characteristics of a sustainable technology commons; identified commons models and variations; applied Appreciative Inquiry principles to one commons model; and identified future research areas.
|
|
||||||
|
|
||||||
* [*Identity Hub Attestation Flows and Components*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/identity-hub-attestations.md)
|
|
||||||
- by Daniel Buchner, Cherie Duncan, John Toohey, Ron Kreutzer, and Stephen Curran
|
|
||||||
|
|
||||||
> In this document, we define a set of user flows and describe the associated Action Objects that support a Hub-centric approach to the request, issuance, presentation, verification, and revocation of interoperable attestations. This document extends the [Identity Hub Explainer](https://github.com/decentralized-identity/hubs/blob/master/explainer.md).
|
|
||||||
|
|
||||||
* [*Introduction to DID Auth*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/did-auth.md)
|
|
||||||
- by Markus Sabadello, Kyle Den Hartog, Christian Lundkvist, Cedric Franz, Alberto Elias, Andrew Hughes, John Jordan & Dmitri Zagidulin
|
|
||||||
|
|
||||||
> The term DID Auth has been used in different ways and is currently not well-defined. We define DID Auth as a ceremony where an identity owner, with the help of various components such as web browsers, mobile devices, and other agents, proves to a relying party that they are in control of a DID. This means demonstrating control of the DID using the mechanism specified in the DID Document's "authentication" object. This could take place using a number of different data formats, protocols, and flows. DID Auth includes the ability to establish mutually authenticated communication channels and to authenticate to web sites and applications. Authorization, Verifiable Credentials, and Capabilities are built on top of DID Auth and are out of scope for this document. This paper gives on overview of the scope of DID Auth, supported protocols and flows, and the use of components of the DID Documents that are relevant to authentication, as well as formats for challenges and responses.
|
|
||||||
|
|
||||||
* [*Open Badges are Verifiable Credentials*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/open-badges-are-verifiable-credentials.md)
|
|
||||||
- By Nate Otto & Kim Hamilton Duffy
|
|
||||||
|
|
||||||
> We identify use cases and requirements that connect threads of work happening in the Rebooting Web of Trust community around: educational achievement claims (particularly using the Open Badges vocabulary); use of decentralized identifiers (DIDs) within web services where educational claims circulate; and integrating blockchain-reliant verification layers. We illustrate each of these cases with a set of example documents and describe user stories for Open Badges ecosystem software in the roles of Issuer, Host/Backpack, Displayer, and Verifier that need to be implemented in order to enable the capabilities described.
|
|
||||||
|
|
||||||
* [*SSI: A Roadmap for Adoption*](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md)
|
|
||||||
- By Moses Ma, Claire Rumore, Dan Gisolfi, Wes Kussmaul & Dan Greening (Senex Rex)
|
|
||||||
|
|
||||||
> This document proposes the formation of a short-term team to develop consistent messaging for the Self-Sovereign Identity (SSI) market. It will target key stakeholders who would actively promote SSI adoption. The goal is to create an SSI market roadmap. This roadmap will help SSI leaders, standards bodies, developers, academics, media, and investors coordinate and clarify their messaging for the market, to accelerate the SSI adoption.
|
|
||||||
|
|
||||||
### Rebooting the Web of Trust VII [**^**](#contents)
|
|
||||||
|
|
||||||
![](http://i.imgur.com/tHcfNsK.png)
|
|
||||||
|
|
||||||
The seventh Rebooting the Web of Trust design workshop, ran near Toronto, Canada, on September 26th to 28th, 2018.
|
|
||||||
|
|
||||||
* [*BTCR v0.1 Decisions*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.md)
|
|
||||||
- Kim Hamilton Duffy, Christopher Allen, and Dan Pape
|
|
||||||
|
|
||||||
> The Bitcoin Reference (BTCR) DID method supports DIDs using the Bitcoin blockchain. This method has been under development through Rebooting Web of Trust events and hackathons over the past year. The BTCR method's reliance on the Bitcoin blockchain presents both advantages and design challenges. During RWOT7, the authors made a number of design and implementation decisions -- largely scope-cutting in nature -- in order to lock down a Minimum Viable Product (MVP) version, which we'll refer to as v0.1. This paper documents those decisions, which will apply to the upcoming v0.1 BTCR method specification and associated v0.1 BTCR reference implementation.
|
|
||||||
|
|
||||||
* [*A DID for Everything*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/A_DID_for_everything.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/A_DID_for_everything.md)
|
|
||||||
- Shaun Conway, Andrew Hughes, Moses Ma, Jack Poole, Martin Riedel, Samuel M. Smith Ph.D., and Carsten Stöcker
|
|
||||||
|
|
||||||
> The decentralized identifier (DID) is a new and open standard type of globally unique identifier that offers a model for lifetime-scope portable digital identity that does not depend on any centralized authority and that can never be taken away by third-parties. DIDs are supported by the W3C community and the Decentralized Identity Foundation (DIF). They are the "atomic units" of a new layer of decentralized identity infrastructure. However, DIDs can be extended from identifiers for people to any entity, thus identifying everything. We can use DIDs to help us identify and manage objects, machines, or agents through their digital twins; we can expand them to locations, to events, and even to pure data objects, which we refer to as decentralized autonomic data (DAD) items.
|
|
||||||
|
|
||||||
> The paper will present novel use-cases for DIDs and DADs and propose a new cryptographic data structure that is a self-contained blockchain of DADs. This enables the verification of the provenance of a given data flow. It builds on a prior paper and an associated reading.
|
|
||||||
|
|
||||||
* [*How to Convince Dad\* of the Importance of Self-Sovereign Identity*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.md)
|
|
||||||
- Shannon Appelcline, Kenneth Bok, Lucas Parker, Peter Scott, and Matthew Wong
|
|
||||||
|
|
||||||
> One of the major problems with bootstrapping self-sovereign identity is that it requires adoption by a large number of people. Pushing self-sovereign identity from the top-down is most likely to result in a technology that’s not actually used, but instead encouraging the average person to demand self-sovereign identity from the bottom-up will result in the organic development of a vibrant, well-utilized decentralized web-of-trust ecosystem.
|
|
||||||
|
|
||||||
> This paper addresses that need by offering arguments to a variety of people who might be reluctant to use self-sovereign identity, uninterested in its possibilities, or oblivious to the dangers of centralization. By focusing on the needs of real people, we hope to also encourage developers, engineers, and software business owners to create the apps that will address their reluctance and fulfill their needs, making self-sovereign identity a reality.
|
|
||||||
|
|
||||||
* [*IPLD as a general pattern for DID documents and Verifiable Claims*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/ipld-did.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/ipld-did.md)
|
|
||||||
- jonnycrunch, Anthony Ronning, Kim Duffy, Christian Lundkvist
|
|
||||||
|
|
||||||
> Since the emergence of the Decentralized Identifier (DID) specification at the Fall 2016 Rebooting the Web of Trust [1], numerous DID method specifications have appeared. Each DID method specification defines how to resolve a cryptographically-tied DID document given a method-specific identifier. In this paper, we describe a way to represent the DID document as a content-addressed Merkle Directed Acyclic Graph (DAG) using Interplanetary Linked Data (IPLD). This technique enables more cost-efficient, scaleable creation of DIDs and can be applied across different DID method specifications.
|
|
||||||
|
|
||||||
* [*Peer to Peer Degrees of Trust*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/peer-to-peer-degrees-of-trust.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/peer-to-peer-degrees-of-trust.md)
|
|
||||||
- Harrison Stahl, Titus Capilnean, Peter Snyder, and Tyler Yasaka
|
|
||||||
|
|
||||||
> Aunthenticity is a challenge for any identity solution. In the physical world, at least in America, it is not difficult to change one's identity. In the digital world, there is the problem of bots. The botnet detection market is expected to be worth over one billion USD by 2023, in a landscape where most digital activity is still heavily centralized. These centralized digital solutions have the advantage of being able to track IP addresses, request phone verification, and present CAPTCHAs to users in order to authenticate them. If this problem is so difficult to solve in the centralized world, how much more challenging will it be in the decentralized world, where none of these techniques are available?
|
|
||||||
|
|
||||||
> In this paper, we explore the idea of using a web of trust as a tool to add authenticity to decentralized identifiers (DIDs). We define a framework for deriving relative trust degrees using a given trust metric: a "trustworthiness" score for a given identity from the perspective of another identity. It is our intent that this framework may be used as a starting point for an ongoing exploration of graph-based, decentralized trust. We believe this approach may ultimately be used as a foundation for decentralized reputation.
|
|
||||||
|
|
||||||
* [*Resource Integrity Proofs*](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/resource-integrity-proofs.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/resource-integrity-proofs.md)
|
|
||||||
- Ganesh Annan and Kim Hamilton Duffy
|
|
||||||
|
|
||||||
> Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?
|
|
||||||
|
|
||||||
> This paper proposes a linking solution that decouples integrity information from link and resource syntaxes, enabling verification of any representation of a resource from any type of link. We call this approach Resource Integrity Proofs (RIPs). RIPs provide a succinct way to link to resources with cryptographically verifiable content integrity. RIPs can be combined with blockchain technology to create discoverable proofs of existence to off-chain resources.
|
|
||||||
|
|
||||||
* [*Use Cases and Proposed Solutions for Verifiable Offline Credentials*](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/offline-use-cases.pdf) [(Text)](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/offline-use-cases.md)
|
|
||||||
- Michael Lodder, Samantha Mathews Chase, and Wolf McNally
|
|
||||||
|
|
||||||
> In this paper we cover various scenarios where some or all parties have intermittent, unreliable, untrusted, insecure, or no network access, but require cryptographic verification (message protection and/or proofs). Furthermore, communications between the parties may be only via legacy voice channels. Applicable situations include marine, subterranean, remote expeditions, disaster areas, refugee camps, and high-security installations. This paper then recommends solutions for addressing offline deployments.
|
|
||||||
|
|
||||||
![](https://i.imgur.com/TpsPXoa.png)
|
|
||||||
|
|
||||||
|
|
||||||
## Topics and Advance Readings [**^**](#contents)
|
|
||||||
|
|
||||||
In advance of the design workshop, all participants are requested to produce a one-or-two page topic paper to be shared with the other attendees on either:
|
|
||||||
|
|
||||||
* A specific problem that they wanted to solve with a web-of-trust solution, and why current solutions (PGP or CA-based PKI) can't address the problem?
|
|
||||||
* A specific solution related to the web-of-trust that you'd like others to use or contribute to?
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 1 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/Hv2rPVy.png)
|
|
||||||
|
|
||||||
* [White Papers, Specifications & Proofs of Concept](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/white-papers--specifications---and-proof-of-concept-code.md)
|
|
||||||
>Our goal for this initial #RebootingWebOfTrust design workshop is to:
|
|
||||||
>
|
|
||||||
> * Focus on the creation of the next generation of decentralized web-of-trust based identity systems.
|
|
||||||
> * To generate 5 technical white papers on topics decided by the group that will have the greatest impact on the future"
|
|
||||||
>
|
|
||||||
> To this end, I thought it would be useful to define what is a white paper, and as some people desire to go beyond this, what is a specification and proof of concept code.
|
|
||||||
* [Advanced Web-of-Trust Concepts](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/advanced-web-of-trust-concepts.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Attempts at common terminology for digital identity systems](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/shared_terminology_for_digital_identity_systems.md)
|
|
||||||
- Christian Lundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Authorities vs. Peers: Pain Points in Security](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/authorities-vs-peers--pain-points-in-security.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [Avoiding Confused Deputy Attack Using Capabilities](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/AvoidingConfusedDeputyAttackUsingCapabilities.md)
|
|
||||||
- Tyler Close *\<tyler.close@gmail.com\>*
|
|
||||||
* [Binding Identity in a Decentralized System](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/binding-identity-in-decentralized-system.md)
|
|
||||||
- Wayne Thayer *[@WThayer](https://twitter.com/wthayer) \<wthayer@gmail.com\>*
|
|
||||||
* [Blockchain-based Trust for Software Components](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/code-and-file-signing.adoc)
|
|
||||||
- Sean Gilligan *[@msgilligan](https://twitter.com/msgilligan) \<sean@msgilligan.com\>*
|
|
||||||
* [Blockchain Tech Opportunities in the Web-of-Trust](blockchain-opportunities.txt)
|
|
||||||
- Peter Todd *[@PeterToddBTC](https://twitter.com/PeterToddBTC) \<pete@petertodd.org\>*
|
|
||||||
* [Building a Web of Trust for E-commerce](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/decentralized_e-commerce.md)
|
|
||||||
- Michael Folkson *[@michaelfolkson](https://twitter.com/michaelfolkson) \<michaelfolkson@gmail.com\>*
|
|
||||||
* [Cool hack with XDI graphs, blockstore, link contracts, and cryptographic identifiers](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/cool-hack-xdi-blockstore-bip32.md)
|
|
||||||
- Markus Sabadello *[@Peacekeeper](https://twitter.com/Peacekeeper) \<markus@projectdanube.org\>*
|
|
||||||
* [Dealing with key loss in digital identity systems](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/dealing_with_key_loss_in_digital_identity.md)
|
|
||||||
- Christian Lundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Decentralized Authentication with Blockchain Auth](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Decentralized-Authentication-with-Blockchain-Auth.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Decentralized Cooperation Needs Decentralized Reputation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/DecentralizedCooperationNeedsDecentralizedReputation.md)
|
|
||||||
- Noah Thorp *[@noahthorp](https://twitter.com/noahthorp) \<noah@citizencode.io\>*
|
|
||||||
* [Different Models for Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/different-models-for-trust.md)
|
|
||||||
- Kaliya Hamlin *[@IdentityWoman](https://twitter.com/identitywoman) \<kaliya@identitywoman.net\>*
|
|
||||||
* [Distributed multi-ledger model for financial industry](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/DistributedMulti-ledgerModelForFinancialIndustry.md)
|
|
||||||
- Pavel Kravchenko *[@kravchenkopo](https://twitter.com/kravchenkopo) \<kravchenkopo@gmail.com\>*
|
|
||||||
* [Distributed Receptor-Based Computing](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Distributed_Receptor-Based_Computing.md)
|
|
||||||
- Arthur Brock - *[@ArtBrock](https://twitter.com/artbrock) \<artbrock@gmail.com>*
|
|
||||||
* [Distributed Trust Systems and the Kenyesian Beauty Contest](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Distributed-Trust-Systems-and-the-Kenyesian-Beauty-Contest.md)
|
|
||||||
- Joel Dietz *[@fractastical](https://twitter.com/fractastical) \<jdietz@gmail.com\>*
|
|
||||||
* [First Encounters with PGP](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/FirstEncountersWithPGP.md)
|
|
||||||
- Kiara Robles *[@anarchoass](https://twitter.com/anarchoass) \<kiara.robles@gmail.com\>*
|
|
||||||
* [Hierarchical Deterministic Keys: BIP32 & Beyond](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/hierarchical-deterministic-keys--bip32-and-beyond.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [How not to build an Orwellian reputation system](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/How-not-to-build-an-orwellian-reputation-system)
|
|
||||||
- Juan S. Galt *[@juansgalt](https://twitter.com/juansgalt) \<juans.galt@tuta.io\>*
|
|
||||||
* [Identity, Guidance and Situational Awareness](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Identity_Guidance_and_Situational_Awareness.md)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [Identity, Property and Simulation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Identity-Property-Simulation.md)
|
|
||||||
- Patrick Deegan \<pdeegan@gmail.com\>
|
|
||||||
* [Key revocation of lost and stolen keys](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Key-revokation-of-lost-and-stolen-keys.md)
|
|
||||||
- Martin Koeppelmann *[@koeppelmann](https://twitter.com/koeppelmann) \<martin.koeppelmann@consensys.net \>*
|
|
||||||
* [Key Transparency for End Users](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/key-transparency-for-end-users.md)
|
|
||||||
- Joseph Bonneau *[@JosephBonneau](https://twitter.com/josephbonneau) \<jbonneau@cs.stanford.edu\>*
|
|
||||||
* [Knowing When Your Digital Identity Has Been Compromised](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/knowing-when-your-identity-has-been-compromised.md)
|
|
||||||
- Justin Newton *[@JustinwNewton](https://twitter.com/justinwnewton) \<justin@netki.com\>*
|
|
||||||
* [Lightning Network and Web of Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/lightning-network-and-web-of-trust.md)
|
|
||||||
- Joseph Poon *\<joseph@lightning.network\>*
|
|
||||||
* [Linked Local Names](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/linked-local-names.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Modern PKI: Identity Assertions Forming Trust Networks](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/modern-pki-identity-assertions.md)
|
|
||||||
- Duke Dorje *[@dukedorje](https://twitter.com/dukedorje) \<duke@citizencode.io\>*
|
|
||||||
* [PGP Paradigm](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/PGP-Paradigm.pdf)
|
|
||||||
- Jon Callas - *[@JonCallas](https://twitter.com/joncallas) \<jon@crypto.expert>* & Phil Zimmerman - *\<prz@mit.edu\>*
|
|
||||||
* [PKI Tools in EVM-based blockchains](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/pki_tools_in_evm_blockchains.md)
|
|
||||||
- ChristianLundkvist - *[@ChrisLundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net>*
|
|
||||||
* [Progressive Trust](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/progressive-trust.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Real life application of WoT: Refugee Use Case](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/refugee-use-case.md)
|
|
||||||
- Alicia Carmona *\<alicia.carmona@id2020.org\>*
|
|
||||||
* [Reputation and the Real World](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/ReputationAndTheRealWorld.md)
|
|
||||||
- Randy Farmer *[@FRandallFarmer](https://twitter.com/FRandallFarmer) \<randy.farmer@pobox.com\>*
|
|
||||||
* [Schnorr Signatures: An Overview](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Schnorr-Signatures--An-Overview.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>* & Shannon Appelcline *[@Appelcline](https://twitter.com/Appelcline) \<ShannonA@skotos.net\>*
|
|
||||||
* [Secret Handshake: Key Exchange as a Capability System](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/key-exchange-as-capability-system.md)
|
|
||||||
- Dominic Tarr *[@DominicTarr](https://twitter.com/DominicTarr) \<dominic.tarr@gmail.com\>*
|
|
||||||
* [Secure Naming on the Blockchain](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Secure-Naming-on-the-Blockchain.md)
|
|
||||||
- Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@onename.com\>* and Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Selective Disclosure of Identity with Hierarchical Deterministic Keys and JSON Web Tokens](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Selective-Disclosure-of-Identity.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
* [Tensions related to identity and community regulation](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/tensions-related-to-identity-and-community-regulation.md)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [The Naming of Things](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/The-Naming-of-Things.txt)
|
|
||||||
- Matthew Schutte *[@MatthewJosef](https://twitter.com/matthewjosef) \<matt@calabs.org\>*
|
|
||||||
* [Thin Clients](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/thin-clients.md)
|
|
||||||
- Greg Slepak *[@TaoEffect](https://twitter.com/TaoEffect) \<hi@okturtles.com\>*
|
|
||||||
* [Trust Exchange: An Architecture for a Permanent Open Trust Network](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Trust-Exchange-An-Architecture-for-a-Permanent-Open-Trust-Network.md)
|
|
||||||
- Harlan T. Wood *[@HarlanTWood](https://twitter.com/harlantwood) \<h@rlan.me \>*
|
|
||||||
* [Web of Trust with Blockchain IDs](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/Web-of-Trust-with-Blockchain-IDs.md)
|
|
||||||
- Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@onename.com\>*
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [XDI Link Contracts: An Overview](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/xdi-link-contracts.md)
|
|
||||||
- Drummond Reed *[@DrummondReed](https://twitter.com/DrummondReed) \<drummond@respect.network\>*
|
|
||||||
* [How Not to build and Orwellian reputation system](How-Not-to-build-an-Orwellian-reputation-system.md)
|
|
||||||
- [Juan S. Galt](http://twitter.com/juansgalt)
|
|
||||||
* [Notes on the IPFS Keychain (or the Web Keychain)](ipfs-keychain.md)
|
|
||||||
* [IPFS - The Permanent Web](ipfs-links.md)
|
|
||||||
* [multiplexed: a 'slightly radical' framing of identity](multiplexed--a-slightly-radical-framing-of-identity.md)
|
|
||||||
- \<[du5t@multiplexed.be](mailto:du5t@multiplexed.be)\>
|
|
||||||
* [RLPx: Cryptographic Network & Transport Protocol - Version 0.3](rlpx.md)
|
|
||||||
- Alex Leverington
|
|
||||||
* [Self-certifying File System](sfs.md)
|
|
||||||
* [Trust Models, Accountability, LIfeCycle and Social Context](Trust%20Models%2C%20Accountability%2C%20LIfeCycle%20and%20Social%20Context.md)
|
|
||||||
- by Kaliya "[Identity Woman](http://www.identitywoman.net/)" Young (formerly Hamlin)
|
|
||||||
|
|
||||||
### RWoT ID2020 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/ZG5msLT.png)
|
|
||||||
|
|
||||||
* [A Double Edge Sword of Having an Identity](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/double_edged_identity.md)
|
|
||||||
- Marta Piekarska \<marta@blockstream.io\>
|
|
||||||
* [A Self-Sovereign Identity Architecture](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/a-self-sovereign-identity-architecture.pdf)
|
|
||||||
- Manu Sporny *[@msporny](https://twitter.com/manusporny?lang=en)* and David Longley
|
|
||||||
* [Blockstack: Design and Implementation of a Global Naming System with Blockchains](https://blockstack.org/blockstack.pdf)
|
|
||||||
- by Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@blockstack.com\>* and Jude Nelson *[@judecnelson](https://twitter.com/judecnelson) \<jude@blockstack.com\>* and Ryan Shea *[@ryaneshea](https://twitter.com/ryaneshea) \<ryan@blockstack.com\>*
|
|
||||||
* [From Identity to Refugee Status Determination](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/identity_to_refugee_status_determination.md)
|
|
||||||
- Susan R. Ramonat \<SRamonat@seic.com\>
|
|
||||||
* [Peer Attestation of Identity in the Real World](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/PeerAttestationofIdentity.pdf)
|
|
||||||
- Dr Shaun Conway & Lohan Spies
|
|
||||||
* [Sovereign Identity Namespaces](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/SovereignIdentityNamespaces.pdf)
|
|
||||||
- Drummond Reed [@DrummondReed](https://twitter.com/drummondreed?lang=en) \<drummond@respectnetwork.com\>
|
|
||||||
* [Identity System Essentials](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/Identity-System-Essentials.pdf)
|
|
||||||
- Samuel Smith and Dmitry Khovratovich
|
|
||||||
* [Decentralized Identifiers (DIDs) and Decentralized Identity Management (DIDM)](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/DID-Whitepaper.md)
|
|
||||||
- Les Chasen
|
|
||||||
* [“Immutable Me” - A Discussion Paper Exploring Data Provenance To Enable New Value Chains](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/immutable-me.pdf)
|
|
||||||
- *George Samman [@sammantic](https://twitter.com/sammantic) \<[George.Samman@meeco.me](mailto:George.Samman@meeco.me)\> and Katryna Dow [@katrynadow](https://twitter.com/katrynadow) \<[Katryna.Dow@meeco.me](mailto:Katryna.Dow@meeco.me)\>*
|
|
||||||
* [No Secure Protocol = No Sovereign Identity](/topics-and-advance-readings/no-secure-protocol-equals-no-sovereign-identity.md)
|
|
||||||
- Greg Slepak *[@taoeffect](https://twitter.com/taoeffect) \<hi@okturtles.com\>*
|
|
||||||
* [Questions around key management for digital ID systems](/topics-and-advance-readings/questions_around_key_management.md)
|
|
||||||
- by Christian Lundkvist *[@chrislundkvist](https://twitter.com/chrislundkvist) \<christian.lundkvist@consensys.net\>* and Rouven Heck *[@rh7](https://twitter.com/rh7) \<rouven.heck@consensys.net\>*
|
|
||||||
* [The Path to Self-Sovereign Identity](/topics-and-advance-readings/the-path-to-self-sovereign-identity.md)
|
|
||||||
- Christopher Allen *[@ChristopherA](https://twitter.com/ChristopherA) \<ChristopherA@LifeWithAlacrity.com\>*
|
|
||||||
* [Distibuted Identity Management - Verifiable Claims Exchange Via Agents](/topics-and-advance-readings/DistibutedIdentityManagement-VerifiableClaimsExchangeViaAgents.pdf)
|
|
||||||
- Gary Zimmerman
|
|
||||||
* [Blockstack Rules and Support for Multiple Blockchains](/topics-and-advance-readings/blockstack-rules-and-multiple-blockchains.md)
|
|
||||||
- Muneeb Ali *[@muneeb](https://twitter.com/muneeb) \<muneeb@blockstack.com\>
|
|
||||||
* [Plurality of Provenance in Distributed Identity](/topics-and-advance-readings/Plurality%20of%20Provenance%20in%20Distributed%20Identity.Andrieu.2016.pdf)
|
|
||||||
- Joe Andrieu \<[joe@joeandrieu.com](mailto:joe@joeandrieu.com)\>
|
|
||||||
* [Identity is a Phenomenon, Not a Property](/topics-and-advance-readings/Identity%20is%20a%20Phenomenon%20Not%20a%20Property.Andrieu.2016.pdf)
|
|
||||||
- Joe Andrieu \<[joe@joeandrieu.com](mailto:joe@joeandrieu.com)\>
|
|
||||||
* [Dex: Deterministic Predicate Expressions for Smarter Signatures](/topics-and-advance-readings/DexPredicatesForSmarterSigs.md)
|
|
||||||
- Peter Todd
|
|
||||||
* [Scaling a BFT Consensus Protocol for Identity](/topics-and-advance-readings/scaling-a-bft-consensus-protocol-for-identity.md)
|
|
||||||
- Jason Law & Lovesh Harchandani
|
|
||||||
* [XDI Graphs in IPFS](/topics-and-advance-readings/XDI-Graphs-in-IPFS.md)
|
|
||||||
- Markus Sabadello
|
|
||||||
* [Replace Blockchain with DLT (Distributed Ledger Technology)](https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/topics-and-advance-readings/Erik%20Anderson-USE%20CASE%20story.md)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Blockchain For Capital Markets](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Blockchain_for_capital_markets.pdf)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Identity Management IdSec](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/PM_15_026_FIN2_IdSEC_160513.pdf)
|
|
||||||
- Erik Anderson
|
|
||||||
* [Trust-i-ness](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Trust-i-ness.md)
|
|
||||||
- by Kaliya "Identity Woman"
|
|
||||||
* [ID2020 - Self-Sovereign Identity](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Rebooting%20Web%20of%20Trust%20Position%20MindMap%20-%20pre-reading%20DRAFT%20ID2020%20Summit%202016.pdf)
|
|
||||||
- Patrick Deegan
|
|
||||||
* [Identity and decentralised Communication](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop/blob/master/topics-and-advance-readings/Identity%20and%20decentralised%20communications.md)
|
|
||||||
- By Harsh Patel
|
|
||||||
* [Chime National Patent ID Challenge](/topics-and-advance-readings/CHIMENationalPatientIDChallenge.pdf)
|
|
||||||
* [Usability and Multiplicity in Global Identity Management](/topics-and-advance-readings/Crocker-ID-Usability-Multiplicity.md) — by D. Crocker ~ \<[dcrocker@bbiw.net](mailto:dcrocker@bbiw.net)\>
|
|
||||||
* [Decentralized Identity Satoshi Style](/topics-and-advance-readings/Decentralized-Identity-Satoshi-Style) - by Darrell Duane - \<[darrell@idi.io](mailto:darrell@idi.io)\>
|
|
||||||
* [Declaration of Identity - Printed.pdf](https://github.com/infominer33/rwot2-id2020/blob/master/topics-and-advance-readings/Declaration%20of%20Identity%20-%20Printed.pdf)
|
|
||||||
* [Identities for Moving Things](/topics-and-advance-readings/IdentitiesForMovingThings.md) - by Daniel Ford - \<[dan@keoja.com](mailto:dan@keoja.com)\>
|
|
||||||
* [Legalizing Identity Protocols for the United Nations 16.9](/topics-and-advance-readings/Legalizing-Identity-Protocols-United-Nations.md)
|
|
||||||
* [Personal Levels of Assurance (PLOA)](/topics-and-advance-readings/PLOA%20White%20Paper%20-%20v1.01.pdf) — by J. Oliver Glasgow and Jeff Dogen, Kennie Kwong, David Chen, Johannes Jaskolski, Kevin Castellow, Dan Druta — An AT&T Whitepaper on Assurance
|
|
||||||
* [Clues](/topics-and-advance-readings/clues.md) — by Nicola Greco
|
|
||||||
— something that serves to guide or direct in the solution of a problem or mystery.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 3 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/05aTksa.png)
|
|
||||||
|
|
||||||
* [Identity as Linked Data on Immutable Ledgers](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md)
|
|
||||||
- Tim Daubenschuetz and Trent McConaghy
|
|
||||||
* [EU General Data Protection Regulation & Self-Sovereign Identifier(s)](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/EU%20General%20Data%20Protection%20Regulation%20%26%20Self-Sovereign%20Identifier(s))
|
|
||||||
- David Robert
|
|
||||||
* [Identity Forking and Federated Reputation](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-forking-and-federated-reputation.md)
|
|
||||||
- Christopher Malon
|
|
||||||
* [OpenTimestamps: Scalable, Trustless, Distributed Timestamping with Bitcoin](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/opentimestamps.md)
|
|
||||||
- Peter Todd
|
|
||||||
* [Distributed Identity, Distributed Self](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/DistributedIdentityDistributedSelf.md)
|
|
||||||
- Natalie Smolenski
|
|
||||||
* [Blockchain Extensions for Linked Data Signatures](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md)
|
|
||||||
- the Signature Super Friends (Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley)
|
|
||||||
* [Fit for Purpose Blockchains](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/fit-for-purpose-blockchains.md)
|
|
||||||
- Digital Bazaar (Manu Sporny, Dave Longley, Dave Lehn, and Adam Lake)
|
|
||||||
* [Taxonomy of Identity Interaction Types](https://github.com/Identitywoman/Writing/blob/master/Taxonomy-of-Identity-Interaction-Types.md)
|
|
||||||
- Kaliya Young
|
|
||||||
* [Privacy Preserving Identity Architectures](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/privacy-preserving-identity-architectures.md)
|
|
||||||
- Anonymous (no, not that Anonymous, the other one)
|
|
||||||
* [A Technlogy-Free Definition of Self-Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)
|
|
||||||
- Joe Andrieu
|
|
||||||
* [Architecture of Proof-of-Stake Blockchain that Doesn’t Have Native Coin and its Applicability to Decentralized Trading](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/Proof-of-stake-without-native-coin.md)
|
|
||||||
- Pavel Kravchenko
|
|
||||||
* [JXD Examples](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/JXD-Examples.md)
|
|
||||||
- Markus Sabadello
|
|
||||||
* [Anonymous Credentials in Sovrin](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/anonymous-credentials-in-sovrin.md)
|
|
||||||
- Jason Law and Daniel Hardman
|
|
||||||
* [Portable Reputation Toolkit](/topics-and-advance-readings/portable-reputation-toolkit.md)
|
|
||||||
- Noah Thorp and Harlan Wood
|
|
||||||
* [Blockchain Attestation Taxonomies](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/attestation-taxonomies.md)
|
|
||||||
- Christian Lundkvist
|
|
||||||
* [Slepak's Triangle: The fundamental user limit of decentralized consensus systems](topics-and-advance-readings/Slepaks-Triangle.pdf)
|
|
||||||
- Greg Slepak (@taoeffect)
|
|
||||||
* [Sovereign Identity Model for Digital Ecologies](topics-and-advance-readings/Sovereign-Identity-Model-for-Digital-Ecologies.md)
|
|
||||||
- Patrick Deegan
|
|
||||||
* [Alternative Futures: Framework for Identity Scenarios](topics-and-advance-readings/alternative-futures-frameworks.md)
|
|
||||||
- Alessandro Voto
|
|
||||||
* [Powering the Physician-Patient Relationship with HIW of One Blockchain Health IT](physician-patient-relationship.pdf)
|
|
||||||
- Adrian Gropper
|
|
||||||
* [Creating a Humanized Internet](https://github.com/vshen2010/rebooting-the-web-of-trust-fall2016/blob/master/topics-and-advance-readings/Creating%20a%20Humanized%20Internet.pdf)
|
|
||||||
- Monique Morrow, et al
|
|
||||||
* [Smart Consent Protocol](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/Consent%20and%20rights%20to%20use%20Personal%20Data.md)
|
|
||||||
- Dr Shaun Conway, Lohan Spies, Jonathan Endersby, Tim Daubenschütz (see [Completed Papers III](#completed-papers-iii-))
|
|
||||||
* [Creating a Humanized Internet](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/Creating%20a%20Humanized%20Internet.pdf)
|
|
||||||
- Akram Alfawakheeri \<[akram.f1_1@gmail.com](mailto:akram.f1_1@gmail.com)\>, Mark Kovarski \<mark@kovarski.org\>, Aron Dutta <\aron_dutta@yahoo.com\>, Monique Morrow \<monique.morrow223@gmail.com\>, Vivien Shen \<vshen670@gmail.com\>
|
|
||||||
* [DIDs and Personal Data Storage for Children](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/DIDsandPersonalDataStorageforChildren.pdf)
|
|
||||||
- Jonathan Endersby, Shaun Conway, Lohan Spies
|
|
||||||
* [BIP32-Ed25519 Hierarchical Deterministic Keys of a Non-Linear Keyspace](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/HDKeys-Ed25519.pdf)
|
|
||||||
- Dmitry Khovratovich, Jason Law
|
|
||||||
* [Sovrin - Digital Identities in the Blockchain Era](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/Sovrin--digital-identities-in-the-blockchain-era.pdf)
|
|
||||||
* [Alternative Futures: Framework for Identity Scenarios](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/alternative-futures-framework.md)
|
|
||||||
- by Alessandro Voto
|
|
||||||
* [Blockchain Technologies Feature Analysis](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/blockchain-technologies-feature-analysis.md)
|
|
||||||
-Copyright 2016 Digital Bazaar, Inc.
|
|
||||||
* [DID (Decentralized Identifier) Specification](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/did-spec-working-draft-03.md)
|
|
||||||
- Editors: Drummond Reed, Les Chasen Contributors: Christopher Allen, Manu Sporny, David Longley, Jason Law, Daniel Hardman, Markus Sabadello (see [Completed Papers III](#completed-papers-iii-))
|
|
||||||
* [Towards a User Interface for Selectively Revealing Fine-Grained Personal Information to Transaction Counterparties](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/rgrant-user-interface-standards-rwot-fall2016.md)
|
|
||||||
* [Recovery strategy for user-controlled keys for self-sovereign identity](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/user-controlled-key-recovery.md)
|
|
||||||
|
|
||||||
|
|
||||||
### RWoT 4 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/HcVlTZQ.png)
|
|
||||||
|
|
||||||
* [Aligning Signature Formats](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/SignatureFormatAlignment.md) by Manu Sporny, Christopher Allen, Jason Law, and Ryan Shea
|
|
||||||
* [Beyond Identity Cards](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Beyond-Identity-Cards.pdf) by Joe Andrieu
|
|
||||||
* [Blockcerts and Open Badges Signature Alignment](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/BlockcertsAlignment.md) by Kim Hamilton Duffy
|
|
||||||
* [Booting a Web of Sovereignty with a Decentralized Social App](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Booting-a-Web-of-Sovereignty-with-a-Decentralized-Social-App.md) by Adam Lake
|
|
||||||
* [Certificate Chains for DID-based Self-sovereign Identities](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/certificate_chains_dids.md) by Christian Lundkvist
|
|
||||||
* [Credit-based Reputations for Identity Management with Blockchain and Flow Networks](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Credit-based-Reputations-for-Identity-Management.md) by Tobias Mayer, Obar Hasan, and Lionel Brunie
|
|
||||||
* [DID Auth](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-auth.md) by James Monaghan
|
|
||||||
* [The DID Family of Specifications](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-family-of-specifications.md) by Drummond Reed
|
|
||||||
* [DID Method Specifications / BTCR and PGPR](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-methods-btcr-pgpr.md) by Ryan Grant
|
|
||||||
* [DID Names](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/did-names.md) by Drummond Reed and James Monaghan
|
|
||||||
* [Distributed Identities as a EU Cross-border Identity Infrastructure](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Levrage_EU_identities.md) by L. Boldrin
|
|
||||||
* [DKMS—Decentralized Key Management System](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/dkms-decentralized-key-mgmt-system.md) by Drummond Reed
|
|
||||||
* [Fostering the Resilience of an Ecosystem of Workers through Regulated Decentralized Reputation](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Fostering-resilience.md) by Philippe Honigman & Klara Sok
|
|
||||||
* [ID-Blockchain: An Initiative towards Privacy-preserving Blockchain-based Identity](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/id-blockchain.md) by Olivier Maas & Florent Poiron
|
|
||||||
* [The IP Blockchain: Enhancing Global Responsiveness to Infectious Disease Outbreaks](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/RWoT_IPblockchain.md) by Moses Ma, Mark van der Waal, and Net Jacobsson
|
|
||||||
* [Project Vouch: A Decentralized Identity Network Based on Public Attestation, Reputation, and Approval of Identity Attributes](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/ProjectVouch_Peer-attestation-and-reputation-based-identity.md) by Angus Champion
|
|
||||||
* [Reputation Proofs](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/rep-proofs.md) by Dmitry Khovratovich
|
|
||||||
* [RWoT Proposals and Modern Portable Secure Hardware](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/RWoT_proposals_and_modern_portable_secure_hardware.md) by Nicolas Bacca
|
|
||||||
* [Self-sovereign Delegated Identity](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/170418_IDEAS_Paper.pdf) by Pierre Noizat
|
|
||||||
* [Towards a User-centered Web of Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/Towards-a-user-centered-web-of-trust.md) by Fabien Petitcolas & Paul Dunphy
|
|
||||||
* [Trust for Security and Security for Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/topic_alexopoulos.md) by Nikolaos Alexopoulos
|
|
||||||
* [Verifiable Claims and Web of Trust](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/WoTVerifiableClaims.md) by Manu Sporny, Christopher Allen, Joe Andrieu, Matthew Collier, Dave Longley, and Adam Lake
|
|
||||||
* [XDI Verifiable Claims and Link Contracts](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/xdi-verifiable-claims-link-contracts.md) by Markus Sabadello
|
|
||||||
|
|
||||||
### RWoT 5 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/0yF0Ai7.png)
|
|
||||||
|
|
||||||
The following advanced readings have been prepared as primers, intended to give you a foundation in some of the topics that may be discussed at the design workshop:
|
|
||||||
|
|
||||||
* [A Primer on Functional Identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/functional-identity-primer.md) by Joe Andrieu
|
|
||||||
* [A Primer on Self-Sovereign identity](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/self-sovereign-identity-primer.md) by Christopher Allen & Shannon Appelcline
|
|
||||||
* [DID Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/did-primer.md) by Drummond Reed & Manu Sporny
|
|
||||||
* [A Verifiable Claims Primer](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/verifiable-claims-primer.md) by Manu Sporny
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md)
|
|
||||||
|
|
||||||
Here are the rest of the advance readings to date:
|
|
||||||
|
|
||||||
* [#RebootingWebOfTrust User Story & Tech Concept](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/RWOT-User-Story.md) by Christopher Allen
|
|
||||||
* [ActivityPub: from decentralized to distributed social networks](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/activitypub-decentralized-distributed.md) by Christopher Lemmer Webber
|
|
||||||
* [Architectural Layering for Decentralized Identification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Architectural-Layering-for-Decentralized-Identification.md) by Drummond Reed
|
|
||||||
* [BFTKV: Byzantine Fault Tolerant Web of Trust based Key-Value Storage](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/byzantine-fault-tolerant-web-of-trust-based-key-value-storage.md) by Ercan Ozturk
|
|
||||||
* [BFTKV DID Method Specification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/BFTKV-DID-Method-Specification.pdf) by Ercan Ozturk
|
|
||||||
* [Biometric transaction signing on blockchain](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Biometric-transaction-signing-on-blockchain.md) by John Callahan & Virgil Tornoreanu
|
|
||||||
* [Blockchain Based Digital Signatures: Admissibility and Enforceability](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Blockchain-Based-Digital-Signatures--Admissibility-and-Enforceability.md) by Dazza Greenwood
|
|
||||||
* [BTCR DIDs and DDOs](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/btcr-dids-ddos.md) by Kim Hamilton Duffy
|
|
||||||
* [Credential Handler API](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/credential-handler-api.md) by Dave Longley and Manu Sporny
|
|
||||||
* [Data Minimization and Selective Disclosure](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Data-minimization-and-selective-disclosure.md) by Lionel Wolberger
|
|
||||||
* [Decentralized Identifier Tooling](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/credential-handler-api.md) by Dave Longley & Manu Sporny
|
|
||||||
* [DID for the 3D Web](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/did-3d-web.md) by Alberto Elias
|
|
||||||
* [DID Tooling](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/did-tooling.md) by Manu Sporny and Matt Collier
|
|
||||||
* [First XDI Link Contract between "btcr" DID and "sov" DID](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/first-xdi-link-contract-between-btcr-did-and-sov-did.md) by Markus Sabadello
|
|
||||||
* [Framework for the Comparison of Identity Systems](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Framework-for-Comparison-of-Identity-Systems.md) by Kyle Den Hartog
|
|
||||||
* [HIE of One Loop: A Patient-Controlled Independent Health Record](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Loop-white-paper.pdf) by Adrian Gropper
|
|
||||||
* [The Horcrux protocol: Biometric credentials as high-privacy verifiable claims](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Biometric-credentials-as-high-privacy-verifiable-claims.md) by John Callahan & Asem Othman
|
|
||||||
* [Hub Asset Access Control System - Intent](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/DIF-Hub-Permissions-RWOT-Intent.md) by Daniel Buchner
|
|
||||||
* [Hypercerts: Blockcerts Revocation Improvements](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/hypercerts-blockcerts_revocation.md) by João Santos and Kim Hamilton Duffy
|
|
||||||
* [Identifying stakeholders' challenges in the digital economy](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Identifying-challenges-in-the-digital-economy.md) by Irene Hernandez
|
|
||||||
* [Open Badges (and Blockcerts) as Verifiable Claims](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/open-badges-as-verifiable-claims.md) by Kim Hamilton Duffy and Nate Otto
|
|
||||||
* [Owned vs. Unowned Claims and Self-Sovereign Identity](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/owned-vs-unowned-claims-and-ssi.md) by Natalie Smolenski
|
|
||||||
* [Recommendations for Decentralized Key Management Systems](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/dkms-recommendations.md) by Michael Lodder
|
|
||||||
* [Trust Objects: Enabling Advanced Reputation Services on the Web of Trust](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/trust-objects-rough-draft.pdf) by Moses Ma & Dr. Rutu Mulka
|
|
||||||
* [Original Proposal](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/trust-objects-proposal.md) by Moses Ma & Dr. Rutu Mulka
|
|
||||||
* [Veres One DID Method Specification](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/veres-one-did-method.md) by Manu Sporny, Dave Longley & Matt Collier
|
|
||||||
* [Verifiable Claims of Impact](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/verifiable-claims-of-impact.md) by Cedric Franz & Dr. Shaun Conway
|
|
||||||
* [Visa? Really?](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Visa-Really.md) by Kaliya Identity Woman
|
|
||||||
* [Data Minimization and Selective Disclosure](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Data-minimization-and-selective-disclosure.md) by Lionel Wolberger
|
|
||||||
* [HIE of One Loop: A Patient-Controlled Independent Health Record](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/Loop-white-paper.pdf) by Adrian Gropper, MD and the Loop Project Team
|
|
||||||
|
|
||||||
### RWoT 6 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/LmmFZws.png)
|
|
||||||
|
|
||||||
* [Attribute Based Credentials and Variable Length Data Graphs](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/AttributeBasedCredentials_and_VariableLengthDataGraphs.md) by nage
|
|
||||||
* [Blockchain Timestamps Unnecessary In Proof-of-Work?](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Blockchains-Timestamps-Unnecessary-In-PoW.md) by Greg Slepak
|
|
||||||
* [BTCR DID Resolver](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/btcr_did_resolver.md) by Kim Hamilton Duffy, Christopher Allen, Ryan Grant
|
|
||||||
* [Collegial Certifcation Works for Truly Collegial Communities](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Collegial%20Certification%20Works%20for%20Truly%20Collegial%20Communities.pdf) by Wes Kussmaul
|
|
||||||
* [Credential Providers for Signing Application Requests](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/CredentialProvider_App_Integration.md) by Cedric Franz
|
|
||||||
* [DClaims News - A Fake News Mitigation Platform](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DClaims.md) by João Santos
|
|
||||||
* [Decentralized Attestations Storage - Current Challenges](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/decentralised-attestations-storage-network-challenges.md) by Kulpreet Singh
|
|
||||||
* [Decentralized Identities for the Cannabis Industry](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/cannabis-kyc.md) by Matthew Nguyen & Nicholas Shook
|
|
||||||
* [Decentralized Interfaces and the Request-Responsive World](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/decentralized-interfaces.md) by Vlad Kahoun
|
|
||||||
* [Decentralized Self-certifying Self-Identifing Data](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Self_ID_Data_KeyMgmt.md) by Samuel M. Smith
|
|
||||||
* [A Demonstration of the Veres One Blockchain](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-demo.md) by David I. Lehn, Manu Sporny, David Longley, Matt Collier, and Chris Webber
|
|
||||||
* [DID-Auth Protocol](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Auth%20protocol.md) by Kyle Den Hartog
|
|
||||||
* [DID Auth: Scope, Formats, and Protocols](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID%20Auth:%20Scope%2C%20Formats%2C%20and%20Protocols.md) by Markus Sabadello
|
|
||||||
* [did:erc725 method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/DID-Method-erc725.md) by Markus Sabadello, Fabian Vogelsteller, and Peter Kolarov <pkolarov@finid.me>
|
|
||||||
* [Distributed Reputation Systems Using Blockchain Records](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/distributed-reputation-systems-kate-sills.md) by Kate Sills
|
|
||||||
* [Hashed PII Question](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/hashed-PII-Question.md) by Identity Woman
|
|
||||||
* [The Horcrux Protocol: A Method for Decentralized Biometric-based Self-sovereign Identity](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/HorcruxProtocol.pdf) by Asem Othman & John Callahan
|
|
||||||
* [Identity System for Immersive and Ambient Computing](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/identy_immersive_ambient_computing.md) by Alberto Elias
|
|
||||||
* [Integrating Identity Silos via Address Books](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Diam.md) by vishal144
|
|
||||||
* [Open Badges Prototypes and Action Items 2018](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/openbadges-prototypes-action-items-2018.md) by Nate Otto and Kim (Hamilton) Duffy
|
|
||||||
* [Open TLS](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/OpenTLS.md) by Sam Curren
|
|
||||||
* [Open Verifiable Data to Drive the Digital Economy](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/TheOrgBook%20-%20RWoT%20Mar%202018%20-%20Province%20of%20BC.md) by John Jordan
|
|
||||||
* [Petnames for Self Sovereign and Human Readable Identifiers](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/petnames.md) by Christopher Lemmer Webber
|
|
||||||
* [Proposed Collaboration on Open Standards for Data Wallet and Data Service Integration](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/data_wallet_serivce_integration.md) by Ron Kreutzer
|
|
||||||
* [Recent Happenings with Linked Data Capabilities](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md) by Christopher Lemmer Webber
|
|
||||||
* [Self-sovereign Compliance](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/self-sovereign-compliance.md) by Moses Ma
|
|
||||||
* [The Three Primary Roles in the Sovrin Web of Trust Model](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/sovrin-web-of-trust-3-primary-roles.md) by Drummond Reed
|
|
||||||
* [Towards a Sustainable Technology Commons](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/SustainableTechnologyCommons-HeatherVescentv3.md) by Heather Vescent
|
|
||||||
* [Using Blockchain to Store Academic Accreditations](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/documentorum.md) by Luiz Gustavo Ferraz Aoqui and Andrei Moskalev
|
|
||||||
* [Veres One Primer](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-primer.md) by Manu Sporny, et. al.
|
|
||||||
* [The Veres One DID Method](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-did-method.md) by Manu Sporny, David Longley, and Chris Webber
|
|
||||||
* [Veres One Demo](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/veres-one-demo.md) by David I. Lehn, et. al.
|
|
||||||
* [Web of Pragmatics: A Comment on Methodology](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/topics-and-advance-readings/Web-of-Pragmatics.md) by D. Crocker
|
|
||||||
|
|
||||||
### RWoT 7 [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/MCjnuJw.png)
|
|
||||||
|
|
||||||
* [Addressing Global/Local Barriers to Adoption of Decentralized Identity Systems](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Adoption.md) by Eric Brown
|
|
||||||
* [Agent to Agent Communication Protocol Overview](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/a2a-comm-protocol-overview.md) by Kyle Den Hartog
|
|
||||||
* [Blockcerts -- Where we are and what's next](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/blockcerts_roadmap.md) by Kim Hamilton Duffy, Anthony Ronning, Lucas Parker, and Peter Scott
|
|
||||||
* [Can Curation Markets Establish a Sustainable Technology Commons](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/CanCurationMarketsEstablishSustainableTechnologyCommons.pdf) by Sam Chase
|
|
||||||
* [CapAuth](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/capauth.md) by Manu Sporny, Dave Longley, Chris Webber, and Ganesh Annan
|
|
||||||
* [A Concept Diagram For RWOT Identity Terms](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/towards-a-terminology-concept-map.md) by Andrew Hughes
|
|
||||||
* [Cryptocurrency Wallets as a Form of Functional Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Cryptocurrency%20wallets%20a%20an%20application%20of%20Functional%20Identity.md) by Mikerah Quintyne-Collins and Abdulwasay Mehar
|
|
||||||
* [Decentralized Error Reporting](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/decentralized-error-reporting.md) by Jack Poole
|
|
||||||
* [Decentralized Identities and eIDAS](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/leveraging-eidas-for-did.md) by Oliver Terbu
|
|
||||||
* [Decentralized Identity: Hub Authentication & Message Encryption](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/did-auth-jwe.md) by Daniel Buchner
|
|
||||||
* [DIDDoc Conventions for Interoperability](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/diddoc-conventions-for-interoperability.md) by Stephen Curran & Olena Mitovska
|
|
||||||
* [DIDs In DPKI](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/dids-in-dpki.md) by Greg Slepak
|
|
||||||
* [DID Resolution Topics](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/did-resolution-topics.md) by Markus Sabadello
|
|
||||||
* [Digital Identity for the Homeless](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Digital-Identity-for-the-Homeless.md) by Matthew Wong, T. Tian & CG Chen
|
|
||||||
* [Exploring Browser Web of Trust Use Cases](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/exploring-browser-wot-use.md) by Peter Snyder and Ben Livshits
|
|
||||||
* [Five Mental Models of Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/five-mental-models-of-identity.md) by Joe Andrieu
|
|
||||||
* [Identity Hub Permissions / Authorization](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/identity-hub-permissions.md) by Daniel Buchner
|
|
||||||
* [IPLD as a general pattern for DID Documents](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/ipld_did_documents.md) by Christian Lundkvist
|
|
||||||
* [Is a Decentralized Collective Identity Possible?](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Decentralized-Collective-Identity.md) by Heather Vescent
|
|
||||||
* [Magenc Magnet URIs: Secure Object Permanence for the Web](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/magenc.md) by Christopher Lemmer Webber
|
|
||||||
* [Measuring Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/measuring-trust.md) by Tyler Yasaka
|
|
||||||
* [More Control for Identity Holders](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/more-control-for-identity-holders.md) by Arturo Manzaneda and Ismenia Galvao
|
|
||||||
* [Nobody REALLY Trusts the Blockchain](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Nobody_REALLY_Trusts_the_Blockchain.md) by Daniel Burnett
|
|
||||||
* [Not-a-Bot: A Use Case for Decentralized Identity using Proximity Verification to generate a Web of Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/not-a-bot.md) by Moses Ma & Claire Rumore
|
|
||||||
* [The Political Economy of Naming](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/political-economy-of-naming.md) by Kate Sills
|
|
||||||
* [A Public Web of Trust of Public Identities](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/a-public-web-of-trust-of-public-identities.md) by Ouri Poupko and Ehud Shapiro
|
|
||||||
* [Resource Integrity Proofs](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/resource-integrity-proofs.md) by Ganesh Annan, Manu Sporny, Dave Longley, and David Lehn
|
|
||||||
* [RWoT Tribal Knowledge: Cryptographic and Data Model Requirements](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/crypto-data-model-requirements.md) by Manu Sporny, Dave Longley, and Chris Webber
|
|
||||||
* [The Role of Standards in Accelerating Innovation](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/The_Role_of_Standards_in_Accelerating_Innovation.md) by Michael B. Jones
|
|
||||||
* [Scoped Presentation Request on Verifiable Credentials](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/presentation-request/presentation-request.md) by Martin Riedel
|
|
||||||
* [Secure Crypto-Wallet Introductions](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Secure%20Crypto-Wallet%20Introductions.md) by Wolf McNally, Ryan Grant
|
|
||||||
* [Standards for Agency and Decentralized Information Governance - Early Experience](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/standards-for-governance.md) by Adrian Gropper, MD, Michael Chen, MD, and Lydia Fazzio, MD
|
|
||||||
* [Towards Proof of Person](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/towards-proof-of-person.md) by Peter Watts
|
|
||||||
* [A Trustless Web-of-Trust](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/trustless-web-of-trust.md) by Ouri Poupko
|
|
||||||
* [Verifiable Displays](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/verifiable_displays.md) by Kim Hamilton Duffy, Lucas Parker & Anthony Ronning
|
|
||||||
* [Verifiable Offline Credentials](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/verifiable-offline-credentials.md) by Michael Lodder
|
|
||||||
* [What (and Who) Is In Your Wallet](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/what-and-who-is-in-your-wallet.md) by Darrell O'Donnell
|
|
||||||
* [Digital Identity for the Homeless](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/Digital-Identity-for-the-Homeless.md) by Matthew Wong, T. Tian & CG Chen
|
|
||||||
* [Zero Trust Computing with DIDs and DADs](https://github.com/WebOfTrustInfo/rwot7/blob/master/topics-and-advance-readings/ZeroTrustComputingWithDidsAndDads.md) by Samuel M. Smith
|
|
||||||
|
|
||||||
## License [**^**](#contents)
|
|
||||||
|
|
||||||
Unless otherwise noted, all RWoT Completed Papers, Topics and Advance Readings are licensed [Creative Commons CC-BY](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/LICENSE-CC-BY-4.0.md).
|
|
||||||
|
|
||||||
|
|
||||||
## RWoT Github Listing [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/self-sovereign-identity" target="_blank">/WebOfTrustInfo/self-sovereign-identity</a> - Articles and documents associated with designing and implementing identity technology using self-sovereign identity principles
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/website" target="_blank">/WebOfTrustInfo/website</a> - Website for http://www.WebOfTrust.info
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/community-resilience" target="_blank">/WebOfTrustInfo/community-resilience</a> - Rebooting Web of Trust Community Resilience Team
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/satyrn" target="_blank">/WebOfTrustInfo/satyrn</a> - A Markdown-based JavaScript Sandbox
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/sss" target="_blank">/WebOfTrustInfo/sss</a> - Library for the Shamir secret sharing scheme
|
|
||||||
- Forked from dsprenkels/sss
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/verifiable-news" target="_blank">/WebOfTrustInfo/verifiable-news</a> - TBD: W3C Credentials Community Group repository for curbing "social bots" and mitigating the spread of online misinformation and "fake news".
|
|
||||||
* <a href="https://github.com/WebOfTrustInfo/portable-reputation-toolkit" target="_blank">/WebOfTrustInfo/portable-reputation-toolkit</a>
|
|
||||||
|
|
||||||
### Workshops [**^**](#contents)
|
|
||||||
|
|
||||||
* [Rebooting the Web of Trust I: San Francisco (November 2015)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust)
|
|
||||||
* [Rebooting the Web of Trust II: ID2020 (May 2016)](https://github.com/WebOfTrustInfo/ID2020DesignWorkshop)
|
|
||||||
* [Rebooting the Web of Trust III: San Francisco (October 2016)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016)
|
|
||||||
* [Rebooting the Web of Trust IV: Paris (April 2017)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2017)
|
|
||||||
* [Rebooting the Web of Trust V: Boston (October 2017)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017)
|
|
||||||
* [Rebooting the Web of Trust VI: Santa Barbara (March 2018)](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018)
|
|
||||||
* [Rebooting the Web of Trust VII: Toronto (September 2018)](https://github.com/WebOfTrustInfo/rwot7-fall2018)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1,72 +0,0 @@
|
|||||||
# The Evolution of Self Sovereign Identity (Draft Seeking Feedback)
|
|
||||||
|
|
||||||
;TLDR A start at examining leading thought around SSI since 2016, and presenting the idea of "modularizing" essential components of SSI documentation.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
Christopher Allen's seminal work, [The Path to Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/ThePathToSelf-SovereignIdentity.md) continues to be an important and influential document for the Self Sovereign Identity community and movement. Rightly so, Allen does a superb job of outlining where digital identity has come from and where its going. However, Christopher intended for the [Principles of SSI](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md), gathered from the leading thought on digital identity, to be the start of a conversation.
|
|
||||||
|
|
||||||
In order to stimulate the discussion, I've been going through a [/infominer33/self-sovereign-identity](https://github.com/infominer33/self-sovereign-identity) and organizing some thoughts on SSI since Christopher's 2016 post. There are a few different ways to approach and describe SSI. What I aim to do is come up with a list of different "SSI Cases" to modularize the treatment of the subject. This will allow each to contribute in the way that makes most sense for themselves, rather than trying to discuss SSI as a whole in a single whitepaper.
|
|
||||||
|
|
||||||
That October, [Joe Andrieu](https://github.com/jandrieu) submitted [A Technology‐Free Definition of Self‐Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf) to the third Rebooting the Web of Trust Design Workshop. Within it, he describes the Characteristics of SSI: **Control**, **Acceptance**, and **Zero Cost**.
|
|
||||||
|
|
||||||
>1 No disrespect to Christopher Allen’s opening to the conversation, The Path to Self Sovereign Identity [...] It gets a lot right, but leaves a few requirements out, e.g., recoverability and zero cost, and conflates “identities” and claims in an ambiguous manner.
|
|
||||||
|
|
||||||
I decided to put the **10 Principles of SSI** up next to Joe Andrieu's **Characteristics of SSI**
|
|
||||||
|
|
||||||
* [SSI Principles vs. Characteristics](https://github.com/infominer33/awesome-decentralized-id/blob/master/self-sovereign/ssi-principles-vs-characteristics.md)
|
|
||||||
|
|
||||||
Which should also be considered against:
|
|
||||||
|
|
||||||
* [Self-Sovereign Bill of Rights](self-sovereign-identity-bill-of-rights.md) - lifeID (founded by [Chris Boscolo](https://github.com/cboscolo)) adapted the 10 Principles of Self-Sovereign Identity into a [Bill of Rights](https://medium.com/@lifeID_io/lifeid-self-sovereign-identity-bill-of-rights-d2acafa1de8b) that all self-sovereign identity solution should uphold.
|
|
||||||
|
|
||||||
* [Schutte's Take](https://github.com/infominer33/self-sovereign-identity/blob/master/Schutte-on-SSI.md) which offers criticism on the 10 principles.
|
|
||||||
|
|
||||||
|
|
||||||
I think all of this thought should be consolidated into a cohesive declaration of ssi. The idea is to come up with list of phinciples, or characteristics, or rights, that is as complete as possible, while also as concise as possible. There are a few 10 pointed lists, I'm ok with combining them as necessary and if it turns into 19, for example, I'm ok w that. I'd rather err on the side of too much and pare it down gradually, than to not include enough.
|
|
||||||
|
|
||||||
* Next, there are the [7 Myths of SSI](https://github.com/infominer33/self-sovereign-identity/blob/master/7-myths-of-self-sovereign-identity.md) from Timothy Ruff's recent blog post. I've extracted them from his two part series into a concise document. There are surely other myths, and perhaps folk who have encountered them first hand will have some comment on the matter. And my condensed version of his myths could surely be improved upon.
|
|
||||||
|
|
||||||
* A gentle introduction to self-sovereign-identity by @antonylewis has a great section, [How would self-sovereign identity work for the user?](https://github.com/infominer33/awesome-decentralized-id/blob/master/self-sovereign/user-experience.md) that I've extracted into github, in order to make a suitable document based upon it. I need to check on certain specifics, basically I want to re-write that section so I saved it here for that purpose.
|
|
||||||
|
|
||||||
* [How to Convince Dad* of the Importance of Self-Sovereign Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.md)
|
|
||||||
* \*and your sister and your daughter and your best friend and your nephew (SSI Use-Cases)
|
|
||||||
|
|
||||||
^^^ This could also be modularized
|
|
||||||
|
|
||||||
Other content highlighted in [/WebOfTrustInfo/self-sovereign-identity](https:github.com/WebOfTrustInfo/self-sovereign-identity) that I haven't had a chance to fully review, yet:
|
|
||||||
|
|
||||||
* [Identity and Digital Self-Sovereignty](https://medium.com/learning-machine-blog/identity-and-digital-self-sovereignty-1f3faab7d9e3#.3jcgvnbok) - Blog post by [Natalie Smolenski](https://medium.com/@nsmolenski)
|
|
||||||
|
|
||||||
* [SSI: A Roadmap for Adoption](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md) from Rebooting the web of trust, Spring 2018.
|
|
||||||
> This document proposes the formation of a short-term team to develop consistent messaging for the Self-Sovereign Identity (SSI) market.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### What I'm hoping for:
|
|
||||||
|
|
||||||
This is a modular breakdown of SSI documentation I would like to facilitate:
|
|
||||||
(each, perhaps, around 800-1200 words)
|
|
||||||
|
|
||||||
1. History of Digital Identity. Along the lines of Christopher Allen
|
|
||||||
|
|
||||||
2. "How SSI works for the User" something along the line of how Antony Lewis
|
|
||||||
- At its essence, this describes "ssi architecture" so to speak: 'wallet', 'identifier', 'credential' etc and how it interelates
|
|
||||||
|
|
||||||
3. "Principles of SSI" whatever you wanna call it, a complete, concise, and "exhaustive" list of foundational SSI principles or progress in that direction.
|
|
||||||
|
|
||||||
4. SSI Why Blockchain?
|
|
||||||
|
|
||||||
5. Myths of SSI
|
|
||||||
|
|
||||||
6. SSI Use Cases. (a'la "how to convince dad")
|
|
||||||
- This uses the foundation "how SSI works for the USER" to go into more specific details of real life UX
|
|
||||||
|
|
||||||
I'm not limited to those 6, and I'm not glued to that order, but thats a general goal, and "how I would do it." We have the foundations of some core SSI content\documentation that I think will improve SSI education\onboarding. Just as in modularizing a codebase, modularizing SSI documentation will make it easier for any aspect to be improved as needed. I hope for these to become living community driven documents. Personally, I'm good at collecting, organizing, and digesting information, but am new to the SSI community, so I'm sure there's plenty I'm not considering.
|
|
||||||
|
|
||||||
I can see that I'll need to spend a lot more time with this content, am just learning my way around it right now.
|
|
||||||
|
|
||||||
I'm not the most qualified, I just have time and motivation. (Specifically, sometimes I write about Self-Sovereign Identity. But I want to write about it in an accurate way, which is difficult to do until some order is made of all this material.)
|
|
||||||
|
|
||||||
## [infominer.id](https://infominer.id) ([**^**](#contents))
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/android-chrome-256x256.png" align="right" width="170" height="170"/>
|
|
@ -1,101 +0,0 @@
|
|||||||
# Self Sovereign Identity (SSI)
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/images/infominer.png" align="right" width="150" height="140"></a>
|
|
||||||
**Articles and documents associated with Self Sovereign Identity Fundamentals.**
|
|
||||||
|
|
||||||
This directory was born from [/WebOfTrustInfo/self-sovereign-identity](https://github.com/WebOfTrustInfo/self-sovereign-identity), the original SSI repository. I've done a bit of work over there, and decided to expand my efforts. The reason I got started on this is because I wanted to write an article about SSI, and saw some areas where I think I can help with some of the legwork towards a more complete, and up-to-date set of SSI literature.
|
|
||||||
|
|
||||||
In my opinion, the best overall article on the subject is still Christopher Allen's rallying cry: [The Path to Self-Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/ThePathToSelf-SovereignIdentity.md). Christopher did an outstanding job of outlining the history of internet identity standards, and introduces [10 Principles of Self-Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md), currently in revision.
|
|
||||||
|
|
||||||
However, considerable additional material has been created on the subject since then, including some helpful criticism on the principles. I've organized some of my initial thoughts in [/evolution-of-ssi.md](evolution-of-ssi.md).
|
|
||||||
|
|
||||||
Then I realized that I should make a more complete survey of the subject, if I want to be thorough. So now I'm collecting as much SSI info as I can, and organizing it here. Once I've completed a review of existing literature on the subject, I'll put it into a google shared doc to encourage further participation.
|
|
||||||
|
|
||||||
![](http://imgur.com/3zz62kpl.png)
|
|
||||||
|
|
||||||
|
|
||||||
## SSI Documentation Components
|
|
||||||
|
|
||||||
* [The Path to Self-Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/ThePathToSelf-SovereignIdentity.md) - The original article on Self-Sovereign Identity and the 10 Principles of Self-Sovereign Identity as published on 2016-04-25 in github and at [Life With Alacrity](http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html) by [Christopher Allen](http://www.github.com/christophera) [[**ϟ**](https://www.coindesk.com/path-self-sovereign-identity/amp/)]
|
|
||||||
* [10 Principles of Self-Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md) - The Self-Sovereign Identity Principles, in progress of being revised.
|
|
||||||
* [Core Characteristics of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/characteristics-of-sovereign-identity.md) - from *[A Technlogy-Free Definition of Self-Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf)* - Topic paper for Rebooting Web of Trust III by [Joe Andrieu](http://www.github.com/jandrieu) (for review and comparison against *10 Principles of SSI*)
|
|
||||||
* [SSI Principles vs. Characteristics](ssi-principles-vs-characteristics.md)
|
|
||||||
* [Self-Sovereign Bill of Rights](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-bill-of-rights.md) - lifeID (founded by [Chris Boscolo](https://github.com/cboscolo)) adapted the 10 Principles of Self-Sovereign Identity into a [Bill of Rights](https://medium.com/@lifeID_io/lifeid-self-sovereign-identity-bill-of-rights-d2acafa1de8b) that all self-sovereign identity solution should uphold.
|
|
||||||
* [Schutte's Take](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/Schutte-on-SSI.md) offers criticism on the 10 principles.
|
|
||||||
* [7 Myths of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/7-myths-of-self-sovereign-identity.md) - from Timothy Ruff's [blog post](https://medium.com/evernym/7-myths-of-self-sovereign-identity-67aea7416b1).
|
|
||||||
* [A Gentle Guide to Self Sovereign Identity](https://bitsonblocks.net/2017/05/17/gentle-introduction-self-sovereign-identity/) has a section called "How would self-sovereign identity work for the user?" that could be [modularized](https://github.com/infominer33/awesome-decentralized-id/blob/master/self-sovereign-identity/user-experience.md).
|
|
||||||
* [How to Convince Dad* of the Importance of Self-Sovereign Identity](https://github.com/WebOfTrustInfo/rwot7/blob/master/final-documents/convincing-dad.md) (\*and your sister and your daughter and your best friend and your nephew) (SSI Use-Cases)
|
|
||||||
* [Self-Sovereign Identity and the Legitimacy of Permissioned Ledgers](http://www.windley.com/archives/2016/09/self-sovereign_identity_and_the_legitimacy_of_permissioned_ledgers.shtml)
|
|
||||||
|
|
||||||
### Assorted
|
|
||||||
|
|
||||||
* [Identity and Digital Self-Sovereignty](https://medium.com/learning-machine-blog/identity-and-digital-self-sovereignty-1f3faab7d9e3#.3jcgvnbok) - Blog post by [Natalie Smolenski](https://medium.com/@nsmolenski)
|
|
||||||
* [Sovereignty in Historical Context for Self-Sovereign Identity – Natalie Smolenski – Webinar 18](http://ssimeetup.org/sovereignty-historical-context-self-sovereign-identity-natalie-smolenski-webinar-18/)
|
|
||||||
* [SSI: A Roadmap for Adoption](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/a-roadmap-for-ssi.md) from Rebooting the web of trust, Spring 2018.
|
|
||||||
> This document proposes the formation of a short-term team to develop consistent messaging for the Self-Sovereign Identity (SSI) market.
|
|
||||||
* [Inevitable Rise of Self-Sovereign Identity](https://sovrin.org/wp-content/uploads/2018/03/The-Inevitable-Rise-of-Self-Sovereign-Identity.pdf)
|
|
||||||
* [Self-Sovereign Identity: Why Blockchain?](https://www.ibm.com/blogs/blockchain/2018/06/self-sovereign-identity-why-blockchain/)
|
|
||||||
* [IBM-Paving the Road to Self-Sovereign Identity with Blockchain, Open Standards](https://www.ibm.com/blogs/think/2017/10/self-sovereign-id-blockchain/)
|
|
||||||
* [The Three Models of Digital Identity Relationships — How self-sovereign identity (SSI) is different, and why it’s better](https://medium.com/evernym/the-three-models-of-digital-identity-relationships-ca0727cb5186)
|
|
||||||
* [The Rise of Self-Sovereign Identity - Hyperledger Indy](https://wso2.com/blog/research/the-rise-of-self-sovereign-identity-hyperledger-indy)
|
|
||||||
* [Paving the Road to Self-Sovereign Identity with Blockchain, Open Standards](https://www.ibm.com/blogs/think/2017/10/self-sovereign-id-blockchain/)
|
|
||||||
* [Deployment of a Blockchain-Based Self-Sovereign Identity - Delft](https://arxiv.org/pdf/1806.01926.pdf)
|
|
||||||
* [The Nail Finds a Hammer: Self-Sovereign Identity, Design Principles, and Property Rights in the Developing World](https://www.newamerica.org/future-property-rights/reports/nail-finds-hammer/)
|
|
||||||
* [GDPR - A reflection on the 'self-sovereign identity' and the Blockchain](https://www.linkedin.com/pulse/gdpr-reflection-self-sovereign-identity-blockchain-nicolas-ameye/)
|
|
||||||
* [Self-Sovereign Privacy By Design](https://github.com/sovrin-foundation/protocol/blob/master/self_sovereign_privacy_by_design_v1.md)
|
|
||||||
* [Is Self-Sovereign Identity the ultimate GDPR compliance tool? [1\3]](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-9d8110752f89) [[**2**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-40db94c1c437)] [[**3**](https://medium.com/evernym/is-self-sovereign-identity-ssi-the-ultimate-gdpr-compliance-tool-7296a3b07769)]
|
|
||||||
* [Towards Self-Sovereign Identity using Blockchain Technology](https://essay.utwente.nl/71274/1/Baars_MA_BMS.pdf)
|
|
||||||
* [Self-sovereign Identity – Opportunities and Challenges for the Digital Revolution](https://arxiv.org/pdf/1712.01767.pdf)
|
|
||||||
* [Decentralized Identity Trilemma](http://maciek.blog/decentralized-identity-trilemma/)
|
|
||||||
>There seems to exist a trilemma in decentralized identity analogous to @Zooko's triangle. None of the existing solutions are at the same time: 1) privacy-preserving, 2) Sybil-resistant 3) self-sovereign -[[**T**](https://twitter.com/MaciekLaskus/status/1031859093072424960)]
|
|
||||||
* [Self Sovereign Identity and MyData](https://medium.com/@apoikola/self-sovereign-identity-and-mydata-e1f996a9451)
|
|
||||||
* [HIPE 0014-ssi-notation](https://github.com/hyperledger/indy-hipe/tree/master/text/0014-ssi-notation)
|
|
||||||
* [IIW - Past Workshops](https://internetidentityworkshop.com/past-workshops/)
|
|
||||||
* [Self Sovereign Identity -identitywoman.net](https://identitywoman.net/self-sovereign-identity/)
|
|
||||||
* [Self Sovereign Identity going where no identity has gone before](https://www.brighttalk.com/webcast/16693/342423/self-sovereign-identity-going-where-no-identity-has-gone-before)
|
|
||||||
* [LESS identity](https://medium.com/@trbouma/less-identity-65f65d87f56b)
|
|
||||||
* [A Primer on Functional Identity](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/functional-identity-primer.md); Joe Andrieu describes identity terms in plain language, with regards to what function they serve.
|
|
||||||
* [Matching Identity Management Solutions to Self Sovereign Identity Solutions](https://www.slideshare.net/TommyKoens/matching-identity-management-solutions-to-selfsovereign-identity-principles)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
#### Video
|
|
||||||
|
|
||||||
* [Identity and the quest for Self Sovereign Identity - Daniel Hardman](https://www.youtube.com/watch?v=iqmY_h49vPs)
|
|
||||||
* [Self Sovereign Identity and the MyData model from Finland - Antti 'Jogi' Poikola](https://www.youtube.com/watch?v=amq88XmWaNs)
|
|
||||||
* [Self-Sovereign Identity (SSI) and Open Source – Richard Esplin from SSIMeetup](http://ssimeetup.org/self-sovereign-identity-ssi-open-source-richard-esplin-webinar-16/)
|
|
||||||
* [Decentralized Identifiers enable self-sovereign identity - MyData 2018](https://www.youtube.com/watch?v=KsIM0zq37fU)
|
|
||||||
* [eIDAS and Self-Sovereign Identity - MyData 2018](https://www.youtube.com/watch?v=AHa175AEVVs)
|
|
||||||
* [uPort: Self-Sovereign Identity Meets Portable Data](https://www.youtube.com/watch?v=hBIragrwqYc)
|
|
||||||
* [Behind the Cloud—Blockchain and Self-Sovereign Identity in the Enterprise](https://www.youtube.com/watch?v=wSdm2-18Z2g)
|
|
||||||
* [The Story of Open SSI Standards - Drummond Reed](https://www.youtube.com/watch?v=RllH91rcFdE&feature=youtu.be&t=4m30s)
|
|
||||||
* [Kim Cameron - Identity Laws](https://channel9.msdn.com/Blogs/scobleizer/Kim-Cameron-Identity-Laws)
|
|
||||||
|
|
||||||
### History
|
|
||||||
|
|
||||||
* [Kim Cameron Identity Laws](https://channel9.msdn.com/Blogs/scobleizer/Kim-Cameron-Identity-Laws)
|
|
||||||
* [Laws of Identity - Whitepaper](https://web.archive.org/web/20080814163727/http://www.identityblog.com/stories/2004/12/09/thelaws.html)
|
|
||||||
* [*What is Sovereign Source Authority?*](https://www.moxytongue.com/2012/02/what-is-sovereign-source-authority.html) shows an early use of 'sovereign' in relation to our internet identities. The term "Self Sovereign Identity" started becoming widely used in 2014.[[**ϟ**](https://www.tokencommons.org/Windhover-Principles-for-Digital-Identity-Trust-Data.html)][[**ϟ**](https://hubculture.com/hubs/47/news/689/)]
|
|
||||||
* [Sovrin Foundation Launches first dedicated Self Sovereign Identity Network](https://www.prnewswire.com/news-releases/sovrin-foundation-launches-first-dedicated-self-sovereign-identity-network-300336702.html)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Assorted
|
|
||||||
|
|
||||||
* <a href="https://twitter.com/ChristopherA/status/989120215702261761?ref_src=twsrc%5Etfw"><img src="https://i.imgur.com/f3FlznM.png"/></a>
|
|
||||||
* <a href="https://twitter.com/VitalikButerin/status/1072160446180810752"><img src="https://i.imgur.com/tNvN7vV.png"/></a>
|
|
||||||
* [There’s A Facebook Alternative, It’s Called Self-Sovereign Identity](https://www.coindesk.com/theres-alternative-facebook-called-self-sovereign-identity) —coindesk
|
|
||||||
* [A Universal Resolver for self-sovereign identifiers](https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c) [[**G**](https://github.com/decentralized-identity/universal-resolver)] [[**>**](#Decentralized-Identity-Foundation)]
|
|
||||||
* [uniresolver.io](https://uniresolver.io/)
|
|
||||||
|
|
||||||
|
|
||||||
### Resources
|
|
||||||
|
|
||||||
* [SSIMeetup](http://ssimeetup.org/) [[**S**](https://www.slideshare.net/SSIMeetup/presentations)] [[**V**](https://www.youtube.com/channel/UCSqSTlKdbbCM1muGOhDa3Og)] [[**tele**](https://t.me/SSIMeetup)]
|
|
||||||
\- SSI Meetup is an open, collaborative community to help SSI evangelists around the world, independent of company interests or standards.
|
|
||||||
* [WebOfTrustInfo/self-sovereign-id](https://github.com/WebOfTrustInfo/self-sovereign-identity)
|
|
||||||
* [Self-Sovereign Identity — wiki.p2pfoundation](https://wiki.p2pfoundation.net/Self-Sovereign_Identity)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### [infominer.id](https://infominer.id)
|
|
||||||
<a href="https://infominer.id"><img src="https://infominer.id/images/infominer.png" align="right" width="150" height="140"></a>
|
|
@ -1,91 +0,0 @@
|
|||||||
# A Comparison Between SSI Principles, and Characteristics
|
|
||||||
|
|
||||||
In April of 2016, Christopher Allen published "[The Path to Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/ThePathToSelf-SovereignIdentity.md)."
|
|
||||||
|
|
||||||
>The idea of digital identity has been evolving for a few decades now, from centralized identities to federated identities to user-centric identities to self-sovereign identities. However, even today exactly what a self-sovereign identity is, and what rules it should recognize, aren’t well-known.
|
|
||||||
>
|
|
||||||
>This article seeks to begin a dialogue on that topic, by offering up a definition and a set of principles as a starting point for this new form of user-controlled and persistent identity of the 21st century.
|
|
||||||
|
|
||||||
His article details the history of digital identity standards, and the user experience accompanying those standards. After describing from where we've come, Allen draws from leading thought on digital identity to compose the [Principles of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md).
|
|
||||||
|
|
||||||
That October, [Joe Andrieu](https://github.com/jandrieu) submitted [A Technology‐Free Definition of Self‐Sovereign Identity](https://github.com/jandrieu/rebooting-the-web-of-trust-fall2016/raw/master/topics-and-advance-readings/a-technology-free-definition-of-self-sovereign-identity.pdf) to the third Rebooting the Web of Trust Design Workshop.
|
|
||||||
|
|
||||||
>1 No disrespect to Christopher Allen’s opening to the conversation, The Path to Self Sovereign Identity [...] It gets a lot right, but leaves a few requirements out, e.g., recoverability and zero cost, and conflates “identities” and claims in an ambiguous manner.
|
|
||||||
|
|
||||||
Andrieu explores what people need from self-sovereign identity, independant from technology. An important consideration, for Joe, is realizing UN Sustainable Development Goal 16.9 “Providing every last person on the planet with a legal identity by 2030."
|
|
||||||
|
|
||||||
>In order to fund, co‐develop, and eventually deploy a global self‐sovereign solution to UN Sustainable Development Goal 16.9, it would be prudent to begin with an explicit requirements process independent of any specific technology.
|
|
||||||
|
|
||||||
In conclusion, we are offered : **Control**. **Acceptance**. **Zero Cost**.
|
|
||||||
|
|
||||||
I'd like to review the <i>the fundamental characteristics of self‐sovereign identity</i> as detailed by Joe Andreiu, and compare each of the <i>principles</i> individually to ensure that all of the essentials are considered.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### Fundamental Characteristics of Self-Sovereign Identity
|
|
||||||
|
|
||||||
#### CONTROL
|
|
||||||
* **Self‐sovereign identities are controlled by the individual:**
|
|
||||||
* **Self‐generatable and Independent:** Individuals must be able to create identity information without asking for permission and be able to assert identity information from any authority. The resulting identity must have the same technical reliability as those provided by well‐known, “official” sources. The observer, of course, is always free to decide whether or not a given piece of information is meritorious, but the information must be able to be verified as a non‐repudiatable statement of correlation using exactly the same mechanisms regardless of source. Further, individuals must be able to present self‐generated identity information without disclosing that the authority in the claim is the subject of the claim.
|
|
||||||
* **Opt‐in**: The affordance for asserting identity information starts with the individual. While an individual may present claims from known or accepted third party authorities, it is the individual who asserts that the claim applies to them. Self‐sovereign identities begin with the will of the individual, with the intentional presentation of identity information.
|
|
||||||
* **Minimal Disclosure**: Individuals should be able to use services with minimal identity information. Features that depend on enhanced correlation must be understood by the average user. Such features should be permissioned with the highest granularity, so functions independent of correlation work equally well alongside those dependent on it. It is not acceptable to deny services because of a refusal to provide unrelated information.
|
|
||||||
* **Non‐participation**: Individuals must be able to choose to not provide identity information for services where it isn’t absolutely required. Any spontaneous identifiers necessary for a service to function, such as cookies or session ids, must use the same infrastructure for consent, persistence, transience, and disclosure as if provided by the individual.
|
|
||||||
* **Opt‐out**: Individuals should be able to opt‐out of identifying records post‐facto as a matter of course. People should be able to stop the use of a correlating identity information by request. Some transactions necessarily require long term retention of identity information, such as financial transactions, purchases, and shipments. Actions that create permanent records should be clearly marked and communicated such that the retention is expected and understood by the average person. All other actions which leverage a self‐sovereign identity should be de‐correlated on‐demand and said identifiers should no longer be used to correlate that individual across contexts.
|
|
||||||
* **Recoverable**: Sovereign identities must be robust enough to be recovered even if hard drives are lost, wallets stolen, or birth certificates lost in a fire. Self‐sovereign identities must provide a way for individuals to recover and reassert that existing identify information applies to them even in the face of complete loss of credentials. This may be challenging given current technical proposals, but the point of this paper is to explore the non‐technical requirements of a self‐sovereign identity. To fully address the needs of UN Sustainable Development Goal 16.9, identity assurance can’t depend on pieces of paper, devices, or other artifacts that can be lost, stolen, destroyed, and falsified.
|
|
||||||
|
|
||||||
#### ACCEPTANCE
|
|
||||||
* **Self‐sovereign identities are accepted wherever observers correlate individuals across contexts.**
|
|
||||||
* **Standard**: There is an open, public standard managed through a formal standards body, free to use by anyone without financial or intellectual encumbrance. Simple The core standard (schema, serialization, and protocols) must be atomically minimal, providing the barest data set, allowing complexity to emerge not from a complicated data model but from a multiplicity of information types, authorities, and observations.
|
|
||||||
* **Non‐repudiatable**: Individual claims should be cryptographically signed to assure non‐repudiatable statements of correlation. Long term, public and semi‐public ledgers should be used to record claims that become statistically impossible to falsify over time. Self‐sovereign identities, at a minimum depend on cryptographic assurances, and most likely will be further enabled by non‐repudiatable public ledgers.
|
|
||||||
* **Reliable**: Access to self‐sovereign identities must be at least as reliable as access to the Internet. It should not rely on any individual or group of centralized servers, connections, or access technologies. Substantially Equivalent Above all, self‐sovereign identities must meet the needs of legacy identity observers at least as well as current solutions. If the core architecture is inherently less capable than existing approaches there is little hope of systemic adoption.
|
|
||||||
|
|
||||||
#### ZERO COST
|
|
||||||
* **Finally, any proposed standard for self‐sovereign identity must be adoptable at absolutely minimal cost.**
|
|
||||||
* Not only must it be free of licensing encumbrances, it must be implementable with readily available, inexpensive, commodity hardware running common operating systems. If it can’t be achieved using today’s commodity products, then we must help manufacturers incorporate what we need.
|
|
||||||
|
|
||||||
**In order to reach every last person on the planet**—the explicit target of UN Sustainable Development Goal 16.9—**self‐sovereign identity must be realizable at massive scale with close to zero marginal cost**.
|
|
||||||
|
|
||||||
The systems we use to make sense of the resulting identity transactions will provide more than enough consulting, software, and hardware revenue to finance the development of the core enabling technology. Just as the web browser was a zero cost entry into a vast economic and innovation engine of the world‐wide web, so too must self‐sovereign identity begin with the most cost‐effective on‐ramp that can be engineered.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### Principles of Self-Sovereign Identity
|
|
||||||
|
|
||||||
Now we'll review Christopher Allen's [Principles of Self Sovereign Identity](https://github.com/WebOfTrustInfo/self-sovereign-identity/blob/master/self-sovereign-identity-principles.md) one at a time to see how well the characteristics compare.
|
|
||||||
|
|
||||||
>1. **Existence.** *Users must have an independent existence.* Any self-sovereign identity is ultimately based on the ineffable “I” that’s at the heart of identity. It can never exist wholly in digital form. This must be the kernel of self that is upheld and supported. A self-sovereign identity simply makes public and accessible some limited aspects of the “I” that already exists.
|
|
||||||
|
|
||||||
I believe, the *Existance* principle is well represented by the first bulletpoint under the characteristic of *Control*, Self‐generatable and Independent.
|
|
||||||
|
|
||||||
>2. **Control.** *Users must control their identities.* Subject to well-understood and secure algorithms that ensure the continued validity of an identity and its claims, the user is the ultimate authority on their identity. They should always be able to refer to it, update it, or even hide it. They must be able to choose celebrity or privacy as they prefer. This doesn’t mean that a user controls all of the claims on their identity: other users may make claims about a user, but they should not be central to the identity itself.
|
|
||||||
|
|
||||||
The principle of Control must be well represented, since the characteristic of *Control* has the following 5 sub-points: **Self Generatable and Independent**, **Opt-In**, **Minimal Disclosure**, **Non-participation**, **Opt-out**, **Recoverable**.
|
|
||||||
|
|
||||||
>3. **Access.** *Users must have access to their own data.* A user must always be able to easily retrieve all the claims and other data within his identity. There must be no hidden data and no gatekeepers. This does not mean that a user can necessarily modify all the claims associated with his identity, but it does mean they should be aware of them. It also does not mean that users have equal access to others’ data, only to their own.
|
|
||||||
>4. **Transparency**. *Systems and algorithms must be transparent.* The systems used to administer and operate a network of identities must be open, both in how they function and in how they are managed and updated. The algorithms should be free, open-source, well-known, and as independent as possible of any particular architecture; anyone should be able to examine how they work.
|
|
||||||
|
|
||||||
Access and Transparency are not not explicitly represented in the Characteristics of SSI. The *Control* characteristic should be examined in relation.
|
|
||||||
|
|
||||||
>5. **Persistence.** *Identities must be long-lived.* Preferably, identities should last forever, or at least for as long as the user wishes. Though private keys might need to be rotated and data might need to be changed, the identity remains. In the fast-moving world of the Internet, this goal may not be entirely reasonable, so at the least identities should last until they’ve been outdated by newer identity systems. This must not contradict a “right to be forgotten”; a user should be able to dispose of an identity if he wishes and claims should be modified or removed as appropriate over time. To do this requires a firm separation between an identity and its claims: they can't be tied forever.
|
|
||||||
>6. **Portability.** *Information and services about identity must be transportable.* Identities must not be held by a singular third-party entity, even if it's a trusted entity that is expected to work in the best interest of the user. The problem is that entities can disappear — and on the Internet, most eventually do. Regimes may change, users may move to different jurisdictions. Transportable identities ensure that the user remains in control of his identity no matter what, and can also improve an identity’s persistence over time.
|
|
||||||
>7. **Interoperability.** *Identities should be as widely usable as possible.* Identities are of little value if they only work in limited niches. The goal of a 21st-century digital identity system is to make identity information widely available, crossing international boundaries to create global identities, without losing user control. Thanks to persistence and autonomy these widely available identities can then become continually available.
|
|
||||||
|
|
||||||
These principles could be more closely examined against the sub-points of the *Acceptance* characteristic.
|
|
||||||
|
|
||||||
>8. **Consent.** *Users must agree to the use of their identity.* Any identity system is built around sharing that identity and its claims, and an interoperable system increases the amount of sharing that occurs. However, sharing of data must only occur with the consent of the user. Though other users such as an employer, a credit bureau, or a friend might present claims, the user must still offer consent for them to become valid. Note that this consent might not be interactive, but it must still be deliberate and well-understood.
|
|
||||||
>9. **Minimalization.** *Disclosure of claims must be minimized.* When data is disclosed, that disclosure should involve the minimum amount of data necessary to accomplish the task at hand. For example, if only a minimum age is called for, then the exact age should not be disclosed, and if only an age is requested, then the more precise date of birth should not be disclosed. This principle can be supported with selective disclosure, range proofs, and other zero-knowledge techniques, but non-correlatibility is still a very hard (perhaps impossible) task; the best we can do is to use minimalization to support privacy as best as possible.
|
|
||||||
|
|
||||||
I think these two principles are well represented by the *Control* characteristic.
|
|
||||||
|
|
||||||
>10. **Protection.** *The rights of users must be protected.* When there is a conflict between the needs of the identity network and the rights of individual users, then the network should err on the side of preserving the freedoms and rights of the individuals over the needs of the network. To ensure this, identity authentication must occur through independent algorithms that are censorship-resistant and force-resilient and that are run in a decentralized manner.
|
|
||||||
|
|
||||||
This is an important principle that I don't think is represented in the Characteristics.
|
|
||||||
|
|
||||||
### Conclusion
|
|
||||||
|
|
||||||
This review leaves me with more questions than answers. I'm not sure if we should implement the best parts of the *Characteristics* into the *Principles*, or the other way around.
|
|
||||||
|
|
||||||
I'm willing to make an attempt at bringing these together if no one else jumps at the chance. However, I'd like to gather some feedback. I'm tempted to use the Characteristics as the foundation, and simply incorporate any principles not well represented. However, I'm not sure if "Control, Acceptance, and Zero Cost" are the best way to divide them up.
|
|
||||||
|
|
||||||
|
|
||||||
Research Based Content **—[infominer.id](https://infominer.id)**
|
|
@ -1,28 +0,0 @@
|
|||||||
# How would self-sovereign identity work for the user?
|
|
||||||
Adapted from [A gentle introduction to self-sovereign-identity](https://bitsonblocks.net/2017/05/17/gentle-introduction-self-sovereign-identity/) by [@antonylewis](https://github.com/antonylewis). I think this could use some polishing, but this is a good start, and a good example of a basic necessary SSI explainer.
|
|
||||||
|
|
||||||
You would have an app on a smartphone or computer, some sort of “identity wallet” where identity data would be stored on the hard drive of your device, or with an agent of your choosing, but crucially not stored in a central repository.
|
|
||||||
|
|
||||||
Your identity wallet would start off empty with only a self-generated Decentralized identifier (DID).
|
|
||||||
|
|
||||||
At this stage, no one else in the world knows about this identification number. No one issued it to you. You created it yourself. It is self-sovereign. The laws of big numbers and randomness ensure that no one else will generate the same identification number as you.
|
|
||||||
|
|
||||||
You then use this identification number, along with your identity claims, and get attestations from relevant authorities.
|
|
||||||
|
|
||||||
You can then use these attested claims as your identity information.
|
|
||||||
|
|
||||||
Claims would be stored by typing text into standardised text fields, and saving photos or scans of documents.
|
|
||||||
|
|
||||||
Proofs would be stored by saving scans or photos of proof documents. However this would be for backward compatibility, because digitally signed attestations remove the need for proofs as we know them today.
|
|
||||||
|
|
||||||
Attestations – and here’s the neat bit – would be stored in this wallet too. These would be machine readable, digitally signed pieces of information, valid within certain time windows. The relevant authority would need to sign these with digital signatures – for example, passport agencies, hospitals, driving licence authorities, police, etc.
|
|
||||||
|
|
||||||
Need to know, but not more: Authorities could provide “bundles” of attested claims, such as “over 18”, “over 21”, “accredited investor”, “can drive cars” etc, for the user to use as they see fit. The identity owner would be able to choose which piece of information to pass to any requester. For example, if you need to prove you are over 18, you don’t need to share your date of birth, you just need a statement saying you are over 18, signed by the relevant authority.
|
|
||||||
|
|
||||||
Sharing this kind of data is safer both for the identity provider and the recipient. The provider doesn’t need to overshare, and the recipient doesn’t need to store unnecessarily sensitive data – for example, if the recipient gets hacked, they are only storing “Over 18” flags, not dates of birth.
|
|
||||||
|
|
||||||
Even banks themselves could attest to the person having an account with them. We would first need to understand what liability they take on when they create these attestations. I would assume it would be no more than the liability they currently take on when they send you a bank statement, which you use as a proof of address elsewhere.
|
|
||||||
|
|
||||||
Data sharing
|
|
||||||
Data would be stored on the person’s device (as pieces of paper are currently stored at home today), and then when requested, the person would approve a third party to collect specific data, by tapping a notification on their device, We already have something similar to this – if you have ever used a service by “linking” your Facebook or LinkedIn account, this is similar – but instead of going to Facebook’s servers to collect your personal data, it requests it from your phone, and you have granular control over what data is shared.
|
|
||||||
|
|
@ -1,63 +0,0 @@
|
|||||||
# State Sponsored Identity Initiatives
|
|
||||||
|
|
||||||
|
|
||||||
* [Identity Validation as a Public Sector Digital Service?](https://blog.aniljohn.com/2014/07/identity-validation-as-a-public-sector-digital-service.html)
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
* [Canada](#canada-)
|
|
||||||
* [European Union](#european-union-)
|
|
||||||
* [Netherlands](#netherlands-)
|
|
||||||
* [Spain](#spain-)
|
|
||||||
* [Switzerland](#switzerland-)
|
|
||||||
* [USA](#usa-)
|
|
||||||
|
|
||||||
## Canada [**^**](#contents) [**>**](#Hyperledger-Indy)
|
|
||||||
![](https://i.imgur.com/1QmQiy2.png)
|
|
||||||
|
|
||||||
>VON's founding members are governments who are, by law, trusted issuers of data about organizations. The Province of British Columbia, Province of Ontario and the Government of Canada have come together to create the initial services needed to establish VON.
|
|
||||||
>
|
|
||||||
>VON's founders have delivered new Indy-based open source components which form VON's backbone. TheOrgBook is a publicly accessible repository of verifiable claims about organizations. VON-X enables services to verify and issue credentials.[[**ϟ**](https://hgf18.sched.com/event/G8rm/verifiable-organizations-network-a-production-government-deployment-of-hyperledger-indy-john-jordan-province-of-british-columbia-stephen-curran-cloudcompass-computing-inc)]
|
|
||||||
|
|
||||||
* [Verified Organization Network](https://vonx.io/) [[**G**](https://github.com/bcgov/von)] [[**D**](https://vonx.io/getting_started/von-overview/)] [[**ϟ**](https://www.iaca.org/wp-content/uploads/VON-Using-Blockchain-Technology.pdf)]
|
|
||||||
* "an initiative by the government of British Columbia to create a trusted network of organizational data. It allows organizations to claim credentials that are part of their own digital identity, using a component called [TheOrgBook](https://theorgbook.pathfinder.gov.bc.ca/en/home)[[**G**](https://github.com/bcgov/theorgbook)] that lists entities with their associated public verifiable claims.
|
|
||||||
* [Pan-Canadian Trust Framework](https://github.com/canada-ca/PCTF-CCP)
|
|
||||||
* [idtrail.org](http://www.idtrail.org/)
|
|
||||||
* [/indy-ecosystem/VON.md](indy-ecosystem/VON.md)
|
|
||||||
<a href="https://twitter.com/sboots/status/1070320318487584768"><img src="https://i.imgur.com/wdbN3Ld.png"/></a>
|
|
||||||
|
|
||||||
|
|
||||||
## European Union [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/DuQXLhs.png)
|
|
||||||
|
|
||||||
* [EU BLOCKCHAIN OBSERVATORY AND FORUM—Workshop Report e-Identity](https://www.eublockchainforum.eu/sites/default/files/reports/workshop_5_report_-_e-identity.pdf)
|
|
||||||
* [Keyp](https://keyp.io/) —"Welcome to Europe’s fastest growing open digital identity ecosystem."
|
|
||||||
* [EU Report Considers Blockchain-Based Digital Identities, Tokenized National Currencies](https://cointelegraph.com/news/eu-report-considers-blockchain-based-digital-identities-tokenized-national-currencies)
|
|
||||||
* EU Blockchain Forum - [BLOCKCHAIN FOR GOVERNMENT AND PUBLIC SERVICES](https://www.eublockchainforum.eu/sites/default/files/reports/eu_observatory_blockchain_in_government_services_v1_2018-12-07.pdf)
|
|
||||||
* [Government services and digital identity](https://www.eublockchainforum.eu/sites/default/files/research-paper/20180801_government_services_and_digital_identity.pdf)
|
|
||||||
|
|
||||||
|
|
||||||
## Netherlands [**^**](#contents)
|
|
||||||
|
|
||||||
![](https://i.imgur.com/CVA9t94.png)
|
|
||||||
|
|
||||||
* [TU Delft helps develop digital ID for use on your phone](https://www.tudelft.nl/en/2018/tu-delft/tu-delft-helps-develop-digital-id-for-use-on-your-phone/)
|
|
||||||
* [Deployment of a Blockchain-Based Self-Sovereign Identity - Delft](https://arxiv.org/pdf/1806.01926.pdf)
|
|
||||||
* [TrustChain: A Sybil-resistant scalable blockchain - Presentation](http://msn.iecs.fcu.edu.tw/report/download.php?)
|
|
||||||
* [Dutch Blockchain Coalition](https://www.dutchdigitaldelta.nl/en/blockchain) [[**ϟ**](https://dutchdigitaldelta.nl/uploads/pdf/Dutch-Blockchain-Coalition-action-agenda-ENG.pdf)]
|
|
||||||
|
|
||||||
## Spain [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/JKDcTOK.png)
|
|
||||||
|
|
||||||
* [Alastria](https://alastria.io/) [[**G**](https://github.com/alastria/alastria-identity)]
|
|
||||||
* a non-profit consortium building a national blockchain ecosystem for Spain. The security and veracity of information will be ensured through the identification of natural and legal persons, while at the same time allowing citizens to have control over their personal information in a transparent way following the guidelines set by the European Union.
|
|
||||||
|
|
||||||
## Switzerland [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/yuP8j7V.png)
|
|
||||||
|
|
||||||
* [Zug ID: Exploring the First Publicly Verified Blockchain Identity](https://medium.com/uport/zug-id-exploring-the-first-publicly-verified-blockchain-identity-38bd0ee3702) (uport\ethereum)
|
|
||||||
|
|
||||||
## USA [**^**](#contents)
|
|
||||||
![](https://i.imgur.com/5TAfj82.png)
|
|
||||||
|
|
||||||
* [Illinois Blockchain Initiative](https://illinoisblockchain.tech/) — [partners with Evernym to launch birth registration pilot](https://illinoisblockchain.tech/illinois-partners-with-evernym-to-launch-birth-registration-pilot-f2668664f67c)
|
|
||||||
* [U.S. Department of Homeland Security funds four Blockchains](https://bravenewcoin.com/insights/u-s-department-of-homeland-security-funds-four-blockchain-companies-developing-new-cyber-security-technology)
|
|
131
docs/xdi.md
131
docs/xdi.md
@ -1,131 +0,0 @@
|
|||||||
# XDI
|
|
||||||
|
|
||||||
The XNS Public Trust Organization was founded in July 2000, shortly after International Planetwork Conference. -[xdi.org - History](http://xdi.org/?page_id=13)
|
|
||||||
> to promote the concept of individuals owning their own digital identity and data based on a nascent technology being produced by two Technical Committees at OASIS: XRI (Extensible Resource Identifier) and XDI (Extensible Data Interchange).
|
|
||||||
|
|
||||||
* [xdi.org](http://xdi.org/) is a non-profit public trust organization whose purpose is to provide public infrastructure for digital identity, security, and privacy using the open standard XDI semantic data interchange protocol developed by the OASIS XDI Technical Committee.
|
|
||||||
|
|
||||||
## Contents
|
|
||||||
|
|
||||||
* [Project Danube](#project-danube-)
|
|
||||||
* [Project Danube Github Repos](#project-danube-github-repos-)
|
|
||||||
* [XDI Libraries](#xdi-libraries-)
|
|
||||||
* [XDI - Various Integrations](#xdi---various-integrations-)
|
|
||||||
* [XDI Configurations](#xdi-configurations-)
|
|
||||||
* [XDI Examples](#xdi-examples-)
|
|
||||||
* [XDI Plugins](#xdi-plugins-)
|
|
||||||
* [Aeternam](#aeternam-)
|
|
||||||
* [XDI Cloud](#xdi-cloud-)
|
|
||||||
* [XDI Server Deployed Via](#xdi-server-deployed-via-)
|
|
||||||
* [Services](#services-)
|
|
||||||
|
|
||||||
## RWoT Papers
|
|
||||||
|
|
||||||
* [Cool hack with XDI graphs, blockstore, link contracts, and cryptographic identifiers](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/cool-hack-xdi-blockstore-bip32.md)
|
|
||||||
- Markus Sabadello *[@Peacekeeper](https://twitter.com/Peacekeeper) \<markus@projectdanube.org\>*
|
|
||||||
* [XDI Link Contracts: An Overview](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/xdi-link-contracts.md)
|
|
||||||
- Drummond Reed *[@DrummondReed](https://twitter.com/DrummondReed) \<drummond@respect.network\>*
|
|
||||||
* [XDI Graphs in IPFS](/topics-and-advance-readings/XDI-Graphs-in-IPFS.md)
|
|
||||||
- Markus Sabadello
|
|
||||||
* [XDI Verifiable Claims and Link Contracts](https://github.com/WebOfTrustInfo/rwot4-paris/tree/master/topics-and-advance-readings/xdi-verifiable-claims-link-contracts.md) by Markus Sabadello
|
|
||||||
* [First XDI Link Contract between "btcr" DID and "sov" DID](https://github.com/WebOfTrustInfo/rwot5-boston/tree/master/topics-and-advance-readings/first-xdi-link-contract-between-btcr-did-and-sov-did.md) by Markus Sabadello
|
|
||||||
|
|
||||||
|
|
||||||
## Project Danube [**^**](#contents)
|
|
||||||
|
|
||||||
Markus Sabadello began working on Project Danube [around 2010](https://web.archive.org/web/20101221105543/http://projectdanube.org/)
|
|
||||||
|
|
||||||
>This is an open-source project offering software for identity and personal data services on the Internet. The core of this project is an XDI-based Personal Data Store - a semantic database for your personal data, which always remains under your control. Applications on top of this database include the Federated Social Web, the selective sharing of personal data with organizations, and much more.
|
|
||||||
|
|
||||||
## Project Danube Github Repos [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2" target="_blank">/projectdanube/xdi2</a> - XDI2 general purpose library and server
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-js" target="_blank">/projectdanube/xdi-js</a> - XDI client library for JavaScript
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-core" target="_blank">/projectdanube/xdi2-connect-core</a> - Shared library for the XDI Connect protocol
|
|
||||||
* <a href="https://github.com/projectdanube/indy-sdk-java" target="_blank">/projectdanube/indy-sdk-java</a> - Java binding to the native Indy SDK
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-tutorial" target="_blank">/projectdanube/xdi-tutorial</a> - XDI Tutorial
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-swing" target="_blank">/projectdanube/XDINinja-swing</a> - XDI-enabled standalone client application
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tools" target="_blank">/projectdanube/xdi2-tools</a> - XDI2 maintenance and other tools
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-docker" target="_blank">/projectdanube/xdi2-docker</a> - Dockerfiles for XDI2
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-buttonbuilder" target="_blank">/projectdanube/xdi2-connect-buttonbuilder</a> - "Button Builder" component for the XDI Connect protocol
|
|
||||||
|
|
||||||
### XDI - Various Integrations [**^**](#contents-)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-bdb" target="_blank">/projectdanube/xdi2-bdb</a> - Support for using BDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-mongodb" target="_blank">/projectdanube/xdi2-mongodb</a> - Support for using MongoDB as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-heroku" target="_blank">/projectdanube/xdi2-server-heroku</a> - XDI2 Server deployed via Heroku
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-redis" target="_blank">/projectdanube/xdi2-redis</a> - Support for using Redis as XDI2 backend storage
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-tor" target="_blank">/projectdanube/xdi2-tor</a> - Integration of XDI and Tor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-ipfs" target="_blank">/projectdanube/xdi2-ipfs</a> - Integration of XDI and IPFS
|
|
||||||
* <a href="https://github.com/projectdanube/withsqlite" target="_blank">/projectdanube/withsqlite</a> - A module for a python dict that back ends on an sqlite3 database. It's bit like shelve but with json and sqlite3.
|
|
||||||
- Forked from jvasile/withsqlite
|
|
||||||
* <a href="https://github.com/projectdanube/blockstack-cli-java" target="_blank">/projectdanube/blockstack-cli-java</a> - Java client for Blockstore
|
|
||||||
|
|
||||||
### XDI Configuration [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-selfhosted" target="_blank">/projectdanube/xdi2-selfhosted</a> - A configuration profile of the XDI2 server for self-hosting a single XDI graph.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-csp" target="_blank">/projectdanube/xdi2-csp</a> - A configuration profile of the XDI2 server for hosting a dynamic number of XDI graphs.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-registry" target="_blank">/projectdanube/xdi2-registry</a> -
|
|
||||||
A configuration profile of the XDI2 server for hosting a registry of XDI names and XDI numbers.
|
|
||||||
|
|
||||||
### XDI Examples [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-messaging" target="_blank">/projectdanube/xdi2-example-messaging</a> - XDI2 Examples: Basic messaging functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-advanced-server" target="_blank">/projectdanube/xdi2-example-advanced-server</a> - XDI2 Examples: Setting up advanced XDI servers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-core" target="_blank">/projectdanube/xdi2-example-core</a> - XDI2 Examples: Simple uses of the core functionality.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-client" target="_blank">/projectdanube/xdi2-example-client</a> - XDI2 Examples: Writing XDI client applications.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-server" target="_blank">/projectdanube/xdi2-example-secp256k1-server</a> - Example XDI server using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-server" target="_blank">/projectdanube/xdi2-example-ec25519-server</a> - Example XDI server using cid-1 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-acmenews" target="_blank">/projectdanube/xdi2-connect-acmenews</a> - +acmenews XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-leshop" target="_blank">/projectdanube/xdi2-connect-leshop</a> - +leshop XDI2 demo
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-secp256k1-client" target="_blank">/projectdanube/xdi2-example-secp256k1-client</a> - Example XDI client using cid-2 cryptographic XDI numbers.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-example-ec25519-client" target="_blank">/projectdanube/xdi2-example-ec25519-client</a> - Example XDI client using cid-1 cryptographic XDI numbers.
|
|
||||||
|
|
||||||
### XDI Plugins [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-secp256k1" target="_blank">/projectdanube/xdi2-crypto-secp256k1</a> - This is an secp256k1 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-crypto-ec25519" target="_blank">/projectdanube/xdi2-crypto-ec25519</a> - This is an Ed25519 crypto plugin for the XDI2 client and server.
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-facebook" target="_blank">/projectdanube/xdi2-connector-facebook</a> - A connector plugin for the XDI2 server that maps data from Facebook to XDI
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-meeco" target="_blank">/projectdanube/xdi2-connector-meeco</a> - A connector plugin for Meeco
|
|
||||||
* <a href="https://github.com/projectdanube/XDINinja-plugin" target="_blank">/projectdanube/XDINinja-plugin</a> - A browser plugin that is like "Twitter for data"
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-cozy" target="_blank">/projectdanube/xdi2-connector-cozy</a> - A connector plugin for CozyCloud
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-filesys" target="_blank">/projectdanube/xdi2-filesys</a> - Plugin for an XDI2 server to integrate with a local filesystem
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connector-personal" target="_blank">/projectdanube/xdi2-connector-personal</a> - A connector plugin for the XDI2 server that maps data from Personal.com to XDI
|
|
||||||
|
|
||||||
### Aeternam [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-sncf" target="_blank">/projectdanube/aeternam-xdi-sncf</a> - Aeternam PNR Demo: SNCF
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-db" target="_blank">/projectdanube/aeternam-xdi-db</a> - Aeternam PNR Demo: Deutsche Bahn
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-tests" target="_blank">/projectdanube/aeternam-xdi-tests</a> - XDI experimentation for ÆTERNAM / ÆVATAR
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-maria" target="_blank">/projectdanube/aeternam-xdi-maria</a> - Aeternam PNR Demo: Maria
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-webshop" target="_blank">/projectdanube/aeternam-xdi-webshop</a> - Aeternam PNR Demo: Webshop
|
|
||||||
* <a href="https://github.com/projectdanube/aeternam-xdi-oebb" target="_blank">/projectdanube/aeternam-xdi-oebb</a> - Aeternam PNR Demo: ÖBB
|
|
||||||
|
|
||||||
### XDI Cloud [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-cloudcards" target="_blank">/projectdanube/xdi2-cloudcards</a> - XDI Cloud Card Viewer
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-messenger" target="_blank">/projectdanube/xdi2-messenger</a> - XDI Cloud Messenger
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-manager" target="_blank">/projectdanube/xdi2-manager</a> - XDI Cloud Manager
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-pixel" target="_blank">/projectdanube/xdi2-pixel</a> - Tool to translate a personal cloud policy language (Pixel) to XDI link contracts.
|
|
||||||
|
|
||||||
### XDI Server Deployed Via [**^**](#contents)
|
|
||||||
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-grizzly" target="_blank">/projectdanube/xdi2-server-grizzly</a> - XDI2 Server deployed via Grizzly
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-mina" target="_blank">/projectdanube/xdi2-server-mina</a> - XDI2 Server deployed via Apache MINA
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-netty" target="_blank">/projectdanube/xdi2-server-netty</a> - XDI2 Server deployed via netty
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-undertow" target="_blank">/projectdanube/xdi2-server-undertow</a> - XDI2 Server deployed via Undertow
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-server-vertx" target="_blank">/projectdanube/xdi2-server-vertx</a> - XDI2 Server deployed via vert.x
|
|
||||||
|
|
||||||
### Sevices [**^**](#contents)
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service" target="_blank">/projectdanube/xdi2-connect-service</a> - This is a "Connect Service" component for the XDI Browser binding.
|
|
||||||
* <a href="https://github.com/projectdanube/neustar-discovery-service" target="_blank">/projectdanube/neustar-discovery-service</a> - Neustar XDI Discovery Service based on XRI Resolution
|
|
||||||
- Forked from neustarpc/neustar-discovery-service
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service-war" target="_blank">/projectdanube/xdi2-connect-auth-service-war</a> - "Authorization Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-service-war" target="_blank">/projectdanube/xdi2-connect-service-war</a> - "Connect Service" for the XDI Connect protocol, packaged as .WAR file
|
|
||||||
* <a href="https://github.com/projectdanube/xdi-grapheditor" target="_blank">/projectdanube/xdi-grapheditor</a> - An XDI Graph Editor
|
|
||||||
-Forked from neustar/xdi-grapheditor
|
|
||||||
* <a href="https://github.com/projectdanube/xdi2-connect-auth-service" target="_blank">/projectdanube/xdi2-connect-auth-service</a> - This is a "Connect Auth Service" component for the XDI Browser binding.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user