Hello, I copied the fabcar code and made a seperate in the fabric-samples and was tinkering with the chaincode to see if I can add new methods and functionalities, but I have been having issues. I

My apologies. If I had read further the first time I would have noticed this JIRA, immediately following the previous one I linked to, which clearly states you are working on documentation updates for

As indicated at https://stackoverflow.com/questions/55394476/error-could-not-send-eof-on-instantiating-chaincode , EOF can be caused by TLS issues between client and orderer. This issue is now

Hello, I am encountering the attached error in the first of my chaincode containers that is being invoked after the chaincode has been installed and instantiated on my peer. I thought this could

Looks like the client failed to send the results to the ordering service node: https://github.com/hyperledger/fabric/blob/release-1.4/peer/common/broadcastclient.go#L63 Not sure why grpc returned EOF

Your chaincode image build took over 3 minutes which is much longer than normal. The instantiation request and container start looks like it was ultimately successful, but the instantiation result was

Hi, I am trying to setup HLF to run in K8s. I see that peer is starting chaincode container and chaincode container is running succesfully. But instantiation step is exiting with EOF and when I

https://jira.hyperledger.org/browse/FABCN-405 https://github.com/hyperledger/fabric-chaincode-node/pull/150 thanks for pointing this out! Ry -- Ry Jones Community Architect, Hyperledger Chat:

Thanks Matthew! I changed the source code of my "package.json" as Matthew indicated, and my chaincode was successfully instantiated. Explanation: (1) I wrote my package.json with reference to the

Hello - the module is `fabric-contract-api` rather than chaincode-api:-) Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at WHITEMAT@... Find me on

The desired solution for this is to allow peers to join channels starting from the latest config block rather than requiring starting from the genesis block. The checkpoint/archive feature will also

I replied in the JIRA, I agree with youranalysis that adding these parameters to configure the peer's channel joiningmight be useful. From: chintanr97@... To: fabric@... Date:

I am encountering the following scenario: I am running a network on multiple hosts. The network has one Orderer Organization (3 orderers in RAFT mode) and 1 Peer organization (2 Peers). Both having

@Yacov, I would like to highlight that why aren't we making using of peer CLI command for this? I mean to say that in "peer channel join" command we have an option of specifying the orderer endpoint,

Hello All! I wrote my chaincode using Node.js API, and now I'm trying to instantiate. image: hyperledger/fabric-peer:1.4.5 My package.json has the follow source: // ------------------- {

You are really asking two separate questions here. 1. ORDERER_GENERAL_TLS_ROOTCAS Strictly speaking, you don't necessarily have to set this at all. This config parameter is used by the orderer to

Read this JIRA https://jira.hyperledger.org/browse/FAB-5288 From: chintanr97@... To: fabric@... Date: 05/18/2020 09:37 AM Subject: [EXTERNAL] [HyperledgerFabric] Adding a peer

You can find the basics of gPRC TLS authentication here: https://blog.gopheracademy.com/advent-2019/go-grps-and-tls/ The article does not cover the usage of multiple CAs, but we could suppose it would

The peer fails to join the channel in the following scenario: A channel was created by the Orderer Organization (running 3 orderers in RAFT mode). A peer organization was added (let's say with 3

There is a config value for each channel named "HashingAlgorithm". This is not currently configurable and it set to SHA256. ----------------------------------------- Gari Singh Distinguished