Node JS Chaincode support for Hyperledger Fabric v1.1
Why Stack Overflow recommends it
Stack Overflow users link it when setting up or debugging Node.js chaincode in Fabric dev mode, since it shows the exact commands for registering chaincode with a peer.
Recommended by 3 people across 3 different months, 2018 to 2018.
What it is
A short screencast from the Hyperledger Fabric project showing how to write and run Node.js chaincode (smart contracts) on Fabric v1.1. It walks through running chaincode in dev mode against a local peer, and credits a Jira issue for background.
What people said
Recommends sara · 2018-04 · Stack Overflow · on “How do I run hyperledger-fabric node js chaincode in dev mode?”
I figured it out by watching this video: node chaincode [this video] You are supposed to build it like this: CORE_CHAINCODE_ID_NAME="mycc:v0" node main-chaincode.js --peer.address peer:7052
Recommends ilegolas · 2018-09 · Stack Overflow · on “Unable to use peer command in docker dev mode in Hyperledger Fabric”
I am trying to test a custom Node JS Chaincode for hyperledger. From the documentation and videos, I understood that I need to use Docker dev mode so that I can access my dev environment out of the box. I tried to start a basic network using the fabric-samples/basic-network/ folder as suggested by this video: [this video] . After I start the network, I am unable to use the peer command through the command line. For example, the below command is not working CORE_PEER_LOCALMSPID=Org1MSP CORE_PEER_MSPCONFIGPATH=/correctPath/users/Admin@org1.example.com/msp peer0.org1.example.com peer channel list I suspect that I am unable to avoid my peer from using TLS. How do I overcome this? Or is there some oth
Recommends SandeepR · 2018-12 · Stack Overflow · on “debug node js chaincode ...?”
This link [this video] gives tutorial on debugging javascript chaincode in hyperledger fabric. I was able to debug my chaincode following it but recently I updated to fabric 1.2 and the peer channel list command CORE_PEER_LOCALMSPID=Org1MSP CORE_PEER_MSPCONFIGPATH=/home/bct/fabric-samples/basic-network/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp peer channel list fails with: Fatal error when initializing core config : error when reading core config file: Unsupported Config Type "" I tried to go back to v1.1 but the problem persists. Can someone give me the complete list of configuration steps that may have been missed in tutorial video (which I was following)
Cites Simon Mullaney · 2018-01 · Stack Overflow · on “Fatal error when initializing core config - trying to deploy chaincode - fabric release version v1.1.0-preview”
I'm trying to deploy Node JS Chaincode on the new fabric release version v1.1.0-preview by following this video - Node JS Chaincode support for Hyperledger Fabric v1.1 ( [this video] ) Commands: CORE_CHAINCODE_ID_NAME="logic:v0" npm start -- --peer.address grpc://192.168.0.4:7052 > logic@1.0.0 start /Users/simonmullaney/block-aviation_angular/lib > node logic.js "--peer.address" "grpc://192.168.x.x:7052" [2018-01-26T15:47:44.701] [INFO] lib/chaincode.js - Registering with peer grpc://192.168.x.x:7052 as chaincode "logic:v0" [2018-01-26T15:47:44.723] [INFO] lib/handler.js - Successfully registered with peer node. State transferred to "established" [2018-01-26T15:47:44.723] [INFO] lib/handler.js -