I have deployed a AWS managed Hyperledger Fabric v1.4.7 blockchain. The HLF blockchain network and the EC2 instance (hlf-client) are in the same VPC and everything seems to be working fine since I am

#fabric #aws

Peer v2.3.3

#fabric

Hi, I am running a fabric network of 3 peers, 2 orderers and 2 external chaincodes on K8s cluster. Everything's running fine and smooth as expected. I have been monitoring the memory usage of the fabr

#fabric

I have got the hyperledger fabric blockchain deployed on kubernetes in namespace: hfl-fabric and the client app using fabric-sdk-go is in another namespace: hlf-app. I am using the gateway api to conn

#fabric

I figure out the issue with this. If anyone encounter the same problem then this might help. Make sure that you're copying the META-INF folder in the external build and release scripts. You can refer

#fabric #couchdb

I am building and deploying the chaincode externally on hyperledger fabric v2.3.2 and using couchdb as the state DB. I would appreciate if anyone could tell me how to package the couch DB indexes? Cou

#fabric #couchdb

The below error might have been caused due to "system-channel" in which orderer is a participant. You might have created "system-channel" first and then an application channel "mychannel" using the ge

#ssl #fabric

The peer are emitting the error logs as:

#fabric-ca #fabric

Hi, Looking at the logs, it seems the error is due to an incorrect path pointing to the msp/certificates. Double-check in the network.json file under the key "organizations.OrgMSP.adminPrivateKey" - b

Hi Gari, To test it out, in the CA config file, i set the expiration to 1h and before the certificates expired i reenrolled the `msp` and `tls cert` again with the `--csr.keyrequest.reusekey` flag in

#fabric-ca #fabric

Hey Chris, Thank you for following up! I will give it a try. One hack I have tried - backup the ledger data, and tear down the network. And then get the fabric network up and running again, in process

#fabric-ca #hyperledger-fabric

I am on fabric v2.3 Anyone here has completed this step/process of renewing the certificates in order to continue submitting the transactions from farbic client sdk? All i can find in the docs is just

#fabric-ca #fabric

I followed that path, and seems like it's not a straight-forward to update the tls-certificates. I pulled the latest config block using the peer channel fetch config and decoded it into json file to c

#fabric-ca #hyperledger-fabric

Hey Chris, Thanks a ton! This definitely points in the right direction.

#fabric-ca #hyperledger-fabric

While renewing/reenrolling what all do we need to do. I mean is there a standard way of doing this? I am on fabric v2.3. This following are straight from the `test-network` fabric sample When we get t

#fabric-ca #hyperledger-fabric

I am getting the transaction from the 'QSCC` chaincode by executing the `GetTransactionByID` function. qscc := network.GetContract("qscc") txn, err := qscc.CreateTransaction("GetTransactionByID",gatew

#fabric

yea like you mentioned i am using InvokeChaincode on the chaincode stub to evaluate transactions on other chaincode. i might have figured out the issue in my use-case. i am creating 1000 connections f

#fabric

I am maintaining 1000 concurrent connections (SubmitTransactions) which invokes the smart-contract. The smart contract does the following operations: 1. "EvaluateTransaction" - on another chaincode 2.

#fabric

i am using the fabric-sdk-go v1.0.0 the below code snippet is throwing the error: Discovery status Code: (11) UNKNOWN. Description: error received from Discovery Server: failed constructing descriptor

#fabric-sdk-go