All right, thank you for that information. Regards, Aboubakar Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday 10 February 2020 15:48, Brett T

We expect sometime mid-year to announce Fabric 2.x as LTS. Once this happens there will be a period of time where both 1.4.4 and 2.x are LTS to provide a transition period for users to migrate to

Hi, With the release of Hyperledger 2.0 I would like to know until when version 1.4 will be maintained. Best regards, Aboubakar

Regular one From: Yacov Manevich <YACOVM@...> Sent: Monday, 10 February 2020 13:19 To: Eryargi, Hakan <hakan.eryargi@...> Cc: fabric@... Subject: [External] Re: [Hyperledger Fabric] Transaction

Is this a system chaincode or a regularone? From: "Eryargi, Hakanvia Lists.Hyperledger.Org" <hakan.eryargi=accenture.com@...> To: "fabric@..."<fabric@...> Cc: fabric@... Date:

Hi, Are all transaction validation failures handled the same way and propagated back to client (Node.js SDK)? In particular I’m asking about EXPIRED_CHAINCODE failure. I’m investigating a

Rui, While it's possible to use the console to build a configuration of any number of ordering nodes (no configuration is explicitly restricted), some numbers provide a better balance between cost

Hello guys, I was just wondering what is the best practice when it comes to the ordering service in a production environment. What is the proportion of ordering service nodes in relation to the size

In green. From: "Tomás Peixinho"<tom.peixinho@...> To: Yacov Manevich <YACOVM@...> Cc: "hyperledger-fabric@..."<hyperledger-fabric@...> Date: 02/08/2020 01:50 AM Subject:

Thanks for the quick response, Yacov! And when I said 2.5 years, I atually meant it. That's the time I have been working on my master's thesis. Anyway... What do you mean when you say I shouldn't use

Answers inline in blue. From: "Tomás Peixinho"<tom.peixinho@...> To: "hyperledger-fabric@..."<hyperledger-fabric@...> Date: 02/08/2020 12:35 AM Subject: [EXTERNAL]

Good evening, I am at my wits end with Hyperledger Fabric. Now that I got this out of the way, on to my question: Apparently, to define the network topology for my blockchain, I have to modify three

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 7 February 2020 4:00pm to 5:00pm (GMT+00:00)

Hey guys, I've been working on a user revoke script but have come across some points after some research and testing. Here's a scenario that makes it very troublesome from the process that I

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 7 February 2020 6:00am to 7:00am (GMT+00:00)

Hello! Please note thechange in time for the Western hemisphere call this week. For this weekonly, it is 1 hour later than usual! The Eastern hemisphere call is atits regular time. Other than

Want to jump in to clear up something Brett said. If the chaincode is non-deterministic, then the read write sets will not match and will not pass the endorsement policy, and proposals will be

In 2.0 Fabric we added logic to remove unreferenced chaincode containers, so once your old version is no longer used anywhere it would be cleaned up. We also introduced a new chaincode builder and

Dear all, I would like to ask about hyperledger performance related to chaincode upgrade. Each time when we upgrade the new chaincode, a new docker container will be created. Do you think this is an

This is not an issue with the submitting client credentials, it is an issue with the peer credentials not matching the org credentials in the channel config. You must approve on a peer of your own