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-21 03:05:54 -05:00
Code Issues Projects Releases Packages Wiki Activity

frontmatter header image description excerpt

Browse source
This commit is contained in:
Infominer 2020-01-07 07:05:23 -05:00
parent 226c83a9a4
commit 5ea3418ad2
11 changed files with 75 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

70
_posts/blockchain/ethereum/2019-03-27-cryptonomica.md Normal file
View file

@ -0,0 +1,70 @@
---
date: 2019-03-27
title: Cryptonomica
description: Cryptonomica.net is an identity verification service based on OpenPGP and Ethereum with legal framework and online dispute resolution for electronic contracts from London-based court of arbitration
excerpt: >
Users have been willing to accept certificates and check their validity manually or to simply accept them. No satisfactory solution has been found for the underlying problem
We offer exactly the solution for this problem that is mentioned in Wikipedia as not yet found. We deny automatic key check, we are offering the user to check and download each key manually.
We make verification of key owner's identity and store data about this verification: who, when, using which document made verification. And unlike in 'Web of trust' there is an established procedure for key verification, i.e. known rules according to witch identity of the key owner have to be proven.
layout: single
classes: wide
toc: false
permalink: blockchain/ethereum/cryptonomica/
canonical_url: 'https://decentralized-id.com/blockchain/ethereum/cryptonomica/'
redirect_from:
- id-initiatives/ethereum/cryptonomica
- id-initiatives/ethereum/cryptonomica/
categories: ["Blockchain"]
tags: ["Ethereum","PGP"]
last_modified_at: 2019-07-11
---
[![](https://i.imgur.com/moVyrrt.png)](https://cryptonomica.github.io)
* [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)
## From [the Cryptonomica Whitepaper](https://github.com/Cryptonomica/cryptonomica/wiki/Cryptonomica-White-Paper#the-problem):
>### The Problem
>
>As stated in [Wikipedia](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Certificates):
>
>> All public key / private key cryptosystems have the same problem (The problem of correctly identifying a public key as belonging to a particular user), even if in slightly different guises and *no fully satisfactory solution is known*.
>
>Existing systems of keys-based digital signature for documents are based on a personal visit to a certification center.
>
>The key pair for the client is in many countries created by the certification center, and given to the client. In this case, a copy of the user's private key can remain in the certification center, i.e. not only user can have access to it. This problem is often not even realized by users.
Often the keys for the client-bank systems are created this way.
>
>Although signature verification is reliable only if no one else except the owner has access to private key.
[...]
>### Our Solution
>
>PGP's ["Web of trust"](https://en.wikipedia.org/wiki/Web_of_trust) was not a success, because, as stated [Wikipedia](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Web_of_trust):
> Users have been willing to accept certificates and check their validity *manually* or to simply accept them. *No satisfactory solution has been found for the underlying problem*
>
>We offer exactly the solution for this problem that is mentioned in Wikipedia as not yet found. We deny automatic key check, we are offering the user to check and download each key manually.
>
>We make verification of key owner's identity and store data about this verification: who, when, using which document made verification. And unlike in ['Web of trust'](https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Web_of_trust) there is an established procedure for key verification, i.e. known rules according to witch identity of the key owner have to be proven.
>
>The user can make the information of the key or keys in the database available to all other users of the database, or available only for specified users or user group. Accordingly database user will have access to data about keys of others users, which is open to all users or shared with him, (for some cases, i.e. for arbitrators, including scans on the paper documents)
>
>And we offer for the market the first legally relevant global system of public key's certification, that can be run around the world, or more precisely in all states where [Hague Convention Abolishing the Requirement for Legalisation for Foreign Public Documents 1961](https://www.hcch.net/en/instruments/conventions/full-text/?cid=41) ([Apostille Convention](https://en.wikipedia.org/wiki/Apostille_Convention)) and [United Nations Convention on the Recognition and Enforcement of Foreign Arbitral Awards 1958](http://www.uncitral.org/uncitral/en/uncitral_texts/arbitration/NYConvention.html) ([New York Convention 1958](https://en.wikipedia.org/wiki/Convention_on_the_Recognition_and_Enforcement_of_Foreign_Arbitral_Awards)) are recognized.
>
>We can provide a legal mechanism for recognizing digitally signed contracts in almost every country: every digital contract in the need can be "transformed" in arbitral award recognized under [The Convention on the Recognition and Enforcement of Foreign Arbitral Awards](http://www.uncitral.org/uncitral/en/uncitral_texts/arbitration/NYConvention.html), and using modern technologies (web-server, databases, videoconferencing, e-mail) make [international arbitration](https://en.wikipedia.org/wiki/International_arbitration) affordable even for small business and individual clients.
## Github Repos
* [Cryptonomica/cryptonomica](https://github.com/Cryptonomica/cryptonomica) - Cryptonomica keys server
* [Cryptonomica/cryptonomica.github.io](https://github.com/Cryptonomica/cryptonomica.github.io) - Cryptonomica frontend
* [Cryptonomica/arbitration-rules](https://github.com/Cryptonomica/arbitration-rules) - Cryptonomica Arbitration Rules
* [Cryptonomica/dappathon-tlv](https://github.com/Cryptonomica/dappathon-tlv)
* [Cryptonomica/Ethereum-IdentityVerification](https://github.com/Cryptonomica/Ethereum-IdentityVerification) - Indentity verification and KYC for Ethereum blockchain
* [Cryptonomica/ethnode.cryptonomica.net](https://github.com/Cryptonomica/ethnode.cryptonomica.net) - Ethereum node with API on nodejs and web3.js
* [Cryptonomica/Ethereum-IdentityProof](https://github.com/Cryptonomica/Ethereum-IdentityProof) - Smart contract for Ethereum's account owner verification using Cryptonomica.net
* [Cryptonomica/international-arbitration-law](https://github.com/Cryptonomica/international-arbitration-law) - Repository for collecting information about international arbitration law and practice

137
_posts/blockchain/ethereum/2019-03-28-uport.md Normal file
View file

@ -0,0 +1,137 @@
---
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."
classes: wide
header:
image: /images/uport.png
caption: "[Releasing uPort Libraries 1.0](https://medium.com/uport/releasing-uport-developer-platform-1-0-97d6f70c5e4a)"
toc: false
permalink: /blockchain/ethereum/uPort/
canonical_url: 'https://decentralized-id.com/blockchain/ethereum/uPort/'
redirect_from:
- id-initiatives/ethereum/uport
- blockchain/ethereum/uPort
- id-initiatives/ethereum/uPort/
categories: ["Blockchain",]
tags: ["Ethereum","Credentials Community Group","GDPR","uPort"]
last_modified_at: 2019-07-11
---
![](https://i.imgur.com/sPAP2g3.png)
* [uPort](https://www.uport.me/) [[**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)
![](https://i.imgur.com/ASI0PaB.png)
## [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
## 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)
## GitHub
* [uPort GitHub Repos](https://decentralized-id.com/ethereum/id-github/#uport)
* [uPort DID](https://decentralized-id.com/ethereum/id-github/#uport-did)
* [uPort Identification](https://decentralized-id.com/ethereum/id-github/#uport-identification)
* [uPort Mobile](https://decentralized-id.com/ethereum/id-github/#uport-mobile)
* [uPort Lambda](https://decentralized-id.com/ethereum/id-github/#uport-lambda)
* [uPort React](https://decentralized-id.com/ethereum/id-github/#uport-react)
* [uPort Assorted](https://decentralized-id.com/ethereum/id-github/#uport-assorted)
## Literature
* [A First Look at Identity Management Schemes on the Blockchain](https://arxiv.org/pdf/1801.03294.pdf)