Hyperledger SSI Ecosystem

• indy-node

  2 675 7.0 Python

  The server portion of a distributed ledger purpose-built for decentralized identity.

  

indy-node contains a source code for the node running as part of the distributed ledger network. It implements PBFT consensus protocol, and it’s not intended to run as a public permissionless network as Bitcoin or Etherum but rather as a permissioned network. There is not one single instance of the Indy network. There are many of them. The most famous and publicly available is Sovrin, which was the first one. You can also use indy-node to run your network or run it locally on your machine via Docker for testing purposes.

• indy-sdk

  2 666 3.2 Rust

  Discontinued indy-sdk

  

indy-sdk works partially as a client for indy-node, but it has much more functionality. The library is written in Rust, and you can find it under the libindy folder. The binary file name is the same. There are also wrappers allowing you to use the library with other languages like Node.js, .NET, Java, Obj-C, and Python. We can divide the functionality into three parts:

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• indy-vdr

  3 50 8.9 Rust

  A library and proxy server for interacting with Hyperledger Indy Node ledger instances

  

indy-vdr: client for distributed ledger.

• indy-shared-rs

  1 14 7.2 Rust

  Shared Rust data types and utility functions for Hyperledger Indy.

  

indy-shared-rs: DIDs and verifiable credentials.

• aries-askar

  2 55 8.7 Rust

  Secure storage designed for Hyperledger Aries agents.

  

aries-askar: a wallet as secure storage.

• verity

  1 - -

There is another project that wants to evolve from indy-sdk. Evernym company forked the indy-sdk and created vdr-tools.

• ursa

  2 319 3.9 Rust

  Discontinued Hyperledger Ursa (a shared cryptographic library) has moved to end-of-life status, with the components of Ursa still in use moved to their relevant Hyperledger projects (AnonCreds, Indy, Aries and Iroha).

  

In the beginning, there was no Ursa or Aries, just Indy with all functionality together. As time went by, the Hyperledger community realized that there are a lot of useful cryptographic primitives which can be extracted and used by other Hyperledger projects. That’s the reason why Ursa has been created. It’s only one ursa repository containing encryption, signatures, and zero-knowledge algorithms. I’m not a cryptographer, and I’ve been working mainly with Indy and Aries, so I don’t know many details about it. I will leave that investigation up to you if you need to learn more. However, for many SSI use case implementations, you will be good just with knowledge of Indy and Aries.

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• aries-rfcs

  3 317 8.6 Python

  Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions

  

In the indy-sdk section, I described that it provides functionality to create DIDs, credentials, proofs, etc. Now, you need a way to securely exchange those items in an interoperable and portable way according to SSI principles. That’s the goal of the Aries project. The specification of the protocol is in aries-rfcs, which originated from an older project, indy-hipe (the protocol was part of Indy in the beginning).

• credo-ts

  1 238 9.3 TypeScript

  Typescript framework for building decentralized identity and verifiable credential solutions

  

Here is a diagram showing how all those components fit together. I took Aries JavaScript Framework for demonstration (I’m a little bit biased here because I started the project, and I’m a fan of it, of course):

Suggest a related project