Hi Omar, The read write set of the transaction contains the hash of the private data. If one organization reads from his implicit collection, the hash of that data is stored in the read set of the tra

Hi Mattia, The chaincode definition approval is stored on your peer. The commit transaction is similar to a chaincode transaction in that it queries your peers to get the required endorsements. Nik --

#fabric-questions

Did you already change the certificate for your admin to the new CA? You would need to do that after you have updated the channel. -----fabric@... wrote: ----- To: fabric@...

Which version of Fabric are you using? If you are using 2.0+, use the test network instead: https://hyperledger-fabric.readthedocs.io/en/release-2.0/test_network.html You can then use this tutorial to

Hey, Does your organization have the endorsement sub policy? Endorsement: Type: Signature Rule: "OR('Org1MSP.peer')" -----fabric@... wrote: ----- To: Fabric <fabric@...

Can you send the checkcommitreadiness command that you submitted? -----fabric@... wrote: ----- To: "fabric@..." <fabric@...> From: "Siddharth Jain

Hi Paul, This message states that you have already approved the chaincode definition as this org. The chaincode definition with sequence 1 has already been defined for that organization, and you canno

There is a currently a PR open to have the fabcar sample use the test network instead: https://github.com/hyperledger/fabric-samples/pull/103 You can either checkout the PR, or use the changes to poin

#hyperledger-fabric #fabric-sdk-node

Hi, Your logs say zero of the endorsement sub-policies were defined. Did you define the endorsement sub policies in configtx.yaml for your organizations? See here: https://github.com/hyperledger/fabri

Want to jump in to clear up something Brett said. If the chaincode is non-deterministic, then the read write sets will not match and will not pass the endorsement policy, and proposals will be rejecte

Hi Marina, I would check the order log to see what the problems are. You can find some help with what to look for with this stack overflow post: https://stackoverflow.com/questions/57662562/when-i-try

You need to set the FABRIC_CONFIG_PATH to to your configtx.yaml file. -----fabric@... wrote: ----- To: "hyperledger-fabric@..." <hyperledger-fabric@...

The approval is at the Org level. You only need to target one peer, and then the approval is distributed to other peers using gossip. The endorsement error also pops up if you try to commit a differen

Hey Ross, The chaincode lifecycle APIs in the Fabric Node SDK were introduced for the Fabric 2.0 Alpha and Beta, but will not be in place for the 2.0 GA. To deploy a chaincode on a channel, you should

Hey Suhan, The membership topic (which is in the process of being overhauled), you can find a description of the certificates in the channel MSP: https://hyperledger-fabric.readthedocs.io/en/latest/me

Hi Anoop, Seems like there is a problem with your crypto config, and the node OU's are not quite right. See this example: https://github.com/hyperledger/fabric-samples/blob/master/test-network/organiz

Hi Siddharth, This error is caused by a certificate problem. You can investigate further by checking your orderer logs. This stack overflow post: https://stackoverflow.com/questions/57662562/when-i-tr

If you are using the CLI to submit a transaction, you can use the peer addresses flag: --peerAddresses peer0.org2.example.com:9051 to target peers that you need for endorsement outside your org even i

Hi, The token work was part of the 2.0 Alpha. However, the maintainers have decided not to move forward with tokens on the 2.0 release. As a result, tokens have been removed from the latest code in ma

Hey Souma, What version is this running on? My guess is that you are not using an admin identity to run the command, or that the admincerts folder of the peer MSP is empty. If you are on Fabric 1.4.3,

#fabric-ca