We could revoke an user successfully. But, unable to update the channel with crl details. We are getting below error Unexpected error error applying config update to existing channel 'trusttrace': ini

#fabric #hyperledger-fabric #fabric-sdk-node

I am trying to install chaincode on a mac catalina which has Symantec WSS. I get following error when I try to install chaincode: + peer lifecycle chaincode install mycc.tar.gz + res=1 Error: chaincod

#fabric-sdk-node #tls #fabric

On May 2, 2021, at 10:51 PM, Kevin X <kevinx8888@...> wrote:  I am trying to install chaincode on a mac catalina which has Symantec WSS. I get following error when I try to install chaincode: +

#fabric-sdk-node #tls #fabric

Do you have Docker installed?

#fabric-sdk-node #tls #fabric

Yes, docker is installed and local network is up. This is happening at npm install stage likely when chaincode docker image is built.

#fabric-sdk-node #tls #fabric

Hello, we are running a Hyperledger Fabric network on Kubernetes (using minikube, kubectl to run locally) and then trying to connect the Node SDK with the network. Currently, we have a fabric network

#fabric #kubernetes #fabric-sdk-node

Those certificate verification failures during the TLS handshake look like a problem to me. I guess the node certificates are not valid for localhost. Maybe you could add entries to your client's loca

#fabric #kubernetes #fabric-sdk-node

Good day, Thank you for your reply! And apologies for my late reply. For the TLS certificates, I used the registerEnroll.sh script that is included in the test-network files (in /test-network/organiza

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Hello everyone, I've been running into a problem with a Hyperledger Fabric network that I’ve deployed non-locally and I would like to ask for some insights or assistance regarding this problem. I depl

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

My guess has something to do with the TLS certs. In order to access your peers by the HL Fabric client, you need to configure the certificates properly. If you access them by IP instead of FQDN, you s

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

To close the loop on this one... we found that two peers were configured to use a single CouchDB database, and therefore the peers were stepping on each other and getting inconsistency between peer da

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes

It is recommended to use endorsement policy > 1 to ensure that multiple peers are in agreement for each transaction. Similarly you can query multiple peers if the state is in doubt. This will protect

#fabric-sdk-node #database #fabric-questions

The value is base64 encoded, not encrypted. The value is represented as bytes and base64 is how bytes are represented in JSON. Your value is decoded as: {"class":"aipay.payment","key":"\"0004_workstat

#fabric-sdk-node #database #fabric-questions

Thanks David! Will probably do your first pair of suggestions as it is the easiest to do for now. I'll be looking forward to the new snapshot feature though.

#fabric-sdk-node #database #fabric-questions

Thanks Matthew! I didn't know decoding it was so easy. By any chance, do you know how to get a block and decode it via APIs instead of CLI?

#fabric-sdk-node #database #fabric-questions

===================== Chaincode is installed on peer0.org2 ===================== Instantiating chaincode on peer0.org2... + peer chaincode instantiate -o orderer.example.com:7050 --tls true --cafile /

#blockchain-explorer #fabric-sdk-node #dstorage #fabric

I am currently migrating my project from v1.4 to v2.x, and found out that the Node SDK fabric-client module will not be supported on v2.x. I was using fabric-client to install and instantiate chaincod

#fabric-sdk-node #fabric

Check out this tutorial, I believe this can be a good place to start: https://chainstack.com/deploy-a-hyperledger-fabric-v2-web-app-using-sdk-for-node-js/

#fabric-sdk-node #fabric

While executing a submitTransaction method i am getting an error like "2020-04-30T17:18:11.313Z - warn: [Transaction]: _validatePeerResponses: Received error response from peer: message=transaction re

#hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabric-sdk-node

I am getting an error while invoking functions in smart contract Could anyone let me know why i getting this silly error, I only have one argument in the function as argument looks like this "async vi

#fabric-sdk-node #hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabricca