Graduated Projects
| Title | Project | Description |
|---|---|---|
| Hyperledger Aries |
| Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions as defined in the Trust over IP Technical Stack, Layers 2 (secure peer to peer communications) and 3 (data exchange protocols). It defines messaging protocols and implements those protocols in shared, reusable, interoperable tool kits designed for initiatives and solutions focused on creating, transmitting and storing verifiable digital credentials. |
| Hyperledger Besu |
| Hyperledger Besu is an Ethereum client designed to be enterprise-friendly for both public and private permissioned network use cases. It can also be ran on test networks such as Rinkeby, Ropsten, and Görli. Hyperledger Besu includes several consensus algorithms including PoW, and PoA (IBFT, IBFT 2.0, Etherhash, and Clique). Its comprehensive permissioning schemes are designed specifically for use in a consortium environment. |
| Hyperledger Fabric |
| Hyperledger Fabric is intended as a foundation for developing applications or solutions with a modular architecture. Hyperledger Fabric allows components, such as consensus and membership services, to be plug-and-play. Its modular and versatile design satisfies a broad range of industry use cases. It offers a unique approach to consensus that enables performance at scale while preserving privacy. |
| Hyperledger Indy |
| Hyperledger Indy provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers so that they are interoperable across administrative domains, applications, and any other silo. Indy is interoperable with other blockchains or can be used standalone powering the decentralization of identity. |
| Hyperledger Iroha |
| Hyperledger Iroha is designed to be simple and easy to incorporate into infrastructural or IoT projects requiring distributed ledger technology. Hyperledger Iroha features a simple construction, modular, domain-driven C++ design, emphasis on client application development and a new, crash fault tolerant consensus algorithm, called YAC. |
| Hyperledger Sawtooth |
| Hyperledger Sawtooth offers a flexible and modular architecture separates the core system from the application domain, so smart contracts can specify the business rules for applications without needing to know the underlying design of the core system. Hyperledger Sawtooth supports a variety of consensus algorithms, including Practical Byzantine Fault Tolerance (PBFT) and Proof of Elapsed Time (PoET). |
Incubating Projects
| Title | Project | Description |
|---|---|---|
| Hyperledger Avalon |
| Hyperledger Avalon enables privacy in blockchain transactions, moving intensive processing from a main blockchain to improve scalability and latency, and to support attested Oracles |
| Hyperledger Burrow |
| Permissioned Ethereum smart-contract blockchain |
| Hyperledger Cactus Home | | Hyperledger Cactus is a plugin based framework which aims to provide developers with an abstraction over protocol specific implementations, and enabling interoperability. This enables solutions to more easily adapt to new protocols, and make transactions involving multiple public and/or permissioned ledgers. |
| Hyperledger Caliper |
| Blockchain benchmark framework which allows users to measure the performance of a specific blockchain implementation with a set of predefined use cases. |
| Hyperledger Cello | | Blockchain operating system |
| Hyperledger Explorer | | Blockchain Web UI |
| Hyperledger Grid |
| Platform for building supply chain solutions that include distributed ledger components. |
| Hyperledger Quilt |
| An interoperability solution for any fungible assets - fiat, crypto, DLT, in-game tokens, or any other type of asset tracked on a ledger. |
| Hyperledger Transact |
| Transact is a transaction execution platform designed to be used as a library or component when implementing distributed ledgers, including blockchains. |
| Hyperledger Ursa |
| A shared cryptographic library that enables people (and projects) to avoid duplicating cryptographic work across projects, increasing security in the process. |
