Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info. I am

If we build chaincode using below steps repeatedly without removing .tar bundle each time, we can observe increase in bundle file size. Eventually we encounter rpc error mentioned. peer lifecycle

I would like to mention that this setup is spread between 2 clusters, I am exposing services between clusters to interconnect using skupper. the current running blockchain is on azure central India

Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info.

Exactly what chaincode build steps are you doing? Are you following one of the samples or docs? What component is the suspected bug in? From:fabric@... <fabric@...> on behalf of satheesh via

Got resolution from this thread: Hyperledger Fabric Go chaincode size too big - Stack Overflow @Fabric team, Is this not a bug ? If the packaged tar is not removed, repeated builds are increasing the

great. good to hear. Minifabric has been really heavily tested. It has been solid for past few years. On Friday, June

Started working now. I'm not sure if something in memory was causing the issue as rebooting my computer seems to have cleared up this issue - at least for now.

hi All, This is my block listener implemented in fabric sdk: Consumer<BlockEvent> blockListener = blockEvent -> { //some lines } networkObj.addBlockListener(startBlockNumber, blockListener);

We are using Hyperledger Fabric 2.3.0 and using SBFT Consensus, and leader is rotating after every block creation. and we set MaxMessageCount to 10 in configtx.yaml but it is not restricting no of

Hi team, I am calling contract event in following way. ==================== await contract.addContractListener(listener, { checkpointer: await

When installing chaincode in a fabric network, I get below error: # peer lifecycle chaincode install contract.tar.gz Error: failed to endorse chaincode install: rpc error: code = ResourceExhausted

A good starting point: https://www.udemy.com/course/hyperledger-fabric-network-design-setup/ Is 2.2 but with some adjustments, you can tailor it to 2.4.x version. And follow de

Hi All, Actually I was testing fabric sdk code. I have this blocklistener: Consumer<BlockEvent> blockListener = blockEvent -> { //some code } //outside //some code while testing it with JUNit

@Dave, Yes the NodeOUs are also configured. The logs state that the sub-policies are not being satisfied but there is evidently no such thing in the configtx.yaml which indicates/backs the claim. How

@Josh, I would love to see if fabric-operator and k8s-builder lifecycle make my life any easier. Need to find time to test them. Also, will keep my investigation of finding what went wrong with the

Dear Team, please reply -- Thanks & Regards Ahmad Hassan

Dear Team, I lost all transaction data in the block chain after restarting the system or network down. I am using hyperledger 2.2 and 2.4 also. -- Thanks & Regards Ahmad Hassan

You can use either OrgMSP.member or OrgMSP.peer format, assuming you’ve configured the MSP for Node OU roles and provided the matching OU “peer” tag in the peer’s certificate. More details at

Argo provides an incredible workflow engine for Kubernetes. It is _more_ than enough to handle the workloads of running Fabric CLI binaries - you are on a solid course for workflow