Created by Andrea Gunderson, last modified by David Enyeart on Oct 22, 2020
Hyperledger Sawtooth https://sawtooth.hyperledger.org/
The primary focus of the last quarter was integrating Hyperledger Transact’s transaction execution platform into the Sawtooth Validator.
The Sawtooth community is actively engaging in live, public working sessions to decide Sawtooth’s future. Some community members have expressed interest in contributing to new Sawtooth features, and others have promised to contribute enhancements and features already developed.
No new issues.
- Sawtooth Library v0.4.0 - 8/4/2020
- Sawtooth Library v0.5.0 - 8/13/2020
- Sawtooth Library v0.6.0 - 9/17/2020
- Sawtooth Library v0.6.1 - 9/24/2020
- Sawtooth Library v0.6.2 - 9/29/2020
- Sawtooth Library v0.6.3 - 10/05/2020
- Sawtooth Rust SDK v0.4.5 - 8/4/2020
- Sawtooth Rust SDK v0.5.0 - 9/3/2020
- Sawtooth Sabre v0.6.0 - 9/8/2020
- Sawtooth PBFT v1.03 - 8/5/2020
- Sawtooth Devmode v1.2.4 - 8/4/2020
The community continues to discuss Sawtooth-related issues on Rocketchat. Live working sessions have also been used on a monthly basis to discuss the future of Sawtooth, with strong participation from the community.
The following key work has been completed in the Sawtooth codebase:
- Sawtooth-core now uses Hyperledger Transact for transaction execution. The Python transaction execution platform has been removed from sawtooth-core. This replaces a large chuck of the validator that was still written in Python and updates it to Rust. Transact does not currently support external smart contract engines, so the required smart contracts are now compiled in, including Sawtooth Sabre to support uploading custom smart contracts.
- The transact-compat feature was removed from the Rust SDK. This feature provided a trait implementation for the Transact signer trait for the sawtooth signer. The signer trait was removed in the 0.3 release of Transact.
- More code has been re-written in Rust and moved to the Sawtooth library from the Sawtooth validator. This is a continuation of the efforts to rewrite the Sawtooth validator entirely in Rust and to provide a library of Sawtooth components that can be used in a variety of ledger implementations.
- The infrastructure and theme for the Sawtooth website refresh have been completed in a new branch.
The following work is currently in progress:
- Long running (LR) network testing of the Sawtooth validator with Hyperledger Transact
- Rewriting the Sawtooth CLI in Rust
- Refreshing the Sawtooth website and documentation
The following work is currently planned:
- Create a new consensus library that will be used by the Sawtooth validator
- Initialize a Sawtooth service for Splinter
- Move portions of Sawtooth Sabre to Hyperledger Transact
Plans will continue to be developed as part of the working sessions.
Maintainers are distributed across Bitwise IO, Cargill, Intel, and Walmart Labs.
Commits from 2020-07-01 to 2020-09-31 : 257
Committers from 2020-07-01 to 2020-09-31 : 8
Domains from 2020-07-01 to 2020-09-31 : 3
- ✅ Angelo De Caro
- ✅ Arnaud J Le Hors
- ✅ Arun S M
- ✅ Baohua Yang
- ✅ Bobbi Muscara
- ✅ Danno Ferrin
- ✅ David Enyeart
- ✅ Gari Singh
- ✅ Grace Hartley
- ✅ Hart Montgomery
- ✅ Maria Teresa Nieto
- 🔲 Mark Wagner
- ✅ Nathan George
- ✅ Tracy Kuhrt
- ✅ Troy Ronda
This question is to help welcoming new contributions to the project. The earlier TSC has decided that the sub-projects do not need formal definition. But it will help to maintain project level document th"at mentions how these sub-projects are connected to each other and this document shall be made public. For example, in the current report there is mention of Hyperledger Sawtooth starting to use Hyperledger Transact (which is categorized as library project), also there is mention of Hyperledger Sawtooth Library releases. This could be an ambiguous question for somebody not directly involved, unless they look into the 2.0 release planning document.
Posted by arsulegai at Oct 15, 2020 03:46