Thanks Dave for opening the bug. Now that's what a helpful response is. From: David Enyeart <enyeart@...> Sent: Thursday, October 24, 2019 7:38 PM To: Nye Liu <nye@...>; siddjain@...

Close... some key within the [Group] config has an illegal character. You can see the valid characters

visit lists.hyperledger.org and you can sign up with your Linux Foundation ID Chris

I might also add that in this case, the error message and backtrace are actually extremely informative "Illegal characters in key: [Group]" I'm guessing it doesn't

Debuggers are overrated. For this sort of thing you just need better error messages. Fabric is full of very cryptic and non-informative error messages. go get

Very often I keep into running cryptic errors with Fabric. E.g., today I ran into this: 2019-10-25 00:20:00.915 UTC [orderer.common.server] Start -> PANI 003 Failed validating bootstrap block:

https://lists.hyperledger.org/g/fabric ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton, MA 01460 Cell:

Hi, I would like to join the hyperledger mailing list. Best regards. -- Amine RachidIngénieur DevOps École nationale supérieure d'informatique et d'analyse des systèmes +212 6 35 80 36

My apologies, the below error: Error: got unexpected status: BAD_REQUEST -- Unknown consortium name: LoanchainConsortium Spencer From: White, Spencer (S.) Sent: Thursday, October 24, 2019 1:57 PM To:

Hello, I am attempting to create a second channel after my test network has already been up and running for awhile. Is it possible to do this? I am encountering the below error and the few comments

Did this discussion take place a long time ago? I hope it will go beyond the concept then :)

Hello All, We hold our regulardocumentation workgroup call this week, both Eastern and Western hemispheres. We moved to theFabric wiki last week for agenda building and minutes. You can seethe new

FYI, I have discussed with one of fabric-sdk-node maintainer, in concept-wise it is possible to implement a nodejs version of configtxgen: "see it as an inverse operation of

You are essentially suggesting to add a warning that private data content can't be known by non-members of the collection. That is the whole point of private data and anybody considering an

Hi Ivan, As far as I know, Blockchain/DLT platform itself does not claim to find fake data. However, one may build an application using blockchain to find fake data. An example from

To be clear, the root certificate is actually not the same although the CN will always be the same unless you actually change it in the config. You can run `fabric-ca-server init` to generate a

Dave, Yacov, and Alex Seems that the general response to this scenario is “this is an application design problem and should be solved by chaincode” But my argument here is that chaincode design

Sorry, I misunderstood the question, giving wrong response.

Hi, This is a tricky thing. I had the same issue and it took me a while to figure out the issue. This is definitely not mandatory to provide the root certificate and the private key to the CA because

That is what I was also thinking but did not know for sure as well. But when I read your previous post stating:I admit I had hope ;)