NOTE: This project is currently in deprecated state. Depending on your needs, please refer to one of the following projects instead:
- for core programming in enclave based confidential computation, Confidential Computing Consortium
- for using Zero Knowledge Proofs in privacy preserving blockchain transactions, Hyperledger Ursa
- for achieving privacy using offchain data channels with blockchain coordination, Hyperledger FireFly
- for similar functionality, Private Data Objects, a Hyperledger Lab
- for confidential smart contracts on Hyperledger Fabric, Hyperledger Fabric Private Chaincode
Hyperledger Avalon (formerly Trusted Compute Framework) enables privacy in blockchain transactions, moving intensive processing from a main blockchain to improve scalability and latency, and to support attested Oracles.
The Trusted Compute Specification was designed to help developers gain the benefits of computational trust and to mitigate its drawbacks. In the case of the Avalon, a blockchain is used to enforce execution policies and ensure transaction auditability, while associated off-chain trusted compute resources execute transactions. By using trusted off-chain compute resources, a developer can accelerate throughput and improve data privacy.
Preservation of the integrity of execution and the enforcement of confidentiality guarantees come through the use of a Trusted Compute (TC) option, e.g. ZKP (Zero Knowledge Proof), MPC (Multi Party Compute), or a hardware-based TEE (Trusted Execution Environment). While the approach will work with any TC option that guarantees integrity and confidentiality for code and data, our initial implementation uses Intel® Software Guard Extensions (SGX).
Hyperledger Avalon leverages the existence of a distributed ledger to
- Maintain a registry of the trusted workers (including their attestation info)
- Provide a mechanism for submitting work orders from a client(s) to a worker
- Preserve a log of work order receipts and acknowledgments
Hyperledger Avalon uses the Off-Chain Trusted Compute Specification defined by Enterprise Ethereum Alliance (EEA) Task Force as a starting point to apply a consistent and compatible approach to all supported blockchains.
For more details on Hyperledger Avalon architecture, see avalon-arch.pdf.
To build Hyperledger Avalon, follow instructions in the build document.
Hyperledger Avalon Documentation
See the contributing document for information on how to contribute and the guidelines for contributions.
- Manjunath A C (manju956)
- Daniel Anderson (danintel)
- Thomas J Barnes (TomBarnes)
- Srinath Duraisamy (srinathduraisamy)
- Manoj Gopalakrishnan (manojgop)
- Karthika Murthy (Karthika)
- Ramakrishna Srinivasamurthy (ram-srini)
- Yevgeniy Y. Yarmosh (EugeneYYY)
- Mic Bowman (cmickeyb) - TSC member
Hyperledger Avalon is released under the Apache License Version 2.0 software license. See the license file for more details.
Hyperledger Avalon documentation is licensed under the Creative Commons Attribution 4.0 International License. You may obtain a copy of the license at: http://creativecommons.org/licenses/by/4.0/.
© Copyright 2019-2020, Intel Corporation.