mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-10-01 05:05:54 +00:00
use-cases \ protocols
This commit is contained in:
⧉ infominer
parent
e5a39a5a2d
commit
29fa3fa9e0
@ -20,22 +20,20 @@ last_modified_at: 2020-11-05
|
||||
|
||||
---
|
||||
|
||||
|
||||
[Blockchain Use Cases - Consensys](https://consensys.net/blockchain-use-cases/digital-identity/)
|
||||
|
||||
> The traditional identity systems of today are fragmented, insecure, and exclusive. Blockchain enables more secure management and storage of digital identities by providing unified, interoperable, and tamper-proof infrastructure with key benefits to enterprises, users, and IoT management systems.
|
||||
|
||||
> - How does identity work today?
|
||||
> - Why do we need blockchain for identity?
|
||||
> - How do decentralized digital identities work on Ethereum?
|
||||
> - What are the use cases of blockchain in identity management?
|
||||
> - What are the benefits of decentralized identity?
|
||||
|
||||
|
||||
### Element
|
||||
[On-Demand: Credential Management for Government and Enterprise on Blockchain](https://pages.consensys.net/credential-management-for-government-and-enterprise) - The future of access controls and credential management on Blockchain
|
||||
|
||||
* [Introducing Element](https://medium.com/transmute-techtalk/introducing-element-328b4260e757)
|
||||
> Transmute is excited to announce Element, an implementation of the Sidetree Protocol on top of Ethereum and IPFS. This work was done in collaboration with Microsoft and Consensys under the Decentralized Identity Foundation (DIF)
|
||||
> ...
|
||||
> We’re excited to use the serviceEndpoints defined in Element DID documents to track external integrations, in a privacy preserving manner, including identity hubs, credential stores, and more. Furthermore, the scalability that Sidetree brings to DIDs is unprecedented.
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/mk4w2tBTgdE" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
[on SSIMeetup](https://ssimeetup.org/element-did-method-sidetree-ethereum-ipfs-orie-steele-webinar-31/)
|
||||
|
||||
* [transmute-industries/sidetree.js](https://github.com/transmute-industries/sidetree.js)
|
||||
> Sidetree.js is an implementation of v0.1.0 of the sidetree specification
|
||||
> 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.
|
||||
|
||||
## Ethereum Enterprise Alliance
|
||||
|
||||
@ -46,7 +44,7 @@ last_modified_at: 2020-11-05
|
||||
> The Infrastructure Contracts and Standards sublayer shows emerging standards outside theEnterprise Ethereum core specification. The components in this layer provide enablers for the applications built on top of them.Role Based Access Control (RBAC) defines methods for authentication and restricting system access to authorized users, potentially realized through smart contracts.Network Governance methods control which entities can join the network and hence assist withsafeguarding exchanges.Token standards provide common interfaces and methods along with best practices. These include[ERC-20], [ERC-223], [ERC-621], [ERC-721], and [ERC-827].
|
||||
|
||||
- [Enterprise Ethereum Alliance Permissioned Blockchains Specification v2](https://entethalliance.github.io/client-spec/chainspec.html) EEA Editor's Draft 01 November 2020
|
||||
> This document, the Enterprise Ethereum Blockchain Specification, defines requirements for Enterprise Ethereum blockchains to ensure they can be processed interoperably by Enterprise Ethereum clients that conform to the Enterprise Ethereum Client specification [EEA-client]. Its primary intended audience is operators of Enterprise Ethereum blockchains.
|
||||
> This document, the Enterprise Ethereum Blockchain Specification, defines requirements for Enterprise Ethereum blockchains to ensure they can be processed interoperably by Enterprise Ethereum clients that conform to the Enterprise Ethereum Client specification [EEA-client]. Its primary intended audience is operators of Enterprise Ethereum blockchains.\
|
||||
> [...]\
|
||||
> **Credential Management Sublayer**\
|
||||
> Credentials, in the context of Enterprise Ethereum blockchains, refer to an individual’s cryptographic private keys, which are associated with that user’s Ethereum account.\
|
||||
@ -58,11 +56,7 @@ last_modified_at: 2020-11-05
|
||||
|
||||
|
||||
|
||||
## [Web3Modal/web3modal](https://github.com/Web3Modal/web3modal)
|
||||
|
||||
> Web3Modal is an easy-to-use library to help developers add support for multiple providers in their apps with a simple customizable configuration.
|
||||
|
||||
> By default Web3Modal Library supports injected providers like (Metamask, Dapper, Gnosis Safe, Web3 Browsers, etc) and WalletConnect, You can also easily configure the library to support Portis, Fortmatic, Squarelink, Torus, Authereum, D'CENT Wallet and Arkane.
|
||||
|
||||
## ERC-EIP
|
||||
|
||||
@ -90,8 +84,62 @@ This presents a method to replace the usual signup/login design pattern with a m
|
||||
* [Ethereum ERC725 Blockchain Based, Self-Sovereign Identity Management](https://bitcoinexchangeguide.com/ethereum-erc725-blockchain-based-self-sovereign-identity-management/)
|
||||
* [erc725alliance.org](https://erc725alliance.org)
|
||||
|
||||
## Protocols
|
||||
### Element
|
||||
|
||||
* [Introducing Element](https://medium.com/transmute-techtalk/introducing-element-328b4260e757)
|
||||
> Transmute is excited to announce Element, an implementation of the Sidetree Protocol on top of Ethereum and IPFS. This work was done in collaboration with Microsoft and Consensys under the Decentralized Identity Foundation (DIF)
|
||||
> ...
|
||||
> We’re excited to use the serviceEndpoints defined in Element DID documents to track external integrations, in a privacy preserving manner, including identity hubs, credential stores, and more. Furthermore, the scalability that Sidetree brings to DIDs is unprecedented.
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/mk4w2tBTgdE" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
[on SSIMeetup](https://ssimeetup.org/element-did-method-sidetree-ethereum-ipfs-orie-steele-webinar-31/)
|
||||
|
||||
* [transmute-industries/sidetree.js](https://github.com/transmute-industries/sidetree.js)
|
||||
> Sidetree.js is an implementation of v0.1.0 of the sidetree specification
|
||||
|
||||
### Web3Modal
|
||||
|
||||
* [Web3Modal/web3modal](https://github.com/Web3Modal/web3modal)
|
||||
|
||||
> Web3Modal is an easy-to-use library to help developers add support for multiple providers in their apps with a simple customizable configuration.
|
||||
|
||||
> By default Web3Modal Library supports injected providers like (Metamask, Dapper, Gnosis Safe, Web3 Browsers, etc) and WalletConnect, You can also easily configure the library to support Portis, Fortmatic, Squarelink, Torus, Authereum, D'CENT Wallet and Arkane.
|
||||
|
||||
|
||||
### Baseline
|
||||
|
||||
[twitter](https://twitter.com/baselineproto) - [docs](https://docs.baseline-protocol.org/) - [slack](https://communityinviter.com/apps/ethereum-baseline/join-us) - [tele](https://t.me/baselineprotocol) - [discord](https://discord.gg/NE8AYD7)
|
||||
|
||||
* [EY, ConsenSys, Microsoft unveil Baseline, a path for enterprises to public blockchain](https://www.ledgerinsights.com/baseline-protocol-ey-consensys-microsoft-enterprises-public-blockchain/)
|
||||
> This is early days for the protocol, with invitations to the community to help to build it out further. The protocol will be governed by the Ethereum-Oasis Project, managed by the open source OASIS community and funded by the Ethereum Foundation and the Enterprise Ethereum Alliance. The code has a very permissive license.
|
||||
* [EY launches Baseline protocol, an open source initiative for the public Ethereum blockchain](https://www.ey.com/en_gl/news/2020/03/ey-launches-baseline-protocol-an-open-source-initiative-for-the-public-etherum-blockchain)
|
||||
> EY today announced the launch of the Baseline protocol, a new package of public domain blockchain tools that will allow enterprises to build and deploy procurement and other business processes securely and privately on the public Ethereum blockchain. EY developed the Baseline protocol in cooperation with ConsenSys and Microsoft.
|
||||
* [Open source proof of concept shows how to privately and securely synchronize data and business logic between companies, using the Ethereum Mainnet](https://oasis-open-projects.org/open-source-proof-of-concept-ethereum-mainnet/)
|
||||
> May 21, 2020 – Today, the Baseline Protocol, an OASIS open source initiative, published a demo of multiple companies digitally managing purchase orders and volume discount agreements across disparate systems. The demo uses an approach called “baselining” to prevent data inconsistencies and workflow errors that often lead to problems in revenue recognition.
|
||||
* [ethereum-oasis/oasis-open-project](https://github.com/ethereum-oasis/oasis-open-project)
|
||||
> The Ethereum OASIS Open Project is an OASIS Open Project that exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The Ethereum OASIS Project intends to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
|
||||
* [ethereum-oasis/baseline](https://github.com/ethereum-oasis/baseline)
|
||||
> The Baseline Protocol is an open source initiative that combines advances in cryptography, messaging, and blockchain to execute secure and private business processes at low cost via the public Ethereum Mainnet. The protocol will enable confidential and complex collaboration between enterprises without leaving any sensitive data on-chain
|
||||
|
||||
### 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.
|
||||
* [Technical Specification](https://github.com/ceramicnetwork/ceramic/blob/master/SPECIFICATION.md)
|
||||
* [ceramicnetwork/ceramic](https://github.com/ceramicnetwork/ceramic)
|
||||
* [github.com/ceramicstudio](https://github.com/ceramicstudio)
|
||||
|
||||
## Companies
|
||||
|
||||
### 3box
|
||||
|
||||
[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.
|
||||
|
||||
### uPort
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user