Hyperledger Avalon

Prepared by Eugene (Yevgeniy) Yarmosh

Project Health

The team was focused on identifying an appropriate path that would split Avalon main into two independent parts – blockchain connectors and confidential computing (Intel SGX based) core. As result there were no commits to the main repository. We continued to work on the Python SDK sub-project and Kata/K8S prototype.  The team continued to support General Department of Vietnam Customs project.

Analytics: link

Required Information

  1. Have you switched from master to main in all your repos? Yes.
  2. Have you implemented repolinter.json in all your repos? No

Questions/Issues for the TSC

There are no issues for the TSC currently.


There was no release in this quarter.

A release schedule will be updated Avalon split plan is finalized.

Overall Activity in the Past Quarter

The primary focus has been on splitting Avalon main into two independent parts – blockchain connectors and confidential computing (Intel SGX based) core. The SGX core may be potentially hosted at Confidential Computing Consortium while Avalon itself will focus on the blockchain integration. This work is in progress and will continue in Q4.  

Other activities during Q3/2021

  • Avalon SDK for direct mode is merged and the package is published at https://pypi.org/project/avalon-sdk-py/
  • Presentation on Avalon at the Webinar organized by STPI India for the upcoming startups/entrepreneurs with panelists from Amazon, IBM, MathWorks and other companies. https://apiary.stpi.in/
  • Continued support for the POC for General Department of Vietnam Customs projects and a corresponding white paper is published by Intel and SAP  at white-paper-link.
  • Started prototyping running SGX enabled microservices in Kata runtime under K8S
  • Started discussions with LF Edge Alvarium team on utilizing Avalon for improved data provenance trust and confidentiality in decentralized use cases

Current Plans

The team is working on

  • Finalizing Avalon code base spilt into independent parts – blockchain specific and confidential compute core with a possibility of hosting the core at Confidential Computing Consortium
  • Engaging with LF Edge Alvarium project on the data provenance solution
  • Defining smart contracts focused on the data provenance use cases   
  • Integrating Python SDK in the main repository
  • Improving deployment and ease-of-use in cloud native (K8S) environment

Maintainer Diversity

No changes to the maintainer list in this quarter.

Contributor Diversity

No changes to the contributors list in this quarter.

Additional Information

None at this time.

Submission date

$action.dateFormatter.formatGivenString("dd-MMM-yyyy", $content.getCreationDate())

Reviewed By


  1. Probably a task for the next TSC, but what would this split look like if the Intel SGX portions move to the Confidential Computing Consortium? Would the code in Hyperledger be blockchain connectors to arbitrary privacy backends?  Blockchain connectors to what would be the CCC Avalon code only?

    1. Eugene Yarmosh - do you have an answer for this question or is it still TBD within the avalon teams?

      1. Could be interesting to see, if in case blockchain part is split as stamping service then there is a possible collaboration across FireFly. Potentially, Avalon becoming one of the connector through FireFly for workloads.

  2. Although I suspect the answer is the same, please, note that the question: "Have you implemented repolinter.json in all your repos?" has been changed to: "Have you implemented the Common Repository Structure in all your repos?"