I noticed that the addorg3 process in fabric2.x is different from that in version 1. I'm trying to use docker-compose - f docker / docker-compose-org3.yaml up - d command to started, the following

Good point David, Please also check for MVCC (Multi Version Concurrent Control) CONFLICT errors at your client and orderer logs. Regards, Marcos Sarres | CEO | +55 61 98116 7866

Just as a complement to Marcos and Tsvetan, I got similar errors due to concurrency control when doing stress tests with the same asset keys. You may check why the transaction fails using QSCC

Hi Curtis, Marcos has a good point and you should check your client logic. To better understand could you share also how many peers participate in the transaction endorsement? Are those failed/bad

Please check your Hyperledger Fabric client. The endorsement policy should be fulfilled at your API sending the message proposals the the endorsement peers further receiving and packaging the

Private Chaincode Lab When: 04/05/2022 8:00am to 9:00am (UTC-07:00) America/Los Angeles Where: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Organizer: Marcus

Ok based on theory I quote:So I understand that in case I have 3 orderer nodes and one is unavailable the Raft works based on the concept of a quorum in which as long as a majority (i.e 2) of the Raft

As the scenarios become more complex, multi-channel, which nodes participate in each, etc… I can only refer you to the docs. The answer to “Are all the nodes joining the channel?” Is “Some or

Also, how can I list which orderers nodes are consenters? Are all the nodes joining the channel?

Sorry but I misspelled. "What I have to change in order the network to keep running with one peer after the second one is down" is wrong. I meant what happens in case where I have only two orderer

Nikos, Be careful about what you mean by “consensus”. In most blockchain conversations consensus refers to an agreement about what is stored in the blocks. In Hyperledger Fabric, that is

Hi all, I created a test network which has 2 orgs (each with one peer), 1 orderer in kubernetes using BAF. Orgs are joined in the channel called testchannel. Orderer msp, peer msp and tls certs

What happens if I have two orderers nodes and one is down? What I have to change in order the network to keep running with one peer after the second one is down (I believe somehow I have to change the

Satheesh, There are many such use cases. What you want to track are linked assets, and you can implement them with both shared and private details, so all participants can see shared info but only

My understanding is, and yes I can accept correction, that the number of consenter nodes is “enough to reach consensus”. If your network relies on majority consensus, the minimum is three. That

Consider supply chain usecase where manufacturer, wholesalers, distributors and retailers are involved. Manufacturer wants to track batch of products manufactured and shipped all the way till

Hi All, Using BAF, I had a hyperledger fabric network v2.2.0 which has 11 orgs, 5 orderers and 5 channels. Org1 is a part of all the channels. Other than that each channel has 2 individual orgs. So

Hello world! I’ve hit what appears to be a strange situation when testing my soon-to-be production network under a bit of (very light) load. I have a very simple chaincode function that is

I created a new orderer node (in the orderer org) and I would like to join this node to the existing channel. Should I add this new orderer node to the consenters? In general, when should I add the

Hi Fabric community, A short notice and request for feedback on the Fabric Gateway client API for Fabric v2.4 and later. At some point in the not-too-distant future, we will publish a v1.1 release of