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 tra

#fabric-orderer #consensus

Hi Yacov, Thanks, I saw the commits with that change so I tried that first, I generated the new certs using the same private keys and uploaded them without changing the configuration but I don't know

#consensus #configtxgen #fabric-orderer

Can't you just issue the certificate with the same public key but with SANs? You don't need to do the config update if the public key of the TLS certificate stays the same. You can just change the cer

#consensus #configtxgen #fabric-orderer

Hi, I'm having trouble updating the TLS certificates for my blockchain's orderers, when I created my certificates, I was using hlf v1.4, golang 1.14 and SANs wasn't enforced, now I have upgraded my bl

#consensus #configtxgen #fabric-orderer

I'm using hyperledger fabric 1.4.9 and my admin certs and tls certs of ordererers expired. I also raised the issue on jira. After enrolling new admin and tls certs i try doing this :- Do config update

#policies #administrator-organiization #consensus #fabric-orderer

Hi Community, We are trying to set up a governance model for our fabric network. The requirement is such that only a specific set of organizations in the consortium should be able to approve the reque

#administrator-organiization #fabric #hyperledger-fabric #consensus #policies

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

Hey, I believe this might be a problem with the read/write set of your transactions. In your chaincode, read the private data hash (as suggested here) of the other (in terms of execution environment)

#hyperledger-fabric #consensus #fabric-chaincode

Hi All, I have blockchain network consisting of two ORGs, each ORG having only single peer. And I have simple chaincode with several functions. One function that I'm invoking has two operations: read

#hyperledger-fabric #consensus #fabric-chaincode

Thanks a lot, Dr Brett. Please forgive my problem. I am also a layman with linux.

#consensus #fabric-questions #fabric #hyperledger-fabric

You have a space between `--config=` and the file name. So it's parsing the file name as a flag, not as an input to a flag. Brett Logan Software Engineer, IBM Blockchain Phone: 1-984-242-6890 E-mail:

#consensus #fabric-questions #fabric #hyperledger-fabric

Thank you for your kind reply, Dr Dave. However, I think there are still differences between first-network in v2.1 and test-network in v2.2. When I check the files in v2.2, I find crypto-config-org1.y

#consensus #fabric-questions #fabric #hyperledger-fabric

If you want to see an example of two peers per org, look at the old Build Your First Network tutorial and sample in v2.1: https://hyperledger-fabric.readthedocs.io/en/release-2.1/build_network.html ht

#consensus #fabric-questions #fabric #hyperledger-fabric

I am using 2.0 and I assume 2.2 did not change this aspect - but you need to look at the policies in configtx.yaml. That defines the consensus via policies. You ask about endorsement, and that is defi

#consensus #fabric-questions #fabric #hyperledger-fabric

Dear everyone, I start to learn hyperledger fabric v2.2 and find that there is only one peer in each org. And the examples including test-network and commercial papers are all in this construction. I

#consensus #fabric-questions #fabric #hyperledger-fabric

If you send a steady flow of updates for the same key, you will always have some transactions in flight (endorsement or ordering phase) while earlier transactions are committing on peers. Since the la

#hyperledger-fabric #fabric-chaincode #consensus #raft

ِThanks Prasnth for your reply. So, you think it is a racing condition. Just to confirm with you. So, what the best way to update a value bases on its previous value? I need an example that does not i

#hyperledger-fabric #fabric-chaincode #consensus #raft

Hi Ali, Yes. MVCC - Multi Version Concurrency Control. It occurs exactly when like you mentioned. You need to design the chaincode in such a way to avoid frequent same key update as much as possible.

#hyperledger-fabric #fabric-chaincode #consensus #raft

Hi everyone, I have this wiered MVCC-conflict issue. It appears occasionally as I benchmark my Java chaincode. I tried everything I possibly could to prevent its occurance. Now, I am going to list the

#hyperledger-fabric #fabric-chaincode #consensus #raft

I am using the fabric 1.4.6. I am unable to use pluggable transaction endorsement and validation. There is no samples available. I also tried http://github.com/hyperledger/fabric-chaincode-go/pkg/stat

#fabric-chaincode #fabric #consensus