| |||
Resource | Project Description | Documentation | Courseware | |
|---|---|---|---|---|
| Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions. It includes a shared cryptographic wallet (the secure storage tech, not a UI) for blockchain clients as well as a communications protocol for allowing off-ledger interaction between those clients. This project consumes the cryptographic support provided by Hyperledger Ursa, to provide secure secret management and decentralized key management functionality. | ||||
| Not Available | None https://www.hyperledger.org/blog/2019/10/03/introducing-hyperledger-avalon | ||
| Besu is an Ethereum client that runs on the Ethereum public network, private networks, and test networks such as Rinkeby, Ropsten, and Görli. | https://besu.hyperledger.org/en/latest/ |
| Besu Style Guide | |
| Permissioned Ethereum smart-contract blockchain | https://godoc.org/github.com/hyperledger/burrow | |||
Blockchain benchmark framework which allows users to measure the performance of a specific blockchain implementation with a set of predefined use cases. | ||||
Hyperledger Cello is a blockchain provision and operation system, which helps manage blockchain networks in an efficient way. | ||||
Development framework/tools for building Blockchain business networks | ||||
Development framework/tools for building Blockchain business networks Blockchain Web UI | ||||
| Distributed ledger in Go | ||||
| Platform for building supply chain solutions that include distributed ledger components. | |||
| Distributed ledger purpose-built for decentralized identity | ||||
| Distributed ledger in C++ | ||||
| An interoperability solution for blockchains, DLTs and other types of ledgers | ||||
| Distributed ledger with Multi-Language Support | ||||
| Transact is a transaction execution platform designed to be used as a library or component when implementing distributed ledgers, including blockchains. | ||||
| A shared cryptographic library that would enable people (and projects) to avoid duplicating other cryptographic work and hopefully increase security in the process. |
CHAOSS Working groups
The goal of the working groups is to refine the metrics and to work with software implementations. The workgroups are built around the four categories of metrics that CHAOSS has identified.
The working groups are:
Common Metrics
Diversity and Inclusion
Evolution
Risk
Value