Error : Cannot find Module 'fabric-client' in fabric 1.2 Even after trying "npm update" command, still i am facing fabric-client error. The error details given below Fabric version - 1.2 | OS -

Hi Chris, Here is the package command: # peer lifecycle chaincode package chaincode.tar.gz --path chaincode/chaincode/javascript/ --lang nod e --label counter_v1 2020-08-28 06:04:04.548 UTC [bccsp]

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 28 August 2020 6:00am to 7:00am (GMT+01:00)

Hi All, We will hold thedocumentation workgroup East hemisphere and Western hemisphere calls asusual this Friday. Please attend, you are very welcome! Thanks againto Pam and Joe for hosting and

Thank you for your response. But I'm not sure if your script generates the correct format for sendInstantiateProposal()​ or sendUpgradeProposal()​? As the output is different from the JSON object

traffic can go out out does not mean that traffic can come in, so ping google does not really mean your necessary ports are open. as I have indicated earlier in this doc,

I already assumed something like this, so I started it as root. It's weirdly causing very similar issues. In my opinion it's more a Fedora/Docker issue and not so much related to permissions. I have

But it's not that it won't work at all: $ docker run --rm -it alpine:latest /bin/sh Unable to find image 'alpine:latest' locally latest: Pulling from library/alpine df20fa9351a1: Already exists

Looks like that the user can not access docker endpoint and also cannot even create a file when the current directory is mounted to the container, you need to fix these permission errors first. I

Hi Bozhidar, Can you share the commands/output from when you packaged the chaincode? You may also find it helpful if you have not already done so, to review the tutorial “Deploying a Smart Contract

Tried. Doesn't work: (base) [user@f30 mywork]$ ./minifab up Unable to find image 'hfrd/minifab:latest' locally latest: Pulling from hfrd/minifab df20fa9351a1: Already exists 16d327ff9a88: Pull

Hello everyone. I got a problem with an 1.4.6 Fabric network with a network (27 peers and 5 orderers) where there is one peer (anchor peer) in an Organization that stopped commiting transactions. I

Hello All, The peer has joined the channel and chaincode is packed on. I have a problem with instantiating chaincode in Hyperledger fabric Network version 2: # peer lifecycle chaincode install

Hello - I do have a pegjs grammar for policies that could be useful. https://gist.github.com/mbwhite/b6f78b60bb9a2d407e7e623ca1e553cf Regards, Matthew. Matthew B White IBM Blockchain Solutions

Hi Everyone, I'm using Node.js Fabric SDK v1.4 for managing chaincode operations such as installing, instantiating, and upgrading. When to instantiate or upgrade a chaincode, I have to provide an

Try minifabric, only takes 5 minutes to know if it works for you or not.

I thought so too at first as I'm aware Fedora has a more restrictive security guideline. I installed firewalld and did according to the provided manual. It's different now, but still nothing

Hi Nathan, This is definitely possible. Chainstack customers are running production-grade Hyperledger Fabric 2.x networks in exactly three clouds you mentioned. Regards, Eugene Aseev

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 28 August 2020, 6:00am to 7:00am, (GMT+01:00)

Hi Nathan, As Jacov suggests you have to upgrade your network (ordering service, peers, etc) to 1.4.x (and then optionally to 2.x) in order to get the RAFT based HLF Ordering Service that can be