Date   

Emergency shutdown of Jenkins servers (Now

Tim Johnson <tijohnson@...>
 

Emergency shutdown of Jenkins build servers required known security
issue in Jenkins that is actively being exploited

Once queues have be cleared they will be back on-line with about 10min

Tim


Re: [Hyperledger social-impact-sig] Can I use Hyperledger if

Middleton, Dan <dan.middleton@...>
 

Hi Alissa,

Let’s see if we can get you a better answer for next time. The projects give quarterly updates to the TSC and that’s a good time to check in with them on design for security and design for accessibility.

 

Cello’s is next:

https://wiki.hyperledger.org/display/HYP/2019+Q2+Hyperledger+Cello

 

 

Regards,

Dan

 

From: <social-impact-sig@...> on behalf of Alissa M Worley <alissa.worley@...>
Reply-To: "social-impact-sig@..." <social-impact-sig@...>
Date: Saturday, May 11, 2019 at 8:45 PM
To: "social-impact-sig@..." <social-impact-sig@...>, "tsc@..." <tsc@...>
Subject: Re: [Hyperledger social-impact-sig] Can I use Hyperledger if

 

Dan – Thanks so much for sharing this. It is so important.

 

During our Inclusion & Diversity lunch at Consensus last year, one of the questions from the audience at the end of the panel was from a visually impaired gentleman who asked what the industry was doing for accessibility with its tools. It’s stuck with me because I don’t have a good answer.  

 

_____________________________________________________________________

Alissa Worley | Global Marketing Director | Blockchain & DLT

Phone: (917) 446-0814 | E-mail: alissa.worley@...

Accenture

Linkedin

Twitter

Facebook

Instagram

YouTube

 

 

From: social-impact-sig@... <social-impact-sig@...> On Behalf Of Middleton, Dan
Sent: Saturday, May 11, 2019 7:53 PM
To: tsc@...
Cc: social-impact-sig@...
Subject: [External] [Hyperledger social-impact-sig] Can I use Hyperledger if

 

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.


 

One outcome of blockchain adoption is an increased accessibility of information, even if that’s just a company to company perspective.

And of course, the adoption of any new technology hinges a lot on usability.

So it’s interesting to watch this 13 minute film, “Access” (https://vimeo.com/311999966), which has nothing to do with blockchain, but a lot to do with the juxtaposition of two forms of accessibility.

 

Regards,

Dan

 



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com


Upcoming Event: Hyperledger Cello Quarterly Update Due #tsc-project-update - Thu, 05/16/2019 #tsc-project-update #cal-reminder

tsc@lists.hyperledger.org Calendar <tsc@...>
 

Reminder: Hyperledger Cello Quarterly Update Due #tsc-project-update

When: Thursday, 16 May 2019

View Event

Description: The Hyperledger Cello update to the TSC was due 13 May, 2019, and it will be presented to the TSC on 16 May, 2019. Please review the update at TSC Project Updates prior to the meeting and add your questions to the update.


Re: [Hyperledger Performance and Scale WG] [Hyperledger TSC] some thoughts on the future of the PSWG

mark wagner <mwagner@...>
 

Thanks Vipin

It seems that many folks are looking for us to define a benchmark so do we start with that or is there sufficient infor in the Emerald benchmark that we can use that to define a payment benchmark (notice not worried about implementation at this point)

We can also circle back to provenance and maybe loop in folks from Project Grid ?

I am also reaching out to my contacts at SPEC, TPC, and STAC one more time to see if there is any interest.

Love to hear what others think about all of this!

-mark


On Tue, Apr 23, 2019 at 3:48 PM VIPIN BHARATHAN <vip@...> wrote:
Hi,
Some of the ideas in today's call were
a. Look at Emerald and suggest ways in which this particular front-end can be hooked into Caliper, we have to look at duplication in both these libraries as well as the interface to decide whether this is worthwhile.
b. What does it take (smart contract wise)  to have Emerald tests run.
c. TPC/STAC Mark says that they run at a glacial pace plus they do not admit non-members (STAC does not) and they dont have Blockchain efforts
d. We spoke about Mark's presentation on May 7th and that he needed volunteers to run the call.
e. We spoke about Identity capabilities in Openshift as well as Oracle Blockchain in a side conversation
f. Spoke about having a quick look at Emerald.

A preliminary look at the github/gitlab repos say.
That you need the following capability (smart contracts etc.) in the platform you are going to test:

"In order for the test harness to measure the performance of a blockchain payents platform. The platform must support the following use cases:

  • Create several accounts that can store tokens
  • Issue tokens to specific accounts
  • Transfer tokens from account to account between nodes.

The third use case is what is measured by this benchmark."

So you have to have a solution that contains these actions

The hyperledger lab is empty except for the Readme file (https://github.com/hyperledger-labs/payments-performance-test-harness)
 
Conclusions:
  1. It would require considerable effort to architect a solution that interacts with caliper; there are also some duplicate facilities around load generation.
  2. The multi location load generation is neat
  3. There is some neat stuff there for the payments use case, since it follows ISO standards for payments payload.
  4. In order to run it against HL Fabric or HL Sawtooth or anything else the DLTs need a prebuilt payment solution (accounts storing tokens, issue tokens, transfer tokens between accounts)
  5. HL Fabric has the new FabToken project maybe this can help
  6. Without Mark Simpson to guide us it would take resources that we do not currently have. Caliper guys have to opine too.
  7. In short not now, not with what we have in PSWG is my conclusion- obviously I am willing to learn if someone says why this isn't so.
Best,
Vipin

dlt.nyc
Vipin Bharathan
Enterprise Blockchain Consultant


From: tsc@... <tsc@...> on behalf of mark wagner via Lists.Hyperledger.Org <mwagner=redhat.com@...>
Sent: Monday, April 22, 2019 9:38 AM
To: Dan Hyperledger
Cc: tsc@...
Subject: Re: [Hyperledger Performance and Scale WG] [Hyperledger TSC] some thoughts on the future of the PSWG
 
Hi Dan

Welcome back!

While I agree that integrity and availability are important and need to be quantified, I think that we still need baseline metrics to do so. "This is what the system does with faults, this is what happens when faults are introduced. "

One of the topics we had previously discussed was the Emerald benchmark that Mark Simpson had been involved in. It is now a Hyperledger lab. It is designed to measure payments. Should we consider using it with Caliper as our next deliverable ?

One of reasons for suggesting this is that it is already defined and has working code, abeit for Corda. However, by taking something that we know works, it should save us some time. The fact that it is a Hyperledger lab means that the code should be clean to start. Attila / Imre, did you ever get time to evaluate how difficult it would be to use emerald benchmark with Caliper ?  Mark Simpson, feel encouraged to jump in here as well!,

With respect to having TPC, SPEC etc to own a benchmark, I have mixed feelings. Red Hat is involved in both organizations and neither appears to be working with blockchain at this point in time. Based on my personal experience with the development of SPECVirt and SPECCloud, it will be at least a year before there is anything usable. Salman do you concur ?

Also, both orgs have fairly stringent rules and use policies, so a benchmark is typically not freely available for anyone to run. So there is no open source component.

Anyway, enough rambling. What do others think ?

-mark



On Tue, Apr 16, 2019 at 5:10 PM Dan Hyperledger <dan.hyperledger@...> wrote:

With respect to PSWG specifically, I think the most significant thing that working group can do is mature our ability to quantify integrity and availability.


The thing that makes blockchain different from other enterprise transaction systems is the use of decentralization in protecting the integrity and availability of the system.


The first output of the PSWG was a metrics document that made strides in measuring performance in that context. What does it mean if a network can execute 1000 TPS but can be taken down by a single node failure? The best we could do was be clear that performance should always be published in the context of the size of the network (as a proxy for a measure of availability and integrity).


We had a lot of discussion about measurements in the presence of faults. We even had some material started by a few of our contributors and while it wasn’t a fit for that draft of the metrics document, it seemed like a good seed for the next round of work.


A different direction of exploration is in workload design. In this case contributors from companies adopting blockchain are invaluable to help inform actual workload characteristics. One reason I don’t list benchmark design with higher importance is I believe it’s better developed by an organization like TPC.


Regards,

Dan Middleton


On Tue, Mar 19, 2019 at 7:44 AM Vipin Bharathan <vipinsun@...> wrote:
Hello Mark and others,

We have been having similar issues with the Architecture and Identity Working Groups.

You do not join a WG to mature into a developer for a particular solution. The work in a WG is complementary to the work in a project. You could do both. The WGs are not just about "documentation".

I have been thinking about the function of Working Groups. In my view it is the following.

The Working Groups were meant to be technical and focused on cross-cutting or primary concerns; like Architecture, Identity, Performance & Scale and now Smart Contracts.

Building stuff does require thinking about what to build. The WGs were meant to be a place where technical concerns from the various projects are aired out and where the collective wisdom of the WG participants could inform us all and prevent the isolation of frameworks from each other. In other words what makes Hyperledger, Hyperledger (beyond a single ledger); to connect projects together. This is evident in the papers published by the Architecture and PSWG groups.  

The Identity WG for example had people from Legal, Technical, Business as well as practitioners from  Identity specific areas all coming together to discuss topics like GDPR, Aadhar etc. and its relevance to the DLTs we are building. We brought Indy into the mix and are now working on L2 protocols in the Identity space. There is no comparable venue in HL for this. Somehow this message has been diluted and projects do not take this seriously enough nor is it effectively communicated.

The WGs were never highlighted in the wiki, and their benefits and contributions were seen as less than "landing patches".  

I see similarities in the way SIGs are forming now. In contrast, to the WGs the SIGs focus on verticals. WGs focus on horizontals. Both are needed. There should be collaboration between the SIGs and the WGs. 

Technical Working Group China and now one for India were formed because of differences in time zones and languages; and they are like all the WGs and SIGs rolled into one for the region. 

So now for some suggestions and ideas to make Working Groups more effective and encourage participation. This is based on conversations I have had with many people:

- It is important to do cross SIG/cross Regional/cross WG presentations
-Promotion in wiki, during bootcamps, messaging and Community Architect Support
-Experimentation with meeting times to encourage worldwide participation
-For PSWG, engagement with TPC, STAC, actual functional use case(Provenance) to look for numbers to measure, Look at ExactPro methodology etc.
-Engagement with Architecture for improvements in Performance like the waterloo project and implications on DLT architecture. What are the implications for other DLTs (other than Fabric)

Hope this long email may be of some use in rebooting the WGs and also rethinking of a more collaborative future. 

Best,
Vipin

On Tue, Mar 19, 2019 at 1:22 AM Kulkarni, Amol <amol.kulkarni@...> wrote:

One of the issues with the WGs as they’re currently set up is that interested folks from Asia cannot call into them.

 

The PSWG, for example, currently meets from 6:30 – 7:30 pm India time. While I’m working on performance and benchmarking specifically, my colleagues and I cannot call into any of these meetings. Perhaps rescheduling meetings to encourage participants from different geos might be one way to increase participation in WGs.

 

Amol

 

From: tsc@... [mailto:tsc@...] On Behalf Of Silona Bonewald
Sent: Tuesday, March 19, 2019 7:49 AM
To: Christopher Ferris <chris.ferris@...>
Cc: Todd Little <todd.little@...>; Montgomery, Hart <hmontgomery@...>; mark wagner <mwagner@...>; perf-and-scale-wg@...; Hyperledger List <tsc@...>
Subject: Re: [Hyperledger Performance and Scale WG] [Hyperledger TSC] some thoughts on the future of the PSWG

 

The Technical Working Group China participated in the HKBootcamp and was highly visible.  I think it is a good idea for other working groups to think about how to recruit and engage more with the community thru events like Bootcamps etc. 

 

For example, my team has been discussing with the Learning Materials Working Group about how they will recruit.  First from the projects themselves, and then how do we help them market themselves to get more volunteers?  Of course, having a good landing page on the wiki helps!

 

Also, Hyperledger has been starting up a bunch of SIGs.  I believe some people are moving to those SIGs.  And Ecosystem team is actively recruiting new members to participate there first.  Should we look at how we cross "advertise" internally?  Or look at how we "advertise" to new members and externally.

 

What other paths to recruitment should we explore? 

 

Silona

 

On Mon, Mar 18, 2019 at 4:15 PM Christopher Ferris <chris.ferris@...> wrote:

Todd, the Fabric maintainers would welcome additional help in documenting Fabric or providing and curating samples. They don’t write themselves.

 

I tend to agree with Hart’s analysis, and while I have a regular call that conflicts, I join occasionally and am definitely interested in the subject matter.

 

I’d agree with Todd that working with a traditional benchmarking org would be good, as would input into Caliper and other performance testing efforts.

 

We aren’t yet at a point where we can effectively provide guidance on comparative performance characteristics, which is ultimately what people will be seeking.

Chris


On Mar 18, 2019, at 6:49 PM, Todd Little <todd.little@...> wrote:

Hi Hart,

I tend to agree, but I also think another factor is that as we've moved from initial versions of the various platforms to production ready platforms, people are probably getting tied up working on those production deployments.  I know for me it's mostly a matter of I participate when I don't have conflicts or not traveling.

Personally I'd like to see us move in the direction of helping some standards organizations define blockchain benchmarks that can be used to evaluate blockchain platforms, as I'm not sure we're in the business of setting those kinds of standards.  Someone please correct me if I'm wrong.  I may have asked this before, but has anyone reached out to TPC to see if they're interested in creating some blockchain benchmarks?

With respect to the documentation, agreed it's fairly weak, and in particular design documentation is sorely lacking, at least for Fabric.  I can't speak to the other platforms.  Samples/examples is another area that is pretty weak.  Our platforms are so feature rich that it's hard to pick them up without a set of rich samples/examples.

-tl

PS FWIW I'll be on the call tomorrow.

On 3/18/2019 5:28 PM, Montgomery, Hart wrote:

Hi Mark,

 

I think this is probably true for most working groups.  At least from what I’ve seen and heard (and to be fair, this is not a huge sample size), fewer people are participating in the working groups, and those who are generally are participating less.

 

I’m not sure this is a bad thing, in many cases.  I think some people have replaced spending time on working groups with time spent on regular projects.  Personally, I’ve spent less time on working group stuff since Ursa has begun (and, obviously, more time on Ursa), which is probably a kind of progression we want to encourage in Hyperledger.  Having people that come into the working groups looking to learn become regular contributors surely is a positive thing. 

 

On the other hand, as the working groups seem to focus more and more on work products—which is typically documentation--fewer people seem to be interested since there is often substantial outside work involved, and not necessarily of the fun kind.  In particular, I think every SWOT analysis we have done on Hyperledger involves documentation being listed as a weakness.   While documentation has gotten better, it’s still something that I think most people would agree needs a lot of work on most aspects of Hyperledger.

 

So, for a TL;DR:  from my viewpoint, people are leaving working groups to contribute (great!)  or avoid documentation work (not so great). 

 

Do these experiences jibe with yours (or others’)?

 

Sorry for another long email.

 

Thanks,

Hart

 

 

 

From: tsc@... [mailto:tsc@...] On Behalf Of mark wagner
Sent: Monday, March 18, 2019 12:33 PM
To: perf-and-scale-wg@...
Cc: Hyperledger List <tsc@...>
Subject: [Hyperledger TSC] some thoughts on the future of the PSWG

 

Hi

 

I would like to carry this discussion mostly in the mailing lists in order to be as inclusive as possible.

 

Over the last few months attendance and participation on the Performance and Scale WG (PSWG) calls has been declining. I am wondering if we need to shift focus a bit to get more people involved and make progress.

 

There are many possible directions we can head in and I have included some thoughts here, but if others have additional ideas please feel encouraged to add them.

 

First is stay the course. We are currently struggling to get our thoughts on describing metrics for provenance captured to paper.

 

Do we want to focus more on actual performance work vs just defining metrics / use case papers. This does not need to be "just running tests".

 

We can do things like examine trade offs between different design decisions, examine different crypto solutions / technologies from a perf and scale perspective, help understand cost performance tradeoffs.

 

Perhaps we help spin up testnets and drive testing of different DLT frameworks ?

 

Do we provide a performance analysis service to the different projects that is based on architecture decisions. Perhaps something similar to what several research students have done (Harish and his team, FastFabric, etc).

 

I am trying to cut a wide swath here to avoid limiting peoples thoughts, so any and all comments are encouraged. If you have not been involved in the PSWG and would be interested in participating if we did "X" then speak up!

 

thanks

 

-mark

--

Mark Wagner

Chair, Performance and Scale Working Group

 



--

Silona Bonewald

VP of Community Architecture, Hyperledger

Mobile/Text: 512.750.9220
https://calendly.com/silona

The Linux Foundation
http://hyperledger.org



--
Mark Wagner
Senior Principal Software Engineer
Performance and Scalability
Red Hat, Inc


--
Mark Wagner
Senior Principal Software Engineer
Performance and Scalability
Red Hat, Inc


Re: [Hyperledger social-impact-sig] Can I use Hyperledger if

Caine Smith <caine@...>
 


In terms of accessibility, this is one of the best examples of seen recently, i've been an active member for about a year. Its a very well executed product. 
https://www.bemyeyes.com/



On Sat, May 11, 2019 at 9:45 PM Alissa M Worley <alissa.worley@...> wrote:

Dan – Thanks so much for sharing this. It is so important.

 

During our Inclusion & Diversity lunch at Consensus last year, one of the questions from the audience at the end of the panel was from a visually impaired gentleman who asked what the industry was doing for accessibility with its tools. It’s stuck with me because I don’t have a good answer.  

 

_____________________________________________________________________

Alissa Worley | Global Marketing Director | Blockchain & DLT

Phone: (917) 446-0814 | E-mail: alissa.worley@...

Accenture

Linkedin

Twitter

Facebook

Instagram

YouTube

 

 

From: social-impact-sig@... <social-impact-sig@...> On Behalf Of Middleton, Dan
Sent: Saturday, May 11, 2019 7:53 PM
To: tsc@...
Cc: social-impact-sig@...
Subject: [External] [Hyperledger social-impact-sig] Can I use Hyperledger if

 

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.


 

One outcome of blockchain adoption is an increased accessibility of information, even if that’s just a company to company perspective.

And of course, the adoption of any new technology hinges a lot on usability.

So it’s interesting to watch this 13 minute film, “Access” (https://vimeo.com/311999966), which has nothing to do with blockchain, but a lot to do with the juxtaposition of two forms of accessibility.

 

Regards,

Dan




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com



--
Kind regards
Caine Smith
Co-Founder & Executive Director 


Re: Can I use Hyperledger if

Worley, Alissa <alissa.worley@...>
 

Dan – Thanks so much for sharing this. It is so important.

 

During our Inclusion & Diversity lunch at Consensus last year, one of the questions from the audience at the end of the panel was from a visually impaired gentleman who asked what the industry was doing for accessibility with its tools. It’s stuck with me because I don’t have a good answer.  

 

_____________________________________________________________________

Alissa Worley | Global Marketing Director | Blockchain & DLT

Phone: (917) 446-0814 | E-mail: alissa.worley@...

Accenture

Linkedin

Twitter

Facebook

Instagram

YouTube

 

 

From: social-impact-sig@... <social-impact-sig@...> On Behalf Of Middleton, Dan
Sent: Saturday, May 11, 2019 7:53 PM
To: tsc@...
Cc: social-impact-sig@...
Subject: [External] [Hyperledger social-impact-sig] Can I use Hyperledger if

 

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.


 

One outcome of blockchain adoption is an increased accessibility of information, even if that’s just a company to company perspective.

And of course, the adoption of any new technology hinges a lot on usability.

So it’s interesting to watch this 13 minute film, “Access” (https://vimeo.com/311999966), which has nothing to do with blockchain, but a lot to do with the juxtaposition of two forms of accessibility.

 

Regards,

Dan




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com


Can I use Hyperledger if

Middleton, Dan <dan.middleton@...>
 

One outcome of blockchain adoption is an increased accessibility of information, even if that’s just a company to company perspective.

And of course, the adoption of any new technology hinges a lot on usability.

So it’s interesting to watch this 13 minute film, “Access” (https://vimeo.com/311999966), which has nothing to do with blockchain, but a lot to do with the juxtaposition of two forms of accessibility.

Regards,

Dan


[Hyperledger Smart Contracts WG] Notice about WG meetings day and time (plus add to my calendar link)

Sofia Terzi
 

Dear all,

 

After exchanging emails with some of you I figured out that due to the change of the day of our meetings many haven’t updated their calendars yet. You can always refer to the Hyperledger Calendar of Public Meetings, but because as Mic said we are “slaves of our calendars” for your convenience I am sending you the “add to my calendar” link as well as information for our next meeting

 

Smart Contracts WG

3:00pm

When Wed, May 22, 3pm – 4pm

Where https://zoom.us/my/hyperledger.community.3 (map)

Description Smart Contracts WG meeting https://zoom.us/my/hyperledger.community.3

more details»  copy to my calendar

I am looking forward to hear from you all in our next call! Thank you for your time, support and contribution J

 

Best regards,

Sofia Terzi

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

Sofia Terzi | Blockchain Solutions Architect MSc.

[Email] <sterzi@...>

[CERTH-ITI] <https://www.iti.gr/iti/index.html>

 


Re: tomorrow’s call

Middleton, Dan <dan.middleton@...>
 

Hate to also drop out last minute but my flight has been unexpectedly canceled/rebooked.

Regrets,

Dan

 

From: <tsc@...> on behalf of Mark Wagner <mwagner114@...>
Date: Wednesday, May 8, 2019 at 1:22 PM
To: Arnaud Le Hors <lehors@...>
Cc: Hyperledger List <tsc@...>
Subject: Re: [Hyperledger TSC] tomorrow’s call

 

me three, at the Red Hat Summit.

 

On Wed, May 8, 2019, 16:20 Arnaud Le Hors <lehors@...> wrote:

Regrets from me as well. Busy at an IBM event.
--
Arnaud  Le Hors - Senior Technical Staff Member, Blockchain & Web Open Technologies - IBM




From:        "Christopher Ferris" <chrisfer@...>
To:        tsc@...
Date:        05/08/2019 07:11 PM
Subject:        [Hyperledger TSC] tomorrow’s call
Sent by:        tsc@...





Regrets... I will miss tomorrow’s call, visiting my MIL in hospital.

Cheers,

Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email:
chrisfer@...
twitter: @christo4ferris

blog: https://developer.ibm.com/code/author/chrisfer/
IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/
phone:
+1 508 667 0402




Re: Urgent Gerrit Downtime Today 16:00 EST

Tim Johnson <tijohnson@...>
 

Configuration change has been performed and gerrit is back on-line.

On 5/8/19 8:38 AM, Tim Johnson wrote:
We have had a DDOS attack on gerrit.hyperledger.org. We are making
configuration changes to gerrit to address the issue. The configuration
changes require a restart of gerrit.

Tim



Re: tomorrow’s call

Mark Wagner
 

me three, at the Red Hat Summit.


On Wed, May 8, 2019, 16:20 Arnaud Le Hors <lehors@...> wrote:
Regrets from me as well. Busy at an IBM event.
--
Arnaud  Le Hors - Senior Technical Staff Member, Blockchain & Web Open Technologies - IBM




From:        "Christopher Ferris" <chrisfer@...>
To:        tsc@...
Date:        05/08/2019 07:11 PM
Subject:        [Hyperledger TSC] tomorrow’s call
Sent by:        tsc@...




Regrets... I will miss tomorrow’s call, visiting my MIL in hospital.

Cheers,

Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: https://developer.ibm.com/code/author/chrisfer/
IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/
phone: +1 508 667 0402





Re: tomorrow’s call

Arnaud Le Hors
 

Regrets from me as well. Busy at an IBM event.
--
Arnaud  Le Hors - Senior Technical Staff Member, Blockchain & Web Open Technologies - IBM




From:        "Christopher Ferris" <chrisfer@...>
To:        tsc@...
Date:        05/08/2019 07:11 PM
Subject:        [Hyperledger TSC] tomorrow’s call
Sent by:        tsc@...




Regrets... I will miss tomorrow’s call, visiting my MIL in hospital.

Cheers,

Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: https://developer.ibm.com/code/author/chrisfer/
IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/
phone: +1 508 667 0402





tomorrow’s call

Christopher Ferris <chrisfer@...>
 

Regrets... I will miss tomorrow’s call, visiting my MIL in hospital.

Cheers,

Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris


Urgent Gerrit Downtime Today 16:00 EST

Tim Johnson <tijohnson@...>
 

We have had a DDOS attack on gerrit.hyperledger.org. We are making
configuration changes to gerrit to address the issue. The configuration
changes require a restart of gerrit.

Tim


Re: CI/CD update

Christopher Ferris <chrisfer@...>
 

We should keep an eye on https://github.com/tektoncd 

Cheers,

Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris

On May 8, 2019, at 12:26 AM, Dave Huseby <dhuseby@...> wrote:

Hi TSC,

After receiving feedback from many of you that you didn't think the CI/CD committee should be private, the CA team has decided to open it all up. I am keeping the one page with all of the outside CI/CD costs private to protect the confidentiality I promised when gathering expense information from companies currently paying to run Hyperledger CI/CD pipelines.

The CI/CD space can be found here:


You can see all of the ongoing research and ideas as well as the meeting minutes from our meetings. If you would like to participate, I am still looking for people to join the committee to help us work out solutions.

The biggest problem we face now is that many of the CI/CD pipelines for Hyperledger projects use docker-in-docker and docker-compose to first build their CI docker image and test it before running it to build the project code and test that. The current idea of airlifting existing pipelines onto a Hypereldger Kube cluster is blocked by the current docker-in-docker requirement.

Thanks to Mark, we have been thinking about how to get away from docker-in-docker since last October at the Montreal meetup. RedHat has a good solution called Buildah and there are a few others. We could really use help examining the different CI pipelines for the different projects to gauge the level of impact switching from docker-in-docker to something like Buildah would cause.

Kube is not a silver bullet. So the end recommendation from the committee should account for the cost moving all of the projects to a Kube cluster, in terms of estimated work hours and risk due to change.

If you can spare the cycles and know your project's CI pipeline fairly well, we could use your help.

Cheers!
Dave
---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...


Re: Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork

VIPIN BHARATHAN
 

Hello all,

Having delved into this more, I have the following comments. 
Agree with Brian's points. 
To the last point: VRF does not appear to have any live patents and is used by other projects (other than Algorand), a more thorough search is warranted.

I will add another route for HL participation: Work with Ursa and get the VRF algorithm into that library.  I believe that the solution can be broader than just applicability to Fabric BFT.

Also, there is a comment on the FAB (https://jira.hyperledger.org/browse/FAB-15350) which argues against the committee selection process and the use of VRF for hashing. 
These have to be addressed.

The commenter (Yakov Manevich) has assumptions about the future (see below). You have to balance this comment against the cost of implementing a VRF based BFT as a pluggable component in Fabric or any other DLT.

"So, clearly - using committee selection is good for large networks with thousands of nodes, and I don't think we'll have a Byzantine ordering service oriented for large networks in the near future. "


Best,
Vipin

dlt.nyc
Vipin Bharathan
Enterprise Blockchain Consultant
vip@...


From: tsc@... <tsc@...> on behalf of Brian Behlendorf via Lists.Hyperledger.Org <bbehlendorf=linuxfoundation.org@...>
Sent: Tuesday, May 7, 2019 10:43 PM
To: tsc@...; 宣章炯
Cc: tsc@...
Subject: Re: [Hyperledger TSC] Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork
 

Further to the other supportive comments:

* The Fabric developer mailing list, and or the chat channel, may be a better place to continue the technical side of this discussion, as it's really up to them what gets integrated directly into Fabric.  TSC is more of a cross-community technical discussion list.  I would bet there's interest in a Sawtooth consensus plugin as well, though, so it's not bad that you asked this here, though a consensus engine would work differently there.

* If your question is less about the technical side of how to build it (or whether it's a good idea) and more about getting it into Hyperledger, you could offer this kind of thing to the Hyperledger Fabric project directly as a PR on Gerrit (what Fabric uses instead of Github) or you could host it as a separate consensus engine under Hyperledger Labs.  That may be obvious but I'm not sure how well you know the community so thought it was worth stating.

* If your intent is to offer it as a contribution of code into Hyperledger (whether into Fabric directly or as an add-on hosted at Labs, etc) then you may want to make sure that there aren't obvious patents that apply to VRF, or if there are, that the patent holders have granted a license to you or to the public in general for open source implementations.  We want to avoid the situation where code that clearly implements a patented algorithm is embedded into Fabric or other open source code, and then a patent holder comes around later to Hyperledger or to end users demanding a license for that use.

Thanks,

Brian

On 5/7/19 12:43 PM, VIPIN BHARATHAN wrote:
Hello Zhangjiong Xuan,
Sounds great. A faster version of consensus in the form of a VRF implementation. There may be some challenges with the structure and functions of nodes in HLF. I am sure you will overcome those. Ever since VRF was opensourced at the end of 2018 I had expected a group like yours to take on the challenge.
Best,
Vipin

 

From: tsc@... on behalf of via Lists.Hyperledger.Org <xzj19922010=gmail.com@...>
Sent: Tuesday, May 7, 2019 8:14 AM
To: tsc@...
Cc: tsc@...
Subject: [Hyperledger TSC] Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork
 

My name is Zhangjiong Xuan. I come from Hangzhou Qulian Technology Co., Ltd. We have a team to research Algorand and VRF Algorithm. Now we have implement the VRF Algorithm in the Golang. And we think there is a good scenario in the Hyperledger Fabric. So we want to ask the communitty if it’s a good Idea to use VRF Algorithm into Ordering Service, to do a feature in the Ordering Service. I hope TSC group can have a discussion whether will receive this proposal. If both of you think it's a good idea .Maybe we can have a try to do this job .And make a more detailed design in the google docs.

Thanks.


Jira:

Google doc:


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@...
Twitter: @brianbehlendorf


TSC Agenda for this week

Silona Bonewald <sbonewald@...>
 

Please remember to add things to the agenda!


Thanks!
--
Silona Bonewald
VP of Community Architecture, Hyperledger
Mobile/Text: 512.750.9220
https://calendly.com/silona
The Linux Foundation
http://hyperledger.org


CI/CD update

Dave Huseby <dhuseby@...>
 

Hi TSC,

After receiving feedback from many of you that you didn't think the CI/CD committee should be private, the CA team has decided to open it all up. I am keeping the one page with all of the outside CI/CD costs private to protect the confidentiality I promised when gathering expense information from companies currently paying to run Hyperledger CI/CD pipelines.

The CI/CD space can be found here:


You can see all of the ongoing research and ideas as well as the meeting minutes from our meetings. If you would like to participate, I am still looking for people to join the committee to help us work out solutions.

The biggest problem we face now is that many of the CI/CD pipelines for Hyperledger projects use docker-in-docker and docker-compose to first build their CI docker image and test it before running it to build the project code and test that. The current idea of airlifting existing pipelines onto a Hypereldger Kube cluster is blocked by the current docker-in-docker requirement.

Thanks to Mark, we have been thinking about how to get away from docker-in-docker since last October at the Montreal meetup. RedHat has a good solution called Buildah and there are a few others. We could really use help examining the different CI pipelines for the different projects to gauge the level of impact switching from docker-in-docker to something like Buildah would cause.

Kube is not a silver bullet. So the end recommendation from the committee should account for the cost moving all of the projects to a Kube cluster, in terms of estimated work hours and risk due to change.

If you can spare the cycles and know your project's CI pipeline fairly well, we could use your help.

Cheers!
Dave
---
David Huseby
Security Maven, Hyperledger
The Linux Foundation
+1-206-234-2392
dhuseby@...


Re: Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork

Brian Behlendorf
 


Further to the other supportive comments:

* The Fabric developer mailing list, and or the chat channel, may be a better place to continue the technical side of this discussion, as it's really up to them what gets integrated directly into Fabric.  TSC is more of a cross-community technical discussion list.  I would bet there's interest in a Sawtooth consensus plugin as well, though, so it's not bad that you asked this here, though a consensus engine would work differently there.

* If your question is less about the technical side of how to build it (or whether it's a good idea) and more about getting it into Hyperledger, you could offer this kind of thing to the Hyperledger Fabric project directly as a PR on Gerrit (what Fabric uses instead of Github) or you could host it as a separate consensus engine under Hyperledger Labs.  That may be obvious but I'm not sure how well you know the community so thought it was worth stating.

* If your intent is to offer it as a contribution of code into Hyperledger (whether into Fabric directly or as an add-on hosted at Labs, etc) then you may want to make sure that there aren't obvious patents that apply to VRF, or if there are, that the patent holders have granted a license to you or to the public in general for open source implementations.  We want to avoid the situation where code that clearly implements a patented algorithm is embedded into Fabric or other open source code, and then a patent holder comes around later to Hyperledger or to end users demanding a license for that use.

Thanks,

Brian

On 5/7/19 12:43 PM, VIPIN BHARATHAN wrote:
Hello Zhangjiong Xuan,
Sounds great. A faster version of consensus in the form of a VRF implementation. There may be some challenges with the structure and functions of nodes in HLF. I am sure you will overcome those. Ever since VRF was opensourced at the end of 2018 I had expected a group like yours to take on the challenge.
Best,
Vipin

 

From: tsc@... on behalf of via Lists.Hyperledger.Org <xzj19922010=gmail.com@...>
Sent: Tuesday, May 7, 2019 8:14 AM
To: tsc@...
Cc: tsc@...
Subject: [Hyperledger TSC] Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork
 

My name is Zhangjiong Xuan. I come from Hangzhou Qulian Technology Co., Ltd. We have a team to research Algorand and VRF Algorithm. Now we have implement the VRF Algorithm in the Golang. And we think there is a good scenario in the Hyperledger Fabric. So we want to ask the communitty if it’s a good Idea to use VRF Algorithm into Ordering Service, to do a feature in the Ordering Service. I hope TSC group can have a discussion whether will receive this proposal. If both of you think it's a good idea .Maybe we can have a try to do this job .And make a more detailed design in the google docs.

Thanks.


Jira:

Google doc:


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@...
Twitter: @brianbehlendorf


Re: Add VRF(Verifiable Random Functions) Into Ordering Service to Support Large-scale COnsensus NetWork

Baohua Yang
 

Great, zhangjiong!

I think this is an interesting topic, as VRP was typically used in public scenarios and some open-sourced repo will be a good start.


On Tue, May 7, 2019 at 10:14 PM 宣章炯 <xzj19922010@...> wrote:

My name is Zhangjiong Xuan. I come from Hangzhou Qulian Technology Co., Ltd. We have a team to research Algorand and VRF Algorithm. Now we have implement the VRF Algorithm in the Golang. And we think there is a good scenario in the Hyperledger Fabric. So we want to ask the communitty if it’s a good Idea to use VRF Algorithm into Ordering Service, to do a feature in the Ordering Service. I hope TSC group can have a discussion whether will receive this proposal. If both of you think it's a good idea .Maybe we can have a try to do this job .And make a more detailed design in the google docs.

Thanks.


Jira:

Google doc:



--
Best wishes!

Baohua Yang

1661 - 1680 of 3898