toc@lists.hyperledger.org

[Hyperledger Project TSC] Hyperledger project strawman proposal

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 -

By Binh Q Nguyen <binhn@...> · #1 ·

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

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:

By Jeff Menso <JeffMenso@...> · #2 ·

[Hyperledger Project TSC] Minutes 02.11.16

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

By Todd Benzies <tbenzies@...> · #3 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Jesus Diaz Vico <jesus.diaz.vico@...> · #4 ·

[Hyperledger Project TSC] Slack access

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

By Thane Thomson <connect@...> · #9 ·

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

By Stefan Buhrmester <buhrmi@...> · #5 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Francisco J. Honrubia Moreno <fjhonrubia@...> · #6 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Thane Thomson <connect@...> · #10 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Ghassan Karame <ghassan.karami@...> · #7 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Stefan Buhrmester <buhrmi@...> · #8 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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"

By Jesus Diaz Vico <jesus.diaz.vico@...> · #11 ·

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

By Fabian Schuh <fabian@...> · #12 ·

Re: [Hyperledger Project TSC] Slack access

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?

By Christopher B Ferris <chrisfer@...> · #13 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Duc.M.Trinh@... · #14 ·

[Hyperledger Project TSC] Suggestion to make this list moderated

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)

By Allen · #15 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Fabian Schuh <fabian@...> · #16 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

+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

By Binh Q Nguyen <binhn@...> · #17 ·

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

+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:

By Christopher B Ferris <chrisfer@...> · #19 ·

Re: [Hyperledger Project TSC] Minutes 02.11.16

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

By Harsh Patel · #18 ·

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

+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"

By Dan O'Prey <dan@...> · #20 ·

Messages