this method: https://fabric-shim.github.io/master/fabric-shim.ChaincodeStub.html#getStateByRange Note that startKey and endKey can be empty string, which implies unbounded range query on start or

Error: Got error while committing(read tcp 10.0.9.49:37944->10.0.9.15:5984: read: connection reset by peer error reading response body We have the following environment setup and

I got this error often, the reason is all the peer node execute their own chaincode individually and even if the result is successful, it doesn't means that all the payload are the same. By looking at

Whatever public IP other peers would use to connect to it. Docker and NAT (in docker's case double or triple NAT) complicate matters, you will have to pay attention to how you will have peers

What should be the CORE_PEER_CHAINCODEADDRESS when the peer is not running in a docker container? E.g., peer is running on the host and listening for chaincode at 0.0.0.0:7052. If we set

could anyone point us to the code where the response payload is generated? is there any doc explaining what the response payload is? its a byte array but what does it contain? From: Siddharth Jain

Your question gets to the heart of many use cases. And with v2.0 release coming, this is a great time to have the discussion. You have two options to choose from depending on your specific

Hello Fabric guys, I have a scenario where there are X orgs in a Hyperledger Fabric network. I would like to have each org can create/set/reset their respective values for key(s). However, other orgs

we get this error when trying to invoke the chaincode on a network of 3 peers. However, we have verified if we invoke the chaincode individually on the peer nodes, all of them respond with Chaincode

I've created a network configuration with 2 orgs, each one with 1 peer and CA. I've successfully installed and instantiated my chaincode on both peers But after invoking a transaction this error

Has anyone taken a look at revive^CC? it is: Static analysis tool for Hyperledger Fabric smart contracts written in Go. Ry-- Ry Jones Community Architect, Hyperledger Chat: @rjones

Listen is for the bind() call. Peer address is the externally visible address published during discovery. Please research bind() if that is unclear.

One more question. I am assuming the CORE_PEER_CHAINCODEADDRESS and CORE_PEER_CHAINCODELISTENADDRESS are analogous to CORE_PEER_ADDRESS and CORE_PEER_LISTENADDRESS respectively i.e., whereas the

What if your friend is abroad and you'recalling his office phone, and he configured his office phone to redirectthe call to his cellphone? The listen address is the address thepeerbinds its socket. It

from the docs w.r.t. CORE_PEER_ADDRESS it is said that this represents the endpoint to other peers in the same organization. and CORE_PEER_LISTENADDRESS is The Address at local network interface this

You can start by having a look at this generic network. https://github.com/lepar/hyperledger-fabric-generic-network Other resources can include the fabric documentation network

Hi, can someone point me to more information on the resources we could need for a Hyperledger Fabric production deployment? The idea is to start with 3 organizations using on premise hardware. We are

https://en.wikipedia.org/wiki/No_true_Scotsman

‘Altar of Proof of Work’ seems to be the biggest sticking point for all the definitions and it echoes “bitcoin maximalism”. In my mind, Linux Foundation, have made so much investment into the

Let's not get too hung up on terminology in such a charged environment. Don't take this as an "official statement". Yes, Fabric's underlying data structure involves a string of