Thanks for reporting that... and Ry for putting in the PR! Will merge it shortly. Sorry about that.. can't believe I put the wrong name in that doc :-( Regards, Matthew. Matthew B White IBM Blockchain

#fabric-sdk-node

https://jira.hyperledger.org/browse/FABCN-405 https://github.com/hyperledger/fabric-chaincode-node/pull/150 thanks for pointing this out! Ry

#fabric-sdk-node

Thanks Matthew! I changed the source code of my "package.json" as Matthew indicated, and my chaincode was successfully instantiated. Explanation: (1) I wrote my package.json with reference to the pack

#fabric-sdk-node

Hello - the module is `fabric-contract-api` rather than chaincode-api:-) Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at WHITEMAT@... Find me on StackOverflow,

#fabric-sdk-node

Hello All! I wrote my chaincode using Node.js API, and now I'm trying to instantiate. image: hyperledger/fabric-peer:1.4.5 My package.json has the follow source: // ------------------- { "name": "demo

#fabric-sdk-node

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

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

===================== 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

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

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

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 I want to write node app for the test network. I see that the fabcar app is available for first-network. But the for test network there is no app example. Can you guide me please. Thanks

#hyperledger-fabric #fabric-sdk-node

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