Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2025-12-15 16:39:25 -05:00
Code Issues Projects Releases Packages Wiki Activity

reorganize + new categories

Browse source
This commit is contained in:
⧉ infominer 2023-06-24 03:03:04 +05:30
parent 654be069ac
commit 5277911d7d
32 changed files with 312 additions and 277 deletions
Download patch file Download diff file Expand all files Collapse all files

132
_posts/web3/2019-03-28-uport.md Normal file
View file

@ -0,0 +1,132 @@
---
date: 2019-03-28
title: uPort
description: A self-sovereign identity and user-centric data platform
layout: single
excerpt: "In your application, you must first configure your uPort object with an identifier and a private key (or signer function). There are several ways to instantiate a credentials object. The most common approach is to save a DID and private key on a server for your application and create a credentials instance from your application's unique private key. Signed JWTs for requests and verifications can then be passed to a client-side application, and presented to a user using a QR code or via another transport."
header:
image: /images/uport.webp
caption: "[Releasing uPort Libraries 1.0](https://medium.com/uport/releasing-uport-developer-platform-1-0-97d6f70c5e4a)"
teaser: /images/uport-teaser.webp
categories: ["Web 3"]
tags: ["Ethereum","Credentials Community Group","GDPR","DID","DIDComm","Consensys","Verifiable Credentials","uPort","Web3","Zug","GLEIF","PWC","Onfido","DIF","uPortlandia","Switzerland"]
redirect_from:
- id-initiatives/ethereum/uport
- blockchain/ethereum/uPort
- id-initiatives/ethereum/uPort/
permalink: /blockchain/ethereum/uPort/
canonical_url: 'https://decentralized-id.com/blockchain/ethereum/uPort/'
last_modified_at: 2020-11-30
---
* [uPort: Self-Sovereign Identity Meets Portable Data](https://www.youtube.com/watch?v=hBIragrwqYc)
**[uPort](https://www.uport.me/) • [GitHub](https://github.com/uport-project) • [Twitter](https://twitter.com/uport_me) • [Developers](https://developer.uport.me/) • [iPhone](https://apps.apple.com/us/app/uport-id/id1123434510) • [Android](https://play.google.com/store/apps/details?id=com.uportMobile&hl=en)**
![](https://i.imgur.com/sPAP2g3.png)
* [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)
![](https://i.imgur.com/ASI0PaB.png)
* [uPort donates code to the Decentralized Identity Foundation](https://medium.com/decentralized-identity/uport-donates-code-to-the-decentralized-identity-foundation-349d4740acbd)
- [decentralized-identity/did-jwt-vc](https://github.com/decentralized-identity/did-jwt-vc) - Create and verify W3C Verifiable Credentials and Presentations in JWT format
* [Trusted P2P Messaging with DIDs, DIDComm and VCs](https://medium.com/uport/trusted-p2p-messaging-with-dids-didcomm-and-vcs-398f4c3f3cda) (h/t @by_caballero)
> By resolving a DID a validator can typically discover the authoritative keys for different purposes or more generally, a set of verification methods for that DID. An Ethereum account could be a verification method as well. Service endpoints are extensible by design, so you could define your own ones if needed. However, the DID community has agreed on a set of well known service endpoints. Amongst them, the DIDComm service endpoint solves the how-to-reach-me problem and can be used to establish a secure communication channel with the other party. Despite there are only a few limitations of what properties can be associated with a DID, privacy regulations such as GDPR need to be considered very carefully.
* [GLEIF and uPort Test Verified Data Exchange in Financial Transactions](https://consensys.net/blog/press-release/gleif-uport-test-verified-data-exchange-in-financial-and-commercial-transactions/)
> Switzerland & Paris — The Global Legal Entity Identifier Foundation ([GLEIF](https://www.gleif.org/en/)) and uPort​, ConsenSys’ digital identity platform anchored on the Ethereum blockchain, have partnered to support the process of exchanging verified data used in financial, commercial, and regulatory transactions. GLEIF is the G20-backed non-profit foundation tasked with promoting the use of legal entity identifiers (LEIs) as the global standard to unambiguously identify parties doing business. Together with uPort, GLEIF is testing how businesses can leverage the Ethereum-backed identity system to increase the efficiency of verifying business identities and persons acting on its behalf within the LEI ecosystem.
* [PWC and Onfido Join uPort's Portable Identity Effort in UK Finserv](https://consensys.net/blog/press-release/pwc-and-onfido-to-join-uports-portable-identify-efforts-in-uk/)
> uPort and Onfido have a shared vision of enabling consumers with access and control over their own data. Earlier this year, both companies applied to and were accepted to the UK’s Financial Conduct Authority Regulatory Sandbox (​Cohort 5​) to test how decentralised identity can enable fintech ecosystems in the UK. PWC’s UK team, believing that such technology can be a key factor to promote more open financial ecosystems, is partnering with them in this pilot. In joining forces, the teams are committed to building a world where users have control over managing their personal data, and where decentralised identity reintroduces trust and privacy into transactions between parties.
* [Welcome to uPortlandia, the Future of Data and Identity Management](https://media.consensys.net/welcome-to-uportlandia-the-future-of-data-and-identity-management-53220ea4e5c)
> [uPortlandia](https://uportlandia.uport.me/) is uPort’s vision of the future of data and identity management. A future of password-free online experiences. A future where you can prove who you are or verify facts about your life while sharing far less personal information. A future where we, the people, we as individuals, control our digital identities. Without being beholden to the Facebooks, Experians, or Googles of the world.
## Zug ID
* [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/)]
> **City of Zug (UPort and ti&m)**
>
> As a first pilot project in Switzerland, the city of Zug is currently piloting a SSI solution. The local administration is cooperating with the IT consulting company ti&m, as well as UPort to provide a basic infrastructure for their citizens to attest their identity. With the SSI implemented in Zug, users can now pay their parking fees, register for elections or perform online sign on for e-government services33. The benefits range for the city of Zug are low infrastructure requirements, decreased security risks, cost effectiveness, GDPR compliance and scalability.
* [Zug ID: Exploring the First Publicly Verified Blockchain Identity](https://medium.com/uport/zug-id-exploring-the-first-publicly-verified-blockchain-identity-38bd0ee3702)
> We recently announced our cooperation with the Swiss City of Zug and local development partner ti&m to introduce the world’s first live implementation of a self-sovereign government issued identity on Ethereum. Thus far, more than 50 citizens in Zug have successfully verified their uPort identity in person with the City, enabling them to access a new suite of e-government services in a trusted and self-reliant manner. With all the excitement around this launch, we wanted to outline for all of you the underlying mechanics of the Zug identity verification system, the benefits this provides for various stakeholders, as well as future use cases and its evolution.
## Literature
* [A First Look at Identity Management Schemes on the Blockchain](https://arxiv.org/pdf/1801.03294.pdf) IEEE 2018
> A uPort identity is underpinned by the interactions between Ethereum smart contracts: bespoke code that can regulate the movement of data and ether (the native cryptocur- rency) on Ethereum. Smart contracts are uniquely addressed by 160-bit hexadecimal identifiers, and, when invoked are executed by the Ethereum Virtual Machine (EVM) installed on every Ethereum node. Two smart contract templates designed by uPort comprise each uPort identity: controller and proxy. To create a new identity, a user’s uPort mobile application creates a new asymmetric key pair and sends a transaction to Ethereum that creates an instantiation of a controller that contains a reference to the newly created public key. Then, a new proxy is created that contains a reference to the address of the just-created controller contract; only the controller contract can invoke functions of the proxy; a constraint that is specified in the controller and enforced by the EVM. The address of the proxy comprises the unique uPort identifier (uPortID) of a user. A user is free to create multiple uPortIDs that are unlinkable. Figure 1 provides an overview of an interaction between a uPortID and the smart contract of a decentralised application on Ethereum.
>
> The private key that controls a uPortID is stored only on the user’s mobile device. Therefore, an important aspect of uPort relates to its social recovery protocol for the event of loss or theft of the user’s mobile device. For that, users must nominate the uPortIDs of trustees who can vote to replace the public key referenced in the controller with one proposed by the user in need; once a quorum is reached between those trustees on the new public key, the controller replaces the lost public key with the newly pro- posed public key. This process enables the user to maintain a persistent uPortID even after the loss of cryptographic keys.
>
> A final aspect of the uPort scheme is its support for securely mapping identity attrib- utes to a particular uPortID. The uPort registry is a smart contract that stores the global mapping of uPortIDs to identity attributes. Any entity can query the registry, however, only the owner of a specific uPortID can modify its respective attributes. Due to the inefficiency of storing large volumes of data in a smart contract, only the hash of the JSON attribute structure is stored in the registry. The data itself is stored on IPFS: a distributed file system where a file can be retrieved by its cryptographic hash.
## [developer.uport.me](https://developer.uport.me/)
**Build User-Centric Ethereum Apps**
* [overview/index#u-port-protocols-and-libraries](https://developer.uport.me/overview/index#u-port-protocols-and-libraries)
> * [uPort transports](https://developer.uport.me/transports/index)
> * [uPort Signed Messages](https://developer.uport.me/messages/index)
> * [JWT RFC 7519](https://tools.ietf.org/html/rfc7519) did-jwt
> * [Decentralized Identifiers (DIDs)](https://w3c-ccg.github.io/did-spec/) did-resolver
> * Public Key Lookup [ERC-1056 Lightweight Ethereum](https://github.com/ethereum/EIPs/issues/1056) Identity ethr-did-resolver
> * Creation/Management [Ethereum DID Registry Contract](https://github.com/uport-project/ethr-did-registry) ethr-did
> * [Ethereum JSON-RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC) Web3 or EthJS
> * [Ethereum.org](https://ethereum.org/)
* [Connect Users to Your web3 dApp](https://developer.uport.me/guides/gettingstarted)
>Add full support for uPort by adding a single line of code to your web3 dApp.
>
> * Onboard new users within minutes
> * Instantly create a privacy-preserving Ethereum account
> * Build for both desktop and mobile browsers
* [Issue & Request Verified Credentials](https://developer.uport.me/uport-credentials/index)
>Help your users build their digital identity by issuing Verified Credentials about them or the things they do in your app.
>
> * Request Ethereum transaction signing with web3
> * Issue and Request Verified Credentials about your users
* [uport-credentials/docs/guides - Getting Started with uPort Credentials](https://github.com/uport-project/uport-credentials/blob/develop/docs/guides/index.md)
* [Transactions](https://developer.uport.me/credentials/transactions)
>It is possible with uport-credentials to create an ethereum transaction request and have a mobile client approve and sign that transaction.
![](https://imgur.com/JU7gOEn.png)
* [uport-connect/guides/usage](https://developer.uport.me/uport-connect/guides/usage)
>The uPort Connect library is a client-side library that allows you to interact with a user's uPort identity through a uPort client, primarily the uPort mobile app. The Connect library bundles functionality from our other libraries into a singular, easy to use interface.
>
>This guide describes the parts which make-up Connect and provides further details on how to configure it for your specific use case. While Connect is likely the best solution for most use cases, you may decide you need greater optionality and control over certain use cases, in that situation, you may be interested in using uport-tranports and uport-credentials as an alternative.
* [RequestVerification](https://developer.uport.me/connect/requestverification)
>Much like logging in, using uport-connect to request verified data about uPort mobile clients is simple. So simple we will follow the same steps of logging in, but this time pass an array of verification titles that we want to request for disclosure. Our connect library manages the flow for you with minimal configuration.
![](https://imgur.com/4OQ5C1E.png)
* [SendVerification](https://developer.uport.me/connect/sendverification)
>Much like logging in, using uport-connect to create and send verifications to uPort mobile clients is simple. Our connect library will manage much of the flow for you with minimal configuration.
![](https://imgur.com/W1ppGwb.png)
* [Goodbye uPort DIDs, Hello Ethr-DIDs](https://medium.com/uport/goodbye-uport-dids-hello-ethr-dids-ea2e80256f54)
> Using the [Ethr-DID](https://developer.uport.me/categories/ethr-did/) library, you can:\
>* Create and manage keys for DID identities
>* Sign JSON Web Tokens
>* Authorize third parties to sign on a DID's behalf
>* Enable discovery of service endpoints (e.g. decentralized identity management services)
>
>The Ethr-DID library conforms to ERC-1056 and supports the proposed Decentralized Identifiers spec from the W3C Credentials Community Group. These allow for Ethereum addresses to be used as fully self-managed Decentralized Identifiers (DIDs), as a result, you can easily create and manage keys for these identities. This library also allows you to sign standard compliant JSON Web Tokens (JWTs) that can be consumed using the DID-JWT library.
* [uPort Credentials](https://developer.uport.me/categories/uport-credentials/) library allows you to:
>* Create and verify authentication requests
>* Request verified claims
>* Verify claims for your users
>* Ask users to sign Ethereum transactions
>* Create Ethereum smartcontract function call requests without web 3.0
* [Ethereum DID Registry](https://developer.uport.me/categories/ethr-did-registry/)
>This contract allows on-chain and off-chain resolving and management for DIDs (Decentralized Identifiers).
>
>A DID is an Identifier that allows you to lookup a DID document that can be used to authenticate you and messages created by you.
>
>It's designed for resolving public keys for off-chain authentication—where the public key resolution is handled by using decentralized technology.
>
>This contract allows Ethereum addresses to present signing information about themselves with no prior registration. It allows them to perform key rotation and specify different keys and services that are used on its behalf for both on and off-chain usage.
* [uPort Transports](https://developer.uport.me/categories/uport-transports/) allows you to:
> * Send messages to users using a QR code
> * Send requests and receive responses through URLs
> * Send encrypted push notifications
> * Create Transports specific to your use case and environment

61
_posts/web3/2020-11-05-3box.md Normal file
View file

@ -0,0 +1,61 @@
---
date: 2020-11-05
title : "3box"
description : 3Box makes it simple to store data securely with your users, letting you focus on building great products.
excerpt : "Ethereum Profiles makes it simple for users to create a reusable profile for their Ethereum address which can easily be shared with dapps to simplify the onboarding experience and create a more frictionless, social web3 dapp ecosystem. Ethereum Profiles allows Ethereum users to collect and control their information on the distributed web using their existing Ethereum wallets."
header:
image: /images/3box_header.webp
teaser: /images/3box-teaser.webp
layout: single
author_profile: false
permalink: /blockchain/3box/
canonical_url: 'https://decentralized-id.com/blockchain/3box/'
categories: ["Web 3"]
tags: ["Ethereum","DIF","Web3","3box","uPort","Verifiable Credentials","IPID"]
last_modified_at: 2020-11-05
toc: false
---
[3box.io](https://3box.io/) • [Blog](https://medium.com/3box) • [GitHub](https://github.com/3box) • [twitter](https://twitter.com/3boxdb) • [discord](https://discord.gg/Z3f3Cxy)
- [Announcing Ethereum Profiles 1.0.0 is Live](https://medium.com/3box/announcing-ethereum-profiles-1-0-0-is-live-f0316e15ce23) - How to get started using 3Box profiles today 😄
> Ethereum Profiles makes it simple for users to create a reusable profile for their Ethereum address which can easily be shared with dapps to simplify the onboarding experience and create a more frictionless, social web3 dapp ecosystem. Ethereum Profiles allows Ethereum users to collect and control their information on the distributed web using their existing Ethereum wallets.
- [Announcing 3Box.js 1.1.0 — API Boost](https://medium.com/3box/https-medium-com-3box-announcing-3box-js-1-1-0-api-boost-1339c8fa4cb8)
> We’re excited to announce the release of 3box-js 1.1.0 which includes new features such as local and network caching and a GraphQL endpoint. Together these features work to improve performance and stability by reducing the average log-in time for users, reducing API response times for getProfile, and allowing developers to be much more efficient in writing their public profile queries.
- [Announcing, 3Box Partnership with Ethstats](https://medium.com/3box/announcing-3box-partnership-with-ethstats-d9c65f582e50)
- [Shareable Public Profiles](https://medium.com/3box/shareable-public-profiles-94387c0d641e)
> Previously user profiles were only viewable to the profile owner when logged-in to 3box.io on a web3-enabled browser, and to third-party apps using the getProfile() API method and rendering details in their app’s UI. Now with the addition of shareable profiles, anyone can view your public profile by clicking your profile URL.
- [A More Human Web3 Activity Feed](https://medium.com/3box/a-more-human-web3-activity-feed-2d3b8f62afec)
> The new and improved 3Box activity feed integrates a user’s activity from across various networks that make up web3 today, including public Ethereum networks and the 3Box data network, into a single coherent view.
- [Launching, 3Box Email Verification Service](https://medium.com/3box/launching-3box-email-verification-service-fc729981ec32)
> In addition to making onboarding more convenient and seamless, verified email addresses also respect user privacy. Emails are saved to a user’s private 3Box profile, giving the user full control of their contact information. Verified emails are only shared with applications that the user explicitly approves.
- [Introducing, 3Box Collectibles GalleryBrowse your digital collectibles, curate your favorites, and](https://medium.com/3box/introducing-3box-collectibles-gallery-4414f2a50551)
> Browse your entire collectibles gallery alongside the rest of your web3 profile and curate a few favorites for others to see. We believe that collectibles represent an important piece of a user’s aggregate web3 identity, reputation, and personality, and we’re proud to now offer them in 3Box profiles.
- [3Box Decentralized Comments API 💬](https://medium.com/3box/3box-decentralized-comments-api-7e495d2ddd24)
> We’re excited to announce that today we’re releasing the first version of our decentralized messaging API: [Open Threads](https://github.com/3box/3box-js#using-threads). Threads allow any number of users to openly send and receive messages in sequence. Thread data is stored on the 3Box network with the users themselves instead of on your server or the blockchain.
- [3Box Builders Series: How to Integrate with Profiles](https://medium.com/3box/3box-builders-series-how-to-integrate-with-profiles-34078af41c47)
> The Builders Series is a collection of blog posts aimed at helping developers easily build better distributed apps using the 3Box suite of APIs. This article is the first in the series, and contains everything you need to start adding profiles to your app today. For more information on Profiles, view our Github documentation.
- [Smarter authentication on 3Box Hub](https://medium.com/3box/smarter-authentication-on-3box-hub-dad11389de2) - Log in with a variety of wallets using web3connect
- [3Box Followers: Your Open Social Graph](https://medium.com/3box/3box-followers-your-open-social-graph-1f5e42c50afd) - Discover and follow Ethereum users. Build trust together.
- [How FOAM uses 3Box threads to create a location-based review system](https://medium.com/3box/how-foam-uses-3box-threads-to-create-a-location-based-review-system-15ca1024e73)**
- [Introducing, 3Box Chatbox Plugin](https://medium.com/3box/introducing-3box-chatbox-plugin-698f4433b9a9) - Drop-in chatrooms for your decentralized app
- [3Box Hub Search](https://medium.com/3box/3box-hub-search-6ba9ec0e672) - Discover users on 3Box with their ETH address
- [Introducing, 3Box Wall](https://medium.com/3box/introducing-3box-wall-7c299f4e0a1d) - Ready, set, socialize...Decentralized comments on 3Box Profiles
- [3Box Edit Profile Plugin](https://medium.com/3box/3box-edit-profile-plugin-8502509a4ff4) - Drop-in component for React applications
- [Building a Distributed AppStore with 3Box](https://medium.com/3box/building-a-distributed-appstore-with-3box-ef7345aab34e) - How to build an app with 3Box SDK and Plugins
- [3Box messaging plugins get more social!](https://medium.com/3box/3box-messaging-plugins-get-more-social-354e2afe88cb) - Message Likes, Reactions, Replies, and Votes
- [3Box Hub now supports ENS](https://medium.com/3box/3box-hub-now-supports-ens-af4a8efbd36e) - View ENS names inside Hub using ENS SDK and The Graph
## Ceramic
* [Introduction to the Ceramic Protocol](https://medium.com/ceramic/introduction-to-the-ceramic-protocol-8d56951ae3f)
> For self-sovereign identity and to enable user-managed access control, 3Box uses Ceramic’s 3ID DID method which allows users to control their identity, information, and services using all of their existing private wallet keys.
* [Identity-centric interoperability with the Ceramic Protocol – Joel Thorstensson – Webinar 57](https://ssimeetup.org/identity-centric-interoperability-ceramic-protocol-joel-thorstensson-webinar-57/)
> Ceramic is a new permissionless protocol for creating and accessing unstoppable documents that serve as the foundation for a connected, interoperable web without silos. Joel Thorstensson is the founder and CTO of 3Box and the primary author of the ceramic protocol as well as several Ethereum standards for identity and will provide a conceptual and technical intro to Ceramic.\
> [...]\
> Ceramic uses DIDs (Decentralized Identifiers), IPLD (InterPlanetary Linked Data), signed messages, and blockchain anchoring to create a trusted and shared graph of verifiable documents. While flexible, these documents are especially well-suited for self-sovereign identity systems, user-centric data ecosystems, and open web services.\
* [Technical Specification](https://github.com/ceramicnetwork/ceramic/blob/master/SPECIFICATION.md)
> Ceramic is a decentralized protocol that enables the creation of mutable, tamper-resistant, smart documents on a worldwide public network. Smart documents are achieved through a combination of digital signatures, document update rules, and blockchain anchoring. A Ceramic document is a flexible data structure that can be used to represent a wide variety of things such as self-sovereign identities, specific pieces of data or content, media files, schemas, policies for data access control, verifiable credentials, agreements between multiple parties, etc. The protocol doesn’t rely on any particular blockchain system, instead it utilizes [IPLD](https://ipld.io/) to encode document changes into a hash linked data structure, called a Merkle DAG (Directed Acyclic Graph), and anchors those updates into a blockchain which provides strict ordering to the content of a given document. As a result, Ceramic can be conceptualized as network of individual "doc-chains." Verifying the state of a particular document only requires a user to sync the data of the given document, and the user does not need to sync the state of the entire network as is the case with all blockchain networks that maintain a global state (i.e. Bitcoin, Ethereum). A node in the Ceramic network can thus choose to only pin the documents it cares about. This means that there is no global ledger of documents.

72
_posts/web3/2020-11-30-consensys.md Normal file
View file

@ -0,0 +1,72 @@
---
date: 2020-11-30
title: Consensys
description: Building Ethereum blockchain infrastructure and applications for new economic systems that are more open, efficient, and secure.
excerpt: >
ConsenSys is the leading Ethereum software company. We enable developers, enterprises, and people worldwide to build next-generation applications, launch modern financial infrastructure, and access the decentralized web. Our product suite, composed of Infura, Quorum, Codefi, MetaMask, and Diligence, serves millions of users, supports billions of blockchain-based queries for our clients, and has handled billions of dollars in digital assets. Ethereum is the largest programmable blockchain in the world, leading in business adoption, developer community, and DeFi activity. On this trusted, open source foundation, we are building the digital economy of tomorrow.
header:
image: /images/consensys-header.webp
teaser: /images/consensys-teaser.webp
categories: ["Web 3"]
tags: ["Ethereum","Web3","Consensys","Zug","uPort","DIF","uPortlandia","RWoT"]
permalink: blockchain/ethereum/consensys/
canonical_url: https://decentralized-id.com/blockchain/ethereum/consensys/
last_modified_at: 2020-11-30
---
**[ConsenSys](https://consensys.net/) • [Discord](https://discord.gg/hYpHRjK) • [Twitter](https://twitter.com/ConsenSys) • [Youtube](https://www.youtube.com/channel/UCBeLEwM-yhIKuIxHTx0VzdQ) • [Blog](https://media.consensys.net/) • [GitHub](https://github.com/ConsenSys)**
> ConsenSys is the leading Ethereum software company. We enable developers, enterprises, and people worldwide to build next-generation applications, launch modern financial infrastructure, and access the decentralized web. Our product suite, composed of [Infura](https://infura.io/), [Quorum](https://consensys.net/quorum/), [Codefi](https://codefi.consensys.net/), [MetaMask](https://metamask.io/), and [Diligence](https://consensys.net/diligence/), serves millions of users, supports billions of blockchain-based queries for our clients, and has handled billions of dollars in digital assets. Ethereum is the largest programmable blockchain in the world, leading in business adoption, developer community, and DeFi activity. On this trusted, open source foundation, we are building the digital economy of tomorrow.
* [Blockchain in Digital Identity](https://consensys.net/blockchain-use-cases/digital-identity/#howddiworks)
> A decentralized identifier (DID) is a pseudo-anonymous identifier for a person, company, object, etc. Each DID is secured by a private key. Only the private key owner can prove that they own or control their identity. One person can have many DIDs, which limits the extent to which they can be tracked across the multiple activities in their life. For example, a person could have one DID associated with a gaming platform, and another, entirely separate DID associated with their credit reporting platform.
>
> Each DID is often associated with a series of attestations (verifiable credentials) issued by other DIDs, that attest to specific characteristics of that DID (e.g., location, age, diplomas, payslips). These credentials are cryptographically signed by their issuers, which allows DID owners to store these credentials themselves instead of relying on a single profile provider (e.g., Google, Facebook). In addition, non-attested data such as browsing histories or social media posts can also be associated to DIDs by the owner or controllers of that data depending on context and intended use.
* [Blockchain in Government and the Public Sector](https://consensys.net/blockchain-use-cases/government-and-the-public-sector/)
> * **Identity Management**: Sotara will enable government workers and citizens to register their identities on the blockchain, manage assets and security, send and request credentials, authorize transactions, and securely manage data
> * **Smart Regulation**: Sotara will allow agencies to design and create legal documents and regulations with tamper-proof blockchain-based smart contracts
> * **Asset Management and Process Tracking**: Sotara will model and facilitate government processes and increase the ability to track digital and physical assets
> * **Budgeting and Financial Management**: Sotara will track and reconcile government transactions immediately and transparently dramatically reducing costs and increasing efficiency.
* [On-Demand: Credential Management for Government and Enterprise on Blockchain](https://pages.consensys.net/credential-management-for-government-and-enterprise)
> Security and identity are complex and ever-evolving issues for enterprise and government systems alike. Blockchain-based solutions are providing exceptional utility in solving issues of identity and digital systems. This webinar—titled Credential Management for Government and Enterprise—offers a high-level overview of where identity management is today, how we got here, and how we can transition to the next stage and beyond while making sure we leverage existing architecture and infrastructure.
* [Zug Digital ID: Blockchain Case Study for Government Issued Identity](https://consensys.net/blockchain-use-cases/government-and-the-public-sector/zug/) - A pilot project testing self-sovereign identities on the Ethereum blockchain.
> Zug leveraged uPort, a decentralized identity platform to create the world’s first live implementation of a self-sovereign government-issued identity project on the Ethereum blockchain, along with the city of Zug, the Institute for Financial Services Zug (IFZ) of the Lucerne University, along with integrator TI&M for the platform and Luxoft to implement voting. In the summer of 2017, they launched a pilot program to register resident IDs on the public Ethereum blockchain. After the pilot program, Zug officially launched the program in November 2017.
## History
### 2015
* [The Identity Crsis](https://medium.com/@ConsenSys/identity-is-defined-in-merriam-s-dictionary-as-who-someone-is-a3d6a69f5fa4) (Devcon 1)
> Identity is defined in Merriam’s dictionary as “who someone is”. As the world and technology evolves one can’t help but notice the changes to the notion of who someone is and how this affects their relation to the world. We’ll focus on the problems that affect humans in regards to their identities, dividing the conversation into developed and developing economies.
* [DIGITAL IDENTITY (CONSENSYS) CHRISTIAN LUNDKVIST](https://drive.google.com/file/d/0B7_8_AY6I9pWTThWb0w1cjRmaHozaVYwTGtDcFN5aGZZcnB3/view)
> ▸ Instead of having a third-party provider for identity the user controls their own identity\
> ▸ Ethereum smart contracts can act as the central identity provider\
> ▸ User controls their private keys, but can also choose to let a third party control keys for them - best of both worlds\
* [uPort: The Wallet is the New Browser](https://media.consensys.net/uport-the-wallet-is-the-new-browser-b133a83fe73)
> ConsenSys internally released a web-based wallet and identity management system — uPort — during our first ‘persona week’ — a period of concerted discussions about wallet, identity, and persona amongst all of our developer teams. While the wallet system is still in its early stages, we have started to integrate an ID and persona construct across all of our dApps. Soon a uPort persona will enable access to any dApp ConsenSys or other developers build. ConsenSys has begun efforts to work with various partners towards standardization of these components.
* [Dealing with private key loss or compromise in digital identity systems](https://github.com/bhaskar20/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/dealing_with_key_loss_in_digital_identity.md) By Christian Lundkvist @ChrisLundkvist <christian.lundkvist@consensys.net> (RWoT 1)
> If an identity is tied to a single persistent private key, then loss or compromise of the private key will mean total loss of the identity. Since key compromise and/or loss do happen there needs to be a way to recover from this in order to have a persistent digital identity. [See here for definitions used](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/shared_terminology_for_digital_identity_systems.md).
>
> If the user of the identity suspects that a key is or may be compromised the user can rotate their key by submitting a new key to the system, signed by the old key. After this the old key can be revoked.
* [PKI Tools in EVM-based Blockchains](https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/topics-and-advance-readings/pki_tools_in_evm_blockchains.md) By Christian Lundkvist @ChrisLundkvist <christian.lundkvist@consensys.net> (RWoT 1)
> A blockchain can provide a good foundation for a PKI since it acts as a distributed well-publicized ledger whose integrity can be validated through the proof-of-work mechanism. A blockchain with a fully featured virtual machine such as Ethereum (with its Ethereum VM or EVM) or the recent Bitcoin sidechain project Rootstock (also EVM-based) provides a rich scripting language with which to build tools that can be used in a PKI.
>
> A blockchain with such a virtual machine allows the user to send transactions creating blockchain-native programs, sometimes called "smart contracts" or simply "contracts". These programs have an associated address and expose API functions which can be called by sending a transaction to the address with a data message containing the signature of the function along with its parameters. The programs are run by miners and they have associated storage and/or funds (Ether in the case of the Ethereum blockchain) which is updated upon contract execution.
### Consensus 2016
* [Identity of the Blockchain: Perils and Promise](https://www.slideshare.net/ChristopherA/identity-of-the-blockchain-perils-and-promise) - slideshare - Christopher Allen
<iframe src="//www.slideshare.net/slideshow/embed_code/key/eqDfBvDHU5COBb" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe> <div style="margin-bottom:5px"> <strong> <a href="//www.slideshare.net/ChristopherA/identity-of-the-blockchain-perils-and-promise" title="Identity of the Blockchain: Perils and Promise" target="_blank">Identity of the Blockchain: Perils and Promise</a> </strong> from <strong><a href="//www.slideshare.net/ChristopherA" target="_blank">Christopher Allen</a></strong> </div>
### Consensus 2017
* [Decentralized Identity Foundation Announces Formation At Consensus 2017](https://web.archive.org/web/20190528130425/https://www.ethnews.com/decentralized-identity-foundation-announces-formation-at-consensus-2017)
> Daniel Buchner, head of decentralized identity at Microsoft, kicked off the discussion by announcing the formation of the DIF, its unifying goals, and who it will benefit.
>
> "We know the only way to this is to join hands with these folks," said Buchner. "We all have the same intents and collaborative ideas. We want to make identity real for people, organizations and devices, and I think the thing that I'm most excited about here, is not only the commercial opportunities that opens up, but the fact that it's actually going to be good for people."
>
> Buchner was joined by ConsenSys’ uPort project lead Rouven Heck, Gem founder and CEO Micah Winkelspecht, Chief Trust Officer at Evernym Drummond Reed, Blockstack co-founder Ryan Shea, and founder and CEO at Tierion Wayne Vaughan. Dakota Gruener, executive director at ID2020 moderated the discussion.
* [Identity at Consensus 2017](https://www.linkedin.com/pulse/identity-consensus-2017-elena-litani/)
> Last week I've attended Consensus 2017 conference and would like to share some highlights. While the overarching theme at the conference continued to be cryptocurrencies (evidenced not only by the surge to all-time highs of Bitcoin and Ether, but also by the attention given to this new asset class by reputable institutional investors), self-sovereign and digital identity topics had strong presence.
>
> As blockchain fever hit financial institutions in 2013, naturally, first use cases were focused on payments and more specifically cross-border payments. Later financial services focused on paper-intense, T+3 capital markets use cases, such as pre-trade, post trade, securities servicing. Oliver Wyman and Euroclear have published a nice report outlining opportunities blockchain could bring to Capital Markets ( 'Blockchain in Capital Markets: The Prize and the Journey', 2016). As use cases expanded to other industries beyond financial industry, and banks started to focus on permissioned blockchain or distributed ledger technologies (DLT), the intersection of blockchain and digital identity became more evident. While I don't intend to cover all the aspects of digital identity, it is probably worth mentioning here that digital identity is defined as an entity's online presence, encompassing personal identifying information (PII) and ancillary information, referred to as attributes or verifiable claims.