Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Project Health

Burrow is doing better than ever before. We've added some significant features and random people from the internet are fixing our off-by-ones. We also have a new team, Damascus Mile, with funding from the UK Cabinet Office who are building out a logistics platform on top of Burrow.

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?
    yes

Questions/Issues for the TSC

No issues, but would like to call out Typescript code generation (AKA solts) along with the improved Javascript/Typescript client gives a vastly  improved application-building experience (here is an example of the generated code). @hyperledger/burrow now exposes a `build` function that takes a Solidity source tree and generates strongly typed bindings for Burrow that embed the contract bytecode, ABI, metadata, and allows you to deploy the contract, stream events, and call functions all via a strongly typed interfaces. Kudos to Gregory Hill for building the original solts.

Um, as ever, this is not very well documented ¯\_(ツ)_/¯.

Releases

  • 0.31.1 - Web3 and Vent fixes
  • 0.31.2 - Dump/restore fixes
  • 0.31.3 - Dump/restore improvements
  • 0.32.0 - Burrow.js rewrite in Typescript, better ABI library, core state cache concurrency fix
  • 0.32.1 - Improved errors and Javascript type coercion
  • 0.33.0 - Introduced Solidity-to-Typescript client-side code generation, fixed client-side events, fixed finite stream bounds
  • 0.33.1 - Inline JS source maps and fixed BytesNN typing
  • 0.34.0 - Simplified JS codegen Provider interface (supporting other implementations), codegen fixes

See https://github.com/hyperledger/burrow/blob/main/CHANGELOG.md for more details.

Overall Activity in the Past Quarter

Chat remains relatively quiet generating a handful of messages per month. Github has seen some small but deep patches which seems to indicate there is some 'serious' usage going on. Damascus Mile has chosen to use Burrow as an ideal 'root stock' for their logistics project - hopefully evidence of Burrow's effort to be extensible and modular. Development activity has picked up quite a bit over previous two quarters.

Current Plans

Two major roadmap items are in play:

  1. State-splitting - providing a better way to divide account state while preserving commitments/proofs. Also the possibility of projecting out some state in an 'export' while preserving proofs. The relevance being around state channels/optimistic roll-ups where we would like to be able to provide a more granular subset of state than our current single global state root allows.
  2. Providing more practical support for WASM contracts (including AssemblyScript being given our Typescript leanings) by providing client library support and doing more testing.

Maintainer Diversity

We have added Ommi Shimizu from Monax.

Active Maintainers

NameGitHubemail
Greg Hill@gregdhillgregorydhill@outlook.com
Sean Young@seanyoungsean@mess.org
Casey Kuhlman@compleatangcasey.kuhlman@monax.io
Silas Davis@silasdavissilas.davis@monax.io
Ommi Shimizu@ommishommi.shimizu@monax.io

Contributor Diversity

We have had around five new individual contributors this quarter and interest in using us from Damascus Mile.

Reviewed By


  • No labels