Closed AdB9 closed 4 years ago
[ec2-user@ip-10-0-51-98 ~]$ docker exec -e "CORE_PEER_TLS_ENABLED=true" -e "CORE_PEER_TLS_ROOTCERT_FILE=/opt/home/managedblockchain-tls-chain.pem" \ > -e "CORE_PEER_LOCALMSPID=$MSP" -e "CORE_PEER_MSPCONFIGPATH=$MSP_PATH" -e "CORE_PEER_ADDRESS=$PEER" \ > cli peer chaincode instantiate -o $ORDERER -C mychannel -n ngo -v v0 -c '{"Args":["init"]}' --cafile /opt/home/managedblockchain-tls-chain.pem --tls 2020-07-03 07:01:23.122 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc 2020-07-03 07:01:23.122 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg instantiation policy violation: signature set did not satisfy policy``
Facing this error when trying to instantiate any node.js chaincode, golang chaincodes are running fine. What should I do ?
My guess is you've probably missed a step somewhere. Pretty tricky to debug this type of error. I'd suggest you start again and follow each step carefully.
Facing this error when trying to instantiate any node.js chaincode, golang chaincodes are running fine. What should I do ?