Todd Benzies <tbenzies@...>
Technical Steering Committee (TSC) Meeting
April 7, 2016 (7:00am - 8:30am PT)
F2F at Linux Foundation Collaboration Summit & via GoToMeeting
Deutsche Boerse Group
Richard G. Brown
Action Item Review
Intel - proposed contribution (Patrick Holmes)
Open sourcing project “distributed ledger”
Highly modular and extensible
Gossip topology: Random walk and Barabasi-Albert
Consensus: PoET and Quorum voting
Solution domains: Transaction Families
Proof of Elapsed Time (PoET) Consensus
A power-efficient replacement for proof-of-work
Each node delays a random duration before claiming leadership
Trusted Execution Environment provides attestation
Internal name “Sawtooth”
Sawtooth core is the fundamental component
Sawtooth validator is the validator process (startup, configuration settings, etc.)
Sawtooth marketplace is more complex marketplace
Sawtooth dev tools is the vagrant environment
Documentation on github.io
Developer’s guide with API documentation
Marketplace Developer’s guide to use marketplace code
Q: Going to make a formal proposal?
Q: Is it possible to use SGX with this code?
SGX is on some processors, but not all. We’ve created a PoET simulator. Simulates it running inside SGX, but not actually running inside SGX. So, it is not secure implementation -- only simulating trusted execution environment. Working on plans now for final implementation using a trusted environment.
DM: Algorithm there is algorithm that would run inside of trusted environment. Important aspects is brings consensus back to 1 CPU 1 vote.
Q: Is there a whitepaper or something on this?
Q: How does validation work? Is there an execution engine or scripting engine?
Q: Business use cases? Have you implement like IoT for example? Or other business cases?
Mic: a couple -- used endpoint registry (IoT)... also participated in R3 projects, financial services uses cases. Have tested consensus mechanism with up to 1000 participating validators. 2,000 was highest it was pushed (on VMs).
Q: What language support for smart contract development?
Q: Transaction families support Turing complete language? Or is it more deterministic?
Q: Privacy achieved in executing through SGX environment?
DM: Anticipate doing some unique things in SGX enclaves to support privacy in transaction models.
DV: So wouldn’t be able to implement with current code base?
DM: There isn’t a private facility within this code. Transactions are fairly open. But, nothing restricts you from layering privacy model into it.
Mic: in this release, does not provide some of the fundamental capabilities of doing peer to peer private transactions at this point.
Q: 1 vote / 1 CPU -- how is permission identified?
Discuss and Finalize
Steve Westmoreland suggested everyone get together for .5 day or 1 day to run through tooling needs, driving integration, Gerrit, integrate with Slack and Travis, Jenkins, etc. or whatever for build orchestration.
ACTION: Todd to create Doodle poll -- sometime during next few weeks.
Location: possibly New York or East Coast?
Next Technical F2F
Next Technical F2F. Possibly 1st week of May during Consensus event?
ACTION: Todd to send Doodle poll -- 2 days would be good. Will start soliciting space, as well.
Chris A and Mic to complete the readme for the merged code proposal that was approved
Chris Ferris to move Project Lifecycle on wiki (no longer under proposals)
Chris Ferris to move Project Proposal on wiki (no longer under proposals)
Dave to finalize wording of whitepaper to get in from of Board to review and opine on.
Dave to update minutes for whitepaper WG
Chris Allen to canvass everyone that expressed interest in Identity subgroup, determine if they prefer a list created or just using slack.
Todd to create Doodle poll for Tooling F2F
- Todd to create Doodle poll for Technical F2F
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)