Hi, I wish to access the public key certificate of the current user prior to invoking a chaincode transaction in my client application. At present to access the identity I do the following using the N

#fabric-sdk-node

Sorry for multiple emails. But to give more information on the problem, I am sending the log of couchdb container. [notice] 2019-12-18T10:44:54.593120Z nonode@nohost <0.340.0> -------- chttpd_auth_cac

#fabric #fabric-sdk-node

Hi Baohua, Me to encoutering problems during chaincode instantiation. I don't use any SDKs. Just using CLI command but I get "Error: could not assemble transaction, err proposal response was not succe

#fabric #fabric-sdk-node

ankit, Seems that's the policy issue, and have you joined the peer into the channel successfully? And what id are you using to do the installation? Besides, I think this project might be helpful for y

#fabric #fabric-sdk-node

The Node, Java and Go SDKs all have the ability to use HSMs. The Go SDK uses a similar config to the peer as it basically embeds the bccsp code. The Node SDK allows you to pass in a PKCS11 crypto suit

#hsm #fabric-sdk-node #fabric

Thank you Gari for your quick reply. So from what I understand, since I created my admin user using the fabric-ca-client plugged to the HSM. If I configure the peer CLI command so that it uses the sam

#hsm #fabric-sdk-node #fabric

The peer CLI currently uses the same config as the peer. If you point the peer CLI at a core.yaml file which uses PKCS11 for the BCCSP (same as you would do for the peer), then things should work. If

#hsm #fabric-sdk-node #fabric

Hi all, I've been trying to plug fabric to an HSM to avoid having the private keys stored in the file system of the components (except the TLS ones since it is currently not possible to do the same fo

#hsm #fabric-sdk-node #fabric

I am using fabric 1.4 with raft configuration. create channel, join channel, update anchor peers and install chaincode worked fine but facing this issue when trying to instantiate chaincode: NodeJS lo

#fabric #fabric-sdk-node

Getting this error when trying to instantiate the chaincode on Org1: Peer isn't eligible for channel mychannel : implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requ

#fabric #fabric-sdk-node

We are not using CLI. We are creating channel using Node SDK and creating infrastructure using shell script. We are using Raft consensus with 5 orderer and Raft cluster is working fine. Orderers elect

#fabric-sdk-node #docker #raft #consensus #cal-notice

Hi All, Is there any recommendation for fabric Node JS SDK version to be used for a specific fabric version running on the network peer/orderer/ca nodes. For example, if my fabric network is running o

#fabric-sdk-node

It was not really a Node SDK limitation but rather a node-gyp issue. We require node-gyp as we use native modules. The latest versions of npm ship with versions of node-gyp which support Python 3.5, 3

#fabric-sdk-node

As per the Official Hyperledger Fabric Doc, "The Fabric Node.js SDK requires an iteration of Python 2.7 in order for npm install operations to complete successfully." As per the https://pythonclock.or

#fabric-sdk-node

I have added in "artifacts/channel/configtx.yaml" file. Profiles: ThreeOrgsOrdererGenesis: Orderer: <<: *OrdererDefaults Organizations: - *OrdererOrg Consortiums: SampleConsortium: Organizations: - *O

#fabric-sdk-node

You will have to add this newly created org Org3 to consortium first as I guess this Org3 is not part any consortium. Thanks, Anil Thanks, Anil Singh +91 8197218180

#fabric-sdk-node

Hi, I was trying to create a new org with name org3 in balance transfer application 1.4.3 version. Started the network, I tried to run all the REST API's as per the documentation. After registering us

#fabric-sdk-node

Hi Kamlesh, PFA the configtx.yaml file. Those 800K records - manually i tried all and i was able to insert all of them but the issue was coming intermittently and wanted to know what's the cause of th

#fabric #fabric-sdk-node

Hi Soumya, Please check your block creation configuration in "configtx.yaml" file. There could be block size is the reason for failure. Can you please share your configtx file. Thanks Kamlesh Nagware

#fabric #fabric-sdk-node

Hi Raj Sekhar, Fabric - v 1.4.3 Environment - Microsoft Azure Cloud - 6 Ubuntu 16.04 VMs , 8 GB RAM, 2vCPU Kafka - Zookeeper Orderer Set up ( 2 Orderers) Organisation 1 Org -- 2 Peers (1 anchor and on

#fabric #fabric-sdk-node