Page Comparison

...

https://zoom.us/j/91526040244?pwd=TjExenBQSU9QYUFjSUMrTjg0MCtBQT09

Hyperledger Anti-Trust Policy

Hyperledger Code of Conduct

Attendees:

•  Kevin O'Donnell 
•  James Barry
•  Andi Gunderson 
•  William Katsak 
•  Joseph Livesey
•  Mark Carroll
•  Ryan Roberts
•  Ry Jones 

Purpose:

To keep the Sawtooth 1.x line current and advancing with code and bug fixes. 

...

• Actions updated
  • Kevin O'Donnell proposed a standing agenda for the meetings: proposal for comments here
    • compare agenda from April meeting 

      https://docs.google.com/document/d/108b0LvennbRiXLLs8jHUE1X0gS7hC58y19Ku3hCPHw0/edit?usp=sharing

  • James Barry PR for the TOC report is not filed, but the document is good to go.  James will file the PR

...

1. Main Branch - tangible steps
   1. Kevin and Shawn will work through pieces on Discord
   2. Shawn would like history in main
   3. Apply a patch to main or move certain items to 1.3 and rename it to main
1. Go through main and identify the pieces that should be shifted to main
2. POET consensus  - should this be updated?
   1. There are security issues within the current POET
   2. Reason it is still there lose the ability to handle forking consensus which is not being able to be tested
   3. Augrun is a consensus library that separates consensus code from implementation
   1. To keep researchers from implementing the entire stack
   4. Can POET be lifted into a new area and made more secure and maintainable?
   1. Can it be made a simulator only so people do not use it for production?
   2. Is the breakage Python libraries or Docker libraries?
   3. Joseph will take a look at cleaning up the code and documentation update - main working again with POET
   1. Go through the documentation and remove mentions
   1. James to clean through the documentation and clean up website 
   2. Make it official
1. Most projects are using PBFT
2. Intel SGX is no longer used by the POET available today
3. Is RAFT decommissioned? Make sure that it is sunsetted - 
3. Long running testing
1. Kevin to drop in code and update the long running test framework

1. Bill Katsak will be releasing Hedera consensus so that a Public consensus is available for Sawtooth the private chain
2. Find and identify additional developers working on Sawtooth and have them on this meeting and contribute

How to turn the end user experience into the documents?

Have some Rust code from the Python

1.   Review of any high priority bugs or issues
2. . Open discussion

1. Listing out tools that are used within the project

• • Joseph Livesey - work to refresh and fix the sawtooth-poet  build is ongoing.
  • Kevin O'Donnell - long-running testing
    • still working on contributing a vanilla version of BTP's helm chart. This will include a Helm test which runs a battery of tests against the deployment.  This can be wrapped in a scheduled job to deliver a relatively constant load.
• Actions carried over
  • we need a solid description of the toolchain in use by the projects (docker, docker-compose, etc.)
  • James Barry will scan the available documentation and media for mentions of the RAFT consensus to identify what needs to be touched when we deprecate/decommission it
• Items Discussed
  • a speculative idea to refactor the POET-CFT version to be based on Time Stamp Authorities 
    • https://www.rfc-editor.org/rfc/rfc3161
    • https://freetsa.org/index_en.php
    • Not as secure as SGX, but more secure than CFT alone
    • Would like to talk to Mick Bowen about the algorithm to sanity-check the idea
  •  sawtooth-core:main  is still the 1.99 version and has yet to be switched to the 1-3  branch content. `1-3 ` is where the current work is going.
  • William Katsak Hedera-based consensus is getting ready for release
    • when ready announce on #sawtooth-contributors, and #sawtooth
  • rust-protobuf  is currently unmaintained, which is a problem. The popular choice appears to be prost 
    • should look in to see how disruptive it will be to migrate sawtooth-sdk-rust to prost 
  • Ryan Roberts - has been working on a tokio+TMQ-based sawtooth-sdk
    • will work to get it published so people can see it and form an opinion
    • current known gaps
      • sawtooth client-side only
      • i.e.
        • no TP
        • no consensus side function
        • no signing
    • should look and see how disruptive it would be to incorporate this into sawtooth-sdk-rust
• New Actions
  •  Mark Carroll - In order to get ahead of the types of questions we are getting on #sawtooth, Mark will review the documentation for the setups of the various "getting started" and identify the gaps
  •  Ryan Roberts - check the impact of migrating to prost on sawtooth-sdk-rust 
  •  Ryan Roberts - check the impact of incorporating/enhancing sawtooth-sdk-with the tokio+TMQ version
  •  Ryan Roberts - get the tokio+TMQ SDK published somewhere so it can be poked at 

Recording: