我对hyperledger fabric1.1.0的执着（四）：部署单机多节点网络

喜欢ヅ旅行 2022-04-17 06:39 301阅读 0赞

1、生成证书文件

（1.1）环境清理

接上一篇，已跑通e2e\_cli案例，此处需要执行以下命令进行环境清理：

cd /opt/gopath/src/github.com/hyperledger/fabric/examples/e2e\_cli

bash network\_setup.sh down

然后依次执行以下命令查看环境：

\# docker ps -a

\# docker images

\# docker-compose version

\# go version

最终结果如图：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70][]

（1.2）在Fabric源码下创建aberic目录，来作为即将运行的单机多节点项目目录。最终目录如图：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 1][]

（1.3）将前面下载的hyperledger-fabric-linux-amd64-1.1.0.tar.gz（内含二进制文件）包上传至该目录并解压，得到bin和config。删除config目录，只保留bin。然后从fabric1.0版本中复制examples/e2e\_cli目录下的configtx.yaml和crypto-config.yaml文件到aberic目录（此处注意我的bin为1.1.0版本的，而configtx.yaml和crypto-config.yaml为1.0版本的，因为1.0的启动类型是solo，而1.1之后启动类型为kafka，这里选用solo进行单机部署），最后tree一下目录结构如图：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 2][]

（1.4）生成证书文件

进入aberic目录：

cd /opt/gopath/src/github.com/hyperledger/fabric/aberic

执行以下命令来生成项目所需文件，如图：

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

（若提示权限不足，如图：

![20181114115640575.png][]

对二进制文件进行授权操作：

chmod +x ./bin/cryptogen

然后查看：

ll ./bin/cryptogen

![20181114120044460.png][]

再执行文件生成命令：./bin/cryptogen generate --config=./crypto-config.yaml）

![20181114111453899.png][]

在ftp中会看到生成一个新目录crypto-config，其中包含ordererOrganizations和peerOrganizations两个目录。如图：

![20181114111947849.png][]

![2018111411200222.png][]

（1.5）为configtxgen工具指定configtx.yaml文件的路径，设置环境变量，执行以下命令：

设置环境变量：

export FABRIC\_CFG\_PATH=$PWD

然后查看该目录是否正确：

echo $PWD

最终结果如图：

![20181114131114683.png][]

（1.6）在aberic文件夹下创建文件夹channel-artifacts。

（1.6）根据configtx.yaml生成chua创世块以及频道认证文件：

\# ./bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

![20181114131234372.png][]

通过ftp可以看到已创建成功：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 3][]

生成channelID为mychannel（可自定义）的tx文件：

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

![20181114131749452.png][]

再看channel-artifacts目录多了mychannel.tx文件：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 4][]

2、部署orderer节点，编写docker-order.yaml文件，如下（注意空格）：

version: '2'

services:  
  orderer.example.com:  
    container\_name: orderer.example.com  
    image: hyperledger/fabric-orderer  
    environment:  
      - CORE\_VM\_DOCKER\_HOSTCONFIG\_NETWORKMODE=aberic\_default  
      \# - ORDERER\_GENERAL\_LOGLEVEL=error  
      - OEDERER\_GENERAL\_LOGLEVEL=debug  
      - OEDERER\_GENERAL\_LISTENADDRESS=0.0.0.0  
      - OEDERER\_GENERAL\_LISTENPORT=7050  
      \#- OEDERER\_GENERAL\_GENESISPROFILE=AntiMothOrdererGenesis  
      - OEDERER\_GENERAL\_GENESISMETHOD=file  
      - OEDERER\_GENERAL\_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block  
      - OEDERER\_GENERAL\_LOCALMSPID=OrdererMSP  
      - OEDERER\_GENERAL\_LOCALMSPDIR=/var/hyperledger/orderer/msp  
      \# enabled TLS  
      - ORDERER\_GENERAL\_TLS\_ENABLED=false  
      - 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\]  
    working\_dir: /opt/gopath/src/github.com/hyperledger/fabric  
    command: orderer  
    volumes:  
    - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block  
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp  
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls  
    networks:  
      default:  
        aliases:  
          - aberic  
    ports:  
      - 7050:7050

3、部署peer0.org1jied节点，编写docker-peer.yaml文件如下（注意空格）：

version: '2'

services:

couchdb:  
    container\_name: couchdb  
    image: hyperledger/fabric-couchdb  
    ports:  
      - "5984:5984"  
        
  ca:  
    container\_name: ca  
    image: hyperledger/fabric-ca  
    environment:  
      - FABRIC\_CA\_HOME=/etc/hyperledger/fabric-ca-server  
      - FABRIC\_CA\_SERVER\_CA\_NAME=ca  
      - FABRIC\_CA\_SERVER\_TLS\_ENABLED=false  
      - FABRIC\_CA\_SERVER\_TLS\_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem  
      - FABEIC\_CA\_SERVER\_TLS\_KEYFILE=/etc/hyperledger/fabric-ca-server-config/8ae7bc9222d051e43cd7f0354c3ba027be91efc1b6c5e9b3619a0988ae6929c1\_sk  
    ports:  
      - "7054:7054"  
    command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/8ae7bc9222d051e43cd7f0354c3ba027be91efc1b6c5e9b3619a0988ae6929c1\_sk -b admin:adminpw -d'  
    volumes:  
      - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config/  
        
  peer0.org1.example.com:  
    container\_name: peer0.org1.example.com  
    image: hyperledger/fabric-peer  
    environment:  
      - CORE\_LEDGER\_STATE\_STATEDATABASE=CouchDB  
      - CORE\_LEDGER\_STATE\_COUCHDBCONFIG\_COUCHDBADDRESS=couchdb:5984  
            
      - CORE\_PEER\_ID=peer0.org1.example.com  
      - CORE\_PEER\_NETWORKID=aberic  
      - 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\_PEER\_LOCALMSPID=Org1MSP  
            
      - CORE\_VM\_ENDPOINT=unix:///host/var/run/docker.sock  
      - CORE\_VM\_DOCKER\_HOSTCONFIG\_NETWORKMODE=aberic  
      - CORE\_LOGGING\_LEVEL=DEBUG  
      - CORE\_VM\_DOCKER\_HOSTCONFIG\_NETWORKMODE=aberic\_default  
      - CORE\_PEER\_GOSSIP\_SKIPHANDSHAKE=true  
      - CORE\_PEER\_GOSSIP\_USELEADERELECTTON=true  
      - CORE\_PEER\_GOSSIP\_ORGLEADER=false  
      - CORE\_PEER\_PROFILE\_ENABLED=false  
      - CORE\_PEER\_TLS\_ENABLED=false  
      - 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  
    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  
    working\_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer  
    command: peer node start  
    ports:  
      - 7051:7051  
      - 7052:7052  
      - 7053:7053  
    depends\_on:  
      - couchdb  
    networks:  
      default:  
        aliases:  
          - aberic  
                
  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=DEBUG  
      - CORE\_PEER\_ID=cli  
      - CORE\_PEER\_ADDRESS=peer0.org1.example.com:7051  
      - CORE\_PEER\_LOCALMSPID=Org1MSP  
      - CORE\_PEER\_TLS\_ENABLED=false  
      - 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/aberic/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  
    depends\_on:  
      - peer0.org1.example.com

注意：CA有两部分需要修改，一个是FABEIC\_CA\_SERVER\_TLS\_KEYFILE，另一处是command中最后一部分。这两处的\_sk文件名称需要替换成之前生成是文件名称。其实这里的主要目的是创建CA并登录CA用户。文件路径为：/opt/gopath/src/github.com/hyperledger/fabric/aberic/crypto-config/peerOrganizations/org1.example.com/ca，如图：

![20181115154651203.png][]

将两处\_sk替换即可。

4、搭建Fabric网络

（4.1）将编写好的docker-orderer.yaml和docker-peer.yaml文件上传至aberic目录下。

（4.2）在aberic目录下创建文件夹chaincode,再在chaincode文件夹下创建文件夹go。将官方demo(我用的fabric1.0版本)中的chaincode\_example02示例上传到go目录下。最终结果如图：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 5][]

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 6][]

（4.3）分别执行以下命令启动orderer和peer（按照顺序应该先启动排序服务），如图：

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

![20181115171710838.png][]

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

![20181115171745688.png][]

我这里有个警告，没影响后面执行就暂时先me启动没管它。接下来执行docker ps查看容器是否启动，如图：

![20181115171904478.png][]

可以看到所有容器都已成功启动，接下来是对channel和chaincode执行操作了。

（4.4）进入客户端对channel进行相关操作：

docker exec -it cli bash

![20181115172601126.png][]

注：上述命令是对docker容器的常规操作，cli则是YAML启动文件中定义的container\_name（容器名称），通过修改上述命令中的cli为其它容器名称，可以开启所写容器的内部服务。（退出容器的操作为ctrl+p+q）

（4.5）创建channel：

peer channel create -o orderer.example.com:7050 -c mychannel -t 50 -f ./channel-artifacts/mychannel.tx

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 7][]

（4.6）通过channel.block文件来加入该channel，以便后续可以安装实例化并测试只能合约。

peer channel join -b mychannel.block

![20181115225723889.png][]

至此，已经完成了channel的创建并成功加入该channel，即一个最小单位的Fabric网络已经成功搭建起来了。

5、智能合约安装部署测试

（5.1）安装智能合约，如图表示安装成功：

peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode\_example02 -v 1.0

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 8][]

（5.2）实例化chaincode，如图表示实例化成功：

peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n mychannel -c '\{"Args":\["init","A","10","B","10"\]\}' -P "OR ('Org1MSP.member')" -v 1.0

![20181115231950294.png][]

由命令可以看出，调用init方法，接受A，10，B，10四个参数。意思是创建一个key为A的账户，并给该账户一个值为10的资产。同时创建一个key为B的账户，也给该账户一个值为10的资产。

（5.3）执行query方法，该方法接收且仅能接收一个参数，所接收的参数为zhin智能合约中所创建账户的key值，返回内容为该账户下的资产。如图，表示查询成功：

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

![20181115232935424.png][]

同理，查询B账户，资产也是10：

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

![20181115233157409.png][]

（5.4）invoke方法，需要传入三个参数，第一个和第二个参数分别是不同的账户名，第三个参数是资产值。方法的核心是第一个账户将自己资产中第三个参数值的资产转移到第二个账户名下。如A账户转移2个资产单位到B账户下，执行命令如下：

peer chaincode invoke -C mychannel -n mychannel -c '\{"Args":\["invoke", "A", "B", "2"\]\}'

这里会执行打印很长的一段日志，这里只截取最后显示成功的部分，如图，可以看到打印Chaincode invoke successful. result: status:200字样的日志信息：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 9][]

此时在查询A账户的资产，发现少了两个：

![20181115233912933.png][]

而查询B账户资产多了两个：

![20181115234003427.png][]

6、部署peer0.org2节点

（6.1）为org2节点准备docker-peer1.yaml启动文件，具体内容如下：

version: '2'

services:

peer0.org2.example.com:  
    container\_name: peer0.org2.example.com  
    image: hyperledger/fabric-peer  
    environment:  
      - CORE\_PEER\_ID=peer0.org2.example.com  
      - CORE\_PEER\_NETWORKID=aberic  
      - CORE\_PEER\_ADDRESS=peer0.org2.example.com:7051  
      - CORE\_PEER\_CHAINCODELISTENADDRESS=peer0.org2.example.com:7052  
      - CORE\_PEER\_GOSSIP\_EXTERNALENDPOINT=peer0.org2.example.com:7051  
      - CORE\_PEER\_LOCALMSPID=Org2MSP

- 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\_VM\_DOCKER\_HOSTCONFIG\_NETWORKMODE=aberic  
      \# - CORE\_LOGGING\_LEVEL=ERROR  
      - CORE\_LOGGING\_LEVEL=DEBUG  
      - CORE\_VM\_DOCKER\_HOSTCONFIG\_NETWORKMODE=aberic\_default  
      - CORE\_PEER\_GOSSIP\_SKIPHANDSHAKE=true  
      - CORE\_PEER\_GOSSIP\_USELEADERELECTION=true  
      - CORE\_PEER\_GOSSIP\_ORGLEADER=false  
      - CORE\_PEER\_PROFILE\_ENABLED=false  
      - CORE\_PEER\_TLS\_ENABLED=false  
      - 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  
    volumes:  
        - /var/run/:/host/var/run/  
        - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp  
        - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls  
    working\_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer  
    command: peer node start  
    ports:  
      - 8051:8051  
      - 8052:8052  
      - 8053:8053  
    networks:  
      default:  
        aliases:  
          - aberic

（6.2）将docker-peer1.yaml文件上传至aberic目录，如图：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 10][]

（6.3）退出docker cli容器，如图：ctrl+p+q（若已退出，忽略此步）

![20181115235814225.png][]

（6.3）进入该目录，并启动docker-peer1.yaml，如图，警告先不管:

cd /opt/gopath/src/github.com/hyperledger/fabric/aberic

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

![20181116000520100.png][]

（6.4）执行docker ps查看启动的docker容器：

![20181116000658939.png][]

如图所示，peer0org2已成功启动。接下来会针对peer0org2执行频道加入、安装合约、测试合约以及背书验证等操作。

（6.5）首先进入cli客户端进行一些全局变量的更改，使得cli可以对peer0org2进行相关操作。命令如下：

docker exec -it cli bash

![20181116001142696.png][]

（6.6）进入容器后，进行一系列当前容器全局变量赋值操作，命令分别如下：

CORE\_PEER\_ID=peer0.org2.example.com

CORE\_PEER\_ADDRESS=peer0.org2.example.com:7051

CORE\_PEER\_CHAINCODELISTENADDRESS=peer0.org2.example.com:7052

CORE\_PEER\_GOSSIP\_EXTERNALENDPOINT=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

CORE\_PEER\_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp

![20181116004354265.png][]

（6.6）执行peer0org2加入频道的操作：

peer channel join -b mychannel.block

![20181116005303609.png][]

安装智能合约：

peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode\_example02 -v 1.0

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 11][]

（6.7）在peer0org2加入频道并安装智能合约之后，可执行以下命令测试合约是否已成功运行：

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

![2018111600570317.png][]

如图，查出来账户A资产为8

（6.8）在当前cli容器中再次执行一次转账命令，这次让B给A转账2个资产：

peer chaincode invoke -C mychannel -n mychannel -c '\{"Args":\["invoke", "B", "A", "2"\]\}'

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 12][]

如图，显示invoke成功。

（6.9）再次查询A和B账户的资产，如图：

![20181116010148274.png][]

![20181116010221637.png][]

此时发现，A和B的资产并未发生变化。原因是在实例化智能合约操作的时候，选择的背书组织为Org1，而后加入的节点组织为Org2，这说明来自Org2的对资产变更的操作都未经过背书，即不具备任何效力。但是因为Org2组织加入了该频道且安装了合法的合约，所以可以对区块链中的数据进行检索。

（6.10）执行exit（或者ctrl+p+q）退出当前cli：

![20181116010634947.png][]

重新进入cli（这时cli容器默认是对peer0org1节点的操作）：

docker exec -it cli bash

再次执行账户B转账2个资产给账户A的操作：

peer chaincode invoke -C mychannel -n mychannel -c '\{"Args":\["invoke", "B", "A", "2"\]\}'

成功之后再次查询A账户的资产，如图，已变为10个：

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

![20181116011030344.png][]

查询B账户资产，也已变为10个：

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

![201811160111200.png][]

[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70]: /images/20220417/12e6bdac4ebb4cf985332338a875787d.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 1]: /images/20220417/bfcf2fdf61be42728103d72370ffebfd.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 2]: /images/20220417/95438d7daae6433d861c141b7a563636.png
[20181114115640575.png]: /images/20220417/b77ff1e3583647d9ad39ebcfaea36ede.png
[20181114120044460.png]: /images/20220417/637e0a0c3a4c4ccaa56c0693870374fb.png
[20181114111453899.png]: /images/20220417/8bb23355a5ec4fc39b00c822d95b297b.png
[20181114111947849.png]: /images/20220417/ddddf07612ff402981b41ce3e0b88ef9.png
[2018111411200222.png]: /images/20220417/e32a9e6d19774f1ab7ab8da624477ce9.png
[20181114131114683.png]: /images/20220417/31db9d6d1d4c4672b0b0d14e1079a5c9.png
[20181114131234372.png]: /images/20220417/49fede4f7d394baeb4f1fa5a1273f0f3.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 3]: /images/20220417/96d76326d6764597aa3072ed6dda19bf.png
[20181114131749452.png]: /images/20220417/0a0feab66c174514ba5c99918372a606.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 4]: /images/20220417/4ad0d712d5834c60973d114b034ff1cb.png
[20181115154651203.png]: /images/20220417/783aa798920443919190de1b812dfc12.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 5]: /images/20220417/26501289cea54580b20027415f9c9d16.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 6]: /images/20220417/228262e238b3462db71ede12b9189a86.png
[20181115171710838.png]: /images/20220417/95b0e33bdc5e4189bb4a9b0afece53df.png
[20181115171745688.png]: /images/20220417/4ded0f483ae24760bc72b7f08c210e7f.png
[20181115171904478.png]: /images/20220417/cf2b558244ac45b2b7bc075834d8fde3.png
[20181115172601126.png]: /images/20220417/f877c3018a3f46f3aba453edbc36bfd7.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 7]: /images/20220417/e8d3d7879d4b45338daa68e36ee35f5c.png
[20181115225723889.png]: /images/20220417/7ad8fcbfc90f424bb7bab16963bbc352.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 8]: /images/20220417/37ff1458285641b9ab199d3ae930ec63.png
[20181115231950294.png]: /images/20220417/bce3609987ac4582a19de6df57161942.png
[20181115232935424.png]: /images/20220417/3a9fff4af37340768ebfc3f033ce023a.png
[20181115233157409.png]: /images/20220417/a57d8fdbff194540a41ec15e5598ab74.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 9]: /images/20220417/8de61d6327c847ccb4bccbb415d5e53d.png
[20181115233912933.png]: /images/20220417/16097c77d2814cfcb5313a484d89a16a.png
[20181115234003427.png]: /images/20220417/cb26ad360b2c4dd197ee5f7f6ef69ccd.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 10]: /images/20220417/37eea8cf15e94284adb388bb68ca8387.png
[20181115235814225.png]: /images/20220417/5d5d6cdefdf94615b72374575045bafe.png
[20181116000520100.png]: /images/20220417/2f7f4fb11fa74920b5fded008862add0.png
[20181116000658939.png]: /images/20220417/e9808e4022e8409487d99a920b972517.png
[20181116001142696.png]: /images/20220417/a4c9c338796646939c614aa2776488b4.png
[20181116004354265.png]: /images/20220417/edaeb357b9ed4b5d90223ce29e649a95.png
[20181116005303609.png]: /images/20220417/d14e65e4542847d09a62ff3ae1e10f36.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 11]: /images/20220417/ad02704928334123a506281602e901ec.png
[2018111600570317.png]: /images/20220417/94015a4ebfbc4fccadfcfd0841b5163c.png
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3RpYW5zaHVoYW81MjE_size_16_color_FFFFFF_t_70 12]: /images/20220417/d05b1ec3291c45ebbf0402ed876e4a4f.png
[20181116010148274.png]: /images/20220417/b8ac76c18fc64db4a67271f95ca2ead4.png
[20181116010221637.png]: /images/20220417/8c5df98e427b4ed69323e36488241c69.png
[20181116010634947.png]: /images/20220417/18e49aa5ab674767bad07ca3193bca88.png
[20181116011030344.png]: /images/20220417/ebb1d8b626a14f0abf031f5b46b411e9.png
[201811160111200.png]: /images/20220417/3c3f37c85e3f4f3f9c3f0668410081e3.png