hello, What is the best way to write test cases for smart contracts written in golang using the fabric-contract-api-go Thanks in advance

#fabric-chaincode

I've improved the error message a bit so that the next people to hit the issue at least know which communication has failed upfront: https://github.com/hyperledger/fabric/pull/1308 Dave Enyeart "Sures

#fabric-chaincode

Just for confirmation - spoke with Marek on rocketchat, and the fix for FABCJ-285 will resolve this... will look to put our a patch release in the coming week. Regards, Matthew. Matthew B White IBM Bl

#couchdb #fabric-chaincode #fabric-sdk-java

Hi, We compared the performance of both v1.4 and v.2.0 using public data, i.e., without collections. We have not observed any performance differences. Since the introduction of pvtdata feature, the go

#fabric #fabric-chaincode

I think most use cases will want the read-write behavior. Append-only use cases may want the blind write behavior. For example consider an IOT sensor that records a data point hourly. There isn't real

#fabric-orderer #fabric-chaincode

If you send a steady flow of updates for the same key, you will always have some transactions in flight (endorsement or ordering phase) while earlier transactions are committing on peers. Since the la

#hyperledger-fabric #fabric-chaincode #consensus #raft

Btw, FoundationDB org officially supports a document layer (https://github.com/FoundationDB/fdb-document-layer based on MongoDB API) on top of the foundationDB. As it is a multi-modal database, they a

#fabric #fabric-chaincode

While executing a submitTransaction method i am getting an error like "2020-04-30T17:18:11.313Z - warn: [Transaction]: _validatePeerResponses: Received error response from peer: message=transaction re

#hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabric-sdk-node

I am getting an error while invoking functions in smart contract Could anyone let me know why i getting this silly error, I only have one argument in the function as argument looks like this "async vi

#fabric-sdk-node #hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabricca

Private data collections define which organization's peers are authorized to receive and store the private data. This is orthogonal to user based access control. You need to consider both aspects. So

#fabric-chaincode #couchdb #fabric-questions #hyperledger-fabric

Hi Kamlesh I have done what you said and this moment I faced"Error:timed out waiting for txid on all peers" error when I executed "peer lifecycle chaincode approveformyorg" command. Do you know how to

#fabric-chaincode #hyperledger-fabric

how chaincode example 02 can be modified in hyperledger 1.4.4 help!!

#fabric-chaincode

Which version of fabric and fabric-samples are you using? example02 was renamed abstore over a year ago. I recommend you move to at least fabric-1.4.6 if not 2.0.1. -- Arnaud Le Hors - Senior Technica

#fabric-chaincode

Hi, You can copy your own chaincode in same folder or mount the chaincode folder to docker-compose file in cli container. For simplicity, you can modify example_02 chaincode as per your own chaincode

#fabric-chaincode

I am using the fabric 1.4.6. I am unable to use pluggable transaction endorsement and validation. There is no samples available. I also tried http://github.com/hyperledger/fabric-chaincode-go/pkg/stat

#fabric-chaincode #fabric #consensus

Hi members, I built my HLF network based on v2.0 test-network and have 3 instances in GCP. - Instance 1 : cli, peer0.meters, peer1.hq, ca.org1, orderer0 - Instance 2 : peer0.hq, peer1.meters, orderer1

#raft #tls #fabric #fabric-chaincode #fabric-orderer

Is there anyway to increase the wait time on a chaincode instantiation? The default seems to be about 10 minutes but I have a peer with low bandwidth and the docker image download combined with the co

#fabric #docker #fabric-chaincode #fabric-questions #hyperledger-fabric

This, I believe, will be a mismatch of versions on the `build.gradle` file; Check the version of the 'shadowJar' plugin used - in some examples there was an older version of this that was for previous

#fabric-chaincode

Hi, I think it might be a problem with the different versions. I upgraded to 2.0 & everything works fine. Thanks

#fabric-chaincode

My guess is that you have either not configured the correct Docker network in the config (vm.docker.hostConfig.NetworkMode / CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE) or that the Docker network you creat

#fabric #fabric-chaincode #fabric-questions