Date   

[Hyperledger Project TSC] Hyperledger project strawman proposal

Binh Q Nguyen <binhn@...>
 

Hi team,

I thought perhaps we could start with something a bit more concrete for our discussion today on the potential seeds for the project.

(See attached file: IBM Hyperledger Project Proposal - 20160207.pdf)

Thanks,

- Binh


Re: [Hyperledger Project TSC] hyperledger-tsc Digest, Vol 1, Issue 3 - Could calls be recorded for replay

Jeff Menso <JeffMenso@...>
 

Any chance of having calls recorded for replay?




Mobile 0412 699 121



hyperledger-tsc-request---12/02/2016 01:33:53 AM---Send hyperledger-tsc mailing list submissions to hyperledger-tsc@...

From: hyperledger-tsc-request@...
To: hyperledger-tsc@...
Date: 12/02/2016 01:33 AM
Subject: hyperledger-tsc Digest, Vol 1, Issue 3
Sent by: hyperledger-tsc-bounces@...





Send hyperledger-tsc mailing list submissions to
hyperledger-tsc@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
or, via email, send a message with subject or body 'help' to
hyperledger-tsc-request@...

You can reach the person managing the list at
hyperledger-tsc-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of hyperledger-tsc digest..."


Today's Topics:

  1. Proposal for Hyperledger Technical Community Call (Michael Dolan)
  2. Hyperledger project strawman proposal (Binh Q Nguyen)


----------------------------------------------------------------------

Message: 1
Date: Wed, 10 Feb 2016 17:56:18 -0500
From: Michael Dolan <mdolan@...>
To: tsc@..., technical-discuss@...
Subject: [Hyperledger Project TSC] Proposal for Hyperledger Technical
Community Call
Message-ID: <D94ABD57-777F-41FA-BD92-CFCA5917BDAF@...>
Content-Type: text/plain; charset="utf-8"

Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week?s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I?m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn?t want to miss anyone this first week, so I?ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here:
https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

? Mike

Proposed Agenda

I?ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.
Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC?d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as
https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
Discuss where/how to land code. Common question we?re getting is ?where is the code?? Need to discuss how to get proposed code into public review.
Discuss process for getting to a code starting point. Proposal template for evaluation?
Discuss proposals for the common starting points
Networking
BFT
Storage
Cryptographic libraries
Member services
1. Proposed TSC Chair Election Process
Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
Send slate of respective nominees to Silver Members: Thursday, Feb 18th
Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (
http://civs.cs.cornell.edu/)
Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
Election winners announced: Wednesday, Feb 24th
GoToMeeting Instructions

URL:
https://www.gotomeeting.com/join/613310429

You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
United States: +1 (312) 757-3119

Access Code: 613-310-429




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://lists.hyperledger.org/mailman/private/hyperledger-tsc/attachments/20160210/dbc46fb8/attachment.html>

------------------------------

Message: 2
Date: Thu, 11 Feb 2016 09:18:03 -0500
From: "Binh Q Nguyen" <binhn@...>
To: hyperledger-tsc@...
Subject: [Hyperledger Project TSC] Hyperledger project strawman
proposal
Message-ID: <201602111418.u1BEIOmQ014408@...>
Content-Type: text/plain; charset="us-ascii"


Hi team,

I thought perhaps we could start with something a bit more concrete for our
discussion today on the potential seeds for the project.

(See attached file: IBM Hyperledger Project Proposal - 20160207.pdf)

Thanks,

- Binh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://lists.hyperledger.org/mailman/private/hyperledger-tsc/attachments/20160211/2736a6dc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IBM Hyperledger Project Proposal - 20160207.pdf
Type: application/pdf
Size: 572617 bytes
Desc: not available
URL: <
https://lists.hyperledger.org/mailman/private/hyperledger-tsc/attachments/20160211/2736a6dc/attachment.pdf>

------------------------------

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


End of hyperledger-tsc Digest, Vol 1, Issue 3
*********************************************





[Hyperledger Project TSC] Minutes 02.11.16

Todd Benzies <tbenzies@...>
 

Hyperledger Project

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting


TSC Members

Emmanuel Viale

Accenture

Present

Kireeti Reddy

CME Group

N/A

Shaul Kfir

DAH

N/A

Stefan Teis

Deutsche Boerse Group

Present

Pardha Vishnumolakala

DTCC

N/A

Kei Taniuchi

Fujitsu

N/A

TBD

Hitachi

N/A

Chris Ferris

IBM

Present

Mic Bowman

Intel

Present

David Voell

J.P. Morgan

Present

Richard G. Brown

R3

Present


More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc


TSC Chair Elections


  • Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.

  • Process for electing a TSC Chair (from the 11 TSC members)

    • Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page

    • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th

    • Send slate of respective nominees to TSC Members: Thursday, Feb 18th

    • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)

    • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time

    • Election winners announced: Wednesday, Feb 24th

  • The TSC operates in the open (open calls, public list)

  • Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.

  • Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.


Tools/Services



Meeting Cadence


  • Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT

    • Evaluate after 1 month if any changes to cadence or timing are necessary


Code



Template for Proposal Evaluation


  • Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review


Proposals for Common Starting Points


  • Previous discussion

    • Networking

    • BFT

    • Storage

    • Cryptographic libraries

    • Member services

  • Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.

  • Needed:  create a github markdown doc for documenting use cases


Agenda Draft for 2/18 TSC Meeting

  • Discussion on basic use cases to address

  • High-level thoughts on how proposed contributions could be converged

  • Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)


Previous Discussions from Formation Meetings


  • Evaluation Criteria

    • Security

    • Interoperability

    • Scalability

    • Extensibility

    • Deployment Environment

    • Ecosystem

    • Change Management

    • Resilience


  • Functional Requirements

    • Contract Execution Environment

    • Transaction

    • Block of Transactions

    • Network

    • Consensus/Validation

    • Authentication & Entitlements

    • Reference Data




On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:
Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

Proposed Agenda

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.
  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services
1. Proposed TSC Chair Election Process
  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th
GoToMeeting Instructions


You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
United States: +1 (312) 757-3119

Access Code: 613-310-429







--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies


Re: [Hyperledger Project TSC] Minutes 02.11.16

Jesus Diaz Vico <jesus.diaz.vico@...>
 

Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hyperledger Project

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting


TSC Members

Emmanuel Viale

Accenture

Present

Kireeti Reddy

CME Group

N/A

Shaul Kfir

DAH

N/A

Stefan Teis

Deutsche Boerse Group

Present

Pardha Vishnumolakala

DTCC

N/A

Kei Taniuchi

Fujitsu

N/A

TBD

Hitachi

N/A

Chris Ferris

IBM

Present

Mic Bowman

Intel

Present

David Voell

J.P. Morgan

Present

Richard G. Brown

R3

Present


More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc


TSC Chair Elections


  • Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.

  • Process for electing a TSC Chair (from the 11 TSC members)

    • Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page

    • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th

    • Send slate of respective nominees to TSC Members: Thursday, Feb 18th

    • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)

    • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time

    • Election winners announced: Wednesday, Feb 24th

  • The TSC operates in the open (open calls, public list)

  • Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.

  • Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.


Tools/Services



Meeting Cadence


  • Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT

    • Evaluate after 1 month if any changes to cadence or timing are necessary


Code



Template for Proposal Evaluation


  • Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review


Proposals for Common Starting Points


  • Previous discussion

    • Networking

    • BFT

    • Storage

    • Cryptographic libraries

    • Member services

  • Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.

  • Needed:  create a github markdown doc for documenting use cases


Agenda Draft for 2/18 TSC Meeting

  • Discussion on basic use cases to address

  • High-level thoughts on how proposed contributions could be converged

  • Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)


Previous Discussions from Formation Meetings


  • Evaluation Criteria

    • Security

    • Interoperability

    • Scalability

    • Extensibility

    • Deployment Environment

    • Ecosystem

    • Change Management

    • Resilience


  • Functional Requirements

    • Contract Execution Environment

    • Transaction

    • Block of Transactions

    • Network

    • Consensus/Validation

    • Authentication & Entitlements

    • Reference Data




On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:
Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

Proposed Agenda

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.
  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services
1. Proposed TSC Chair Election Process
  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th
GoToMeeting Instructions


You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
United States: +1 (312) 757-3119

Access Code: 613-310-429







--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Jesús Díaz Vico


[Hyperledger Project TSC] Slack access

Thane Thomson <connect@...>
 

Hi everybody!

Thanks so much for the meeting minutes. Is the Slack team only available for TSC purposes, or are technical discussions welcome too? If so, how does a technical contributor (such as I’d like to be) gain access?

Thane


Re: [Hyperledger Project TSC] Minutes 02.11.16

Stefan Buhrmester <buhrmi@...>
 

I don't think we have to consider privacy in an open ledger system. In an open ledger system all information is open. By definition. So there is no private information. If somebody wants to keep information private, he is not supposed to put the information into the system the first place.

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hyperledger Project

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting


TSC Members

Emmanuel Viale

Accenture

Present

Kireeti Reddy

CME Group

N/A

Shaul Kfir

DAH

N/A

Stefan Teis

Deutsche Boerse Group

Present

Pardha Vishnumolakala

DTCC

N/A

Kei Taniuchi

Fujitsu

N/A

TBD

Hitachi

N/A

Chris Ferris

IBM

Present

Mic Bowman

Intel

Present

David Voell

J.P. Morgan

Present

Richard G. Brown

R3

Present


More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc


TSC Chair Elections


  • Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.

  • Process for electing a TSC Chair (from the 11 TSC members)

    • Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page

    • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th

    • Send slate of respective nominees to TSC Members: Thursday, Feb 18th

    • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)

    • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time

    • Election winners announced: Wednesday, Feb 24th

  • The TSC operates in the open (open calls, public list)

  • Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.

  • Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.


Tools/Services



Meeting Cadence


  • Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT

    • Evaluate after 1 month if any changes to cadence or timing are necessary


Code



Template for Proposal Evaluation


  • Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review


Proposals for Common Starting Points


  • Previous discussion

    • Networking

    • BFT

    • Storage

    • Cryptographic libraries

    • Member services

  • Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.

  • Needed:  create a github markdown doc for documenting use cases


Agenda Draft for 2/18 TSC Meeting

  • Discussion on basic use cases to address

  • High-level thoughts on how proposed contributions could be converged

  • Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)


Previous Discussions from Formation Meetings


  • Evaluation Criteria

    • Security

    • Interoperability

    • Scalability

    • Extensibility

    • Deployment Environment

    • Ecosystem

    • Change Management

    • Resilience


  • Functional Requirements

    • Contract Execution Environment

    • Transaction

    • Block of Transactions

    • Network

    • Consensus/Validation

    • Authentication & Entitlements

    • Reference Data




On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:
Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

Proposed Agenda

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.
  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services
1. Proposed TSC Chair Election Process
  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th
GoToMeeting Instructions


You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
United States: +1 (312) 757-3119

Access Code: 613-310-429







--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Jesús Díaz Vico

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Re: [Hyperledger Project TSC] Minutes 02.11.16

Francisco J. Honrubia Moreno <fjhonrubia@...>
 

I think privacy is a key point to be included if we are thinking in a "business ready" system, sometimes by law or by others actors I think privacy mandatory to be considered in this project.

 

Regards,

Fran.

 

De: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] En nombre de Stefan Buhrmester via hyperledger-tsc
Enviado el: viernes, 12 de febrero de 2016 9:23
Para: Jesus Diaz Vico
CC: tsc@...
Asunto: Re: [Hyperledger Project TSC] Minutes 02.11.16

 

I don't think we have to consider privacy in an open ledger system. In an open ledger system all information is open. By definition. So there is no private information. If somebody wants to keep information private, he is not supposed to put the information into the system the first place.

 

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

 

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hyperledger Project

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting

 

TSC Members

Emmanuel Viale

Accenture

Present

Kireeti Reddy

CME Group

N/A

Shaul Kfir

DAH

N/A

Stefan Teis

Deutsche Boerse Group

Present

Pardha Vishnumolakala

DTCC

N/A

Kei Taniuchi

Fujitsu

N/A

TBD

Hitachi

N/A

Chris Ferris

IBM

Present

Mic Bowman

Intel

Present

David Voell

J.P. Morgan

Present

Richard G. Brown

R3

Present

 

More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc

 

TSC Chair Elections

 

·  Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.

·  Process for electing a TSC Chair (from the 11 TSC members)

o Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page

o End nomination period: 9pm Pacific Time on Wednesday, Feb 17th

o Send slate of respective nominees to TSC Members: Thursday, Feb 18th

o Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)

o Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time

o Election winners announced: Wednesday, Feb 24th

·  The TSC operates in the open (open calls, public list)

·  Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.

·  Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.

 

Tools/Services

 

·  IRC:  #hyperledger on freenode.net (has Meetbot)

·  Public lists:  lists.hyperledger.org

·  Slack:  hyperledgerproject.slack.com (it was noted that it is possible to bridge IRC w/ Slack)

·  Wiki would be useful -- Linux Foundation to set up

 

Meeting Cadence

 

·  Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT

o Evaluate after 1 month if any changes to cadence or timing are necessary

 

Code

 

·  Discussion on where and how to land code -- getting proposed code into public review.

·  Should code under review remain on www.github.com/staging-blockchain or be moved to the formal org www.github.com/hyperledger?

o Consensus:  use www.github.com/hyperledger, companies with proposed code can point to their repos from the readme, and note whether those linked repos are either “snapshot” or “ongoing development”

 

Template for Proposal Evaluation

 

·  Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review

 

Proposals for Common Starting Points

 

·  Previous discussion

o Networking

o BFT

o Storage

o Cryptographic libraries

o Member services

·  Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.

·  Needed:  create a github markdown doc for documenting use cases

 

Agenda Draft for 2/18 TSC Meeting

·  Discussion on basic use cases to address

·  High-level thoughts on how proposed contributions could be converged

·  Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)

 

Previous Discussions from Formation Meetings

 

·         Evaluation Criteria

o    Security

o    Interoperability

o    Scalability

o    Extensibility

o    Deployment Environment

o    Ecosystem

o    Change Management

o    Resilience

 

·         Functional Requirements

o    Contract Execution Environment

o    Transaction

o    Block of Transactions

o    Network

o    Consensus/Validation

o    Authentication & Entitlements

o    Reference Data

 

 

 

On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:

Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

 

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

 

I look forward to our discussion tomorrow.

 

— Mike

 

Proposed Agenda

 

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.

  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services

1. Proposed TSC Chair Election Process

  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th

GoToMeeting Instructions

 

 

You can also dial in using your phone.

 

United States (toll-free): 1 877 309 2070

United States: +1 (312) 757-3119

 

Access Code: 613-310-429

 

 

 

 



 

--

Todd Benzies

Senior Program Manager

The Linux Foundation
+1 (415) 412-0310 (m)

Skype: tbenzies

 

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--

Jesús Díaz Vico


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

 


Re: [Hyperledger Project TSC] Minutes 02.11.16

Thane Thomson <connect@...>
 

Perhaps Jesus means, will the ledger system include any information that could potentially be used to identify a person? (e.g. an e-mail address or social security number or company registration number). This is different to using some kind of UUID (for example) to represent the transacting entity, which makes it very difficult/expensive to trace a real-world person.

The UUIDs are and should, of course, be openly and publicly visible, but personal/company information should not. Otherwise this opens companies and individuals up to all sorts of attacks. If there’s no privacy, it’s akin to opening up your personal/business bank account (or transaction log/etc.) for the world to see. Nobody wants that for themselves.

Privacy should be one of the top priorities.


On 12 Feb 2016, at 10:22, Stefan Buhrmester via hyperledger-tsc <hyperledger-tsc@...> wrote:

I don't think we have to consider privacy in an open ledger system. In an open ledger system all information is open. By definition. So there is no private information. If somebody wants to keep information private, he is not supposed to put the information into the system the first place.

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hyperledger Project
Technical Steering Committee (TSC) Meeting
February 11, 2016 (7:00am - 8:30am PT)
via GoToMeeting

TSC Members
Emmanuel Viale
Accenture
Present
Kireeti Reddy
CME Group
N/A
Shaul Kfir
DAH
N/A
Stefan Teis
Deutsche Boerse Group
Present
Pardha Vishnumolakala
DTCC
N/A
Kei Taniuchi
Fujitsu
N/A
TBD
Hitachi
N/A
Chris Ferris
IBM
Present
Mic Bowman
Intel
Present
David Voell
J.P. Morgan
Present
Richard G. Brown
R3
Present

More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc

TSC Chair Elections

  • Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.
  • Process for electing a TSC Chair (from the 11 TSC members)
    • Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page
    • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
    • Send slate of respective nominees to TSC Members: Thursday, Feb 18th
    • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
    • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
    • Election winners announced: Wednesday, Feb 24th
  • The TSC operates in the open (open calls, public list)
  • Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.
  • Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.

Tools/Services


Meeting Cadence

  • Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT
    • Evaluate after 1 month if any changes to cadence or timing are necessary

Code


Template for Proposal Evaluation

  • Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review

Proposals for Common Starting Points

  • Previous discussion
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services
  • Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.
  • Needed:  create a github markdown doc for documenting use cases

Agenda Draft for 2/18 TSC Meeting
  • Discussion on basic use cases to address
  • High-level thoughts on how proposed contributions could be converged
  • Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)

Previous Discussions from Formation Meetings

  • Evaluation Criteria
    • Security
    • Interoperability
    • Scalability
    • Extensibility
    • Deployment Environment
    • Ecosystem
    • Change Management
    • Resilience

  • Functional Requirements
    • Contract Execution Environment
    • Transaction
    • Block of Transactions
    • Network
    • Consensus/Validation
    • Authentication & Entitlements
    • Reference Data



On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:
Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

Proposed Agenda

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.
  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services
1. Proposed TSC Chair Election Process
  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th
GoToMeeting Instructions


You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
United States: +1 (312) 757-3119

Access Code: 613-310-429







--
Todd Benzies
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)
Skype: tbenzies

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Jesús Díaz Vico

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


Re: [Hyperledger Project TSC] Minutes 02.11.16

Ghassan Karame <ghassan.karami@...>
 

Indeed, the fact that the ledger is open should not prevent the integration of privacy-preservation mechanisms. In most use cases, the lack of privacy would constitute a show-stopper to adoption.

Ghassan

Please excuse the brevity. Sent from my phone.

On Feb 12, 2016, at 09:28, Francisco J. Honrubia Moreno via hyperledger-tsc <hyperledger-tsc@...> wrote:

I think privacy is a key point to be included if we are thinking in a "business ready" system, sometimes by law or by others actors I think privacy mandatory to be considered in this project.

 

Regards,

Fran.

 

De: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] En nombre de Stefan Buhrmester via hyperledger-tsc
Enviado el: viernes, 12 de febrero de 2016 9:23
Para: Jesus Diaz Vico
CC: tsc@...
Asunto: Re: [Hyperledger Project TSC] Minutes 02.11.16

 

I don't think we have to consider privacy in an open ledger system. In an open ledger system all information is open. By definition. So there is no private information. If somebody wants to keep information private, he is not supposed to put the information into the system the first place.

 

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

 

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hyperledger Project

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting

 

TSC Members

Emmanuel Viale

Accenture

Present

Kireeti Reddy

CME Group

N/A

Shaul Kfir

DAH

N/A

Stefan Teis

Deutsche Boerse Group

Present

Pardha Vishnumolakala

DTCC

N/A

Kei Taniuchi

Fujitsu

N/A

TBD

Hitachi

N/A

Chris Ferris

IBM

Present

Mic Bowman

Intel

Present

David Voell

J.P. Morgan

Present

Richard G. Brown

R3

Present

 

More information on the TSC Members can be found at https://www.hyperledger.org/about/tsc

 

TSC Chair Elections

 

·  Note:  if you are a Premier member and have not yet notified tbenzies@... of your TSC representative, please do so ASAP.

·  Process for electing a TSC Chair (from the 11 TSC members)

o Begin nomination period: Today, Feb 11th, nominations includes a short bio/pitch less than 1 page

o End nomination period: 9pm Pacific Time on Wednesday, Feb 17th

o Send slate of respective nominees to TSC Members: Thursday, Feb 18th

o Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)

o Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time

o Election winners announced: Wednesday, Feb 24th

·  The TSC operates in the open (open calls, public list)

·  Startup Period: During the first six (6) months after project launch, the TSC voting members shall consist of one (1) appointed representative from each Premier Member and each Top Level Project Maintainer, provided that no company (including related companies or affiliates under common control) shall have more than three (3) votes on the TSC.

·  Steady State: After the Startup Period, there shall be a nomination and election period for electing Contributors or Maintainers to the TSC. The TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors. An Active Contributor is defined as any Contributor who has had a contribution accepted into the codebase during the prior twelve (12) months. The TSC shall approve the process and timing for nominations and elections held on an annual basis.

 

Tools/Services

 

·  IRC:  #hyperledger on freenode.net (has Meetbot)

·  Public lists:  lists.hyperledger.org

·  Slack:  hyperledgerproject.slack.com (it was noted that it is possible to bridge IRC w/ Slack)

·  Wiki would be useful -- Linux Foundation to set up

 

Meeting Cadence

 

·  Consensus:  [weekly] Thursdays, 7:00am - 8:30am PT

o Evaluate after 1 month if any changes to cadence or timing are necessary

 

Code

 

·  Discussion on where and how to land code -- getting proposed code into public review.

·  Should code under review remain on www.github.com/staging-blockchain or be moved to the formal org www.github.com/hyperledger?

o Consensus:  use www.github.com/hyperledger, companies with proposed code can point to their repos from the readme, and note whether those linked repos are either “snapshot” or “ongoing development”

 

Template for Proposal Evaluation

 

·  Stefan Buhrmester and Vipin Bharathan have volunteered to help edit an initial template for TSC review

 

Proposals for Common Starting Points

 

·  Previous discussion

o Networking

o BFT

o Storage

o Cryptographic libraries

o Member services

·  Consensus:  start lower down the stack where people are much closer in agreement, and then slowly work up the stack.

·  Needed:  create a github markdown doc for documenting use cases

 

Agenda Draft for 2/18 TSC Meeting

·  Discussion on basic use cases to address

·  High-level thoughts on how proposed contributions could be converged

·  Walk-through of project proposal template (Stefan Buhrmester and Vipin Bharathan)

 

Previous Discussions from Formation Meetings

 

·         Evaluation Criteria

o    Security

o    Interoperability

o    Scalability

o    Extensibility

o    Deployment Environment

o    Ecosystem

o    Change Management

o    Resilience

 

·         Functional Requirements

o    Contract Execution Environment

o    Transaction

o    Block of Transactions

o    Network

o    Consensus/Validation

o    Authentication & Entitlements

o    Reference Data

 

 

 

On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan <mdolan@...> wrote:

Welcome to the (now official) Hyperledger Community. Thank you to everyone who helped with the launch of the project and getting everything lined up for a very strong start.

 

We have a technical community call scheduled for Thursday at 10am Eastern Time. The GoToMeeting details are below. Our apologies for last week’s disruption with the 25 person limit. We have fixed that issue and now have a 100 person capacity. I’m also copying both the TSC and the technical-discuss mailing lists. In the future, we will just use the TSC mailing list for TSC meetings. However, I didn’t want to miss anyone this first week, so I’ve copied both lists. If you have not signed up for any mailing lists, you will want to do so here: https://lists.hyperledger.org/mailman/listinfo

 

I look forward to our discussion tomorrow.

 

— Mike

 

Proposed Agenda

 

I’ll propose the agenda below for tomorrow, if you have other thoughts / comments, please let me know.

  1. Process for electing a TSC Chair (10 mins). Also, if you are a Premier member and have not yet notified Todd (CC’d) of your TSC Chair representative, please do so ASAP. We will distribute a list of the TSC reps to the TSC when we have everyone identified.
  2. Discussion of tools/services that would be helpful to the community. We have setup IRC:  #hyperledger on freenode with Meetbot. We have the mailing lists. Does the TSC want to see anything else? E.g. Slack? A wiki such as https://wiki.linuxfoundation.org/hyperledger shared wiki or setup wiki.hyperledger.org?
  3. Future meeting day/times? Do we use this time slot for the TSC going forward or does the TSC prefer a different cadence and/or time or day?
  4. Discuss where/how to land code. Common question we’re getting is “where is the code?” Need to discuss how to get proposed code into public review.
  5. Discuss process for getting to a code starting point. Proposal template for evaluation? 
  6. Discuss proposals for the common starting points 
    • Networking
    • BFT
    • Storage
    • Cryptographic libraries
    • Member services

1. Proposed TSC Chair Election Process

  • Begin nomination period: Thursday, Feb 11th, nominations includes a short bio/pitch less than 1 page
  • End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
  • Send slate of respective nominees to Silver Members: Thursday, Feb 18th
  • Send TSC members the ballot link to electronic voting: Thursday, Feb 18th using Condorcet voting (http://civs.cs.cornell.edu/)
  • Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
  • Election winners announced: Wednesday, Feb 24th

GoToMeeting Instructions

 

 

You can also dial in using your phone.

 

United States (toll-free): 1 877 309 2070

United States: +1 (312) 757-3119

 

Access Code: 613-310-429

 

 

 

 



 

--

Todd Benzies

Senior Program Manager

The Linux Foundation
+1 (415) 412-0310 (m)

Skype: tbenzies

 

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--

Jesús Díaz Vico


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

 

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


Re: [Hyperledger Project TSC] Minutes 02.11.16

Stefan Buhrmester <buhrmi@...>
 

As I said, if you don't want the world to see your personal/business account details​, simply don't put them in the ledger. That's the privacy-preservation mechanism. The ledger won't know anything about your personal details unless you feed them to it. A ledger in the historical sense is a book. An empty book has no information until somebody writes information to it. The author should not be concerned about who's going to read the book. If the author has something to hide, he should not write it into the book.


Re: [Hyperledger Project TSC] Minutes 02.11.16

Jesus Diaz Vico <jesus.diaz.vico@...>
 

It may not be necessary to put personal/business details into the blockchain to threaten privacy. See, for instance, the paper "Evaluating User Privacy in Bitcoin" (https://eprint.iacr.org/2012/596.pdf).

But again, the level of privacy that a ledger achieves will depend on the specific use cases that it has been built for, so we just cannot say now whether it would or would not be private. And that is precisely my point. Once there are specific proposals and use cases, whether or not privacy is achieved should be taken into account.

On Fri, Feb 12, 2016 at 9:47 AM, Stefan Buhrmester <buhrmi@...> wrote:
As I said, if you don't want the world to see your personal/business account details​, simply don't put them in the ledger. That's the privacy-preservation mechanism. The ledger won't know anything about your personal details unless you feed them to it. A ledger in the historical sense is a book. An empty book has no information until somebody writes information to it. The author should not be concerned about who's going to read the book. If the author has something to hide, he should not write it into the book.



--
Jesús Díaz Vico


Re: [Hyperledger Project TSC] Minutes 02.11.16

Fabian Schuh <fabian@...>
 

I think privacy is an integral part of blockchains.

If you consider integrating a Bond Market into a blockchain (which you technically could do), then Privacy evolves into a requirement. Otherwise you could
profit from force liquidate other positions.
It's like playing poker on a blockchain (which you could also technically do) .. but if you know your enemies hands .. well .. you shouldn't "play".

In short, Privacy (by what every technological means) is VERY important for any future blockchain!

Cheers
-- Fabian

On 02/12/2016 09:43 AM, Ghassan Karame via hyperledger-tsc wrote:
Indeed, the fact that the ledger is open should not prevent the integration of privacy-preservation mechanisms. In most use cases, the lack of privacy would constitute a show-stopper to adoption.

Ghassan

Please excuse the brevity. Sent from my phone.

On Feb 12, 2016, at 09:28, Francisco J. Honrubia Moreno via hyperledger-tsc <hyperledger-tsc@... <mailto:hyperledger-tsc@...>> wrote:

I think privacy is a key point to be included if we are thinking in a "business ready" system, sometimes by law or by others actors I think privacy mandatory to be considered in this project.

Regards,

Fran.

*De:*hyperledger-tsc-bounces@... <mailto:hyperledger-tsc-bounces@...> [mailto:hyperledger-tsc-bounces@...] *En nombre de *Stefan Buhrmester via hyperledger-tsc
*Enviado el:* viernes, 12 de febrero de 2016 9:23
*Para:* Jesus Diaz Vico
*CC:* tsc@... <mailto:tsc@...>
*Asunto:* Re: [Hyperledger Project TSC] Minutes 02.11.16

I don't think we have to consider privacy in an open ledger system. In an open ledger system all information is open. By definition. So there is no private information. If somebody wants to keep information private, he is not supposed to put the information into the system the first place.

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc <hyperledger-tsc@... <mailto:hyperledger-tsc@...>> wrote:

Hi all.

Thanks for the email, it is very useful for all of us who could not attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being considered as part of the security criteria (or any other criteria, although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give it a thought. A system may be really secure (in terms of confidentiality (!= privacy), integrity, availability and so on) against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a proposal may be privacy-respectful depending on the use case For instance, private "enough" for conventional value transactions, but not private enough for managing information storage.

Best,

Jesus

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@... <mailto:hyperledger-tsc@...>> wrote:

*Hyperledger Project*

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting

*TSC Members*

Emmanuel Viale



Accenture



Present

Kireeti Reddy



CME Group



N/A

Shaul Kfir



DAH



N/A

Stefan Teis



Deutsche Boerse Group



Present

Pardha Vishnumolakala



DTCC



N/A

Kei Taniuchi



Fujitsu



N/A

TBD



Hitachi



N/A

Chris Ferris



IBM



Present

Mic Bowman



Intel



Present

David Voell



J.P. Morgan



Present

Richard G. Brown



R3



Present

More information on the TSC Members can be found at
https://www.hyperledger.org/about/tsc

*TSC Chair Elections*

·Note: if you are a Premier member and have not yet notified
tbenzies@...
<mailto:tbenzies@...> of your TSC representative,
please do so ASAP.

·Process for electing a TSC Chair (from the 11 TSC members)

o*Begin nomination period:*Today, Feb 11th, nominations includes
a short bio/pitch less than 1 page

o*End nomination period:*9pm Pacific Time on Wednesday, Feb 17th

o*Send slate of respective nominees to TSC Members:*Thursday, Feb
18th

o*Send TSC members the ballot link to electronic
voting:*Thursday, Feb 18th using Condorcet voting
(http://civs.cs.cornell.edu/ <http://civs.cs.cornell.edu/>)

o*Voting period ends:*Tuesday, Feb 23rd at 9pm Pacific Time

o*Election winners announced:*Wednesday, Feb 24th

·The TSC operates in the open (open calls, public list)

·Startup Period: During the first six (6) months after project
launch, the TSC voting members shall consist of one (1) appointed
representative from each Premier Member and each Top Level
Project Maintainer, provided that no company (including related
companies or affiliates under common control) shall have more
than three (3) votes on the TSC.

·Steady State: After the Startup Period, there shall be a
nomination and election period for electing Contributors or
Maintainers to the TSC. The TSC voting members shall consist of
eleven (11) elected Contributors or Maintainers chosen by the
Active Contributors. An Active Contributor is defined as any
Contributor who has had a contribution accepted into the codebase
during the prior twelve (12) months. The TSC shall approve the
process and timing for nominations and elections held on an
annual basis.

*Tools/Services*

·IRC: #hyperledger on freenode.net <http://freenode.net> (has
Meetbot)

·Public lists: lists.hyperledger.org <http://lists.hyperledger.org>

·Slack: hyperledgerproject.slack.com
<http://hyperledgerproject.slack.com> (it was noted that it is
possible to bridge IRC w/ Slack)

·Wiki would be useful -- Linux Foundation to set up

*Meeting Cadence*

·Consensus: [weekly] Thursdays, 7:00am - 8:30am PT

oEvaluate after 1 month if any changes to cadence or timing are
necessary

*Code*

·Discussion on where and how to land code -- getting proposed
code into public review.

·Should code under review remain on
www.github.com/staging-blockchain
<http://www.github.com/staging-blockchain> or be moved to the
formal org www.github.com/hyperledger
<http://www.github.com/hyperledger>?

oConsensus: use www.github.com/hyperledger
<http://www.github.com/hyperledger>, companies with proposed code
can point to their repos from the readme, and note whether those
linked repos are either “snapshot” or “ongoing development”

*Template for Proposal Evaluation*

·Stefan Buhrmester and Vipin Bharathan have volunteered to help
edit an initial template for TSC review

*Proposals for Common Starting Points*

·Previous discussion

oNetworking

oBFT

oStorage

oCryptographic libraries

oMember services

·Consensus: start lower down the stack where people are much
closer in agreement, and then slowly work up the stack.

·Needed: create a github markdown doc for documenting use cases

*Agenda Draft for 2/18 TSC Meeting*

·Discussion on basic use cases to address

·High-level thoughts on how proposed contributions could be converged

·Walk-through of project proposal template (Stefan Buhrmester and
Vipin Bharathan)

*Previous Discussions from Formation Meetings*

·Evaluation Criteria

oSecurity

oInteroperability

oScalability

oExtensibility

oDeployment Environment

oEcosystem

oChange Management

oResilience

·Functional Requirements

oContract Execution Environment

oTransaction

oBlock of Transactions

oNetwork

oConsensus/Validation

oAuthentication & Entitlements

oReference Data

On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan
<mdolan@... <mailto:mdolan@...>>
wrote:

Welcome to the (now official) Hyperledger Community. Thank you to
everyone who helped with the launch of the project and getting
everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am
Eastern Time. The GoToMeeting details are below. Our apologies
for last week’s disruption with the 25 person limit. We have
fixed that issue and now have a 100 person capacity. I’m also
copying both the TSC and the technical-discuss mailing lists. In
the future, we will just use the TSC mailing list for TSC
meetings. However, I didn’t want to miss anyone this first week,
so I’ve copied both lists. If you have not signed up for any
mailing lists, you will want to do so here:
https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

*Proposed Agenda*

I’ll propose the agenda below for tomorrow, if you have other
thoughts / comments, please let me know.

1. Process for electing a TSC Chair (10 mins). Also, if you are
a Premier member and have not yet notified Todd (CC’d) of
your TSC Chair representative, please do so ASAP. We will
distribute a list of the TSC reps to the TSC when we have
everyone identified.
2. Discussion of tools/services that would be helpful to the
community. We have setup IRC: #hyperledger on freenode with
Meetbot. We have the mailing lists. Does the TSC want to see
anything else? E.g. Slack? A wiki such as
https://wiki.linuxfoundation.org/hyperledger shared wiki or
setup wiki.hyperledger.org <http://wiki.hyperledger.org>?
3. Future meeting day/times? Do we use this time slot for the
TSC going forward or does the TSC prefer a different cadence
and/or time or day?
4. Discuss where/how to land code. Common question we’re getting
is “where is the code?” Need to discuss how to get proposed
code into public review.
5. Discuss process for getting to a code starting point.
Proposal template for evaluation?
6. Discuss proposals for the common starting points

* Networking
* BFT
* Storage
* Cryptographic libraries
* Member services

*1. Proposed TSC Chair Election Process*

* Begin nomination period: Thursday, Feb 11th, nominations
includes a short bio/pitch less than 1 page
* End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
* Send slate of respective nominees
to Silver Members: Thursday, Feb 18th
* Send TSC members the ballot link to electronic
voting: Thursday, Feb 18th using Condorcet voting
(http://civs.cs.cornell.edu/ <http://civs.cs.cornell.edu/>)
* Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
* Election winners announced: Wednesday, Feb 24th

*GoToMeeting Instructions*

URL: https://www.gotomeeting.com/join/613310429

You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
<tel:1%20877%20309%202070>

United States: +1 (312) 757-3119
<tel:%2B1%20%28312%29%20757-3119>

Access Code: 613-310-429



--

*Todd Benzies*

Senior Program Manager

The Linux Foundation
+1 (415) 412-0310 <tel:%2B1%20%28415%29%20412-0310> (m)

tbenzies@... <mailto:tbenzies@...>

Skype: tbenzies

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
<mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--

Jesús Díaz Vico


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@... <mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@... <mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

*Fabian Schuh* / Business Developer, Technical Consultant
fabian@... <mailto:fabian@...>


CRYPTONOMEX, INC.

2020 Kraft Dr Suite 3040
Blacksburg, VA 24060
www.cryptonomex.com <https://www.cryptonomex.com>

<https://www.linkedin.com/company/cryptonomex-inc-> <https://github.com/cryptonomex> <https://twitter.com/cryptonomex> <https://www.facebook.com/cryptonomex>

Cryptonomex is a leading supplier of advanced block chain technology. That can range from simple advice, to deployment of your application on one of our public block chains, to creating your own private chain


Re: [Hyperledger Project TSC] Slack access

Christopher B Ferris <chrisfer@...>
 

Slack is open to everyone, but because Slack has a more enterprise login approach, we have to add the domains.
 
Todd will you please add any domains of members not already white-listed?
 
Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Open Technology
IBM Cloud, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: https://developer.ibm.com/opentech/author/chrisfer/
phone: +1 508 667 0402
 
 

----- Original message -----
From: Thane Thomson via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: hyperledger-tsc@...
Cc:
Subject: [Hyperledger Project TSC] Slack access
Date: Fri, Feb 12, 2016 3:53 AM
 
Hi everybody!

Thanks so much for the meeting minutes. Is the Slack team only available for TSC purposes, or are technical discussions welcome too? If so, how does a technical contributor (such as I’d like to be) gain access?

Thane
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 


Re: [Hyperledger Project TSC] Minutes 02.11.16

Duc.M.Trinh@...
 

Is the goal to support anonymity (from an identity perspective) or is the goal to mask the actual contents/value of your transactions? IMO, the former is a reasonable requirement. However, the latter seems contradictory to the original purpose of the blockchain.

--
Duc M. Trinh @ Wells Fargo

-----Original Message-----
From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of Fabian Schuh via hyperledger-tsc
Sent: Friday, February 12, 2016 5:11 AM
To: hyperledger-tsc@...
Subject: Re: [Hyperledger Project TSC] Minutes 02.11.16

I think privacy is an integral part of blockchains.

If you consider integrating a Bond Market into a blockchain (which you technically could do), then Privacy evolves into a requirement.
Otherwise you could
profit from force liquidate other positions.
It's like playing poker on a blockchain (which you could also technically do) .. but if you know your enemies hands .. well .. you shouldn't "play".

In short, Privacy (by what every technological means) is VERY important for any future blockchain!

Cheers
-- Fabian

On 02/12/2016 09:43 AM, Ghassan Karame via hyperledger-tsc wrote:
Indeed, the fact that the ledger is open should not prevent the
integration of privacy-preservation mechanisms. In most use cases, the
lack of privacy would constitute a show-stopper to adoption.

Ghassan

Please excuse the brevity. Sent from my phone.

On Feb 12, 2016, at 09:28, Francisco J. Honrubia Moreno via
hyperledger-tsc <hyperledger-tsc@...
<mailto:hyperledger-tsc@...>> wrote:

I think privacy is a key point to be included if we are thinking in a
"business ready" system, sometimes by law or by others actors I think
privacy mandatory to be considered in this project.

Regards,

Fran.

*De:*hyperledger-tsc-bounces@...
<mailto:hyperledger-tsc-bounces@...>
[mailto:hyperledger-tsc-bounces@...] *En nombre de
*Stefan Buhrmester via hyperledger-tsc *Enviado el:* viernes, 12 de
febrero de 2016 9:23
*Para:* Jesus Diaz Vico
*CC:* tsc@... <mailto:tsc@...>
*Asunto:* Re: [Hyperledger Project TSC] Minutes 02.11.16

I don't think we have to consider privacy in an open ledger system.
In an open ledger system all information is open. By definition. So
there is no private information. If somebody wants to keep
information private, he is not supposed to put the information into
the system the first place.

On Fri, Feb 12, 2016 at 5:10 PM, Jesus Diaz Vico via hyperledger-tsc
<hyperledger-tsc@...
<mailto:hyperledger-tsc@...>> wrote:

Hi all.

Thanks for the email, it is very useful for all of us who could not
attend the complete meeting (or attend at all).

One doubt/comment about the evaluation criteria. Is privacy being
considered as part of the security criteria (or any other criteria,
although I'd say that it fits better in security, if any) or not at all?

If not being considered either explicitly nor implicitly, I'll give
it a thought. A system may be really secure (in terms of
confidentiality (!= privacy), integrity, availability and so on)
against any kind of considered attacker, but still lack privacy.

In the concrete context of blockchain, as in most other contexts, a
proposal may be privacy-respectful depending on the use case For
instance, private "enough" for conventional value transactions, but
not private enough for managing information storage.

Best,

Jesus

On Fri, Feb 12, 2016 at 1:11 AM, Todd Benzies via hyperledger-tsc
<hyperledger-tsc@...
<mailto:hyperledger-tsc@...>> wrote:

*Hyperledger Project*

Technical Steering Committee (TSC) Meeting

February 11, 2016 (7:00am - 8:30am PT)

via GoToMeeting

*TSC Members*

Emmanuel Viale



Accenture



Present

Kireeti Reddy



CME Group



N/A

Shaul Kfir



DAH



N/A

Stefan Teis



Deutsche Boerse Group



Present

Pardha Vishnumolakala



DTCC



N/A

Kei Taniuchi



Fujitsu



N/A

TBD



Hitachi



N/A

Chris Ferris



IBM



Present

Mic Bowman



Intel



Present

David Voell



J.P. Morgan



Present

Richard G. Brown



R3



Present

More information on the TSC Members can be found at
https://www.hyperledger.org/about/tsc

*TSC Chair Elections*

·Note: if you are a Premier member and have not yet notified
tbenzies@...
<mailto:tbenzies@...> of your TSC representative,
please do so ASAP.

·Process for electing a TSC Chair (from the 11 TSC members)

o*Begin nomination period:*Today, Feb 11th, nominations includes
a short bio/pitch less than 1 page

o*End nomination period:*9pm Pacific Time on Wednesday, Feb 17th

o*Send slate of respective nominees to TSC Members:*Thursday, Feb
18th

o*Send TSC members the ballot link to electronic
voting:*Thursday, Feb 18th using Condorcet voting
(http://civs.cs.cornell.edu/ <http://civs.cs.cornell.edu/>)

o*Voting period ends:*Tuesday, Feb 23rd at 9pm Pacific Time

o*Election winners announced:*Wednesday, Feb 24th

·The TSC operates in the open (open calls, public list)

·Startup Period: During the first six (6) months after project
launch, the TSC voting members shall consist of one (1) appointed
representative from each Premier Member and each Top Level
Project Maintainer, provided that no company (including related
companies or affiliates under common control) shall have more
than three (3) votes on the TSC.

·Steady State: After the Startup Period, there shall be a
nomination and election period for electing Contributors or
Maintainers to the TSC. The TSC voting members shall consist of
eleven (11) elected Contributors or Maintainers chosen by the
Active Contributors. An Active Contributor is defined as any
Contributor who has had a contribution accepted into the codebase
during the prior twelve (12) months. The TSC shall approve the
process and timing for nominations and elections held on an
annual basis.

*Tools/Services*

·IRC: #hyperledger on freenode.net <http://freenode.net> (has
Meetbot)

·Public lists: lists.hyperledger.org
<http://lists.hyperledger.org>

·Slack: hyperledgerproject.slack.com
<http://hyperledgerproject.slack.com> (it was noted that it is
possible to bridge IRC w/ Slack)

·Wiki would be useful -- Linux Foundation to set up

*Meeting Cadence*

·Consensus: [weekly] Thursdays, 7:00am - 8:30am PT

oEvaluate after 1 month if any changes to cadence or timing are
necessary

*Code*

·Discussion on where and how to land code -- getting proposed
code into public review.

·Should code under review remain on
www.github.com/staging-blockchain
<http://www.github.com/staging-blockchain> or be moved to the
formal org www.github.com/hyperledger
<http://www.github.com/hyperledger>?

oConsensus: use www.github.com/hyperledger
<http://www.github.com/hyperledger>, companies with proposed code
can point to their repos from the readme, and note whether those
linked repos are either “snapshot” or “ongoing development”

*Template for Proposal Evaluation*

·Stefan Buhrmester and Vipin Bharathan have volunteered to help
edit an initial template for TSC review

*Proposals for Common Starting Points*

·Previous discussion

oNetworking

oBFT

oStorage

oCryptographic libraries

oMember services

·Consensus: start lower down the stack where people are much
closer in agreement, and then slowly work up the stack.

·Needed: create a github markdown doc for documenting use cases

*Agenda Draft for 2/18 TSC Meeting*

·Discussion on basic use cases to address

·High-level thoughts on how proposed contributions could be
converged

·Walk-through of project proposal template (Stefan Buhrmester and
Vipin Bharathan)

*Previous Discussions from Formation Meetings*

·Evaluation Criteria

oSecurity

oInteroperability

oScalability

oExtensibility

oDeployment Environment

oEcosystem

oChange Management

oResilience

·Functional Requirements

oContract Execution Environment

oTransaction

oBlock of Transactions

oNetwork

oConsensus/Validation

oAuthentication & Entitlements

oReference Data

On Wed, Feb 10, 2016 at 2:56 PM, Michael Dolan
<mdolan@... <mailto:mdolan@...>>
wrote:

Welcome to the (now official) Hyperledger Community. Thank you to
everyone who helped with the launch of the project and getting
everything lined up for a very strong start.

We have a technical community call scheduled for Thursday at 10am
Eastern Time. The GoToMeeting details are below. Our apologies
for last week’s disruption with the 25 person limit. We have
fixed that issue and now have a 100 person capacity. I’m also
copying both the TSC and the technical-discuss mailing lists. In
the future, we will just use the TSC mailing list for TSC
meetings. However, I didn’t want to miss anyone this first week,
so I’ve copied both lists. If you have not signed up for any
mailing lists, you will want to do so here:
https://lists.hyperledger.org/mailman/listinfo

I look forward to our discussion tomorrow.

— Mike

*Proposed Agenda*

I’ll propose the agenda below for tomorrow, if you have other
thoughts / comments, please let me know.

1. Process for electing a TSC Chair (10 mins). Also, if you are
a Premier member and have not yet notified Todd (CC’d) of
your TSC Chair representative, please do so ASAP. We will
distribute a list of the TSC reps to the TSC when we have
everyone identified.
2. Discussion of tools/services that would be helpful to the
community. We have setup IRC: #hyperledger on freenode with
Meetbot. We have the mailing lists. Does the TSC want to see
anything else? E.g. Slack? A wiki such as
https://wiki.linuxfoundation.org/hyperledger shared wiki or
setup wiki.hyperledger.org <http://wiki.hyperledger.org>?
3. Future meeting day/times? Do we use this time slot for the
TSC going forward or does the TSC prefer a different cadence
and/or time or day?
4. Discuss where/how to land code. Common question we’re getting
is “where is the code?” Need to discuss how to get proposed
code into public review.
5. Discuss process for getting to a code starting point.
Proposal template for evaluation?
6. Discuss proposals for the common starting points

* Networking
* BFT
* Storage
* Cryptographic libraries
* Member services

*1. Proposed TSC Chair Election Process*

* Begin nomination period: Thursday, Feb 11th, nominations
includes a short bio/pitch less than 1 page
* End nomination period: 9pm Pacific Time on Wednesday, Feb 17th
* Send slate of respective nominees
to Silver Members: Thursday, Feb 18th
* Send TSC members the ballot link to electronic
voting: Thursday, Feb 18th using Condorcet voting
(http://civs.cs.cornell.edu/ <http://civs.cs.cornell.edu/>)
* Voting period ends: Tuesday, Feb 23rd at 9pm Pacific Time
* Election winners announced: Wednesday, Feb 24th

*GoToMeeting Instructions*

URL: https://www.gotomeeting.com/join/613310429

You can also dial in using your phone.

United States (toll-free): 1 877 309 2070
<tel:1%20877%20309%202070>

United States: +1 (312) 757-3119
<tel:%2B1%20%28312%29%20757-3119>

Access Code: 613-310-429



--

*Todd Benzies*

Senior Program Manager

The Linux Foundation
+1 (415) 412-0310 <tel:%2B1%20%28415%29%20412-0310> (m)

tbenzies@...
<mailto:tbenzies@...>

Skype: tbenzies

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
<mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--

Jesús Díaz Vico


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
<mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
<mailto:hyperledger-tsc@...>
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

*Fabian Schuh* / Business Developer, Technical Consultant fabian@... <mailto:fabian@...>


CRYPTONOMEX, INC.

2020 Kraft Dr Suite 3040
Blacksburg, VA 24060
www.cryptonomex.com <https://www.cryptonomex.com>

<https://www.linkedin.com/company/cryptonomex-inc->
<https://github.com/cryptonomex> <https://twitter.com/cryptonomex> <https://www.facebook.com/cryptonomex>

Cryptonomex is a leading supplier of advanced block chain technology.
That can range from simple advice, to deployment of your application on one of our public block chains, to creating your own private chain

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


[Hyperledger Project TSC] Suggestion to make this list moderated

Allen
 

I would suggest that this list (hyperledger-tsc) be turned into a moderated list.  Otherwise, all kinds of technical discussions are going to end up posted to this list (or cross posted to this list) when they should be posted to only to hyperledger-technical-discuss.  Leaving this list unmoderated will cause confusion and undermine the reason two lists were set up in the first place...


Re: [Hyperledger Project TSC] Minutes 02.11.16

Fabian Schuh <fabian@...>
 

I agree that we need to distinguish
a) identity privacy from
b) transaction content privacy
and it depends on the purpose of the blockchain and the kind of transactions that you want to use on the blockchain.

For instance, if you just want to transfer a token (such as bitcoin), you don't need to actually hide the amount of tokens transfered (even though that would be very well possible, such that only sender and receiver can figure out the actual amount).
But, as described in the other mail, if you want to put a decentralized exchange or a bond market on a blockchain, you NEED to hide prices/amounts to not be the victim of
people that misuse the information to cheat your 'orders' .. such as short orders or loans in a bond market.

Another use case wold be health insurance. You can put your health data in a public blockchain, but you want that only your doctors are able to decrypt it and not everyone else.

All of what I said above is technologically feasible today.

Cheers
-- Fabian

On 02/12/2016 03:59 PM, Duc.M.Trinh@... wrote:
Is the goal to support anonymity (from an identity perspective) or is the goal to mask the actual contents/value of your transactions? IMO, the former is a reasonable requirement. However, the latter seems contradictory to the original purpose of the blockchain.
--

*Fabian Schuh* / Business Developer, Technical Consultant
fabian@... <mailto:fabian@...>


CRYPTONOMEX, INC.

2020 Kraft Dr Suite 3040
Blacksburg, VA 24060
www.cryptonomex.com <https://www.cryptonomex.com>

<https://www.linkedin.com/company/cryptonomex-inc-> <https://github.com/cryptonomex> <https://twitter.com/cryptonomex> <https://www.facebook.com/cryptonomex>

Cryptonomex is a leading supplier of advanced block chain technology. That can range from simple advice, to deployment of your application on one of our public block chains, to creating your own private chain


Re: [Hyperledger Project TSC] Minutes 02.11.16

Binh Q Nguyen <binhn@...>
 

+1

In OBC, we differentiate between privacy (your a) from confidentiality (your b) and provide both as options, depending on the requirements of the blockchain deployment.

- Binh

Fabian Schuh via hyperledger-tsc ---02/12/2016 10:56:59 AM---I agree that we need to distinguish a) identity privacy from

From: Fabian Schuh via hyperledger-tsc <hyperledger-tsc@...>
To: Duc.M.Trinh@...
Cc: hyperledger-tsc@...
Date: 02/12/2016 10:56 AM
Subject: Re: [Hyperledger Project TSC] Minutes 02.11.16
Sent by: hyperledger-tsc-bounces@...





I agree that we need to distinguish
a) identity privacy from
b) transaction content privacy
and it depends on the purpose of the blockchain and the kind of
transactions that you want to use on the blockchain.

For instance, if you just want to transfer a token (such as bitcoin),
you don't need to actually hide the amount of tokens transfered (even
though that would be very well possible, such that only sender and
receiver can figure out the actual amount).
But, as described in the other mail, if you want to put a decentralized
exchange or a bond market on a blockchain, you NEED to hide
prices/amounts to not be the victim of
people that misuse the information to cheat your 'orders' .. such as
short orders or loans in a bond market.

Another use case wold be health insurance. You can put your health data
in a public blockchain, but you want that only your doctors are able to
decrypt it and not everyone else.

All of what I said above is technologically feasible today.

Cheers
 -- Fabian


On 02/12/2016 03:59 PM, Duc.M.Trinh@... wrote:
> Is the goal to support anonymity (from an identity perspective) or is the goal to mask the actual contents/value of your transactions?  IMO, the former is a reasonable requirement.  However, the latter seems contradictory to the original purpose of the blockchain.
>

--

*Fabian Schuh* / Business Developer, Technical Consultant
fabian@... <mailto:fabian@...>


   CRYPTONOMEX, INC.

2020 Kraft Dr Suite 3040
Blacksburg, VA 24060
www.cryptonomex.com <https://www.cryptonomex.com>

<
https://www.linkedin.com/company/cryptonomex-inc->
<
https://github.com/cryptonomex> <https://twitter.com/cryptonomex>
<
https://www.facebook.com/cryptonomex>

Cryptonomex is a leading supplier of advanced block chain technology.
That can range from simple advice, to deployment of your application on
one of our public block chains, to creating your own private chain

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




Re: [Hyperledger Project TSC] Suggestion to make this list moderated

Christopher B Ferris <chrisfer@...>
 

+1, great idea
 
Todd, wonder if you could set that up?
 
Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Open Technology
IBM Cloud, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: https://developer.ibm.com/opentech/author/chrisfer/
phone: +1 508 667 0402
 
 

----- Original message -----
From: Allen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: hyperledger-tsc@...
Cc:
Subject: [Hyperledger Project TSC] Suggestion to make this list moderated
Date: Fri, Feb 12, 2016 10:54 AM
 
I would suggest that this list (hyperledger-tsc) be turned into a moderated list.  Otherwise, all kinds of technical discussions are going to end up posted to this list (or cross posted to this list) when they should be posted to only to hyperledger-technical-discuss.  Leaving this list unmoderated will cause confusion and undermine the reason two lists were set up in the first place...
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 


Re: [Hyperledger Project TSC] Minutes 02.11.16

Harsh Patel
 

Hi Fabian,

In such a situation from system design end we would need a blockchains which has three mode of operation. 
  • Public mode (No Privacy) 
  • Semi Private ( Limited parameters of the application kept private.) 
  • Fully private operation  (All Parameters kept private )
Where by keeping the amount of privacy, at the disposal of the user. As all three modes have their own use cases and application. In case of fully private operation would be application for Health records. 

--
Regards 

Harsh

On Fri, Feb 12, 2016 at 9:25 PM, Fabian Schuh via hyperledger-tsc <hyperledger-tsc@...> wrote:
I agree that we need to distinguish
a) identity privacy from
b) transaction content privacy
and it depends on the purpose of the blockchain and the kind of transactions that you want to use on the blockchain.

For instance, if you just want to transfer a token (such as bitcoin), you don't need to actually hide the amount of tokens transfered (even though that would be very well possible, such that only sender and receiver can figure out the actual amount).
But, as described in the other mail, if you want to put a decentralized exchange or a bond market on a blockchain, you NEED to hide prices/amounts to not be the victim of
people that misuse the information to cheat your 'orders' .. such as short orders or loans in a bond market.

Another use case wold be health insurance. You can put your health data in a public blockchain, but you want that only your doctors are able to decrypt it and not everyone else.

All of what I said above is technologically feasible today.

Cheers
 -- Fabian

On 02/12/2016 03:59 PM, Duc.M.Trinh@... wrote:
Is the goal to support anonymity (from an identity perspective) or is the goal to mask the actual contents/value of your transactions?  IMO, the former is a reasonable requirement.  However, the latter seems contradictory to the original purpose of the blockchain.


--

*Fabian Schuh* / Business Developer, Technical Consultant
fabian@... <mailto:fabian@...>


   CRYPTONOMEX, INC.

2020 Kraft Dr Suite 3040
Blacksburg, VA 24060
www.cryptonomex.com <https://www.cryptonomex.com>

<https://www.linkedin.com/company/cryptonomex-inc-> <https://github.com/cryptonomex> <https://twitter.com/cryptonomex> <https://www.facebook.com/cryptonomex>

Cryptonomex is a leading supplier of advanced block chain technology. That can range from simple advice, to deployment of your application on one of our public block chains, to creating your own private chain

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


Re: [Hyperledger Project TSC] Suggestion to make this list moderated

Dan O'Prey <dan@...>
 

+1

Would be good to be read only for anyone but posting restricted to TSC members.

sent from a phone, excuse typos

On Feb 12, 2016 11:30 AM, "Christopher B Ferris via hyperledger-tsc" <hyperledger-tsc@...> wrote:
+1, great idea
 
Todd, wonder if you could set that up?
 
Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Open Technology
IBM Cloud, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: https://developer.ibm.com/opentech/author/chrisfer/
phone: +1 508 667 0402
 
 
----- Original message -----
From: Allen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: hyperledger-tsc@...
Cc:
Subject: [Hyperledger Project TSC] Suggestion to make this list moderated
Date: Fri, Feb 12, 2016 10:54 AM
 
I would suggest that this list (hyperledger-tsc) be turned into a moderated list.  Otherwise, all kinds of technical discussions are going to end up posted to this list (or cross posted to this list) when they should be posted to only to hyperledger-technical-discuss.  Leaving this list unmoderated will cause confusion and undermine the reason two lists were set up in the first place...
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.

1 - 20 of 3873