Re: validation of endorsement policy for chaincode failed #consensus #fabric-chaincode #hyperledger-fabric



I believe this might be a problem with the read/write set of your transactions. In your chaincode, read the private data hash (as suggested here) of the other (in terms of execution environment) peer and see if it works. You could probably also just read the private data hashes from both organizations implicit collections and compare them for the sake of achieving consistent r/w sets.


Join to automatically receive all group messages.