2019 Q4 Hyperledger Burrow
Project
https://github.com/hyperledger/burrow/
Project Health
Our last update mentioned that there was a lack of documentation, which was inhibiting new users. This has mostly been rectified and now documentation requests are for more obscure features.Â
Questions/Issues for the TSC
Some work has gone toward promoting burrow, for example https://www.hyperledger.org/blog/2019/10/08/burrow-the-boring-blockchain
We are always looking for further to promote burrow. Suggestions are welcome.
Releases
- v0.28.0Â Burrow now remembers contact ABIs (and other metadata), bond and unbond transactions, many fixes.
- v0.28.1Â Burrow node js module in main repo
- v0.28.2Â burrow vent decodes evm events before applying any filters
- v0.29.0Â web3 support, IdentifyTx, lots of new documentation. natives contracts are first class contracts.
- v0.29.1 bug fixes
- v0.29.2 bug fixes
Overall Activity in the Past Quarter
There has been plenty of development, the vast majority from Monax employees, including:
- lots of documentation has been written and it can be read at https://hyperledger.github.io/burrow.
- web3 support
- metadata for contract. The metadata includes ABI, source file, contract name and compiler version. This stored on-chain. As a result it is no longer necessary to manage ABIs in files.
- "native" contracts (written in go and compiled into the burrow binary are now first class contracts. This means that burrow supports Solidity (EVM) contracts, WASM (e.g. solang) contracts, and native golang contract which can all call each other.
- New command "burrow accounts" which lists all the contract names, ABI etc for all accounts.
- state is now serialised in protobuf, rather than go-amino
- The node npm to interact with burrow has been merged into main burrow repo.
- Work on identifyTx, bond, and unbond transactions.
- Many other issues have also been solved.
Current Plans
We need to have a push on explaining Burrow and documenting. A lot has already been done towards this goal.
Now that golang native contracts (called "natives") are first class contracts it is planned that burrow functionality which unique to burrow (e.g. name reg, governance) will be implemented as natives so that the can be called from regular call transactions, or from solidity, or from our deploymen tool, burrow deploy.
Otherwise plans are unchanged since last update.
Maintainer Diversity
No new maintainers. We have 4 from Monax, 2 non-Monax
Contributor Diversity
No new no-Monax contributers.
Additional Information
Reviewed by
- Angelo de Caro
- Arnaud J LE HORS
- Christopher Ferris
- Dan Middleton
- Gari Singh
- Hart Montgomery
- Mark Wagner (Deactivated)
- Nathan George
- Swetha Repakula
- Tracy Kuhrt
- Troy Ronda