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

Compare with Current View Page History

« Previous Version 19 Current »

Hyperledger Sawtooth was moved to end of life status at the request of the maintainers on Feb 1, 2024.  You are welcome to use and contribute to this code, although the maintainers may or may not be responsive to any questions you have.  Note that the developers have said they plan to continue making ongoing maintenance releases of this code in the Splinter community at https://www.splinter.dev/.

Project

Status
CII Badge

DescriptionHyperledger Sawtooth offers a flexible and modular architecture separates the core system from the application domain, so smart contracts can specify the business rules for applications without needing to know the underlying design of the core system. Hyperledger Sawtooth supports a variety of consensus algorithms, including Practical Byzantine Fault Tolerance (PBFT) and Proof of Elapsed Time (PoET).


Originally contributed by Intel, Sawtooth is a blockchain suite designed for versatility and scalability. Distributed Ledger Technology has potential in many fields with use cases from IoT to Financials. This architecture recognizes the diversity of requirements across that spectrum. Sawtooth supports both permissioned and permissionless deployments. It includes a novel consensus algorithm, Proof of Elapsed Time (PoET). PoET targets large distributed validator populations with minimal resource consumption. Transaction business logic is decoupled from the consensus layer into Transaction Families that allow for restricted or unfettered semantics.

Key Characteristics

  • Pluggable consensus algorithms (Change consensus on the fly by transaction)

  • Includes Proof of Elapsed Time (PoET) consensus

  • Write smart contracts in almost any language

  • Ethereum contract support via Hyperledger Burrow integration

  • Supply Chain example out of the box

  • Parallel transaction execution for added throughput

Documentation

Repositories

Discord

To join Hyperledger's Discord, you'll need to do a few things:

  1. First, please install and use a client. Using Discord in the browser is the #1 cause of help desk requests.
  2. Second, you will need to join the Discord server.

For more details on Hyperledger's Discord instance see: Our chat service.

Channels

 There are three Discord channels:

  1. #sawtooth - general discussion / Q&A
  2. #sawtooth-contributors - contributor discussion
  3. #sawtooth-announcements - official announcements

Meetings

Monthly contributor meetings are held on Zoom. You can check the calendar here.

Mailing List

There is a sawtooth mailing list but the most active discussions are on Discord.

Process Notes

  • Release Notes: Release notes will be provided for release 1.0 and thereafter.

  • The project will follow the Hyperledger security bug process and identify any security vulnerabilities fixed in the release.

    • Security bugs: Security bugs can be reported to security@hyperledger.org.

    • The Sawtooth project will follow the HyperLedger security process and will respond within 14 days.

  • Static analysis: The Sawtooth project will follow the Hyperledger security process and address bugs found by static analysis in a timely manner.

  • Dynamic analysis: The Sawtooth project will perform dynamic analysis prior to major releases will follow the Hyperledger security process and address bugs found by static analysis in a timely manner.

History

Space contributors

{"mode":"list","scope":"descendants","limit":"5","showLastTime":"true","order":"update","contextEntityId":120521127}






  • No labels