No, we need the data to exist in all the nodes in network. No hiding required. Can you elaborate a little on how do you suggest to use private data here? Id you're thinking about some special exploita

#fabric-chaincode

Hello; could you give me some more info please about how you're sending transactions. Do you have the chaincode logs for example? Or post to rocketchat #fabric-chaincode-java and we can discuss there.

#fabric-questions #fabric-chaincode #fabric

FYI issue raised here https://jira.hyperledger.org/browse/FAB-17110 Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at WHITEMAT@... Find me on StackOverflow, and g

#fabric-questions #fabric-chaincode #fabric

After upgrading to 1.4.4 i receive the following error in my chaincode logs: `transaction returned with failure: Failed to submit task for processing` I'm sending transactions in a multithread enviror

#fabric-questions #fabric-chaincode #fabric

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

#fabric-chaincode

Hi All, Fabric - v1.4.3 (RAFT Orderer Set Up) I have two Orgs network. OrgA and OrgB. Installed the chaincode on both the anchor peers of OrgA and OrgB. Instantiated the chaincode from the anchor peer

#fabric #fabric-chaincode

Resolved the issue . The chaincode folder structure should be exactly same in both the peers to get the same hash fingerprintID which will create chaincode containers for both the org peers

#fabric #fabric-chaincode

Hey, there's an easier and more trusted way for production. First you run the command peer chaincode package -n ccName -p /opt/chaincodePath -v 1 chaincode.pak -l node Then you get that chaincode.pak

#fabric #fabric-chaincode

Thanks Nicholas for the reply. One thing i noticed is when i am installing the private chaincode . i checked in both the peer org machines the IDs of the installed chaincode is same but still the cont

#fabric #fabric-chaincode

Hi Murali and Team, The issue has been raised in JIRA. Find the below link https://jira.hyperledger.org/browse/FAB-16652 Regards, Soumya

#fabric #fabric-chaincode

Hi Sowmya, Its worth investigating why a user-level invalid configtx.yaml entry should cause a delayed side effect of a chaincode crash (as a side note, surprised its the chaincode that's crashing giv

#fabric #fabric-chaincode

No, that's right, for a minimal test case I only changed the class name. In the original attempt I changed both and got the same behaviour.

#fabric-questions #fabric-chaincode

PS: A simpler and more easily reproducible test is now available in Stack Overflow

#fabric-questions #fabric-chaincode

It seems you didn't change the contract name in package.json papercontract as the contract installed on peer with details name: papercontract, Version: 0

#fabric-questions #fabric-chaincode

I am trying to adapt the commercial paper tutorial to a custom contract, and cannot instantiate it. In commercial-paper/organization/magnetocorp/contract, I updated: package.json with a new name, vers

#fabric-questions #fabric-chaincode

Hi Team, Fabric - v1.4.3 RAFT Orderer Set up ( 5 Orderers) I am facing a issue where the chaincode container is exiting, not sure why. I have installed the same chaincode (different versions) many tim

#fabric #fabric-chaincode

Also attached the docker container logs for the chaincode exited container

#fabric #fabric-chaincode

Hi Murali, Will raise the JIRA and update here. Regards, Soumya

#fabric #fabric-chaincode

Hi All, v1.4.3 Any idea from Fabric-CLI tool how to run the invoke chaincode command to send to multiple anchor peers from different orgs for endorsement in Mutual TLS fabric set up? Regards, Soumya

#fabric #fabric-chaincode

Hi All, Now am able to invoke the chaincode using the *--peerAddresses* and *--tlsRootCertFiles* attributes But one more doubt i had was - lets say OrgA and OrgB peers have to endorse a transaction --

#fabric #fabric-chaincode