uport-project
All you need to know about uPort Identity management

• did-jwt, for signing and verifying signatures for any DID-compliant identity;
• did-resolver, the universal resolver for Decentralized IDs;
• ethr-did-resolver, for resolving identities from Ethereum addresses via the ERC1056 specification; and of course
• The ethr-did-registry Smart Contract, which anchors it all to the blockchain.

a simple consent interface for dapps to request private data from users, and users can approve or reject this request. This interface is called Selective Disclosure Request

A mobile application that holds the user’s keys and lets him communicate with the smart contract (sign transaction). The key is held in the secure enclave of his device and accessed via local biometric authentication whenever the key is used to sign. The key remains on the device and there is no means of exporting the private key off the device.

only the uPort proxy is authorized to update the Registry contract.

Registry Contract : maintain cryptographic bindings between a uPort identity and an off-chain data structure (IPFS, etc).

Privacy-preserving user sessions. In the old days, apps stored users’ information in databases, and gave their browsers access tokens to keep them logged in between sessions. We’ve adapted that concept for Web 3.0, by storing the app identity and logged in user’s did in localStorage, as well as an optional cache of any verified data they have shared with the app.

simplifying-identity-verification-for-financial-services
reusable verifiable credentials can be used to reduce KYC-related costs. In our hypothesis, we believe by allowing users to manage their own credentials, they can get verified once and then they are able to reuse that verification across multiple financial service providers. This ultimately reduces costs and time burden of the KYC process across stakeholders.

Making the uPort Smart Contracts Smarter
-> Up Next uPort IdentityManager

uport-project/ uport-identity
uPort Contracts for managing identity DEPRECATED
-> https://developer.uport.me/ Identity Document (DEPRECATED)
-> https://developer.uport.me/ Decentralized Identity Document (DID Document)

All data management and storage meets GDPR guidelines, and we never store any personally identifiable information (PII) on the blockchain.

以太坊上的身分自主系統
uPort 是一套自主的身份系統，透過智能合約所建立的無需第三方驗證的身份系統，介紹 uPort 的系統設計，以及展示整個應用。

EtherTW/Taipei-Ethereum-Wiki
https://youtu.be/HyMC9TOGmL0

Uport-为分布式网络设计的开放式身份系统

uport-project/ethr-did-registry Ethereum registry for ERC-1056 ethr did methods

所有标准提案（ERC） ERC 主要是应用程序标准或约定，比如：ERC20 Token 标准。

ERC: Lightweight Identity #1056
ERC-1056 Ethereum Lightweight Identity 輕量級身份系統

從ERC-725到ERC-1484，去中心化身份標準「自我進化」正當時

uPort白皮书

我们特意设计了这个用户体验，用户不需要知道公钥/私钥密码学。用户的心理模式应该是他们的智能手机和uPort应用可以用来与dapps交互，登录到网站、验证交易、用他们的名字签署文件等，如果他们失去了手机，他们可以请求朋友帮助他们再次恢复身份。

在当前的体系结构中，用户的所有恢复委托都可以在区块链上公开获得。这可能构成安全风险，因为攻击者可能决定攻击用户的委托人以破坏其身份。在未来，我们将使用一系列一次性使用的恢复密钥，这些密钥不会公开与特定身份的关联。

讓用戶成爲個人數據的主人，微軟等公司的去中心化身份工具如何顛覆傳統遊戲規則？

uPort 的聯合創始人佩爾•布蘭德加德（Pelle Braendgaard）向 Cointelegraph 獨家介紹道：

“作爲 DIF 的成員，我們定期審查和反饋彼此的 DID 方法，以確保它們是可互操作的。在 ConsenSys，我們開發了多種 DID 方法，基本方法被稱爲 Ethr-DID。”

根據布蘭德加德的說法，雖然 Ethr-DID 和 SideTree （微軟用於 ION 的區塊鏈第二層協議）都是“可擴展的”，但兩者之間存在一些差異。具體來說，他認爲，基於 SideTree 的去中心化身份“必須由一個微軟託管的中心化服務器創建”。

一文讀懂加密貨幣智能錢包生態先行者

https://developer.uport.me/

Build User-Centric Ethereum Apps
npm uport-connect

Web3 Login Example