mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2025-05-31 20:14:39 -04:00
hyperledger sort \ org
This commit is contained in:
⧉ infominer
parent
61e3f53ac1
commit
e505b49686
16 changed files with 313 additions and 1029 deletions
|
|
@ -27,7 +27,7 @@ sidebar:
|
|||
nav: "didnav"
|
||||
categories: ["Open Source Projects"]
|
||||
tags: ["Sovrin Foundation","Verifiable Organizations Network","Verifiable Credentials","IBM","Evernym","Indy","RDF","IOT","Hyperledger Foundation","Adoption","Blockchain","Aries","Accenture","Consensys","Cisco","Ethereum Enterprise Alliance","CULedger","Truu","Tykn","Ursa","ATB","IOTA","UNSDGs","MyData"]
|
||||
last_modified_at: 2023-06-04
|
||||
last_modified_at: 2023-06-12
|
||||
---
|
||||
|
||||
**Protocol, Governance, Education, Ecosystem**
|
||||
|
|
@ -45,90 +45,101 @@ last_modified_at: 2023-06-04
|
|||
> This is the official SDK for Hyperledger Indy, which provides a distributed-ledger-based foundation for self-sovereign identity. Indy provides a software ecosystem for private, secure, and powerful identity, and the Indy SDK enables clients for it. The major artifact of the SDK is a C-callable library; there are also convenience wrappers for various programming languages and Indy CLI tool.
|
||||
|
||||
## About
|
||||
* [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)
|
||||
* [Blockchain for Business](https://www.edx.org/professional-certificate/linuxfoundationx-blockchain-for-business) Linux Foundation, may be freely audited and has a section about Indy.
|
||||
> 2–4 hours per week, for 10 weeks. A primer to blockchain, distributed ledgers and Hyperledger technologies.
|
||||
|
||||
<img src="https://i.imgur.com/a0dpDtr.png"/>
|
||||
|
||||
* [An overview of Self-Sovereign Identity: the use case at the core of Hyperledger Indy](https://www.hyperledger.org/blog/2019/05/01/an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy)
|
||||
* [Strengthening Hyperledger Indy and Self-Sovereign Identity](https://www.hyperledger.org/blog/2019/07/18/strengthening-hyperledger-indy-and-self-sovereign-identity) 2019-07-08
|
||||
> Forrester’s recent “[Top Recommendations for Your Security Program, 2019](https://www.forrester.com/report/Top+Recommendations+For+Your+Security+Program+2019/-/E-RES151535),” testifies to this, describing SSI as a “win” for customers and businesses, and urged chief information security officers (CISO) to “Empower your customers to control their own identities via self-sovereign identity.”
|
||||
>
|
||||
> They can do this because exchanging verifiable digital credentials is at the heart of SSI. This ends the need for massive data silos, honeypots, and unsecured data repositories housed at countless corporations and organizations. Instead, anyone can hold secure and verifiable information about themselves
|
||||
* [An overview of Self-Sovereign Identity: the use case at the core of Hyperledger Indy](https://www.hyperledger.org/blog/2019/05/01/an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy) 2019-05-01
|
||||
> Credential issuers, holders, and verifiers are peers on an SSI network. Any person or organization can play any or all of the roles, creating a decentralized system for the exchange of trustworthy, digital credentials.
|
||||
>
|
||||
> - Credential issuers determine what credentials to issue, what the credential means, and how they’ll validate the information they put in the credential.
|
||||
> - Credential holders determine what credentials they need and which they’ll employ in workflows to prove things about themselves.
|
||||
> - Credential verifiers determine what credentials to accept, and which issuers to trust.
|
||||
* [Strengthening Hyperledger Indy and Self-Sovereign Identity](https://www.hyperledger.org/blog/2019/07/18/strengthening-hyperledger-indy-and-self-sovereign-identity)
|
||||
> Forrester’s recent “[Top Recommendations for Your Security Program, 2019](https://www.forrester.com/report/Top+Recommendations+For+Your+Security+Program+2019/-/E-RES151535),” testifies to this, describing SSI as a “win” for customers and businesses, and urged chief information security officers (CISO) to “Empower your customers to control their own identities via self-sovereign identity.”
|
||||
>
|
||||
> They can do this because exchanging verifiable digital credentials is at the heart of SSI. This ends the need for massive data silos, honeypots, and unsecured data repositories housed at countless corporations and organizations. Instead, anyone can hold secure and verifiable information about themselves
|
||||
* [Hyperledger Indy Explainer Video](https://www.youtube.com/watch?v=MnO2L6WoqD0) Hyperledger Foundation
|
||||
> Individuals will not have to rely on big organizations to store and share their personal data. Instead the user controls what data they want to provide access to and for how long.
|
||||
* [Self-Sovereign Identity with Hyperledger Indy\Sovrin](https://www.youtube.com/watch?v=hfyIZu3_fw8) Calvin Cheng - FOSSASIA 2018
|
||||
> Implementing a public, permissioned blockchain for online digital identities.
|
||||
* [Sovrin: Public, Permissioned and Still Decentralized](https://www.youtube.com/watch?v=lVHJiUrHv2A&app=desktop) Nathan George
|
||||
* [Sovrin: Public, Permissioned and Still Decentralized](https://www.youtube.com/watch?v=lVHJiUrHv2A&app=desktop) 2018-12-17 Nathan George
|
||||
> Lighting talk with Nathan George (Sovrin CTO) taking the audience through a high-level look at the Sovrin DLT, how it can be public/permissioned yet still decentralized, and why this is right for identity solutions.
|
||||
* [Hyperledger Indy Explainer Video](https://www.youtube.com/watch?v=MnO2L6WoqD0) 2018-12-06 Hyperledger Foundation
|
||||
> Individuals will not have to rely on big organizations to store and share their personal data. Instead the user controls what data they want to provide access to and for how long.
|
||||
* [Self-Sovereign Identity with Hyperledger Indy\Sovrin](https://www.youtube.com/watch?v=hfyIZu3_fw8) 2018-05-26 Calvin Cheng FOSSASIA 2018
|
||||
> Implementing a public, permissioned blockchain for online digital identities.
|
||||
* [Implementing Privacy by Design in Hyperledger Indy](https://www.infoq.com/news/2018/09/Hyperledger-Indy-Privacy) 2018-09 Infoq
|
||||
> Hyperledger Indy has been built using a privacy first approach. As the world shifts to more regulation, including GDPR and ePrivacy requirements, Indy can minimize the amount of details a user shares when having their data validated by a third-party system.
|
||||
* [Privacy by Design in Hyperledger Indy](https://www.hyperledger.org/blog/2018/09/12/privacy-by-design-in-hyperledger-indy) 2018-09-12 Hyperledger Foundation
|
||||
> Hyperledger Indy’s approach to privacy includes elliptic curve cryptography, [pairwise DIDs](https://docs.google.com/document/d/1hnQPEdfmAG-DnXGrDXowjc5J571pK7Ub4bWkUlzrH1Y/edit), [semi-trusted agents](https://docs.google.com/presentation/d/1H7KKccqYB-2l8iknnSlGt7T_sBPLb9rfTkL-waSCux0/edit#slide=id.g2f2a8bc547_0_0), [agent-to-agent communication](https://github.com/hyperledger/indy-hipe/blob/35c9a8fda2011763d85df2a57bccc67bcdc28760/text/transport-layer-messaging/README.md) using techniques such as [libsodium’s sealed box](https://download.libsodium.org/doc/public-key_cryptography/sealed_boxes.html) and [authenticated encryption](https://download.libsodium.org/doc/public-key_cryptography/authenticated_encryption.html), zero-knowledge proofs, a separation between credentials and proofs, [privacy-preserving credential revocation](https://github.com/hyperledger/indy-hipe/blob/4fd9db5801f24f4e9ec122db98d4f725a394617c/text/0011-cred-revocation/README.md) features, an [affinity for data and key storage at the edge](https://docs.google.com/document/d/1Tcz06KtmnTysW38qT5K_oVzsWV9TjQFR4No9rRJEGFA/edit#heading=h.26in1rg), and a [carefully constructed wallet interface](https://github.com/hyperledger/indy-hipe/blob/36d3eddf4213b3a5f4bc9355cd6a645e819b1f31/text/wallets/README.md) that manages personal secrets with industry best practices. In addition, privacy-preserving [agent (device) revocation](https://github.com/hyperledger/indy-sdk/blob/677a0439487a1b7ce64c2e62671ed3e0079cc11f/doc/design/005-dkms/DKMS%20Design%20and%20Architecture%20V3.md#92-policy-registries) has been demonstrated as a proof of concept.
|
||||
* [Blockchain for Business](https://www.edx.org/professional-certificate/linuxfoundationx-blockchain-for-business) 2018-07-10 Linux Foundation
|
||||
> 2–4 hours per week, for 10 weeks. A primer to blockchain, distributed ledgers and Hyperledger technologies.
|
||||
* [The Rise of Self-Sovereign Identity - Hyperledger Indy](https://wso2.com/blog/research/the-rise-of-self-sovereign-identity-hyperledger-indy) 2018-07-03 WSO2
|
||||
> You can store your identities in a location where you can edit or delete them. After giving the location of your identities, the Indy platform lists your location with a globally identifiable name. When someone wants to read your identity data, the Indy platform points out the location of your identities. Let’s look into the details of how it works.
|
||||
* [Hyperledger Welcomes Project Indy](https://www.hyperledger.org/blog/2017/05/02/hyperledger-welcomes-project-indy) 2017-05-02 {ANN)
|
||||
> Indy is all about giving identity owners independent control of their personal data and relationships. Indy is built so that the owner of the identity is structurally part of transactions made about that identity. Pairwise identifiers not only prevent correlation, but they stop third parties from transacting without the identity owner taking part since the identity owner is the only place pairwise identifiers can be correlated.
|
||||
|
||||
### Working Group
|
||||
* [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)
|
||||
* [Hyperledger Indy Working Group Calls](https://drive.google.com/drive/u/0/folders/1AwHWN95KmSEi5fijraID0tFFMzYHoMwt?ogsrc=32)
|
||||
<img src="https://i.imgur.com/a0dpDtr.png"/>
|
||||
|
||||
## Development
|
||||
|
||||
* [Hyperledger completes development of DID:Indy Method and advances toward a network of networks](https://www.hyperledger.org/blog/2022/05/02/hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks) 2022-05-02 Linux Foundation, Howland & Bluhm
|
||||
> With the groundwork complete, networks and agent frameworks now need to incorporate the Indy:DID Method. This community adoption will increase the viability of the Indy and Aries project stack and position it to be the globally dominant way to issue and share verifiable credentials in a multi-ledger world.
|
||||
* [Building a Hyperledger Indy Network](https://iiw.idcommons.net/1H/_Building_a_Hyperledger_Indy_Network_-_Questions,_discussion,_etc.) 2021-05-06 Lynn Bendixsen IIW
|
||||
* [Slides](https://docs.google.com/presentation/d/1sUG4297GiRcUdu4aqQnc0Op0LMhbwiqy9LIAINHfSFQ/edit#slide=id.p1)
|
||||
* Creating your own Indy network:
|
||||
* High level: [Utility Foundry WG](https://github.com/trustoverip/utility-foundry-wg)
|
||||
* Implementation: [Technical details](https://docs.google.com/document/d/1Tg4dAEtC78TxG9AsIby_CfpbeOicK_YMKznSQOvtIVU/edit):
|
||||
* [Introduction to the Architecture of Indy Plenum and Node](https://www.youtube.com/watch?v=WZin717AT_A) Evernym, 2018-12-03
|
||||
> An internal training Evernym held to help new team members understand the details of Indy Plenum and Indy Node.
|
||||
* [Hyperledger Indy Project Enhancements](https://indy.readthedocs.io/projects/hipe/en/latest/) [GitHub](https://github.com/hyperledger/indy-hipe/blob/main/index.md)
|
||||
> This repo holds RFCs for the Indy project. We call them HIPEs (Hyperledger Indy Project Enhancements, pronounced like "hype" for short). They describe important topics (not minor details) that we want to standardize across the Indy ecosystem.
|
||||
|
||||
### GitHub
|
||||
|
||||
* [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.
|
||||
> "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)
|
||||
* [Hyperledger Indy Project Enhancements](https://indy.readthedocs.io/projects/hipe/en/latest/) [GitHub](https://github.com/hyperledger/indy-hipe/blob/main/index.md)
|
||||
> This repo holds RFCs for the Indy project. We call them HIPEs (Hyperledger Indy Project Enhancements, pronounced like "hype" for short). They describe important topics (not minor details) that we want to standardize across the Indy ecosystem.
|
||||
* [indy-crypto](https://github.com/hyperledger/indy-crypto) - shared crypto library for Hyperledger Indy components. To be:
|
||||
* [hyperledger/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/display/ursa)]
|
||||
* [indy-test-automation](https://github.com/hyperledger/indy-test-automation) 2023-03-28
|
||||
> Automation tools for testing of Indy Project components.
|
||||
|
||||
### Implementation
|
||||
* [hyperledger-labs/business-partner-agent](https://github.com/hyperledger-labs/business-partner-agent) 2023-05-17 - The Business Partner Agent allows to manage and exchange master data between organizations
|
||||
> The current maintainers stop active contribution to the further development of the Hyperledger Labs project Business Partner Agent, as well as the related project Business Partner Agent Helm Chart. To give existing users of the Business Partner Agent enough lead time, we are willing to continue maintaining the project for now. For more information see the Hyperledger Discord channel.
|
||||
* [IDunion](https://idunion.org/?lang=en)
|
||||
> enables self-determined identities based on Self-Sovereign Identity (SSI) technologies Hyperledger Indy and Hyperledger Aries. The aim of the IDunion organisation is to create an open ecosystem for decentralised identity management, which can be used worldwide and is based on European values and regulations. IDunion is also a [project](https://www.digitale-technologien.de/DT/Redaktion/DE/Standardartikel/SchaufensterSichereDigIdentProjekte/Schaufensterprojekte/sdi-projekt_idunion.html) co-funded by the [German Federal Ministry of Economic Affairs (BMWi)](https://www.bmwi.de/Navigation/EN/Home/home.html) as part of the [Showcases Secure Digital Identities program](https://www.digitale-technologien.de/DT/Navigation/DE/ProgrammeProjekte/AktuelleTechnologieprogramme/Sichere_Digitale_Identitaeten/sichere_digitale_ident.html). We gave an introduction covering
|
||||
* [BC Gov Collaboration on the Business Partner Agent, sharing our Roadmap (Create Creds, Issue them, Verify them, Hold them, publish them, ZKPs, Selective Disclosure)](https://iiw.idcommons.net/24A/_BC_Gov_Collaboration_on_the_Business_Partner_Agent,_sharing_our_Roadmap-Create_Creds,_Issue_them,_Verify_them,_Hold_them,_publish_them,_ZKPs,_Selective_Disclosure-) 2021-05-06 Matthew Hall IIW
|
||||
> - Viewing organizations as Issuers, Verifiers and Holders
|
||||
> - Talked about the complexity of defining a verifiable credential, I.e. what are you attesting to?
|
||||
> - Went over the need to make it easier for users to be able to create credential schemas and credential definitions without having to gain understanding about the tech.
|
||||
* [DEMO](https://www.youtube.com/watch?v=09-LOHPTHWs)
|
||||
* [Connect with Us](https://chat.hyperledger.org/channel/business-partner-agent)
|
||||
* [Repo](https://github.com/hyperledger-labs/business-partner-agent/projects/1) 2022-07-28
|
||||
* [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)] (ethereum ocean ipld)
|
||||
>"Achieving the Sustainable Development Goals demands embracing the data revolution " UN Secretary - General (2014)
|
||||
* [Legal Entity Identifier blockchained by a Hyperledger Indy implementation of GraphChain](http://www.graphchain.io/MTSR2018.pdf)
|
||||
* [Legal Entity Identifier blockchained by a Hyperledger Indy implementation of GraphChain](http://web.archive.org/web/20220221134446/http://graphchain.io/MTSR2018.pdf) 2018-10-23
|
||||
>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).
|
||||
* [CULedger partners with decentralized identity innovator Evernym to create MyCUID](https://www.cuinsight.com/press-release/culedger-partners-decentralized-identity-innovator-evernym-create-mycuid)
|
||||
* [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.
|
||||
* <a href="https://twitter.com/ByteSizeCapital/status/1046067509869367307"><img src="https://i.imgur.com/WeLDs34.png"/></a>
|
||||
* [Cordenity: Evernym and R3 Partner to make Corda compatible with Indy](http://www.paymentsjournal.com/evernym-r3-partner-apply-self-sovereign-identity-financial-services/) [[GitHub](https://github.com/Luxoft/cordentity)] [[Docs](https://schd.ws/hosted_files/hgf18/0e/Indy%20Identity%20on%20R3s%20Corda.pdf)]
|
||||
* [NB Orbit Enterprise/](https://northernblock.io/orbit-enterprise/) 2022
|
||||
> NB Orbit Enterprise is a no-code self-sovereign identity platform that facilitates the storage, issuance and verification of verifiable credentials that are held and owned by end users in digital wallets.
|
||||
>
|
||||
> The platform contains a collection of technologies and concepts in identity management, distributed and edge computing, distributed ledger technologies and cryptography.
|
||||
|
||||
### Literature
|
||||
* [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)
|
||||
* [A Framework for Designing Cryptographic Key Management Systems](https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-130.pdf) 2023-06-12
|
||||
> This Framework for Designing Cryptographic Key Management Systems (CKMS1) is a description of the topics to be considered and the documentation requirements (henceforth referred to as requirements) to be addressed when designing a CKMS. The CKMS designer satisfies the requirements by selecting the policies, procedures, components (hardware, software, and firmware), and devices (groups of components) to be incorporated into the CKMS, and then specifying how these items are employed to meet the requirements of this Framework
|
||||
* [An automatized Identity and Access Management system for IoT combining SSI and smart contracts](https://arxiv.org/pdf/2201.00231.pdf) 2023-06-11 Montassar Naghmouchi, Hella Kaffel, and Maryline Laurent
|
||||
> This paper proposes a blockchain-based identity and access management system for IoT – specifically smart vehicles- as an example of use-case, showing two interoperable blockchains, Ethereum and Hyperledger Indy, and a self-sovereign
|
||||
* [Technical Design and Development of a Self-Sovereign Identity Management Platform for Patient-Centric Healthcare Using Blockchain Technology](https://blockchainhealthcaretoday.com/index.php/journal/article/view/196#.Yjkahet3YEM.twitter) 2022-04-22 Blockchain Healthcare Today
|
||||
> To manage patient’s self-sovereign identity, we leveraged the Hyperledger Indy blockchain framework to store patient’s decentralized identifiers (DIDs) and the schemas or format for each credential type. In contrast, the credentials containing patient data are stored “off-ledger” in each person’s wallet and accessible via a computer or smartphone. We used Hyperledger Aries as a middleware layer (API) to connect Hyperledger Indy with the front-end, which was developed using a JavaScript framework, ReactJS (Web Application) and React Native (iOS Application).
|
||||
* [Blockchain Trilemma for Decentralized Identity: Learning from Hyperledger Indy](https://arxiv.org/pdf/2204.05784.pdf) 2022-04-12 Paul Dunphy, OneSpan, Cambridge, UK
|
||||
> The current credential verification process relies on transaction processing by a ledger with transaction processing bottlenecks, which may constrain the ideal of non-repudiation.
|
||||
* [Blockchain Trilemma for Decentralized Identity: Learning from Hyperledger Indy](https://arxiv.org/pdf/2204.05784.pdf) 2022-04-22 Paul Dunphy, OneSpan, Cambridge, UK
|
||||
> The current credential verification process relies on transaction processing by a ledger with transaction processing bottlenecks, which may constrain the ideal of non-repudiation.
|
||||
|
||||
## Zero Knowledge Proofs in Indy
|
||||
|
||||
|
||||
|
||||
* [Privacy Preserving Authentication—Another reason to care about ZKP](https://www.slideshare.net/eralcnoslen/privacypreserving-authentication-another-reason-to-care-about-zeroknowledge-proofs)
|
||||
* [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)]
|
||||
* [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)
|
||||
* [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)
|
||||
> 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).
|
||||
|
||||
### Prior Work
|
||||
* [How is IDEMix Implemented?](https://forum.sovrin.org/t/how-idemex-is-implemented-in-sovrin-indy/)
|
||||
> 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.
|
||||
* [IDEMIX Blog](https://idemix.wordpress.com/)
|
||||
* [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)
|
||||
|
||||
|
|
|
|||
|
|
@ -85,3 +85,10 @@ last_modified_at: 2023-06-12
|
|||
> Hyperledger Aries Cloud Agent Python (ACA-Py) is a foundation for building decentralized identity applications and services running in non-mobile environments.
|
||||
>
|
||||
> This is the Read The Docs site for the Hyperledger Aries Cloud Agent Python. This site contains only the ACA-Py docstrings documentation extracted from the Python Code. For other documentation, please consult the links in the Readme for the ACA-Py GitHub Repo.
|
||||
* [GlobaliD releases new open source applications](https://medium.com/global-id/globalid-shares-ssi-code-at-the-internet-identity-workshop-446debec43e7) 2020-10-30
|
||||
> They open source their open-sourced iOS and Android native Aries frameworks and donated them to the Hyperledger Aries project.
|
||||
>
|
||||
> They also shared their Dynamic Governance API using GlobaliD Groups.
|
||||
* [Tutorials](https://aries.js.org/guides/0.4/tutorials) Aries JavaScript Docs
|
||||
> First we’re going to create a holder Agent, this will be the Agent that receives the membership credential. During their life, the holder will collect many different verifiable credentials. Memberships, ID-cards, even purchasing records.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,18 +10,22 @@ permalink: blockchain/hyperledger/ursa/
|
|||
canonical_url: 'https://decentralized-id.com/blockchain/hyperledger/ursa/'
|
||||
categories: ["Open Source Projects"]
|
||||
tags: ["Ursa","Kiva","Sovrin Foundation","Web3","ACM","Bitwise","DFINITY","Evernym","Fujitsu","Intel","Linux Foundation","Sovrin Foundation","State Street"]
|
||||
last_modified_at: 2021-04-16
|
||||
last_modified_at: 2023-06-12
|
||||
header:
|
||||
image: /images/ursa-head.webp
|
||||
teaser: /images/ursa-square.webp
|
||||
---
|
||||
|
||||
[Website](https://www.hyperledger.org/use/ursa) • [Wiki](https://wiki.hyperledger.org/display/ursa) • [GitHub](https://github.com/hyperledger/ursa) • [RFCs](https://github.com/hyperledger/ursa-rfcs) • [Docs](hyperledger.org/ursa-docs/) • [Mailing List](https://lists.hyperledger.org/g/ursa) • [Chat](https://chat.hyperledger.org/channel/ursa)
|
||||
[Website](https://www.hyperledger.org/use/ursa) • [Wiki](https://wiki.hyperledger.org/display/ursa) • [GitHub](https://github.com/hyperledger/ursa) • [RFCs](https://github.com/hyperledger/ursa-rfcs) • [Docs](hyperledger.org/ursa-docs/) • [Mailing List](https://lists.hyperledger.org/g/ursa) • [Chat](https://chat.hyperledger.org/channel/ursa) • [Blog](https://www.hyperledger.org/category/hyperledger-ursa)
|
||||
|
||||
* [Welcome Hyperledger Ursa!](https://www.hyperledger.org/blog/2018/12/04/welcome-hyperledger-ursa)
|
||||
> Ursa aims to include things like a comprehensive library of modular signatures and symmetric-key primitives built on top of existing implementations, so blockchain developers can choose and modify their cryptographic schemes with a simple configuration file change. Ursa will also have implementations of newer, fancier cryptography, including things like pairing-based signatures, threshold signatures, and aggregate signatures, and also zero-knowledge primitives like SNARKs.
|
||||
* [Sovrin contributes to Hyperledger Ursa: A win for cryptography, security, and interoperability](https://sovrin.org/sovrin-contributes-to-hyperledger-ursa-a-win-for-cryptography-security-and-interoperability/)
|
||||
> Ursa is a library for cryptography and the result of a collaborative effort from teams at ACM, Bitwise, DFINITY, Evernym, Fujitsu, Intel, the Linux Foundation, the Sovrin Foundation, and State Street. Duplication among blockchain project features heightens security risks. Ursa, however, gathers up crypto implementations across projects and compiles them into a single metalibrary, creating a central repository for crypto code. This way, projects can select sources of code from Ursa, instead of the original source, decreasing duplication security risks and boosting interoperability among projects.
|
||||
* [Kiva Protocol, Built on Hyperledger Indy, Ursa and Aries, Powers Africa’s First Decentralized National ID system](https://www.hyperledger.org/category/hyperledger-ursa)
|
||||
* [Hyperledger Ursa code review](https://www.hyperledger.org/hyperledger-ursa/2022/05/31/hyperledger-ursa-code-review) Hyperledger 2022-05-31
|
||||
> Rooted in a “trust but verify” mindset, several Canadian public sector entities and [Interac](https://www.interac.ca/en/) (Canada’s interbank network) sponsored a project at the [Digital Identity Laboratory of Canada](https://idlab.org/) (IDLab) to perform a security and cryptography code review of Hyperledger Ursa (full report is available [here](https://www.hyperledger.org/wp-content/uploads/2022/05/URSA-IDLab-Code-Review.pdf)).
|
||||
* [Hyperledger Launches Cryptography Toolbox for Blockchain Developers](https://www.coindesk.com/hyperledger-launches-cryptography-toolbox-for-blockchain-developers) 2021-09-13 Coindesk
|
||||
> The Linux Foundation-led group announced Tuesday that Hyperledger Ursa will act as a repository of "trusted" cryptographic implementations, aimed to make it easier for blockchain developers within its community and the wider open-source space to avoid duplication of development efforts.
|
||||
* [Kiva Protocol, Built on Hyperledger Indy, Ursa and Aries, Powers Africa’s First Decentralized National ID system](https://www.hyperledger.org/blog/2021/01/20/kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system) 2021-01-20 Hyperledger
|
||||
> Kiva Protocol is built using Hyperledger Indy, Aries, and Ursa, and as implemented in Sierra Leone, allows citizens to perform electronic Know Your Customer (eKYC) verifications in about 11 seconds, using just their national ID number and a fingerprint. With this verification, it is possible for the nation’s unbanked to open a savings account and move into the formally banked population.
|
||||
* [Sovrin contributes to Hyperledger Ursa: A win for cryptography, security, and interoperability](https://sovrin.org/sovrin-contributes-to-hyperledger-ursa-a-win-for-cryptography-security-and-interoperability/) 2019-12-12 Sovrin
|
||||
> Ursa is a library for cryptography and the result of a collaborative effort from teams at ACM, Bitwise, DFINITY, Evernym, Fujitsu, Intel, the Linux Foundation, the Sovrin Foundation, and State Street. Duplication among blockchain project features heightens security risks. Ursa, however, gathers up crypto implementations across projects and compiles them into a single metalibrary, creating a central repository for crypto code. This way, projects can select sources of code from Ursa, instead of the original source, decreasing duplication security risks and boosting interoperability among projects.
|
||||
* [Welcome Hyperledger Ursa!](https://www.hyperledger.org/blog/2018/12/04/welcome-hyperledger-ursa) Hyperledger Foundation 2018-12-04
|
||||
> Hyperledger Ursa is the latest project to be accepted by the TSC! It is a modular, flexible cryptography library that is intended for—but not limited to—use by other projects in Hyperledger. Ursa’s objective is to make it much safer and easier for our distributed ledger projects to use existing, time tested, and trusted cryptographic libraries but also new cryptographic library implementations being developed.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue