Prasanth, did you check for private data collection implementation in the chaincodes? Regards, Mayank Tiwari.

Thanks for quick reply! I will try those suggestions. I had thought separating these chaincodes could help manageability more and might increase development pace. Although you make a valid point, I

Each chaincode corresponds to a differentnamespace, and has a different endorsement policy. Software engineering idioms such as"separation of business logic from tech logic" should never bea reason

Hi Atsushi, My response in blue in-lined text… Thanks, Manish

Hi Guys, I've been trying to separate one big chaincode into multiple chaincodes and also for separating business logic from tech logic. Here, the tech logic service (eg: EncryptAndSaveState) needs

All I wanted to say here is that, it would be good if someone wants one of the peers file to act as a repo as well…. in other words, it still has all what a repo offers and code will be outside core

below is our truncated logs 2019-12-02 09:42:46.771 PST [policies] Evaluate -> DEBU 4d3 == Evaluating *policies.implicitMetaPolicy Policy /Channel/Application/ChannelCreationPolicy == 2019-12-02

Hi Siddharth, This error is caused by a certificate problem. You can investigate further by checking your orderer logs. This stack overflow post:

I don’t have definite answer, like side by side comparison. But I am working very fine with node sdk, especially when my middle tier application, and front end app are (everything in Typescript). I

Hello - both SDKs have the updated programming model. Both have the same features, and able to support the same Fabric use-cases. It's possibly more important to consider the development

Hello, Are there any recommendations around which fabric sdk should be used(node sdk vs java sdk) for various hyperledger fabric blockchain use cases. Are there any guidelines for choice of SDK

Hi All, Is there any recommendation for fabric Node JS SDK version to be used for a specific fabric version running on the network peer/orderer/ca nodes. For example, if my fabric network is running

we get the error below when trying to create a channel using the peer CLI2019-11-30 20:53:15.482 UTC [orderer.common.broadcast] ProcessMessage -> WARN 00c [channel: mychannel] Rejecting broadcast of

After 4 years, we're back home where we started. Thanks!

All, I have exported all of the git data from Gerrit (except for the fabric-test repo, which is still undergoing development). I have also exported the comments and the like as JSON. I've set up a new

Thanks, Manish, Yacov, and Gari. I really appreciate for your feedback and insights. (Feedback from Manish) Thank you so much for a quite important point. We're now reviewing and analyzing the

Hello All, Due to our colleaguesin the US celebrating Thanksgiving there will not be a call this week!Our next call will be Dec 6. You can read thesummary minutes for last week's call:

Joson, I just did as per your suggestion, signed config changes (envelop) with orderer MSP admin. As I already mentioned in below mail, "When we create certificates using cryptogen tool, for peer

thanks. this is helpful. From: David Enyeart <enyeart@...> Sent: Wednesday, November 27, 2019 10:51 AM To: Siddharth Jain <siddjain@...> Cc: fabric@... <fabric@...> Subject: Re: [Hyperledger Fabric]

You can see an explanation and proposal to enforce the database target here: https://jira.hyperledger.org/browse/FAB-17163 Dave Enyeart "Siddharth Jain" ---11/27/2019 01:01:52 PM---I read somewhere in