HyperLedger Fabric(单机Solo版)

本次环境还是基于Vagrant，创建1peer节点1组织1个排序节点的fabric网络，其实这个和first-network差不多，只是使用手动的方式完成fabric网络的部署。

实验环境搭建

创建虚拟机

1. 创建vagrant配置文件，这里指定操作系统为centos7

   vagrant init centos/7
   

2. 编写启动脚本 bootstrap.sh

   #!/usr/bin/bash
   sudo su
   echo "nameserver 8.8.8.8" >> /etc/resolv.conf
   sleep 3s
   yum install -y epel-release
   yum install -y vim
   yum install -y golang
   
   yum remove docker docker-common docker-selinux docker-engine
   yum install -y yum-utils device-mapper-persistent-data lvm2
   yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
   yum makecache fast
   yum -y install docker-ce
   yum -y install docker-compose
   service docker start
   
   mkdir -p /etc/docker
   echo {\"registry-mirrors\": [\"https://8w1wqmsz.mirror.aliyuncs.com\"]} > /etc/docker/daemon.json
   service docker restart
   
   echo "export GOPROXY=https://goproxy.io,direct" >> /etc/profile
   

3. 修改vagrantfile配置文件

   # -*- mode: ruby -*-
   # vi: set ft=ruby :
   
   # All Vagrant configuration is done below. The "2" in Vagrant.configure
   # configures the configuration version (we support older styles for
   # backwards compatibility). Please don't change it unless you know what
   # you're doing.
   Vagrant.configure("2") do |config|
     # The most common configuration options are documented and commented below.
     # For a complete reference, please see the online documentation at
     # https://docs.vagrantup.com.
   
     # Every Vagrant development environment requires a box. You can search for
     # boxes at https://vagrantcloud.com/search.
     config.vm.box = "centos/7"
   
     # Disable automatic box update checking. If you disable this, then
     # boxes will only be checked for updates when the user runs
     # `vagrant box outdated`. This is not recommended.
     # config.vm.box_check_update = false
   
     # Create a forwarded port mapping which allows access to a specific port
     # within the machine from a port on the host machine. In the example below,
     # accessing "localhost:8080" will access port 80 on the guest machine.
     # NOTE: This will enable public access to the opened port
     # config.vm.network "forwarded_port", guest: 80, host: 8080
   
     # Create a forwarded port mapping which allows access to a specific port
     # within the machine from a port on the host machine and only allow access
     # via 127.0.0.1 to disable public access
     # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
   
     # Create a private network, which allows host-only access to the machine
     # using a specific IP.
     # config.vm.network "private_network", ip: "192.168.33.10"
   
     # Create a public network, which generally matched to bridged network.
     # Bridged networks make the machine appear as another physical device on
     # your network.
     # config.vm.network "public_network"
   
     # Share an additional folder to the guest VM. The first argument is
     # the path on the host to the actual folder. The second argument is
     # the path on the guest to mount the folder. And the optional third
     # argument is a set of non-required options.
     # config.vm.synced_folder "../data", "/vagrant_data"
   
     # Provider-specific configuration so you can fine-tune various
     # backing providers for Vagrant. These expose provider-specific options.
     # Example for VirtualBox:
     #
     # config.vm.provider "virtualbox" do |vb|
     #   # Display the VirtualBox GUI when booting the machine
     #   vb.gui = true
     #
     #   # Customize the amount of memory on the VM:
     #   vb.memory = "1024"
     # end
     #
     # View the documentation for the provider you are using for more
     # information on available options.
   
     # Enable provisioning with a shell script. Additional provisioners such as
     # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
     # documentation for more information about their specific syntax and use.
      config.vm.provision "shell", path: "bootstrap.sh"
    
   end
   

Fabric配置文件

1. configtx.yaml 该文件用于生成创世区块和channel配置文件

   # Copyright IBM Corp. All Rights Reserved.
   #
   # SPDX-License-Identifier: Apache-2.0
   #
   
   ---
   ################################################################################
   #
   #   Section: Organizations
   #
   #   - This section defines the different organizational identities which will
   #   be referenced later in the configuration.
   #
   ################################################################################
   Organizations:
   
       # SampleOrg defines an MSP using the sampleconfig.  It should never be used
       # in production but may be used as a template for other definitions
       - &OrdererOrg
           # DefaultOrg defines the organization which is used in the sampleconfig
           # of the fabric.git development environment
           Name: OrdererOrg
   
           # ID to load the MSP definition as
           ID: OrdererMSP
   
           # MSPDir is the filesystem path which contains the MSP configuration
           MSPDir: crypto-config/ordererOrganizations/example.com/msp
   
           # Policies defines the set of policies at this level of the config tree
           # For organization policies, their canonical path is usually
           #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
           Policies:
               Readers:
                   Type: Signature
                   Rule: "OR('OrdererMSP.member')"
               Writers:
                   Type: Signature
                   Rule: "OR('OrdererMSP.member')"
               Admins:
                   Type: Signature
                   Rule: "OR('OrdererMSP.admin')"
   
       - &Org1
           # DefaultOrg defines the organization which is used in the sampleconfig
           # of the fabric.git development environment
           Name: Org1MSP
   
           # ID to load the MSP definition as
           ID: Org1MSP
   
           MSPDir: crypto-config/peerOrganizations/org1.example.com/msp
   
           # Policies defines the set of policies at this level of the config tree
           # For organization policies, their canonical path is usually
           #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
           Policies:
               Readers:
                   Type: Signature
                   Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"
               Writers:
                   Type: Signature
                   Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"
               Admins:
                   Type: Signature
                   Rule: "OR('Org1MSP.admin')"
   
           AnchorPeers:
               # AnchorPeers defines the location of peers which can be used
               # for cross org gossip communication.  Note, this value is only
               # encoded in the genesis block in the Application section context
               - Host: peer0.org1.example.com
                 Port: 7051
   
   ################################################################################
   #
   #   SECTION: Capabilities
   #
   #   - This section defines the capabilities of fabric network. This is a new
   #   concept as of v1.1.0 and should not be utilized in mixed networks with
   #   v1.0.x peers and orderers.  Capabilities define features which must be
   #   present in a fabric binary for that binary to safely participate in the
   #   fabric network.  For instance, if a new MSP type is added, newer binaries
   #   might recognize and validate the signatures from this type, while older
   #   binaries without this support would be unable to validate those
   #   transactions.  This could lead to different versions of the fabric binaries
   #   having different world states.  Instead, defining a capability for a channel
   #   informs those binaries without this capability that they must cease
   #   processing transactions until they have been upgraded.  For v1.0.x if any
   #   capabilities are defined (including a map with all capabilities turned off)
   #   then the v1.0.x peer will deliberately crash.
   #
   ################################################################################
   Capabilities:
       # Channel capabilities apply to both the orderers and the peers and must be
       # supported by both.  Set the value of the capability to true to require it.
       Global: &ChannelCapabilities
           # V1.1 for Global is a catchall flag for behavior which has been
           # determined to be desired for all orderers and peers running v1.0.x,
           # but the modification of which would cause incompatibilities.  Users
           # should leave this flag set to true.
           V1_1: true
   
       # Orderer capabilities apply only to the orderers, and may be safely
       # manipulated without concern for upgrading peers.  Set the value of the
       # capability to true to require it.
       Orderer: &OrdererCapabilities
           # V1.1 for Order is a catchall flag for behavior which has been
           # determined to be desired for all orderers running v1.0.x, but the
           # modification of which  would cause incompatibilities.  Users should
           # leave this flag set to true.
           V1_1: true
   
       # Application capabilities apply only to the peer network, and may be safely
       # manipulated without concern for upgrading orderers.  Set the value of the
       # capability to true to require it.
       Application: &ApplicationCapabilities
           # V1.1 for Application is a catchall flag for behavior which has been
           # determined to be desired for all peers running v1.0.x, but the
           # modification of which would cause incompatibilities.  Users should
           # leave this flag set to true.
           V1_2: true
   
   ################################################################################
   #
   #   SECTION: Application
   #
   #   - This section defines the values to encode into a config transaction or
   #   genesis block for application related parameters
   #
   ################################################################################
   Application: &ApplicationDefaults
   
       # Organizations is the list of orgs which are defined as participants on
       # the application side of the network
       Organizations:
   
       # Policies defines the set of policies at this level of the config tree
       # For Application policies, their canonical path is
       #   /Channel/Application/<PolicyName>
       Policies:
           Readers:
               Type: ImplicitMeta
               Rule: "ANY Readers"
           Writers:
               Type: ImplicitMeta
               Rule: "ANY Writers"
           Admins:
               Type: ImplicitMeta
               Rule: "MAJORITY Admins"
   
       # Capabilities describes the application level capabilities, see the
       # dedicated Capabilities section elsewhere in this file for a full
       # description
       Capabilities:
           <<: *ApplicationCapabilities
   
   ################################################################################
   #
   #   SECTION: Orderer
   #
   #   - This section defines the values to encode into a config transaction or
   #   genesis block for orderer related parameters
   #
   ################################################################################
   Orderer: &OrdererDefaults
   
       # Orderer Type: The orderer implementation to start
       # Available types are "solo" and "kafka"
       OrdererType: solo
   
       Addresses:
           - orderer0.example.com:7050
   
       # Batch Timeout: The amount of time to wait before creating a batch
       BatchTimeout: 2s
   
       # Batch Size: Controls the number of messages batched into a block
       BatchSize:
   
           # Max Message Count: The maximum number of messages to permit in a batch
           MaxMessageCount: 10
   
           # Absolute Max Bytes: The absolute maximum number of bytes allowed for
           # the serialized messages in a batch.
           AbsoluteMaxBytes: 98 MB
   
           # Preferred Max Bytes: The preferred maximum number of bytes allowed for
           # the serialized messages in a batch. A message larger than the preferred
           # max bytes will result in a batch larger than preferred max bytes.
           PreferredMaxBytes: 512 KB
       # Organizations is the list of orgs which are defined as participants on
       # the orderer side of the network
       Organizations:
   
       # Policies defines the set of policies at this level of the config tree
       # For Orderer policies, their canonical path is
       #   /Channel/Orderer/<PolicyName>
       Policies:
           Readers:
               Type: ImplicitMeta
               Rule: "ANY Readers"
           Writers:
               Type: ImplicitMeta
               Rule: "ANY Writers"
           Admins:
               Type: ImplicitMeta
               Rule: "MAJORITY Admins"
           # BlockValidation specifies what signatures must be included in the block
           # from the orderer for the peer to validate it.
           BlockValidation:
               Type: ImplicitMeta
               Rule: "ANY Writers"
   
       # Capabilities describes the orderer level capabilities, see the
       # dedicated Capabilities section elsewhere in this file for a full
       # description
       Capabilities:
           <<: *OrdererCapabilities
   
   ################################################################################
   #
   #   CHANNEL
   #
   #   This section defines the values to encode into a config transaction or
   #   genesis block for channel related parameters.
   #
   ################################################################################
   Channel: &ChannelDefaults
       # Policies defines the set of policies at this level of the config tree
       # For Channel policies, their canonical path is
       #   /Channel/<PolicyName>
       Policies:
           # Who may invoke the 'Deliver' API
           Readers:
               Type: ImplicitMeta
               Rule: "ANY Readers"
           # Who may invoke the 'Broadcast' API
           Writers:
               Type: ImplicitMeta
               Rule: "ANY Writers"
           # By default, who may modify elements at this config level
           Admins:
               Type: ImplicitMeta
               Rule: "MAJORITY Admins"
   
   
       # Capabilities describes the channel level capabilities, see the
       # dedicated Capabilities section elsewhere in this file for a full
       # description
       Capabilities:
           <<: *ChannelCapabilities
   
   ################################################################################
   #
   #   Profile
   #
   #   - Different configuration profiles may be encoded here to be specified
   #   as parameters to the configtxgen tool
   #
   ################################################################################
   Profiles:
   
       TwoOrgsOrdererGenesis:
           <<: *ChannelDefaults
           Orderer:
               <<: *OrdererDefaults
               Organizations:
                   - *OrdererOrg
           Consortiums:
               SampleConsortium:
                   Organizations:
                       - *Org1
   
       TwoOrgsChannel:
           Consortium: SampleConsortium
           Application:
               <<: *ApplicationDefaults
               Organizations:
                   - *Org1
   

2. crypto-config.yaml 用于生成各个节点的ca证书文件

   # Copyright IBM Corp. All Rights Reserved.
   #
   # SPDX-License-Identifier: Apache-2.0
   #
   
   # ---------------------------------------------------------------------------
   # "OrdererOrgs" - Definition of organizations managing orderer nodes
   # ---------------------------------------------------------------------------
   OrdererOrgs:
     # ---------------------------------------------------------------------------
     # Orderer
     # ---------------------------------------------------------------------------
     - Name: Orderer
       Domain: example.com
       CA:
           Country: US
           Province: California
           Locality: San Francisco
       # ---------------------------------------------------------------------------
       # "Specs" - See PeerOrgs below for complete description
       # ---------------------------------------------------------------------------
       Specs:
         - Hostname: orderer0
   # ---------------------------------------------------------------------------
   # "PeerOrgs" - Definition of organizations managing peer nodes
   # ---------------------------------------------------------------------------
   PeerOrgs:
     # ---------------------------------------------------------------------------
     # Org1
     # ---------------------------------------------------------------------------
     - Name: Org1
       Domain: org1.example.com
       EnableNodeOUs: true
       CA:
           Country: US
           Province: California
           Locality: San Francisco
       # ---------------------------------------------------------------------------
       # "Specs"
       # ---------------------------------------------------------------------------
       # Uncomment this section to enable the explicit definition of hosts in your
       # configuration.  Most users will want to use Template, below
       #
       # Specs is an array of Spec entries.  Each Spec entry consists of two fields:
       #   - Hostname:   (Required) The desired hostname, sans the domain.
       #   - CommonName: (Optional) Specifies the template or explicit override for
       #                 the CN.  By default, this is the template:
       #
       #                              "{{.Hostname}}.{{.Domain}}"
       #
       #                 which obtains its values from the Spec.Hostname and
       #                 Org.Domain, respectively.
       # ---------------------------------------------------------------------------
       # Specs:
       #   - Hostname: foo # implicitly "foo.org1.example.com"
       #     CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
       #   - Hostname: bar
       #   - Hostname: baz
       # ---------------------------------------------------------------------------
       # "Template"
       # ---------------------------------------------------------------------------
       # Allows for the definition of 1 or more hosts that are created sequentially
       # from a template. By default, this looks like "peer%d" from 0 to Count-1.
       # You may override the number of nodes (Count), the starting index (Start)
       # or the template used to construct the name (Hostname).
       #
       # Note: Template and Specs are not mutually exclusive.  You may define both
       # sections and the aggregate nodes will be created for you.  Take care with
       # name collisions
       # ---------------------------------------------------------------------------
       Template:
         Count: 1
         # Start: 5
         # Hostname: {{.Prefix}}{{.Index}} # default
       # ---------------------------------------------------------------------------
       # "Users"
       # ---------------------------------------------------------------------------
       # Count: The number of user accounts _in addition_ to Admin
       # ---------------------------------------------------------------------------
       Users:
         Count: 1
   

3. orderer0 配置文件

   # Copyright IBM Corp. All Rights Reserved.
   #
   # SPDX-License-Identifier: Apache-2.0
   #
   
   version: '2'
   
   services:
     orderer0.example.com:
       container_name: orderer0.example.com
       image: hyperledger/fabric-orderer
       environment:
         - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
         - ORDERER_GENERAL_LOGLEVEL=debug
         - ORDERER_HOST=orderer0.example.com
         - ORDERER_GENERAL_GENESISMETHOD=file
         - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/genesis.block
         - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
         - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
         # enabled TLS
         - ORDERER_GENERAL_TLS_ENABLED=true
         - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
         - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
         - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
         - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s 
         - ORDERER_KAFKA_RETRY_LONGTOTAL=100s
         - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s
         - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s
         - ORDERER_KAFKA_VERBOSE=true
       working_dir: /opt/gopath/src/github.com/hyperledger/fabric
       command: orderer
       volumes:
         - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/genesis.block
         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/var/hyperledger/orderer/msp
         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/var/hyperledger/orderer/tls
   

4. peer0-org1

   # All elements in this file should depend on the docker-compose-base.yaml
   # Provided fabric peer node
   
   version: '2'
   
   services:
     peer0.org1.example.com:
       container_name: peer0.org1.example.com
       hostname: peer0.org1.example.com
       image: hyperledger/fabric-peer
       environment:
          - CORE_PEER_ID=peer0.org1.example.com
          - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
          - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com:7052
          - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=vagrant_default #这里需要修改成你network的名字
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
          # the following setting starts chaincode containers on the same
          # bridge network as the peers
          # https://docs.docker.com/compose/networking/
          #- CORE_LOGGING_LEVEL=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_GOSSIP_USELEADERELECTION=true
          - CORE_PEER_GOSSIP_ORGLEADER=false
          - CORE_PEER_PROFILE_ENABLED=true
          - CORE_PEER_TLS_ENABLED=true
          - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
          - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
          - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt
       working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
       command: peer node start
       volumes:
          - /var/run/:/host/var/run/
          - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp
          - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls
       ports:
         - 7051:7051
         - 7052:7052
         - 7053:7053
     cli:
       container_name: cli
       image: hyperledger/fabric-tools
       tty: true
       environment:
         - GOPATH=/opt/gopath
         - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
         # - CORE_LOGGING_LEVEL=ERROR
         - CORE_LOGGING_LEVEL=DEBUG
         - CORE_PEER_ID=cli
         - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
         - CORE_PEER_LOCALMSPID=Org1MSP
         - CORE_PEER_TLS_ENABLED=true
         - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
         - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
         - 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
         - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
       working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
       volumes:
           - /var/run/:/host/var/run/
           - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/go
           - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
           - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
   

部署Fabric网络

二进制工具 cryptogen、configtxgen 安装

1. 获取fabric源码

   go get github.com/hyperledger/fabric
   

2. 切换到v1.4.0分支

   git checkout v1.4.0
   

3. 安装cryptogen 工具

   cd common/tools/cryptogen/
   go install
   

4. 安装configtxgen工具

   cd common/tools/configtxgen/
   go install
   

5. 配置环境变量

   vim /etc/profile
   export PATH=$PATH:/root/go/bin
   source /etc/profile
   

证书、创世区块、通道生成

切换到 /vagrant目录下，之前编写的fabric配置文件会自动同步到这个目录下

cd /vagrant

1. 生成证书，生成的证书在crypto-config目录下。

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

   image-20200127162844255

2. 生成创世区块

   # 创建文件夹
   mkdir channel-artifacts
   configtxgen -profile TwoOrgsOrdererGenesis --configPath=./  -outputBlock ./channel-artifacts/genesis.block
   

3. 生成channel.tx

   configtxgen -profile TwoOrgsChannel --configPath=./ -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel
   

启动各个节点

1. 启动orderer

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

2. 启动peer

   docker-compose -f docker-compose-peer0-org1.yaml up -d
   

创建通道

1. 进入cli

   docker exec -it cli bash
   

2. 创建通道

   peer channel create -o orderer0.example.com:7050 -c mychannel -t 50s -f ./channel-artifacts/mychannel.tx --outputBlock ./channel-artifacts/mychannel.block --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
   

   当看到如下结果即位创建成功

   image-20200127160532435

3. 加入通道

   peer channel join -b ./channel-artifacts/mychannel.block
   

chaincode

1. 安装chaincode

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

2. 实例化chaincode

   peer chaincode instantiate -o orderer0.example.com:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n mycc -v 1.0 -c '{"Args":["init","a","200","b","400"]}'
   

3. 查询a

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

   image-20200127161334667

4. 交易：a转给b20

   peer chaincode invoke  -C mychannel -n mycc -c '{"Args":["invoke","a","b","20"]}' --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
   

   查询a

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

   image-20200127161653164

源码献上