Hyperledger Burrow

Project Health

All maintainers and contributors have had less time to work on Burrow but it continues to be used and work proceeds at a reasonable pace, though slower in the last month or so. Given the world is on fire this state of affairs does not seem particularly surprising. Most notable is work on eWASM and Typescript client which is important foundation for future development. 

Questions/Issues for the TSC

We have issues reported with our documentation, some of which our minor, but we have limited to fix right now. I remain willing to work with anyone who is able to provide assistance here. To work through our tutorials with an impartial eye, and fix wrong or confusing information or flows. We put significant effort into raising the coverage of our docs and tutorials but never had time to do any user testing


  • v0.29.4 - Upgrade to Solidity 0.5.12
  • v0.29.5 - Improve Vent synchronisation and improve GRPC status codes, Upgrade Tendermint to 0.32.8
  • v0.29.8 - 1,2, miss a few, 99, 100 (build issues)
  • v0.30.0 - Rewrite JS library in Typescript, fix intial commit panic
  • v0.30.1 - Governance primitive fixes
  • v0.30.2 - Patch upstream issue with IAVL concurrency with mutex for concurrent reads on simulated calls
  • v0.30.3 - Expose 'burrow compile' test fixture functionality in binary
  • v0.30.4 - Groundwork for EVM fixes coming up in next version (ensuring valid jumps)

Overall Activity in the Past Quarter

Had a significant bug fix from developer at CertiK with possibility of future collaboration. Quite a few important fixes and and continued issues.

Current Plans

eWASM support, IBC support

Maintainer Diversity


Contributor Diversity

Significant contribution from CertiK

Reviewed by


  1. Can you please list the actual maintainers and contributors (or provide links)? As I think Mark Wagner would say: we typically don't know what it was on the last report, and having every TSC member search for the info isn't very efficient.

    Regarding the activity, we have a new analytics tool: which shows 2 commits over the last 2 months. I don't know that I would call that "a reasonable pace" but I can understand that in those troubled months we are currently living in one may not be the most productive.

  2. I did think about adding maintainer list, but the update template says:

    > Required: Please include the maintainers that were added since your last report

    so I didn't, they are here:

    The tool does not appear to accurately represent the number of commits: in a way that seems odd.

    We've shipped more releases this quarter that in many others, but like I said, not much happened in May.

    1. It looks like anything with the green github "verified" tag is being labeled a bot and an empty commit.  Take those two filters off (on a drill down page, not the front dashboard which lacks the option) and a different chart results.

    2. Taking a quick look, it seems a lot of commits are of this form, which is not a valid DCO.