Hi Community, We're trying to run hlf explorer instance in k8s. Explorer looses a connection to a peer sometimes and outputs an error. [2020-11-26T12:55:34.394] [ERROR] FabricGateway - Failed to get d

#fabric-questions #blockchain-explorer #fabric-kubernetes

Hi Community, Whenever we deploy hlf peers in k8s, especially if there are more than 2-3 of them, the "context deadline exceeded" error happens from time to time while calling peer cli commands (like

#fabric-kubernetes #fabric-questions

Sorry, I don't quite understand. my_array is a single array here, no?

#fabric-questions #fabric-chaincode

Hello - The 'submitTransaction' function takes and array of parameters. In this case the transaction function has a single parameter, but it's an array. So you need to pass a single element array to '

#fabric-questions #fabric-chaincode

In the chaincode (in Golang) I have the following function: func (s *SmartContract) f(ctx contractapi.TransactionContextInterface, arr []string) error { /* function details */ } When I attempt to call

#fabric-questions #fabric-chaincode

Yes. It also requires Orderer's Admin user, i.e., change this env var: CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/test-network/organizations/ordererOrganizations/example.com/users/Admin\@...

#fabric-orderer #fabric-questions

Hey Yueming, The problem is that the system-channel can only be fetched using the identity/MSP of the orderer. So in your CLI you gotta use CORE_PEER_ADDRESS and CORE_PEER_LOCALMSPID as the OrdererMSP

#fabric-orderer #fabric-questions

Here are some details of my cli container added to the test-network to run this test. Same problem: CORE_PEER_LOCALMSPID=Org1MSP CORE_PEER_ID=cli CORE_PEER_ADDRESS=peer0.org1.example.com:7051 CORE_VM_

#fabric-orderer #fabric-questions

I can get config block of normal app channels, and previously I can also get the config block of the system-channel, but now after upgraded to v2.2, the following command returned error on system-chan

#fabric-orderer #fabric-questions

Hi All, I've managed to invoke the qscc chaincode to retrieve the transaction serialized response. My question is how do I deserialize it in node.js to get some relevant info out of the same? Can it b

#wsl2 #fabric #fabric-questions #consensus #fabric-sdk-node

More deeply, the question goes as: 1. Should we implement chaincodes from v2.2.x onwards such that we do not use `Init` and `Invoke` function in the source code. In this case to initialize ledger with

#externalbuilders #fabric-questions #hyperledger-fabric

Hi Team, I was searching for a command line equivalent support for `--isInit` flag in Fabric Node SDK v2.2.x. However, I could not find the same in the documentation. The other lifecycle commands can

#externalbuilders #fabric-questions #hyperledger-fabric

I tried and figured it out. The answer is that org2 user msp does not matter. When the client app belongs to org1, you need to configure only users of org1. It makes sense that org1's client app shoul

#fabric-sdk-go #fabric-questions

Assume that a chaincode is deployed on peers of 2 orgs, and I am a client of org1 that have signing keys of only users of org1, but the transaction must be endorsed by both org1 and org2. I guess that

#fabric-sdk-go #fabric-questions

>> Ideally, content is exactly same, creating packages at different timestamps, should not affect the hash right? ​ No. A tar file contains timestamps of the files included. So the tar files will give

#fabric-questions #externalbuilders #fabric

I am using "chaincode as an external service". So likely my package does not have any chaincode related dependencies. My package mycc.tgz contains following contents: 1. code.tar.gz This contains `con

#fabric-questions #externalbuilders #fabric

The unique identifier on the package ID is the sha256 of the chaincode "package" bytes. When you package the chaincode a metadata file is added that contains the path to the chaincode, its language, a

#fabric-questions #externalbuilders #fabric

Hi Team, I was trying to identify how is the chaincode package id calculated in HLF v2.2.x. More specifically, I understand that when dependencies change, the package ID would change too, for same pac

#fabric-questions #externalbuilders #fabric

I am not familiar with that log message so maybe somebody else can help there. On the latency, it's worth having a clear picture of the transaction flow and where latency will occur. For the client su

#fabric-questions #fabric #fabric-orderer #hyperledger-fabric

Thanks for Mark‘s referral of my open source helper. It is always welcome to use, comment and contribute for `npm khala-fabric-admin` Best Regards, David Liu 发件人: Mark.S.Lewis@... 发送时间: 2020年1

#fabric-sdk-node #fabric-questions