发表于 | 分类于

我这个人，一般现场做或者线上做面试题，表现都很差，但是給我一个IDE，我就起飞了，面向IDE编程的选手。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
package com.alonelaval.java.leetcode;
import java.util.Arrays;
/**
 * @author huawei
 * @create 2019-11-28
 **/
public class Code2 {
    /**
     * 递归合并两个已按升序排列的数组.
     *
     * <p>
     *   提示：
     *     1. 必须使用递归写法，循环写法无效。
     *     2. 可以定义辅助函数。
     *     3. test case执行时可能出现StackOverFlowError。
     * </p>
     *
     * @param a 升序排列数组，长度可能为0-10000
     * @param b 升序排列数组，长度可能为0-10000
     * @return a和b合并后的升序排列数组
     */
    public static int[] merge(int[] a, int[] b) {
        if(a == null || b== null){
            return a==null ? b :a;
        }
        int [] result = new int[a.length+b.length];
        return merge(a,b,0,0,result,0);
    }
    public static int[] merge(int []a,int [] b,int aIndex,int bIndex,int []result,int resultIndex){
        if(result.length ==resultIndex){
            return result;
        }
        if(aIndex == a.length){
            result[resultIndex++]=b[bIndex++];
            return merge(a,b,aIndex,bIndex,result,resultIndex);
        }
        if(bIndex == b.length){
            result[resultIndex++]=a[aIndex++];
            return merge(a,b,aIndex,bIndex,result,resultIndex);
        }
        if(a[aIndex] == b[bIndex]){
            result[resultIndex++] = a[aIndex++];
            result[resultIndex++] = b[bIndex++];
        }
        else if (a[aIndex] < b[bIndex]) {
            result[resultIndex++] = a[aIndex++];
        }
        else if (a[aIndex] > b[bIndex]) {
            result[resultIndex++] = b[bIndex++];
        }
        return merge(a,b,aIndex,bIndex,result,resultIndex);
    }
    public static void main(String[] args) {
        int a []= new int[]{1,3,5,12,12,12,12};
        int b []= new int[]{2,4,62,90};
        System.out.println(Arrays.toString(merge(a,b)));
    }
}

发表于 | 分类于

我这个人，一般现场做或者线上做面试题，表现都很差，但是給我一个IDE，我就起飞了，面向IDE编程的选手。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
package com.alonelaval.java.leetcode;
/**
 * @author huawei
 * @create 2019-11-28
 **/
public class AsciiTest {
     /**
     * 找出字符串中出现次数最多的字母，次数相同的情况下返回ascii code更小的，没有字母的话返回null(忽略大小写，统一当成小写处理).
     *
     * <p>
     * 提示:
     * 1. 字符串长度在1000以内，且只包含ascii字符
     * </p>
     *
     * @param string 只包含ascii字符的字符串.
     * @return 出现次数最多的字母.
     */
    public static Character countStr(String str ) {
        if(str == null ) {
            return null;
        }
        int results []= new int[128];
        int c = 0;
        int maxValue=0;
        for(int i=0; i < str.length();i++){
            int a = str.charAt(i);
            if(results[a]+1 > maxValue){
                maxValue = results[a]+1;
                c = a;
            }else if(results[a] == maxValue && c < a){
                c= a;
            }
            results[a]=results[a]+1;
        }
        return  (char)c;
    }
    public static void main(String[] args) {
        String str="12122";
        System.out.println(countStr(str));
    }
}

发表于 | 分类于 ，

使用GO语言开发区块链应用

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
package query
//引入hypeledger 相关包
import (
	"encoding/json"
	"fmt"
	"github.com/hyperledger/fabric/common/flogging"
	"github.com/hyperledger/fabric/core/chaincode/shim"
	"github.com/hyperledger/fabric/protos/peer"
	"strconv"
)
var chaincodeLogger = flogging.MustGetLogger("QueryChaincode")
// 设置存证的索引的前缀，用来隔离别的应用的数据
const Query_Prefix = "Query_"
//定义存证链，需要进行存证的数据
type QueryData struct {
	QueryId  int `json:"queryId"`
	IndexDigest string `json:"indexDigest"`
	ProvideQueryOrg string  `json:"provideQueryOrg"`
	OfferOrg string `json:"offerOrg"`
	QueryTime string `json:"queryTime"`
	QueryType int  `json:"queryType"`
	QueryResult int `json:"queryResult"`
	QuerySerial string `json:"querySerial"`
	Hit int `json:"hit"`
}
type QueryChainCode struct {
}
// 应用返回的数据结构
type ChaincodeRet struct {
	Code int `json:code`
	Message  string `json:message`
	Data interface{} `json:data`
}
//进行初始化，改方法实现了Chaincode接口的Init方法
//GO语言的接口，只要你实现了改接口的方法，就可以认为是该接口的实现类。
//如果它看起来像鸭子，走起来像鸭子，叫起来像鸭子，它就是鸭子。
//这也是与JAVA不一样的地方，JAVA必须要关键字来指定实现某个接口
func (a *QueryChainCode) Init(stub shim.ChaincodeStubInterface) peer.Response {
	return shim.Success(nil)
}
//进行初始化，改方法实现了Chaincode接口的Init方法
func (a *QueryChainCode) Invoke(stub shim.ChaincodeStubInterface) peer.Response {
	//获取调用方法的名称和参数
	fun,args := stub.GetFunctionAndParameters()
	if fun =="query"{
		//通过key查询数据
		return a.getDataById(stub,args[0])
	} else if fun == "put"{
		var data QueryData
		err := json.Unmarshal([]byte(args[0]), &data)
		if err != nil{
			fmt.Println(err)
			return shim.Error("保存数据报错"+err.Error())
		}
		//保存数据
		return a.putData(stub,data)
	}
	return shim.Error("找不到方法！")
}
func (a *QueryChainCode) getDataById(stub shim.ChaincodeStubInterface,queryId string)peer.Response  {
	var data QueryData
	//将ID加上前缀再进行查询
	key := Query_Prefix+queryId
	b ,err := stub.GetState(key)
	if b == nil{
		return shim.Error("null")
	}
	err = json.Unmarshal(b,&data)
	if err !=nil{
		return shim.Error("null")
	}
	return shim.Success(getRetByte(0,"",data))
}
func (a *QueryChainCode) putData(stub shim.ChaincodeStubInterface,data QueryData) peer.Response{
	d,err := json.Marshal(data)
	if err !=nil {
		return shim.Error("null")
	}
	txId :=	stub.GetTxID()
	//将ID加上前缀进行保存
	err = stub.PutState(Query_Prefix+ strconv.Itoa(data.QueryId),d)
	if err != nil{
		return shim.Error("null")
	}
	fmt.Println(stub.GetChannelID())
	//将TXID返回給调用方，方便跟业务数据进行对应
	return shim.Success(getRetByte(0,"",txId))
}
func getRetByte(code int,msg string,data interface{}) []byte {
	var r ChaincodeRet
	r.Code = code
	r.Message= msg
	r.Data = data
	//将数据封装成JSON对象返回給调用方
	b,err := json.Marshal(r)
	if err!=nil {
		fmt.Println("marshal Ret failed"+err.Error())
		return nil
	}
	return b
}

发表于 | 分类于 ，

机器准备

功能 ip 机器名称
orderer 10.9.149.68 order.bits.com
peer0 10.9.149.68 peer0.org1.bits.com
peer0 10.9.84.83 peer0.org2.bits.com

创建目录

1
2
mkdir bits
cd bits

获取生成工具

1
2
3
把下载的hyperledger-fabric-linux-amd64-1.4.1.tar.gz二进制文件包解压，
把其中的bin目录拷贝到bits目录下。
设置权限：chmod -R 777 ./bin

准备生成证书和区块配置文件

配置crypto-config.yaml和configtx.yaml文件，拷贝到bits目录下。

crypto-config.yaml 文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
  # ---------------------------------------------------------------------------
  # Orderer
  # ---------------------------------------------------------------------------
  - Name: Orderer
    Domain: bits.com
    CA:
        Country: US
        Province: California
        Locality: San Francisco
    # ---------------------------------------------------------------------------
    # "Specs" - See PeerOrgs below for complete description
    # ---------------------------------------------------------------------------
    Specs:
      - Hostname: orderer
# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
  # ---------------------------------------------------------------------------
  # Org1
  # ---------------------------------------------------------------------------
  - Name: Org1
    Domain: org1.bits.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
  # ---------------------------------------------------------------------------
  # Org2: See "Org1" for full specification
  # ---------------------------------------------------------------------------
  - Name: Org2
    Domain: org2.bits.com
    EnableNodeOUs: true
    CA:
        Country: US
        Province: California
        Locality: San Francisco
    Template:
      Count: 1
    Users:
      Count: 1

configtx.yaml文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
# 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/bits.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.bits.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.bits.com
              Port: 7051
    - &Org2
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org2MSP
        # ID to load the MSP definition as
        ID: Org2MSP
        MSPDir: crypto-config/peerOrganizations/org2.bits.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('Org2MSP.admin', 'Org2MSP.peer', 'Org2MSP.client')"
            Writers:
                Type: Signature
                Rule: "OR('Org2MSP.admin', 'Org2MSP.client')"
            Admins:
                Type: Signature
                Rule: "OR('Org2MSP.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.org2.bits.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" and "raft"
    OrdererType: solo
    Addresses:
        - orderer.bits.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
    Kafka:
        # Brokers: A list of Kafka brokers to which the orderer connects. Edit
        # this list to identify the brokers of the ordering service.
        # NOTE: Use IP:port notation.
        Brokers:
            - 127.0.0.1:9092
    # 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
                    - *Org2
    TwoOrgsChannel:
        Consortium: SampleConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2

生成公私钥和证书

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

生成创世区块

1
2
mkdir channel-artifacts
./bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

生成通道配置区块

1
./bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/bits-query.tx -channelID bits-query

拷贝到别的电脑

1
2
cd ..
scp -r bits ubuntu@10.9.84.83:/data/bits

部署order，配置docker-compose-orderer.yaml文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
  orderer.example.com:
    container_name: orderer.bits.com
    image: hyperledger/fabric-orderer
    environment:
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_GENESISMETHOD=file
      - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/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_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/orderer.genesis.block
      - ./crypto-config/ordererOrganizations/bits.com/orderers/orderer.bits.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/bits.com/orderers/orderer.bits.com/tls/:/var/hyperledger/orderer/tls
    ports:
      - 7050:7050

启动Fabric orderer排序服务

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

部署peer0.org1.bits.com,配置docker-compose-org1-peer0.yaml文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
  peer0.org1.bits.com:
    container_name: peer0.org1.bits.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_PEER_ID=peer0.org1.bits.com
      - CORE_PEER_ADDRESS=peer0.org1.bits.com:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.bits.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.bits.com:7051
      - 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_VM_DOCKER_HOSTCONFIG_NETWORKMODE=bits_default
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_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.bits.com/peers/peer0.org1.bits.com/msp:/etc/hyperledger/fabric/msp
        - ./crypto-config/peerOrganizations/org1.bits.com/peers/peer0.org1.bits.com/tls:/etc/hyperledger/fabric/tls
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    extra_hosts:
      - "orderer.bits.com:10.9.149.68"
  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.bits.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.bits.com/peers/peer0.org1.bits.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.bits.com/peers/peer0.org1.bits.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.bits.com/peers/peer0.org1.bits.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.bits.com/users/Admin@org1.bits.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/bits/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.bits.com
    extra_hosts:
       - "orderer.bits.com:10.9.149.68"
       - "peer0.org1.bits.com:10.9.149.68"
       - "peer0.org2.bits.com:10.9.84.83"

启动peer0.org1.bits.com

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

进入容器

1
docker exec -it cli bash

创建Channel通道

1
2
3
4
# 因为创建通道需要通知orderer 所以设置oderer的tls证书
ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/bits.com/orderers/orderer.bits.com/msp/tlscacerts/tlsca.bits.com-cert.pem
peer channel create -o orderer.bits.com:7050 -c bits-query -f ./channel-artifacts/bits-query.tx --tls --cafile $ORDERER_CA

加入channel通道

1
peer channel join -b bits-query.block

保存通道信息,需将通道信息拷贝至其他节点

1
2
3
4
#容器名
docker cp xxxxxxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/bits-query.block /data/bits/channel-artifacts
scp -r /data/bits xxx:/data

打包智能合约

1
2
3
4
5
# 每台机器单独安装的话，里面的编号不一致，所以打包好后，去有需要的节点再安装
peer chaincode package -n bits-query -p query/cmd/ -v 1.0 bits-query.pak
docker cp xxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/bits-query.pak /data/bits/channel-artifacts

peer0.org1.bits.com安装

1
peer chaincode install bits-query.pak

部署peer0.org2.bits.com,配置docker-compose-org2-peer0.yaml文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
  peer0.org2.bits.com:
    container_name: peer0.org2.bits.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_PEER_ID=peer0.org2.bits.com
      - CORE_PEER_ADDRESS=peer0.org2.bits.com:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org2.bits.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.bits.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=bits_default
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_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/org2.bits.com/peers/peer0.org2.bits.com/msp:/etc/hyperledger/fabric/msp
        - ./crypto-config/peerOrganizations/org2.bits.com/peers/peer0.org2.bits.com/tls:/etc/hyperledger/fabric/tls
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    extra_hosts:
      - "orderer.bits.com:10.9.149.68"
  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.org2.bits.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.bits.com/peers/peer0.org2.bits.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.bits.com/peers/peer0.org2.bits.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.bits.com/peers/peer0.org2.bits.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.bits.com/users/Admin@org2.bits.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/bits/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.org2.bits.com
    extra_hosts:
       - "orderer.bits.com:10.9.149.68"
       - "peer0.org1.bits.com:10.9.149.68"
       - "peer0.org2.bits.com:10.9.84.83"

启动peer0.org2.bits.com

1
docker-compose -f docker-compose-org2-peer0.yaml up -d

进入容器

1
docker exec -it cli bash

加入通道

1
2
3
docker cp /data/bits/channel-artifacts/bits-query.block xxxxxxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/
peer channel join -b bits-query.block

peer0.org2.bits.com安装

1
2
3
4
5
6
docker cp /data/bits/channel-artifacts/bits-query.pak xxxxxxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/
##安装
peer chaincode install bits-query.pak
##查看是否安装成功
peer chaincode list --installed
peer chaincode list --instantiated -C bits-query

调用

添加数据

1
2
3
4
5
6
7
ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/bits.com/orderers/orderer.bits.com/msp/tlscacerts/tlsca.bits.com-cert.pem
<!--peer chaincode instantiate -o orderer.bits.com:7050 --tls --cafile $ORDERER_CA -C bits-query -n bit-query -v 1.0 -c '{"Args":["init","","","",""]}' -P "OR ('Org1MSP.peer','Org2MSP.peer')"-->
peer chaincode invoke --tls --cafile $ORDERER_CA -C bits-query -n bits-query -c '{"Args":["put","{\"queryId\":233,\"indexDigest\":\"indexDigest\",\"provideQueryOrg\":\"provideQueryOrg\",\"offerOrg\":\"offerOrg\",\"queryTime\":\"queryTime\",\"queryType\":11,\"queryResult\":11,\"querySerial\":\"querySerial\",\"hit\":1}"]}'

查看数据

1
peer chaincode query  -C bits-query -n bits-query -c '{"Args":["query","222"]}'

发表于 | 分类于 ，

下载

1
git clone https://github.com/hyperledger/fabric-samples.git

执行安装程序,安装环境，拉取docker镜像

1
./bootstrap.sh

启动测试

1
docker-compose -f docker-compose.yml up -d

查看运行多少镜像

1
docker ps

切换环境到管理员用户的 MSP ，进入 Peer 节点容器 peerO.orgl.example .com

1
docker exec -it -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp" peer0.org1.example.com bash

创建通道

1
peer channel create -o orderer.example.com:7050 -c mychannel -f /etc/hyperledger/configtx/channel.tx

加入通道

1
peer channel join -b mychannel.block

退出 Peer 节点容器 peerO.orgl.example .com

1
exit

进入 cli 容器

1
docker exec -it cli /bin/bash

给 Peer 节点 peerO.orgl.example.com 安装链码

1
2
3
4
-- cp /opt/gopath/src/github.com/chaincode_example02/go/chaincode_example02.go
-- $GOPATH/src/
-- peer chaincode install -n mycc -v vO -p github.com/chaincode_example02/go
peer chaincode install -n mycc -v 1.0 -p github.com/chaincode_example02/go

实例化链码

1
2
-- peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n mycc -v v0 -c '{"Args":["init","a","100","b","200"]}'
peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n mycc -c '{"Args":["init","A","10","B","10"]}' -P "OR ('Org1MSP.member')" -v 1.0

查询

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

转移 调用链码， 从“ a ”转移 IO 到“ b ”：

1
peer chaincode invoke -C mychannel -n mycc  -c '{"Args":["invoke","A","B","10"]}'

查询转移后的值

1
2
peer chaincode query -C mychannel -n mycc -c '{"Args":["query","A"]}'
peer chaincode query -C mychannel -n mycc -c '{"Args":["query","B"]}'