安装fabric链码

最新推荐文章于 2023-10-25 21:51:15 发布
最新推荐文章于 2023-10-25 21:51:15 发布
阅读量3.1k 收藏
点赞数
文章标签： fabric github docker
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_15799869/article/details/125621439
版权

[root@iZ8vbjcbks7pzj9po96hleZ test-network]# go env -w GOPROXY=https://goproxy.cn,direct
[root@iZ8vbjcbks7pzj9po96hleZ test-network]# ./network.sh deployCC -ccn basic -ccp …/asset-transfer-basic/chaincode-go -ccl go
Using docker and docker-compose
deploying chaincode on channel ‘mychannel’
executing with the following

  • CHANNEL_NAME: mychannel
  • CC_NAME: basic
  • CC_SRC_PATH: …/asset-transfer-basic/chaincode-go
  • CC_SRC_LANGUAGE: go
  • CC_VERSION: 1.0
  • CC_SEQUENCE: 1
  • CC_END_POLICY: NA
  • CC_COLL_CONFIG: NA
  • CC_INIT_FCN: NA
  • DELAY: 3
  • MAX_RETRY: 5
  • VERBOSE: false
    Vendoring Go dependencies at …/asset-transfer-basic/chaincode-go
    ~/fabric/scripts/fabric-samples/asset-transfer-basic/chaincode-go ~/fabric/scripts/fabric-samples/test-network
    go: downloading github.com/golang/protobuf v1.3.2
    go: downloading github.com/hyperledger/fabric-contract-api-go v1.1.0
    go: downloading github.com/hyperledger/fabric-chaincode-go v0.0.0-20200424173110-d7076418f212
    go: downloading github.com/hyperledger/fabric-protos-go v0.0.0-20200424173316-dd554ba3746e
    go: downloading github.com/stretchr/testify v1.5.1
    go: downloading google.golang.org/grpc v1.23.0
    go: downloading github.com/xeipuuv/gojsonschema v1.2.0
    go: downloading github.com/go-openapi/spec v0.19.4
    go: downloading github.com/gobuffalo/packr v1.30.1
    go: downloading github.com/pmezard/go-difflib v1.0.0
    go: downloading google.golang.org/genproto v0.0.0-20180831171423-11092d34479b
    go: downloading golang.org/x/net v0.0.0-20190827160401-ba9fcec4b297
    go: downloading github.com/gobuffalo/envy v1.7.0
    go: downloading github.com/gobuffalo/packd v0.3.0
    go: downloading github.com/xeipuuv/gojsonreference v0.0.0-20180127040603-bd5ef7bd5415
    go: downloading golang.org/x/sys v0.0.0-20190710143415-6ec70d6a5542
    go: downloading github.com/go-openapi/jsonpointer v0.19.3
    go: downloading github.com/go-openapi/jsonreference v0.19.2
    go: downloading github.com/go-openapi/swag v0.19.5
    go: downloading github.com/joho/godotenv v1.3.0
    go: downloading github.com/rogpeppe/go-internal v1.3.0
    go: downloading github.com/xeipuuv/gojsonpointer v0.0.0-20180127040702-4e3ac2762d5f
    go: downloading github.com/PuerkitoBio/purell v1.1.1
    go: downloading github.com/mailru/easyjson v0.0.0-20190626092158-b2ccc519800e
    go: downloading golang.org/x/text v0.3.2
    go: downloading github.com/PuerkitoBio/urlesc v0.0.0-20170810143723-de5bf2ad4578
    ~/fabric/scripts/fabric-samples/test-network
    Finished vendoring Go dependencies
  • peer lifecycle chaincode package basic.tar.gz --path …/asset-transfer-basic/chaincode-go --lang golang --label basic_1.0
  • res=0
    Chaincode is packaged
    Installing chaincode on peer0.org1…
    Using organization 1
  • peer lifecycle chaincode install basic.tar.gz
  • res=0
    2022-07-05 15:43:54.270 CST 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:“\nJbasic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7\022\tbasic_1.0” >
    2022-07-05 15:43:54.270 CST 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7
    Chaincode is installed on peer0.org1
    Install chaincode on peer0.org2…
    Using organization 2
  • peer lifecycle chaincode install basic.tar.gz
  • res=0
    2022-07-05 15:44:02.571 CST 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:“\nJbasic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7\022\tbasic_1.0” >
    2022-07-05 15:44:02.571 CST 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7
    Chaincode is installed on peer0.org2
    Using organization 1
  • peer lifecycle chaincode queryinstalled
  • res=0
    Installed chaincodes on peer:
    Package ID: basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7, Label: basic_1.0
    Query installed successful on peer0.org1 on channel
    Using organization 1
  • peer lifecycle chaincode approveformyorg -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile /root/fabric/scripts/fabric-samples/test-network/organizations/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem --channelID mychannel --name basic --version 1.0 --package-id basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7 --sequence 1
  • res=0
    2022-07-05 15:44:04.674 CST 0001 INFO [chaincodeCmd] ClientWait -> txid [f3a4477fe7445aeb09557e806eb283943efa9c1007216a8ca8709e25dc78db81] committed with status (VALID) at localhost:7051
    Chaincode definition approved on peer0.org1 on channel ‘mychannel’
    Using organization 1
    Checking the commit readiness of the chaincode definition on peer0.org1 on channel ‘mychannel’…
    Attempting to check the commit readiness of the chaincode definition on peer0.org1, Retry after 3 seconds.
  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name basic --version 1.0 --sequence 1 --output json
  • res=0
    {
    “approvals”: {
    “Org1MSP”: true,
    “Org2MSP”: false
    }
    }
    Checking the commit readiness of the chaincode definition successful on peer0.org1 on channel ‘mychannel’
    Using organization 2
    Checking the commit readiness of the chaincode definition on peer0.org2 on channel ‘mychannel’…
    Attempting to check the commit readiness of the chaincode definition on peer0.org2, Retry after 3 seconds.
  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name basic --version 1.0 --sequence 1 --output json
  • res=0
    {
    “approvals”: {
    “Org1MSP”: true,
    “Org2MSP”: false
    }
    }
    Checking the commit readiness of the chaincode definition successful on peer0.org2 on channel ‘mychannel’
    Using organization 2
  • peer lifecycle chaincode approveformyorg -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile /root/fabric/scripts/fabric-samples/test-network/organizations/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem --channelID mychannel --name basic --version 1.0 --package-id basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7 --sequence 1
  • res=0
    2022-07-05 15:44:12.827 CST 0001 INFO [chaincodeCmd] ClientWait -> txid [cda362eaafb282ff7973b49f667bea6ce8ef516f13984060cc6392be9f5ff97c] committed with status (VALID) at localhost:9051
    Chaincode definition approved on peer0.org2 on channel ‘mychannel’
    Using organization 1
    Checking the commit readiness of the chaincode definition on peer0.org1 on channel ‘mychannel’…
    Attempting to check the commit readiness of the chaincode definition on peer0.org1, Retry after 3 seconds.
  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name basic --version 1.0 --sequence 1 --output json
  • res=0
    {
    “approvals”: {
    “Org1MSP”: true,
    “Org2MSP”: true
    }
    }
    Checking the commit readiness of the chaincode definition successful on peer0.org1 on channel ‘mychannel’
    Using organization 2
    Checking the commit readiness of the chaincode definition on peer0.org2 on channel ‘mychannel’…
    Attempting to check the commit readiness of the chaincode definition on peer0.org2, Retry after 3 seconds.
  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name basic --version 1.0 --sequence 1 --output json
  • res=0
    {
    “approvals”: {
    “Org1MSP”: true,
    “Org2MSP”: true
    }
    }
    Checking the commit readiness of the chaincode definition successful on peer0.org2 on channel ‘mychannel’
    Using organization 1
    Using organization 2
  • peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile /root/fabric/scripts/fabric-samples/test-network/organizations/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem --channelID mychannel --name basic --peerAddresses localhost:7051 --tlsRootCertFiles /root/fabric/scripts/fabric-samples/test-network/organizations/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem --peerAddresses localhost:9051 --tlsRootCertFiles /root/fabric/scripts/fabric-samples/test-network/organizations/peerOrganizations/org2.example.com/tlsca/tlsca.org2.example.com-cert.pem --version 1.0 --sequence 1
  • res=0
    2022-07-05 15:44:21.078 CST 0001 INFO [chaincodeCmd] ClientWait -> txid [afbaba0a6b95b3be829efce6b3a802667008470cc079427438e7e8eef0e4fde7] committed with status (VALID) at localhost:7051
    2022-07-05 15:44:21.079 CST 0002 INFO [chaincodeCmd] ClientWait -> txid [afbaba0a6b95b3be829efce6b3a802667008470cc079427438e7e8eef0e4fde7] committed with status (VALID) at localhost:9051
    Chaincode definition committed on channel ‘mychannel’
    Using organization 1
    Querying chaincode definition on peer0.org1 on channel ‘mychannel’…
    Attempting to Query committed status on peer0.org1, Retry after 3 seconds.
  • peer lifecycle chaincode querycommitted --channelID mychannel --name basic
  • res=0
    Committed chaincode definition for chaincode ‘basic’ on channel ‘mychannel’:
    Version: 1.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]
    Query chaincode definition successful on peer0.org1 on channel ‘mychannel’
    Using organization 2
    Querying chaincode definition on peer0.org2 on channel ‘mychannel’…
    Attempting to Query committed status on peer0.org2, Retry after 3 seconds.
  • peer lifecycle chaincode querycommitted --channelID mychannel --name basic
  • res=0
    Committed chaincode definition for chaincode ‘basic’ on channel ‘mychannel’:
    Version: 1.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]
    Query chaincode definition successful on peer0.org2 on channel ‘mychannel’
    Chaincode initialization is not required
    [root@iZ8vbjcbks7pzj9po96hleZ test-network]# ./network.sh deployCC
    Using docker and docker-compose
    deploying chaincode on channel ‘mychannel’
    executing with the following
  • CHANNEL_NAME: mychannel
  • CC_NAME: NA
  • CC_SRC_PATH: NA
  • CC_SRC_LANGUAGE: NA
  • CC_VERSION: 1.0
  • CC_SEQUENCE: 1
  • CC_END_POLICY: NA
  • CC_COLL_CONFIG: NA
  • CC_INIT_FCN: NA
  • DELAY: 3
  • MAX_RETRY: 5
  • VERBOSE: false
    No chaincode name was provided. Valid call example: ./network.sh deployCC -ccn basic -ccp …/asset-transfer-basic/chaincode-go -ccl go
    Deploying chaincode failed
    [root@iZ8vbjcbks7pzj9po96hleZ test-network]# ./network.sh deployCC -ccn basic -ccp …/asset-transfer-basic/chaincode-go -ccl go
    Using docker and docker-compose
    deploying chaincode on channel ‘mychannel’
    executing with the following
  • CHANNEL_NAME: mychannel
  • CC_NAME: basic
  • CC_SRC_PATH: …/asset-transfer-basic/chaincode-go
  • CC_SRC_LANGUAGE: go
  • CC_VERSION: 1.0
  • CC_SEQUENCE: 1
  • CC_END_POLICY: NA
  • CC_COLL_CONFIG: NA
  • CC_INIT_FCN: NA
  • DELAY: 3
  • MAX_RETRY: 5
  • VERBOSE: false
    Vendoring Go dependencies at …/asset-transfer-basic/chaincode-go
    ~/fabric/scripts/fabric-samples/asset-transfer-basic/chaincode-go ~/fabric/scripts/fabric-samples/test-network
    ~/fabric/scripts/fabric-samples/test-network
    Finished vendoring Go dependencies
  • peer lifecycle chaincode package basic.tar.gz --path …/asset-transfer-basic/chaincode-go --lang golang --label basic_1.0
  • res=0
    Chaincode is packaged
    Installing chaincode on peer0.org1…
    Using organization 1
  • peer lifecycle chaincode install basic.tar.gz
  • res=1
    Error: chaincode install failed with status: 500 - failed to invoke backing implementation of ‘InstallChaincode’: chaincode already successfully installed (package ID ‘basic_1.0:2e20ce421c8037420718c8a3918a1eea76343b7361fffdac454181c54e5736c7’)
    Chaincode installation on peer0.org1 has failed
    Deploying chaincode failed
    [root@iZ8vbjcbks7pzj9po96hleZ test-network]#
推荐江湖2020
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
Fabric中链码安装
weixin_41946008的博客
10-06 785
链码安装的代码如下： # peer chaincode install -n firstcode -v 1.0 -p github.com/chaincode/firstcode/go/ -n 代表链码的名称 -v 代表链码的版本 -p 代表链码安装的位置（ps：安装的位置是相对于$GOPATH/src/ 目录而言） 但是我们在执行命令时需要在链码安装的位置添加一个链码的文件 package main //WARNING - this chaincode's ID is hard-coded in
Fabric 链码Chaincode　的安装、初始化、调用、升级
01-20
Fabric 链码Chaincode　的安装、初始化、调用、升级　 Fabric   chaincode 上一篇文章，我们启动了一个Fabric网络，这篇文章来看看在Fabric网络进行应用的开发。 上一篇文章，我们启动了一个 Fabric 网络，这篇文章来看看在 Fabric 网络进行应用的开发。 什么是 chaincode chaincode 是 fabric 的智能合约，又叫做链码。Chaincode 是生成交易 transacton 的唯一方式，是外界与区块链系统交互的唯一渠道，开发 Fabric 区块链应用就是要编写 Chaincode, Chaincode 就是业务逻辑实现。
fabric多机安装链码
qq_23215009的博客
01-26 1042
fabric多机安装链码 一、如何安装链码 1.安装链码 -打包链码，由于这次的例子是基于 go 语言开发的智能合约，会依赖 go 的开发环境进行安装，如果使用 peer chaincode install 命令指定链码路径安装，可能会造成其他虚拟上安装的同样的链码无法同步实例化（go 开发环境不一致引起的问题），所以这里使用 go chaincode package 打包链码，然后通过安装打包链...
Hyperledger fabric部署链码（一）打包链码
最新发布
wangzelong046的博客
10-25 424
Hyperledger Fabric 是 Hyperledger （超级账本）中的区块链项目之一，也是经典的联盟链之一。它有一个账本，使用智能合约，由参与者管理交易的系统，但它又不完全去中心化，即想要加入联盟的成员们需要从可信赖的成员服务提供者（MSP）注册，以下是一些相关概念的介绍。
手把手教你hyperledger fabric2.4测试网络安装链码
u012421101的博客
01-10 541
seq是指智能合约安装的次数，我这是第三此安装，所以设置为3。其它的设置容易理解不在这里解释了。，然后再secure_path里添加fabric-samples/bin的位置。进入文件夹运行命令，生成vendor文件夹。可以查询哪个组织同意了哪个没有。可以看到Org1以及同意。接下来切换到Org2。
Hyperledger Fabric 链码开发介绍1
08-04
Hyperledger Fabric Chaincode for Developersmkdir -p $GOPATH/src/sacc && cd $GOPA
Hyperledger Fabric 链码开发实战1
08-04
Hyperledger Fabric 链码开发实战 Hyperledger Fabric 是一个开源的分布式账本技术，旨在提供一个灵活、可扩展、安全的平台，以便开发者构建区块链应用程序。链码是 Fabric 中的一种业务逻辑实现，用于处理具体的...
Fabric 系统链码
01-08
fabric 自 1.0 版本开始，将链码分为系统链码和普通链码两种。普通链码（智能合约）用于实现业务逻辑，而系统链码则是用于系统管理，例如 lscc、qscc等。 与普通链码需要独立沙盒环境运行不同，系统链码在 peer 服务...
chaincode:HyperLedger Fabric链码示例
04-22
链码笔记参见版本图2.0： golang：1.13.x去做使用go mod摆脱GOROOT限制使用golang 1.13作为开发环境在npm fabric-chaincode中用log4js替换winstonjs
Hyperledger Fabric 开发——Node.js SDK与fabric链码交互1
08-04
Hyperledger Fabric Writing Your First Applicationcd fabric-samples/fabcar && lse
Fabric链码Basic的使用以及部署（release 2.2）
aitutou的博客
04-11 867
#合约描述 此合约是一个基础的实例智能合约，演示如何使用资产初始化分类帐、查询这些资产、创建新资产、基于资产 ID 查询单个资产、更新现有资产以及将资产转让给新所有者。 #准备工作 在开始之前，需要先搭建一下运行fabric智能合约的环境，具体步骤请参见： 原文链接：https://blog.csdn.net/qq_42482245/article/details/109801959 文中需要下载二进制的可执行文件以下载好放入网盘 链接：https://pan.baidu.com/s/1XpGvJ_W7d5
fabric2.2环境搭建，链码部署至通道
J2633500154的博客
12-14 1540
fabric2.2环境搭建，链码部署至通道
Fabric开发模式链码部署测试
攻城老湿的博客
12-06 582
完成 Fabric 的安装与初步尝试后，需要我们进一步的对 Fabric 的部署做了解。由于在生产环境下，无法对链码错误进行有效定位。故而本节首先完成 Fabric 开发环境的部署，可以由程序员手动执行链码，而非提交给 Fabric 去执行，从log日志中可以有效定位问题。另外，本节完成链码的整体操作流程。enjoy！ 1 基础 chaincode 编写 在 chaincode 文件夹中创建...
354-fabric安装链码
Lich Howger
04-15 697
安装链码 peer chaincode install 常用参数: -l --lang golang,node,java -n --name 链码的名字 -p --path 链码的路径 $GOPATH/src -v --version 链码的版本 我们去sample例子里面找一个chaincode的例子 打开 sample/fabric-samples/c...
fabric 2.4.2-simple（1）链码开发（go）
afei8080的专栏
02-19 3045
链码开发（go）基于fabric-contract-api-go项目进行开发。这里以fabric-samples/asset-transfer-basic/chaincode-go为例进行说明。 开发步骤： 1）本地保证工程编译通过； 2）部署到测试网络环境，然后进行打包、安装、实例化、提交等。 1 fabric-contract-api-go github： https://github.com/hyperledger/fabric-contract-api-go hyperledger fabric平台
Hyperledger2.0 链码安装
热门推荐
qq_36566262的博客
01-04 1万+
简介 以Hyperldger2.0为例，链码的安装主要分为以下几部分： package ：打包源代码 install： 安装链码 approveformyorg: 节点所在组织审批链码 commit： 提交链码 在完成之后可以执行链码的查询和调用 package 首先需要对合约进行编译，首先把我们写的go语言合约放到chaincode下新建的test文件夹下。 root@lamaxiya:/opt/gopath/src/github.com/hyperledger/fabric-samples/ch
centos7.6部署fabric以及链码
qq_51955445的博客
09-14 2040
自己通过总结几篇博客以及反复安装几次后得出的可行部署方案代码
Fabric-samples asset-transfer-basic 链码部署与升级（Fabric 2.4.4）
ling1998的博客
10-08 2875
打包链码peer lifecycle chaincode package 安装链码peer lifecycle chaincode install （不同的组织分别安装） 查看链码安装结果： peer lifecycle chaincode queryinstalled 授权链码peer lifecycle chaincode approveformyorg （不同的组织分别授权） 查看链码授权结果：peer lifecycle chaincode checkcommitreadiness 提交链码等
搭建fabric2.1环境问题解决
weixin_68483967的博客
02-01 530
搭建fabric2.1环境过程中遇到的问题以及解决方案
fabric 链码升级
10-14
2. 在 peer 节点上安装新版本的链码。 3. 在通道上进行链码升级操作。 具体步骤可以参考官方文档：https://hyperledger-fabric.readthedocs.io/en/release-2.2/chaincode_lifecycle.html#upgrade-a-chaincode

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值