decentralized-id.github.io/identosphere-dump/open-source-projects/hyperledger/hyperledger-umbrella.md
2023-01-15 01:30:53 -05:00

15 KiB
Raw Blame History

published
false

Hyperledger umbrella

DIDs Fabric and Decentralized Networking

  • DEON is a new Hyperledger project focused in off-line communication networks, independent of internet infrastructure. This could be used to enable networks of devices to communicate peer-to-peer (without the need to phone home over the internet), inter-enterprise consortia networks, and enabling user-centric data sharing in a more secure and private fashion.

  • Add support for "did:indy" to Hyperledger Indy Node and Indy VDR </>Code With Us

Accpting Applications until 1/10 4:00 PM PST

The total funding for the challenge is $70,000CDN and is divided into 4 phases. The first 3 phases require the use of Python working on the Indy Node.

The current credential verification process relies on transaction processing by a ledger with transaction processing bottlenecks, which may constrain the ideal of non-repudiation.

  • GlobaliD releases new open source applications

    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 Aries JavaScript Docs

    First were 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.

  • Why Are Governments Choosing Hyperledger? Northern Block

    • Open Data Standards (W3Cs DID & VC Standards)
    • Open Tech Standards (Hyperledger Aries, Indy, Ursa)
    • Achieving W3C-Compliance on Aries and Indy
  • Building a Hyperledger Indy Network - Questions, discussion, etc. by Lynn Bendixsen

Slides link: https://docs.google.com/presentation/d/1sUG4297GiRcUdu4aqQnc0Op0LMhbwiqy9LIAINHfSFQ/edit#slide=id.p1

Links to guides for creating your own Indy network:

High level:

Technical details (implementation):

Join the discussion: https://chat.hyperledger.org/channel/business-partner-agent

There was some discussion about the way to present such a profile, especially the way it is currently implemented as an endpoint in the did document pointing to a https ressource (json-ld document served using normal https).

One alternative, to create a DIDcomm-based protocol for public profile was discussed and would be a good alternative at the cost of every client having to be able to speak DIDcomm.

As our approach evolves, we also remain keen to support open source solutions that interoperate with other national and international efforts. There is no dominant design yet, no one network or technology, so we must remain nimble and flexible in our exploration. We also need to coexist with existing identity solutions that millions of British Columbians already rely upon.

  • The IDunion consortium consists of 37 partners - other major partners have already signaled interest in participating
  • Our solution is enabled by the distributed ledger technology (DLT) and the concept of self-sovereign identities (SSI)
  • Instead of a central authority, trust is organized via a DLT network, which works as a decentralized PKI system
  • In recent months, in addition to intensive research, we have developed a DLT test network including governance structure, 35+ use cases and numerous software components for the allocation, verification and management of digital identity data developed
  • In the future, the identity network will be managed by a European cooperative in which every institution in the EU can participate
  • In total, we are working on 35 use cases in the areas of eGovernment, education, finance, industry/IOT, eCommerce/mobility, IAM, and eHealth

IDunion | SSI | Identity | Consortium | Cooperative | Germany | Europe | BWMi

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

Business partner agent, credential management, issuers, verifiers, holders, digital wallet

Practical session, what we are actually building today using the hyper ledger Aries tools

Some interesting points

  • 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.
  • Question was asked about where do we start, do we have to bootstrap the first credential? And we went over being able to start with existing governance structures, and the trust that is already accepted there to issue the first credentials.
  • I gave a demo of our prototype that shows three actors (Mine, Bank, Verifier) doing a credential exchange flow between them

Links:

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

IdRamp presented with Oracle at Hyperledger Global Forum June 2021. The event focused on enterprise use of blockchain technologies using the 15 projects that fall under the Hyperledger “greenhouse”. Keynotes and speakers shared their insights on the current state of enterprise blockchain adoption across several hot topics including central bank digital currencies (CBDCs), non fungible tokens (NFTs), and most importantly identity.

Here, we go through how we went about standing up our Indico node. In brief:

  • The Indicio MainNet is an enterprise-grade ledger for use by decentralized identity applications.
  • We brought up the node using AWS Elastic Cloud Computing (EC2) instances within a Virtual Private Cloud (VPC).
  • We pulled the validator algorithms from the open-source project, Hyperledger Indy.
  • A supporting machine operates the command line interface used to perform steward operations onthe ledger.
  • We used security groups at the network interface level to create a firewall.
  • We set up monitoring in AWS CloudWatch using a variety of bash scripting in conjunction with Ubuntu and AWS provided utilities.
  • We created a regular maintenance schedule.

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.

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 * Hyperledger Identity Screencast: Social Recovery for Passwords and Secrets

A demonstration of using social recovery for things like recovery passwords of self-sovereign identity digital wallets. The website http://passguardian.com is used to show how a secret can be encoded and distributed as shards, and then later some of the shards combined to restore the secret. This video is part of a Linux Foundation course on Hyperledger Identity, published on edX. identity model.

To manage patients self-sovereign identity, we leveraged the Hyperledger Indy blockchain framework to store patients 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 persons 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).