sh脚本，简化项目运行。现在开始一一验证本文开始定下的需 求。 部署Asset.sol合约 注册资产 查询资产 // select接口调用 Tuple2 result = asset.select(assetAccount).send(); // register接口调用 TransactionReceipt receipt = asset.register(assetAccount [group:1]> getPbftView 2730 [group:1]> getConsensusStatus [ { "id": 1, "jsonrpc": "2.0", "result": [ { "accountType": 1, "allowFutureBlocks": true, "cfgErr": false, "connectedNodes": "method":"getPeers","params": [1],"id":1}' http://127.0.0.1:8545 |jq { "id": 1, "jsonrpc": "2.0", "result": [ { "Agency": "agency", "IPAndPort": "127.0.0.1:62774", "Node": "node3", 配置黑名单：node0拒绝node1的连接

credentials, new StaticGasProvider(gasPrice, gasLimit)); // select接口调用 Tuple2 result = asset.select(assetAccount).send(); 运行 至此我们已经介绍使用区块链开发资产管理应用的所有流程并实现了功能， 接下来可以运行项目，测试功能是否正常。 [group:1]> getPbftView 2730 [group:1]> getConsensusStatus [ { "id": 1, "jsonrpc": "2.0", "result": [ { "accountType": 1, "allowFutureBlocks": true, "cfgErr": false, "connectedNodes": "method":"getPeers","params": [1],"id":1}' http://127.0.0.1:8545 |jq { "id": 1, "jsonrpc": "2.0", "result": [ { "Agency": "agency", "IPAndPort": "127.0.0.1:62774", "Node": "node3",

credentials, new StaticGasProvider(gasPrice, gasLimit)); // select接口调用 Tuple2 result = asset.select(assetAccount).send(); // register接口调用 TransactionReceipt receipt = asset.register(assetAccount [group:1]> getPbftView 2730 [group:1]> getConsensusStatus [ { "id": 1, "jsonrpc": "2.0", "result": [ { "accountType": 1, "allowFutureBlocks": true, "cfgErr": false, "connectedNodes": "method":"getPeers","params": [1],"id":1}' http://127.0.0.1:8545 |jq { "id": 1, "jsonrpc": "2.0", "result": [ { "Agency": "agency", "IPAndPort": "127.0.0.1:62774", "Node": "node3",

credentials, new StaticGasProvider(gasPrice, gasLimit)); // select接口调用 Tuple2 result = asset.select(assetAccount).send(); // register接口调用 TransactionReceipt receipt = asset.register(assetAccount [group:1]> getPbftView 2730 [group:1]> getConsensusStatus [ { "id": 1, "jsonrpc": "2.0", "result": [ { "accountType": 1, "allowFutureBlocks": true, "cfgErr": false, "connectedNodes": "method":"getPeers","params": [1],"id":1}' http://127.0.0.1:8545 |jq { "id": 1, "jsonrpc": "2.0", "result": [ { "Agency": "agency", "IPAndPort": "127.0.0.1:62774", "Node": "node3",

credentials, new StaticGasProvider(gasPrice, gasLimit)); // select接口调用 Tuple2 result = asset.select(assetAccount).send(); // register接口调用 TransactionReceipt receipt = asset.register(assetAccount 运行getConsensusStatus，查看共识状态。 [group:1]> getConsensusStatus [ { "id": 1, "jsonrpc": "2.0", "result": [ { "accountType": 1, "allowFutureBlocks": true, "cfgErr": false, "connectedNodes": "method":"getPeers","params": [1],"id":1}' http://127.0.0.1:8545 |jq { "id": 1, "jsonrpc": "2.0", "result": [ { "Agency": "agency", "IPAndPort": "127.0.0.1:62774", "Node": "node3",

sequenced, tamper-resistant record of all state transitions in the fabric. State transitions are a result of chaincode invocations (‘transactions’) submitted by participating parties. Each transaction results certificates which are tied to organizations, network components, and end users or client applications. As a result, data access control can be manipulated and governed on the broader network and on channel levels CAs can also be used to sign transactions to indicate that an organization endorses the transaction result – a precondition of it being accepted onto the ledger. Let’s examine these two aspects of a CA in

pledging to provide bug fixes for a period of one year from the date of release. This will likely result in a series of patch releases (v1.4.1, v1.4.2, and so on), where multiple fixes are bundled into (consensus) and encryption, for example, can be plugged in to any Hyperledger Fabric network. The result is a universal blockchain architecture that any industry or public domain can adopt, with the assurance sequenced, tamper-resistant record of all state transitions in the fabric. State transitions are a result of chaincode invocations (‘transactions’) submitted by participating parties. Each transaction results

pledging to provide bug fixes for a period of one year from the date of release. This will likely result in a series of patch releases (v1.4.1, v1.4.2, and so on), where multiple fixes are bundled into (consensus) and encryption, for example, can be plugged in to any Hyperledger Fabric network. The result is a universal blockchain architecture that any industry or public domain can adopt, with the assurance sequenced, tamper-resistant record of all state transitions in the fabric. State transitions are a result of chaincode invocations (‘transactions’) submitted by participating parties. Each transaction results

pledging to provide bug fixes for a period of one year from the date of release. This will likely result in a series of patch releases (v1.4.1, v1.4.2, and so on), where multiple fixes are bundled into (consensus) and encryption, for example, can be plugged in to any Hyperledger Fabric network. The result is a universal blockchain architecture that any industry or public domain can adopt, with the assurance sequenced, tamper-resistant record of all state transitions in the fabric. State transitions are a result of chaincode invocations (‘transactions’) submitted by participating parties. Each transaction results

pledging to provide bug fixes for a period of one year from the date of release. This will likely result in a series of patch releases (v1.4.1, v1.4.2, and so on), where multiple fixes are bundled into (consensus) and encryption, for example, can be plugged in to any Hyperledger Fabric network. The result is a universal blockchain architecture that any industry or public domain can adopt, with the assurance sequenced, tamper-resistant record of all state transitions in the fabric. State transitions are a result of chaincode invocations (‘transactions’) submitted by participating parties. Each transaction results