Hello, In Fabric 2.3 the system channel is not required. osnadmin cli offers a way to join / remove orderer nodes to a channel. The peer cli is still used to join peers to a channel. For more

Ah, I understand now I guess. Maybe osnadmin is there to manage channels on an orderer and to manage a channel on peer I need to use peer command. Can someone please confirm this. Thanks Shantanu

Hi Team, Please suggest the difference between managing a channel(create/join/fetch) via peer command vs osnadmin command. I have gone through few pieces of documentation and I am not sure which one

Also, I forgot to mention that when running on Kubernetes I set the environment variable for the CORE_VM_ENDPOINT to “http://localhost:2375” and not unix:///var/run/docker.sock There is more

Hi Ramesh, I am still looking into the ramifications of the Deprecation of Docker Runtime in Kubernetes for my network. I’ll post what I find out. As far as your second question, you can do either.

Hello Everyone, Any further updates on this issue? I am facing the same issue, currently using HLF 1.4 version on Kubernetes 1.18 version and trying to upgrade kubernetes version to 1.19 version.

A good approach to achieve what Dave suggests is to use chaincode events to trigger business processes in response to committed transactions on the ledger. You emit an chaincode event from your smart

I am getting an occasional "Error: 14 UNAVAILABLE: Connection dropped" when calling Fabric chaincode via evaluateTransaction from my Node client. I haven't figured out the trigger for this

Private Chaincode Lab When: Tuesday, 27 April 2021 8:00am to 9:00am (GMT-07:00) America/Los

Meant to say it must be 'set' to true.

Hello, --tls.enabled is not complete. It must equal "true" so --tls.enabled true if using command line flags Note the 'tls' section of the following

hello, when we start fabric-ca server we get the following files are generated. -------------------------------------------------------------------------------- fabric-ca-server start \ -b

Hi Nikos, I have done this within my company and I prefer to issue identities to the end devices as we would the users. We do not use an intermediate DB as we use our Fabric blockchain network

Hello, I want to build a smart building IoT BC network and I am working to the network architecture. At this point I have built the IoT infrastructure and I am looking to integrate the BC idea.

Remember that chaincode execution is only a transaction simulation that builds a read/write set. The transaction doesn't get validated and committed until after it is ordered into a block. Therefore

You should also take a look at attribute based access control in chaincode, to authorize users to chaincode actions based on issued role attributes. See the sample and linked docs:

Hyperledger Fabric fix releases v1.4.12, v2.2.3, and v2.3.2 are now available. See details of the fixes in the release

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 23 April 2021 11:00am to 12:00pm (GMT-04:00) America/New

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 23 April 2021, 11:00am to 12:00pm, (GMT-04:00) America/New

Hi Jay, That's a good point. Thanks for the pointer. However, based on the criteria in the Operator Capability Levels page, the answer is a bit blurry. As it's now, Fabric Operator spans capabilities