Project Health

Overall health is OK with working on the coming v1.0 release.  v1.0.0-alpha is released on Jan 19, 2022. v1.0.0-alpha2 is coming this quarter.

The 1.0 release is with new architecture.

  1. Continue with the new dashboard;
  2. Finish new agent design and docker agent implementation;
  3. Continue the API Engine;
  4. Finish two demos: creating nodes, new cliSDK;

On the other hand, the internship project is done well with Yuanmao Zhu , who will continue to work on the project as an open-source contributor.

Required Information

  1. Have you switched from master to main in all your repos? yes
  2. Have you implemented the Common Repository Structure in all your repos?
    1. LICENSE - yes
    2. - yes
    3. - yes
    4. - yes
    5. - yes
    6. - yes
    7. CHANGELOG - yes




Jan 19, 2022: v1.0.0-alpha is released

Overall Activity in the Past Quarter

This quarter, we mainly have been focusing on the implementation of API engine and front end.

  • Completed the front end basic work on the deployment operations;
  • Finish the new backend agent (based on Docker);
  • Finish the cli SDK for dashboard usage.
  • Continued development of API engine.
    • node APIs are done;
    • channel APIs are almost done;
    • chaincode APIs are on-going.

Current Plans

Next steps include:

  • Finish the v1.0.0-alpha2 release this quarter;
  • Finish the v1.0.0-beta release in the 2nd quarter of 2022.

Maintainer Diversity

Current there are 3 maintainers, and those active developers who contribute to cello continuously (3 month) may be nominated as new maintainers. 

1 maintainer (Haitao Yue ) is retired this quarter and a new one is nominated (Yang Feng).

  • Baohua Yang (Oracle)
  • Qiang Xu (JiLi Technology)
  • Yang Feng (H3C)

Contributor Diversity

This quarter, we have a total of 26 commits from 6 contributors.

Additional Information

Insights from Dec 7, 2021  to  Feb 26 2022 ,can be found at Cello stats for last quarter.

Reviewed by

Submission date

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


  1. There are a couple of new questions in the latest project report template. Can you answer the following questions:

    1. Has your project implemented these inclusive language changes listed below to your repo? You can optionally use the DCI Lint tool to make this a recurring action on your repo.
      1. master → main
      2. slave → replicas
      3. blacklist → denylist
      4. whitelist → allowlist
    2. Have you added an Inclusive Language Statement to your project's documentation and/or Wiki pages? 
    1. yes, the inclusive language changes are implemented.

  2. The original project proposal included plans to support multiple blockchains (Fabric, Sawtooth Lake, Iroha specifically).  However the docs I read only mentions Fabric.  Are there roadmaps to supporting those blockchains?

    1. Not in short term. Our 1.0 release is still focused on fabric supports.

  3. As the TSC we are very interested in whether the project is keeping up with upstream changes in dependencies.   At a more basic level than Danno’s question, is there enough developer support to keep up with new releases of Hyperledger Fabric, and is there anything that could help support the project to keep current functionality healthy?

    1. Yes, it's to support the latest stable release of fabric.

      The resource is a bottleneck here. Not easy to find more contributors who are familiar with fabric, and have free time.

      We've lost 4 maintainers in past year, due to their job changing.

  4. In terms of attracting more contributors, I think one thing that would definitely help is enhancing the documentation. The current documentation is pretty thin and missing critical content such as a comprehensive tutorial to get started (the link to the "tutorial" in the README returns 404), more detailed architecture information, API spec, CLI command reference, samples.

    Also I was also not able to find enough architectural information to conclude how Cello is different from other alternatives, specifically Bevel. Even if someone is interested in contributing, as things stand now, they would quickly get turned off by the lack of information to get started.

    Hope as part of the release 1.0 effort (congrats on getting close to achieving this important milestone!) there will be improved documentation.