Thanks Alexandre, #3 is what I was kind of considering. And regarding the malicious acts, I was wondering too about more subtle cases like let's say the member running the orderer is also an

"is there some general rule of thumb that advises when it's appropriate to create multiple channels within a single network, and when it's appropriate to simply create entirely distinct

is there some general rule of thumb that advises when it's appropriate to create multiple channels within a single network, and when it's appropriate to simply create entirely distinct

Luiz, These are good questions for orderer ownership. The options you have are as follows: 1. One member of the network runs the orderer, that member must be trusted by everyone else. 2. A third party

Hi, I have been wondering about the Orderer nodes also, but from a deployment and ownership perspective. The documentation seems to indicate that there should be of course at least one instance, which

I do agree Sjir, to be more explicit would be helpful. Chris

Very clear answers. I will propose in the Doc WG to include these crystal clear statements in the Conceptual topics, where appropriate. I would prefer instead of the first two sentences of item 2

1) a network is comprised of the peer nodes, the orderer nodes and the optional MSP (fabric-ca or other substitute) nodes. So, yes. The peer nodes obviously comprise the bulk of nodes (there will be

(more nitpicky pedantry ...) currently perusing the entire section on "peers" under key concepts, and want to clarify a few things that don't seem clear. first, in the opening sentence, a fabric

Hi, I am trying following steps from Go SDK (quoting package instructions with my comments). ### Running a portion of the test suite ```bash # In the Fabric SDK Go directory cd

hello, I was getting this error because the default nodes is not the latest, but an older one. After fixing this, I ran #./runApp.sh on 1 terminal and #./testApis.sh -l gaoling in another terminal

How is Idemix going to prevent same person impersonating as two different entities while signing (handle the problem of double signing) ? -- Yours sincerely, Subhra Mazumdar.

Yes, i got similar error -- Nik Frunza

Composer 19 exposes fabric SDK, so it is quite possible to write chaincode with the same behaviors as those in node or Go, however transactions and queries written that way do bypass the excellent

I was getting an error (Invalid characters) while creating a channel with upper case name. The error went away when the name was changed to all lower case. I do not recall anywhere in documentation

Invoking chaincode from chaincode is language independent. Both the Go and Node ChaincodeStub objects provide the "InvokeChaincode" function and it can be used to call chaincode written in any

Hi, There is no universalanswer to your question. Each possibility has its own pros and cons. Composercan certainly speed things up when it comes to development because it providesyou with a higher

I can find some documents that explain how to call chaincode function from another different chaincode written in same language (Go). But I don't know whether it is also possible to call a chaincode

Hello Folks, Am trying to develop Blockchain solution using Hyperledger and the approach that I have taken is to use the fabric samples “BYFN” sample for the configuration file templates and

I never said there was a hard coded limit. We’ve done stress testing with over 300 channels. Chris