I am using the following Fabric Versions: 1. Fabric binaries: 1.4.4. 2. Fabric Node SDK version: 1.4.9 (fabric-network, fabric-client, fabric-ca-client). 3. Node.js version: v8.10.0 I wish to perform

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

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

You are correct that EventHub is the wrong thing to be using, and this is removed in the v2.x SDK. If possible, I would strongly recommend using fabric-gateway-java rather than fabric-sdk-java. It lay

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

Since there is no fabric-client anymore, what are solutions for automated(scripted) dynamic update of channel configuration? In my use-case organizations should be able to dynamically add each other t

#fabric-sdk-node #fabric

Hi, In version 2.0 of the node sdk for fabric it appears channel.queryBlock, channel.queryBlockByHash, channel.queryInfo and similar have been removed from fabric-network. How does one now query block

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

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

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

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

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

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

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

#fabric-sdk-node