When I just started to up first-network example by./byfn.sh up of fabric 1.1, I got this error on Macbook pro. What could be the issue and how to resolve this? I tried to change mod to 777, but no

Hello Folks, When am trying to connect my peer to a channel created using cli “peer channel join -b sunsuchannel.block” I fails with below error, anyone can please suggest what am I missing

Hello, Our project currently connected with IoT, and we are concerned about network traffic in HPF. In Fabric 0.6 there was an peer network requests to subscribe to chaincode events and transaction

Well, isn't one of the biggest selling points of (D)LT to avoid the requirement of having third parties to establish trust? Of course, I understand that this is not black and white, and in this case

We have thus far only shipped a crash-fault tolerant ordering service. BFT orderer is coming later this year, along with a less operationally complex RAFT orderer based on etcd-raft. The whole point

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