Hyperledger Fabric中First Network的示例分析

這篇文章將為大家詳細(xì)講解有關(guān)Hyperledger Fabric中First Network的示例分析，小編覺得挺實(shí)用的，因此分享給大家做個(gè)參考，希望大家閱讀完這篇文章后可以有所收獲。

First Network 詳細(xì)分析

生成 fabric 證書和配置等文件

./byfn.sh generate

日志分析并手動(dòng)構(gòu)建細(xì)節(jié)

• 1. 以獲取生成將用于crypto-config.yaml文件中定義的網(wǎng)絡(luò)配置的證書，對(duì)應(yīng)手工配置：

  ../bin/cryptogen generate --config=./crypto-config.yaml

  
  

  對(duì)應(yīng)輸出日志：

  org1.example.com
  org2.example.com

  
  

  證書和密鑰（即MSP材料）將輸出到 first-network 目錄中的 crypto-config 文件夾。

• 2. configtxgen 工具在哪里查找配置文件 configtx.yaml 并調(diào)用 configtxgen 工具來創(chuàng)建 orderer 創(chuàng)世區(qū)塊，對(duì)應(yīng)手工配置：

  export FABRIC_CFG_PATH=$PWD && ../bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

  
  

  對(duì)應(yīng)輸出類似日志：

  2018-08-23 10:36:13.825 CST [common/tools/configtxgen] main -> WARN 001 Omitting the channel ID for configtxgen is deprecated.  Explicitly passing the channel ID will be required in the future, defaulting to 'testchainid'.
  2018-08-23 10:36:13.825 CST [common/tools/configtxgen] main -> INFO 002 Loading configuration
  2018-08-23 10:36:13.831 CST [common/tools/configtxgen/encoder] NewChannelGroup -> WARN 003 Default policy emission is deprecated, please include policy specificiations for the channel group in configtx.yaml
  2018-08-23 10:36:13.832 CST [common/tools/configtxgen/encoder] NewOrdererGroup -> WARN 004 Default policy emission is deprecated, please include policy specificiations for the orderer group in configtx.yaml
  2018-08-23 10:36:13.832 CST [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 005 Default policy emission is deprecated, please include policy specificiations for the orderer org group OrdererOrg in configtx.yaml
  2018-08-23 10:36:13.832 CST [msp] getMspConfig -> INFO 006 Loading NodeOUs
  2018-08-23 10:36:13.832 CST [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 007 Default policy emission is deprecated, please include policy specificiations for the orderer org group Org1MSP in configtx.yaml
  2018-08-23 10:36:13.832 CST [msp] getMspConfig -> INFO 008 Loading NodeOUs
  2018-08-23 10:36:13.832 CST [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 009 Default policy emission is deprecated, please include policy specificiations for the orderer org group Org2MSP in configtx.yaml
  2018-08-23 10:36:13.832 CST [common/tools/configtxgen] doOutputBlock -> INFO 00a Generating genesis block
  2018-08-23 10:36:13.833 CST [common/tools/configtxgen] doOutputBlock -> INFO 00b Writing genesis block

  
  

  創(chuàng)世區(qū)塊 genesis.block 將輸出到 first-network 目錄中的 channel-artifacts 文件夾。

• 3. 創(chuàng)建通道配置文件，對(duì)應(yīng)手工配置：

  export CHANNEL_NAME=mychannel  && ../bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID $CHANNEL_NAME

  
  

  對(duì)應(yīng)輸出類似日志：

  2018-08-23 10:55:33.393 CST [common/tools/configtxgen] main -> INFO 001 Loading configuration
  2018-08-23 10:55:33.399 CST [common/tools/configtxgen] doOutputChannelCreateTx -> INFO 002 Generating new channel configtx
  2018-08-23 10:55:33.399 CST [common/tools/configtxgen/encoder] NewApplicationGroup -> WARN 003 Default policy emission is deprecated, please include policy specificiations for the application group in configtx.yaml
  2018-08-23 10:55:33.399 CST [msp] getMspConfig -> INFO 004 Loading NodeOUs
  2018-08-23 10:55:33.399 CST [common/tools/configtxgen/encoder] NewApplicationOrgGroup -> WARN 005 Default policy emission is deprecated, please include policy specificiations for the application org group Org1MSP in configtx.yaml
  2018-08-23 10:55:33.400 CST [msp] getMspConfig -> INFO 006 Loading NodeOUs
  2018-08-23 10:55:33.400 CST [common/tools/configtxgen/encoder] NewApplicationOrgGroup -> WARN 007 Default policy emission is deprecated, please include policy specificiations for the application org group Org2MSP in configtx.yaml
  2018-08-23 10:55:33.401 CST [common/tools/configtxgen] doOutputChannelCreateTx -> INFO 008 Writing new channel tx

  
  

  通道配置文件 channel.tx 將輸出到 first-network 目錄中的 channel-artifacts 文件夾。

   

• 4. 構(gòu)建的通道上為Org1組織錨節(jié)點(diǎn)配置文件，對(duì)應(yīng)手工配置：

  ../bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID $CHANNEL_NAME -asOrg Org1MSP

  
  

  對(duì)應(yīng)輸出類似日志：

  2018-08-23 11:07:49.817 CST [common/tools/configtxgen] main -> INFO 001 Loading configuration
  2018-08-23 11:07:49.823 CST [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
  2018-08-23 11:07:49.823 CST [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer update

  
  

  通道上為Org1定義錨對(duì)等節(jié)點(diǎn)配置文件 Org1MSPanchors.tx 將輸出到 first-network 目錄中的 channel-artifacts 文件夾。

   

• 5. 構(gòu)建的通道上為Org2組織錨節(jié)點(diǎn)配置文件，對(duì)應(yīng)手工配置：

  ../bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID $CHANNEL_NAME -asOrg Org2MSP

  
  

  對(duì)應(yīng)輸出類似日志：

  2018-08-23 11:10:02.486 CST [common/tools/configtxgen] main -> INFO 001 Loading configuration
  2018-08-23 11:10:02.493 CST [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
  2018-08-23 11:10:02.493 CST [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer upda

  
  

  通道上為Org2定義錨對(duì)等節(jié)點(diǎn)配置文件 Org2MSPanchors.tx 將輸出到 first-network 目錄中的 channel-artifacts 文件夾。

網(wǎng)絡(luò)啟動(dòng)

./byfn.sh up

 日志分析可以分為兩部分并手動(dòng)構(gòu)建細(xì)節(jié)

• 第一日志部分

  Creating network "net_byfn" with the default driver
  Creating volume "net_orderer.example.com" with default driver
  Creating volume "net_peer0.org1.example.com" with default driver
  Creating volume "net_peer1.org1.example.com" with default driver
  Creating volume "net_peer0.org2.example.com" with default driver
  Creating volume "net_peer1.org2.example.com" with default driver
  Creating peer0.org2.example.com ... done
  Creating orderer.example.com    ... done
  Creating peer1.org1.example.com ... done
  Creating peer1.org2.example.com ... done
  Creating peer0.org1.example.com ... done
  Creating cli                    ... done

  
  

  這部分其實(shí)是利用 docker-compose 啟動(dòng)容器編排，具體命令為：

  docker-compose -f docker-compose-cli.yaml up -d

  
  

• 第二日志部分

  ____    _____      _      ____    _____ 
  / ___|  |_   _|    / \    |  _ \  |_   _|
  \___ \    | |     / _ \   | |_) |   | |  
   ___) |   | |    / ___ \  |  _ <    | |  
  |____/    |_|   /_/   \_\ |_| \_\   |_|  
  
  Build your first network (BYFN) end-to-end test
  
  Channel name : mychannel
  Creating channel...
  + peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
  + res=0
  + set +x
  2018-08-23 04:18:50.971 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:18:50.985 UTC [cli/common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
  2018-08-23 04:18:50.987 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
  2018-08-23 04:18:51.193 UTC [cli/common] readBlock -> INFO 004 Received block: 0
  ===================== Channel 'mychannel' created ===================== 
  
  Having all peers join the channel...
  + peer channel join -b mychannel.block
  + res=0
  + set +x
  2018-08-23 04:18:51.282 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:18:51.386 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
  ===================== peer0.org1 joined channel 'mychannel' ===================== 
  
  + peer channel join -b mychannel.block
  + res=0
  + set +x
  2018-08-23 04:18:54.468 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:18:54.577 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
  ===================== peer1.org1 joined channel 'mychannel' ===================== 
  
  + peer channel join -b mychannel.block
  + res=0
  + set +x
  2018-08-23 04:18:57.680 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:18:57.790 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
  ===================== peer0.org2 joined channel 'mychannel' ===================== 
  
  + peer channel join -b mychannel.block
  + res=0
  + set +x
  2018-08-23 04:19:00.881 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:19:00.991 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
  ===================== peer1.org2 joined channel 'mychannel' ===================== 
  
  Updating anchor peers for org1...
  + peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
  + res=0
  + set +x
  2018-08-23 04:19:04.082 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:19:04.089 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
  ===================== Anchor peers updated for org 'Org1MSP' on channel 'mychannel' ===================== 
  
  Updating anchor peers for org2...
  + peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
  + res=0
  + set +x
  2018-08-23 04:19:07.175 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 04:19:07.183 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
  ===================== Anchor peers updated for org 'Org2MSP' on channel 'mychannel' ===================== 
  
  Installing chaincode on peer0.org1...
  + peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
  + res=0
  + set +x
  2018-08-23 04:19:10.273 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 04:19:10.273 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
  2018-08-23 04:19:10.401 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" > 
  ===================== Chaincode is installed on peer0.org1 ===================== 
  
  Install chaincode on peer0.org2...
  + peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
  + res=0
  + set +x
  2018-08-23 04:19:10.461 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 04:19:10.461 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
  2018-08-23 04:19:10.573 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" > 
  ===================== Chaincode is installed on peer0.org2 ===================== 
  
  Instantiating chaincode on peer0.org2...
  + peer chaincode instantiate -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n mycc -l golang -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P 'AND ('\''Org1MSP.peer'\'','\''Org2MSP.peer'\'')'
  + res=0
  + set +x
  2018-08-23 04:19:10.634 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 04:19:10.634 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
  ===================== Chaincode is instantiated on peer0.org2 on channel 'mychannel' ===================== 
  
  Querying chaincode on peer0.org1...
  ===================== Querying on peer0.org1 on channel 'mychannel'... ===================== 
  Attempting to Query peer0.org1 ...3 secs
  + peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
  + res=0
  + set +x
  
  100
  ===================== Query successful on peer0.org1 on channel 'mychannel' ===================== 
  Sending invoke transaction on peer0.org1 peer0.org2...
  + peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c '{"Args":["invoke","a","b","10"]}'
  + res=0
  + set +x
  2018-08-23 04:19:31.656 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200 
  ===================== Invoke transaction successful on peer0.org1 peer0.org2 on channel 'mychannel' ===================== 
  
  Installing chaincode on peer1.org2...
  + peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
  + res=0
  + set +x
  2018-08-23 04:19:31.708 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 04:19:31.708 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
  2018-08-23 04:19:31.815 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" > 
  ===================== Chaincode is installed on peer1.org2 ===================== 
  
  Querying chaincode on peer1.org2...
  ===================== Querying on peer1.org2 on channel 'mychannel'... ===================== 
  + peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
  Attempting to Query peer1.org2 ...3 secs
  + res=0
  + set +x
  
  90
  ===================== Query successful on peer1.org2 on channel 'mychannel' ===================== 
  
  ========= All GOOD, BYFN execution completed =========== 
  
  
   _____   _   _   ____   
  | ____| | \ | | |  _ \  
  |  _|   |  \| | | | | | 
  | |___  | |\  | | |_| | 
  |_____| |_| \_| |____/

  
  

  這部分其實(shí)是利用 docker exec 命令 進(jìn)入 cli 容器中執(zhí)行 scripts/script.sh 腳本，其參數(shù)為 mychannel 3 golang 10 false，具體命令為：

  docker exec cli scripts/script.sh mychannel 3 golang 10 false

  
  

         第二部分日志具體分析

• 
  

• 首先進(jìn)入 cli 容器：

  docker exec -it cli bash

  
  

• 接下來在容器里操作，配置環(huán)境變量：

  export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
  export CORE_PEER_ADDRESS=peer0.org1.example.com:7051
  export CORE_PEER_LOCALMSPID="Org1MSP"
  export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt

  
  

• 創(chuàng)建 mychannel 通道(相當(dāng)于通過創(chuàng)世區(qū)塊創(chuàng)建區(qū)塊鏈，每個(gè)通道相當(dāng)于每條獨(dú)立的區(qū)塊鏈)：

  export CHANNEL_NAME=mychannel
  peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

  
  

  輸出日志：

  2018-08-23 06:56:14.257 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 06:56:14.273 UTC [cli/common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
  2018-08-23 06:56:14.274 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
  2018-08-23 06:56:14.480 UTC [cli/common] readBlock -> INFO 004 Received block: 0

  
  

• 節(jié)點(diǎn)加入 mychannel 通道(相當(dāng)于節(jié)點(diǎn)加入?yún)^(qū)塊鏈網(wǎng)絡(luò))： 加入通道需要用到環(huán)境變量的值，默認(rèn)為 peer0.org1 節(jié)點(diǎn)加入通道。

  peer channel join -b mychannel.block

  
  

  輸出日志：

  2018-08-23 07:10:09.620 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  2018-08-23 07:10:09.729 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel

  
  

  要其他節(jié)點(diǎn)也加入 mychannel 通道，需要修改環(huán)境變量的值，也很簡(jiǎn)單，舉個(gè)例子,如果 peer1.org2 節(jié)點(diǎn)加入通道，只要把所有環(huán)境變量值出現(xiàn) org1 替換成 org2 ，并把 CORE_PEER_ADDRESS值中的 peer0替換成 peer1 ，如下：

  CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
  CORE_PEER_ADDRESS=peer1.org2.example.com:7051
  CORE_PEER_LOCALMSPID="Org2MSP"
  CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt

  
  

  修改后繼續(xù)執(zhí)行：peer channel join -b mychannel.block，同理完成 peer0.org2，peer1.org1，peer1.org2 加入 mychannel 通道。

• 更新通道的錨節(jié)點(diǎn)，實(shí)質(zhì)上是在通道的創(chuàng)世塊之上添加了額外的配置信息(所謂錨節(jié)點(diǎn)就是某聯(lián)盟在通道中公開鏈接的一個(gè)或多個(gè)節(jié)點(diǎn)) 更新通道中 Org1 組織的錨節(jié)點(diǎn)為 peer0.org1.example.com： 首先確保環(huán)境變量是 peer0.org1 的信息：

  CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
  CORE_PEER_ADDRESS=peer0.org1.example.com:7051
  CORE_PEER_LOCALMSPID="Org1MSP"
  CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt

  
  

  然后更新

  peer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

  
  

  更新通道中 Org2 組織的錨節(jié)點(diǎn)為 peer0.org2.example.com： 首先確保環(huán)境變量是 peer0.org2 的信息：

  CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
  CORE_PEER_ADDRESS=peer0.org2.example.com:7051
  CORE_PEER_LOCALMSPID="Org2MSP"
  CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt

  
  

  然后更新

  peer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

  
  

• 安裝和實(shí)例化Chaincode 安裝 golang版 Chaincode ，安裝到的節(jié)點(diǎn)為環(huán)境變量的配置節(jié)點(diǎn):

  peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/

  
  

  日志輸出：

  2018-08-23 11:25:20.439 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 11:25:20.439 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
  2018-08-23 11:25:20.831 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" >

  
  

  接下來，在通道上實(shí)例化鏈碼。這將初始化通道上的鏈代碼，設(shè)置鏈代碼的認(rèn)可策略，并為目標(biāo)節(jié)點(diǎn)啟動(dòng)鏈代碼容器：

  peer chaincode instantiate -o orderer.example.com:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C $CHANNEL_NAME -n mycc -v 1.0 -c '{"Args":["init","a", "100", "b","200"]}' -P "AND ('Org1MSP.peer','Org2MSP.peer')"

  
  

  日志輸出：

  2018-08-23 11:31:33.050 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
  2018-08-23 11:31:33.050 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc

  
  

• 查詢以確保鏈代碼已正確實(shí)例化并填充狀態(tài)數(shù)據(jù)庫：

  peer chaincode query -C $CHANNEL_NAME -n mycc -c '{"Args":["query","a"]}'

  
  

  日志輸出：

  100

  
  

• 調(diào)用，a取10給b

  peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C $CHANNEL_NAME -n mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c '{"Args":["invoke","a","b","10"]}'

  
  

  輸出

  INFO 001 Chaincode invoke successful. result: status:200

  
  

  查詢結(jié)果得到： a：90，b：210，成功結(jié)束 !!!

關(guān)于“Hyperledger Fabric中First Network的示例分析”這篇文章就分享到這里了，希望以上內(nèi)容可以對(duì)大家有一定的幫助，使各位可以學(xué)到更多知識(shí)，如果覺得文章不錯(cuò)，請(qǐng)把它分享出去讓更多的人看到。