If keys are generated by the CA then what is the best way to distribute these keys? Thanks Trevor

I'm able to create the channel. But while joining the channel, I'm getting the error given below: [2019-10-24 09:34:38.049] [DEBUG] Join-Channel - Join Channel R E S P O N S E : [ [ { "status": 500,

Check out my article: https://medium.com/coinmonks/demystifying-hyperledger-fabric-1-3-fabric-architecture-a2fdb587f6cb#4573-- Best Regards, Phuwanai Thummavet Blockchain Architect and Full-Stack

https://hyperledger-fabric.readthedocs.io/en/release-1.4/gossip.html Ben Taylor, CEO LedgerDomain 212.332.4466

Hello Everyone, I have some confusions regarding how state ledgers are persisted across multiple ledgers. I have an intuition that every org's peers have a copy of the ledger from where they generate

dear Fabric ApplicationDeveloper, the next FabricApplication Developer community call is scheduled for this ThursdayOct 31st @ 4pm UTC (4pm UK, 11am ET, 8am PT) . It lasts approx 30-60 mins FYI.

Hi Dave, One quick question, does the support for " external chaincode " include support to run chaincode as a remote grpc server? Hu Xiang Dong (胡香冬) IBM Blockchain Platform

Hi jeroiraz Oct: : there are actually quite a few ways to validate anything including national ID using ZKP or ZKP like technique (e.g. I can design my crypto to validate if the two text data

Hey, I've had this problem before. What I did to solve it and seems bizarre is I created a new file and just simply copied and pasted the entire chaincode to the new file and used that.

I am writing a chaincode in Typescript and trying to deploy on to a Custom Network with an orderer, one Peer with Couch DB and a CA. When i deploy the chaincode on to the peer , the following

Hey Siddharth, If you're trying to debug the peer binary, I would recommend eschewing the docker containers entirely and just running the peer binary directly on your computer, and using the standard

Go does exist in the parent docker image of the orderer i.e., hyperledger/fabric-baseimage root@2c068c753e05:/# find . -name

The go binary is not needed in that container, it is only needed to build it. You misapprehend what the go image is used for.

root@c754367ff2ba:/home# go bash: go: command not found root@c754367ff2ba:/home# ls /usr/bin/go ls: cannot access '/usr/bin/go': No such file or directory root@c754367ff2ba:/home# ls

/usr/bin/go, /usr/local/bin/go, and /usr/lib/go-x.xx/bin/go are all more likely than /usr/local/go

I logged into a fabric-orderer:1.4.3 container and cannot find Go in it. root@c754367ff2ba:/home# echo $GOPATH root@c754367ff2ba:/home# ls /go ls: cannot access '/go': No such file or

Unfortunately, the CLI for both the peer and the orderer is actually the same peer CLI. "peer channel join" talks to the peer whereas "peer channel create" talks to the orderer. Not my favorite

The system channel is on the orderer, not the peers.

Is the system channel always the first channel that you create/define? And this would mean I need to follow a similar path as the adding org to existing channel i.e. getting the channel config, adding

Ah ... so in that case you will first need to update the system channel with the new consortium definition prior to trying to create channel for that