Project Health
Project health is largely the same as in previous update. We have a number of casual contributors. We still lack maintainer diversity outside of Monax. There is a steady flow of interest and we are pushing plenty of code relating to our continued heavy use of Burrow.
The biggest areas of help would be with tooling and documentation.
We have implemented some EVM opcodes and upgraded our tests to use Solidity 0.5.4 and improved our deploy tool to increase concurrency. All state is now stored in a mutable forest so proof can be given for contract state root (not implemented yet, just the plumbing). Lots of porcelain updates to burrow deploy tool.
Work item | Effort (1, 2, 3, 5, 8, 13) | Priority |
---|---|---|
NameReg extension to support authenticated namespaces (including design) | 13 | Medium |
Burrow-side ABI registry mechanism (probably based on above) | 8 | Low |
Prototype 'new train' WASM execution | 13 | Low |
Implement token economics primitives | 13 | Medium |
Secure access to Burrow chain | 5 | Medium |
We have an active side project looking at using modern compiler tooling to compile Solidity to WASM and are interested in being part of any future movement to share code/structures through WASM execution and interfaces. To that end we are planning to look into the possibility of mounting Go wagon as a WASM interpreter next to our EVM.
We have also been building much business-process-on-a-blockchain functionality with the combination of Burrow and Blackstone our BPM engine implemented in Solidity and Node.JS. We are looking at improving Burrow's native abilities as a process-focussed blockchain. We'd like to explore the possibility of Hyperledger being host to the Blackstone project in some form - it should have relevance to fabric-evm and sawtooth-seth.
We have added one maintainer from Monax and have a new maintainer, Pierrick Hymbert, from outside Monax
Current maintainers are:
Greg Hill (Monax)
Silas Davis (Monax)
Sean Young (Monax)
Casey Kuhlman (Monax)
Tyler Jackson (Monax)
Required: A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve the needs of many parties. Include information on the number of unique organizations currently contributing to the project. NOTE: The contributions do not need to be source code.
Optional: Please provide any additional information that you feel would be useful for TSC to be aware.