I have installed hyperledger fabric 2.0.0. When I try to run the fabcar example, I am getting an error like this "Error: error getting endorser client for channel: endorser client failed to connect to

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

Failure Scenario 1- Started the network with privatechannel_cc v1 chaincode installed 2- Did multiple transactions 3- Ran a script to upgrade the privatechannel_cc v2 ( GOT THE ABOVE ERROR) `COULD NOT

#fabric-chaincode

Fabric only exposes a subset of CouchDB functionality. JSON queries and associated indexes are supported, but map reduce queries are not supported, since this is not a pattern we expect many databases

#fabric-chaincode #couchdb

this statement is so flawed, there is no such requirement in ALL public blockchains. at most you can say is this is true for private/consortium blockchains, even that is terribly flawed since even PBF

#fabric-chaincode #ssl #fabric #fabric-questions #fabric-dstorage

PBFT has an "all to all" message pattern, so it means that all nodes need to send to all nodes messages. While it can sustain up to a third faults, it doesn't mean you'd want to run a deployment of PB

#fabric-chaincode #ssl #fabric #fabric-questions #fabric-dstorage

Hi All, Initially, I have Org1 in my fabric network. after that, I added Org2 into the consortium My question is I already install and instantiated the chain code in org1 Now I stall the same chaincod

#fabric-chaincode #fabric-questions

Hi Suresh, It must be the exact same folder with the exact same files when you install. But that's not for production, here's what you do: 1. In org1 where you instantiated the chaincode, run the the

#fabric-chaincode #fabric-questions

Looks like you were actually not persisting the storage for your peers (ledger, installed chaincode, etc). It seems the orderer was still running so the channel already considered the chaincode to be

#fabric-chaincode

If you run "install" with the package option on two different machines then instantiation can fail due to the mismatch issue. Did you try packaging first and then installing the same package on both p

#fabric-chaincode

I can see how that is a problem when we are upgrading the chaincode (Hash might have changed due to the timestamp) but we tried installing and instantiating a chaincode with a different name first on

#fabric-chaincode

Yes we have tried packaging, signing and then installing on each peer. We also confirmed by listing the chaincodes on both the peers and the IDs matched. The IDs also matched in the previous case as w

#fabric-chaincode

Hello, On today's contributors call I will be discussing the design for the updated programming model for Go chaincode in Fabric. Attached are the slides that will be run through which explain the app

#fabric #fabric-chaincode

goleveldb stores keys in sorted order. Therefore key queries and key range queries (such as those used under the covers for chaincode composite key queries) are both extremely efficient and have simil

#fabric-chaincode #fabric-questions

Thanks Andrew! As always, the recording can be found at: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings Dave Enyeart andrew.hurt1---11/13/2019 05:37:48 AM---Hello, On today's contrib

#fabric #fabric-chaincode

Oh, is it? Thanks for reply David.

#fabric-chaincode #fabric-questions

Hello Ivan, I have been following this thread for a while. Thanks for raising some of these issues. While it is important to question and to challenge the assumptions underlying Hyperledger Fabric, th

#fabric-chaincode #ssl #fabric #fabric-questions #fabric-dstorage

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 to

#fabric-chaincode

Hi All, This issue is resolved . Actually there was an issue in the configtx.yaml where the allignment of the key - Organization under Application section was not proper it was under the ACLs. Configt

#fabric #fabric-chaincode

Hi Yacov again you are bypassing the question, to be honest I am quiet frustrated now. the community is not about defending a stance but to find a solution to on going problems, and if something is wr

#fabric-chaincode #ssl #fabric #fabric-questions #fabric-dstorage

Hi guys, I have been using leveldb as the state database for my application and use golang for chaincode. Here, to do a query of a field of a struct other than the key / primary identifier, I chose to

#fabric-chaincode #fabric-questions