hyperledger多节点交易

最新推荐文章于 2023-03-04 09:56:42 发布
最新推荐文章于 2023-03-04 09:56:42 发布
阅读量1.4k 收藏
点赞数
分类专栏： 区块链 超级账本
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_30505673/article/details/84976628
版权

root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# ls
channel-artifacts crypto testchannel.block
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channle ls
Error: unknown command “channle” for “peer”

Did you mean this?
channel

Run ‘peer --help’ for usage.
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel ls
Operate a channel: create|fetch|join|list|update|signconfigtx|getinfo.

Usage:
peer channel [command]

Available Commands:
create Create a channel
fetch Fetch a block
getinfo get blockchain information of a specified channel.
join Joins the peer to a channel.
list List of channels peer has joined.
signconfigtx Signs a configtx update.
update Send a configtx update.

Flags:
–cafile string Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
–certfile string Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
–clientauth Use mutual TLS when communicating with the orderer endpoint
–connTimeout duration Timeout for client to connect (default 3s)
-h, --help help for channel
–keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
-o, --orderer string Ordering service endpoint
–ordererTLSHostnameOverride string The hostname override to use when validating the TLS connection to the orderer.
–tls Use TLS when communicating with the orderer endpoint

Global Flags:
–logging-level string Default logging level and overrides, see core.yaml for full syntax

Use “peer channel [command] --help” for more information about a command.
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel list
2018-12-12 07:52:31.312 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Channels peers has joined:
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# ls
channel-artifacts crypto testchannel.block
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b testchannel.block
2018-12-12 07:53:06.800 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-12-12 07:53:06.924 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -l golang -n testcc -p github.com/chaincode -v v1.0
2018-12-12 07:54:07.280 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 07:54:07.280 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-12-12 07:54:07.669 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:“OK” >
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode instantiate -o orderer.wilsoner.com:7050 -C testchannel -l golang -n testcc -v v1.0 --tls true --cafile $CAFILE -P “AND (‘OrgGoMSP.member’, ‘OrgCppMSP.member’)” -c ‘{“Args”:[“init”, “a”, “100”, “b”, “200”]}’
2018-12-12 07:54:31.182 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 07:54:31.182 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg chaincode with name ‘testcc’ already exists
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# ---------------------
bash: ---------------------: command not found
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer#
Display all 928 possibilities? (y or n)
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# 93
bash: 93: command not found
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/tlscacerts/tlsca.wilsoner.com-cert.pemCSDN
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/tlscacerts/tlsca.wilsoner.com-cert.pemhttps://blog.csdn.net/qq_30505673/article/details/84963320
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# #
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/
tlscacerts/tlsca.wilsoner.com-cert.pem
channel-artifacts/ crypto/ testchannel.block
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/
tlscacerts/tlsca.wilsoner.com-cert.pem
channel-artifacts/ crypto/ testchannel.block
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/
tlscacerts/tlsca.wilsoner.com-cert.pem
channel-artifacts/ crypto/ testchannel.block
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/wilsoner.com/orderers/orderer.wilsoner.com/msp/tlscacerts/tlsca.wilsoner.com-cert.pem
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode instantiate -o orderer.wilsoner.com:7050 -C testchannel -l golang -n testcc -v v1.0 --tls true --cafile $CAFILE -P “AND (‘OrgGoMSP.member’, ‘OrgCppMSP.member’)” -c ‘{“Args”:[“init”, “a”, “100”, “b”, “200”]}’
2018-12-12 07:55:29.600 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 07:55:29.600 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg chaincode with name ‘testcc’ already exists
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “a”]}’
100
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# echo $CORE_PEER_ADDRESS
peer1.orgcpp.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_ADDRESS=peer0.orggo.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_LOCALMSPID=OrgGoMSP
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/users/Admin@orggo.wilsoner.com/msp
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer0.orggo.wilsoner.com/tls/ca.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer0.orggo.wilsoner.com/tls/server.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer0.orggo.wilsoner.com/tls/server.key
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b testchannel.block
2018-12-12 08:01:44.925 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-12-12 08:01:45.051 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -l golang -n testcc -p github.com/chaincode -v v1.0
2018-12-12 08:03:12.017 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 08:03:12.017 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-12-12 08:03:12.253 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:“OK” >
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode instantiate -o orderer.wilsoner.com:7050 -C testchannel -l golang -n testcc -v v1.0 --tls true --cafile $CAFILE -P “AND (‘OrgGoMSP.member’, ‘OrgCppMSP.member’)” -c ‘{“Args”:[“init”, “a”, “100”, “b”, “200”]}’
2018-12-12 08:03:41.322 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 08:03:41.322 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg chaincode with name ‘testcc’ already exists
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “a”]}’
100
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# echo $CORE_PEER_ADDRESS
peer0.orggo.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_ADDRESS=peer1.orggo.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_LOCALMSPID=OrgGoMSP
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/users/Admin@orggo.wilsoner.com/msp
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer1.orggo.wilsoner.com/tls/ca.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer1.orggo.wilsoner.com/tls/server.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer1.orggo.wilsoner.com/tls/server.key
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# echo $CORE_PEER_ADDRESS
peer1.orggo.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b testchannel.block
2018-12-12 08:25:26.198 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-12-12 08:25:26.322 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -l golang -n testcc -p github.com/chaincode -v v1.0
2018-12-12 08:26:23.503 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-12-12 08:26:23.503 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-12-12 08:26:23.740 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:“OK” >
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “a”]}’
100
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# ROORCERT1=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.wilsoner.com/peers/peer0.orggo.wilsoner.com/tls/ca.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# ROORCERT2=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.wilsoner.com/peers/peer1.orgcpp.wilsoner.com/tls/ca.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode invoke -o orderer.wilsoner.com:7050 --tls true --cafile $CAFILE -C testchannel -n testcc -c ‘{“Args”:[“invoke”,“a”,“b”,“10”]}’ --peerAddresses peer0.orggo.wilsoner.com:7051 --tlsRootCertFiles $ROORCERT1 --peerAddresses peer1.orgcpp.wilsoner.com:7051 --tlsRootCertFiles $ROORCERT2
2018-12-12 08:30:20.637 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “a”]}’
90
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “b”]}’
210
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# echo $CORE_PEER_ADDRESS
peer1.orggo.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_ADDRESS=peer0.orgcpp.wilsoner.com:7051
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_LOCALMSPID=OrgCppMSP
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.wilsoner.com/users/Admin@orgcpp.wilsoner.com/msp
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.wilsoner.com/peers/peer0.orgcpp.wilsoner.com/tls/ca.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.wilsoner.com/peers/peer0.orgcpp.wilsoner.com/tls/server.crt
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.wilsoner.com/peers/peer0.orgcpp.wilsoner.com/tls/server.key
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -n testcc -C testchannel -c ‘{“Args”:[“query”, “a”]}’
90
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer#

wilson_go
关注
专栏目录
Fabric_超详细的fabric网络搭建04.2-Peer节点相关操作
Grayan的博客
03-11 802
4.Peer操作 5.链码初始化 背书策略的几种方式: AND AND (‘Org1MSP.member’, ‘Org2MSP.member’, ‘Org3MSP.member’) 按照该背书规则进行交易, 必须通过组织Org1MSP，Org2MSP，Org3MSP中的用户共同验证交易才能生效 OR OR (‘Org1MSP.member’, ‘Org2MSP.member’, ‘Org3...
Hyperledger Fabric 节点分类以及配置
TBBetter的博客
04-28 1791
Fabric 节点分类以及配置节点分类Endorsing PeerCommitting PeerAnchor PeerLeading PeerOrderer Peer（O_S） 节点分类 在 HF 中，有背书节点，提交节点，锚节点和领导节点。一个节点可以同时是一个提交节点，背书节点，领导节点和锚节点！出于实践的考虑，总会有一个领导节点，至少一个背书节点和至少一个提交节点。 排序节点是特殊的，它不属...
docker容器执行shell命令
lazy_ting的博客
12-09 4128
参考资料：https://blog.csdn.net/wangctes/article/details/95867068 目前还摸太清楚，只做记录 注意点：需要将shell文件放到docker能访问到的目录下 我的docker进入容器后默认路径为/opt/gopath/src/github.com/hyperledger/fabric/peer/ 所以我写的命令是 docker exec...
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg
zhuiyunzhugang的博客
06-18 2368
root@51a09023bf05:/opt/gopath/src/github.com/hyperledger/fabric/peer# Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Failed to generate platform-speci
在cli容器中实例化链码时报错
weixin_57534018的博客
06-26 1004
-
hyperledger中安装链码
qq_30505673的博客
12-12 3039
root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# # root@c6de44112a9f:/opt/gopath/src/github.com/hyperledger/fabric/peer# CAFILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/...
Hyperledger详解
01-08
这篇文章介绍了Hyperledger区块链技术的原理、构架和协议。1.1 Fabric介绍Fabric是数字事件(交易)的账簿，这个账簿由多个参与者共享，每个参与者都在系统中拥有权益。账簿只有在所有参与者达成共识的情况下才能够...
Hyperledger Fabric 应用实战（2）--网络节点设置
最新发布
weixin_43274469的博客
03-04 4039
Fabric网络通过证书和密钥来管理和认证成员身份，Fabric通过Fabric-CA提供了PKI服务。为了方便批量管理组织证书，fabric基于Go语言的标准crypto库提供了cryptogen工具。用了cryprtogen工具生成加密材料，就无需CA来到动态生成加密材料。
多机部署Hyperledger Fabric+Composer(两台机器)
03-01
### 多机部署Hyperledger Fabric+Composer(两台机器) #### 概述 本文档将指导您通过两台虚拟机（VMs）部署一个Hyperledger Fabric区块链网络，并使用Hyperledger Composer构建业务网络。该网络包括两个组织：Org1...
Hyperledger Fabric linux二进制文件
03-29
Hyperledger Fabric是Linux基金会发起的开源项目，是一个用于构建企业级分布式应用的区块链框架。它提供了模块化的架构，允许在区块链网络中灵活地选择共识机制、身份管理、数据存储等核心组件。本压缩包“hyper...
Fabric1.4.x_Error
qq_22016915的博客
08-22 2989
1.ERROR: for cli b'cannot stop container: 81ea509ef7934b2059d47c0c8ffd5c17e229356a8465c28ff0cf42fd7afa06e3: Cannot kill container 81ea509ef7934b2059d47c0c8ffd5c17e229356a8465c28ff0cf42fd7afa06e3: unknown error after kill: runc did not terminate sucessfully
fabric错误总结
qq_44579341的博客
06-02 2933
总结我在尝鲜fabric网络遇到的错误..只记录我整了挺久的部分 1.could not assemble transaction,err proposal response was not successful,error code 500,msg error starting container:err starting container:API error(404):network _byfn not found 这是peer节点和docker启动的网络不对应,这种情况一般发生在手动启动网络的时
fabric 启动peer_Hyperledger Fabric 1.0 学习搭建 （五）--- 启动Fabric多节点集群
weixin_29084231的博客
01-17 273
5.1、启动orderer节点服务上述操作完成后，此时各节点的compose配置文件及证书验证目录都已经准备完成，可以开始尝试启动多机Fabric集群。首先启动orderer节点，切换至orderer.example.com服务器，即前文指定的10.130.116.8服务器，执行如下命令进入启动docker进程：docker-compose -f docker-compose-orderer.ya...
Hyperledger Fabric 开发环境搭建
热门推荐
lucasma的博客
11-09 1万+
开发环境介绍仅以我自己的环境为例 UBUNTU 16.04 LTS虚拟机 docker docker-compose git docker和docker-compose的安装省略
深入解析Hyperledger Fabric搭建的全过程
weixin_30265103的博客
06-22 629
在这篇文章中，使用fabric-samples/first-network中的文件进行fabric网络(solo类型的网络)搭建全过程的解析。如有错误欢迎批评指正。 至于Fabric网络的搭建这里不再介绍，可以参考这一篇文章Hyperledger Fabric环境搭建过程 fabric网络：单机，solo类型，两个组织，分别有两个节点 首先看一下该文件夹内有哪些文件： base ...
Hyperledger/fabric(v0.7) create and join peer to a new channel
c785795635的专栏
02-24 1007
用docker搭建fabric网络
7.3 多链及多通道实现
hanxiaodong
03-01 1049
目标 Hyperledger Fabric 多链&amp;amp;多通道 多链&amp;amp;&amp;amp;多通道的实现 任务实现 7.3.1 多链及多通道 在 Hyperledger Fabric 0.6 版本中，所有节点都属于同一个链中，由此产生了数据处理、存储及访问安全的问题。在后期的 Hyperledger Fabric 1.0 版本中，新增加了对多链实现。 链是由一个通道 + 一个共享账本 + N个...
Error: could not assemble transaction: ProposalResponsePayloads do not match - proposal response: ve
lakersssss24的博客
06-21 1750
最近在跑fabric2.3自测链码的时候遇到了很多错误，自己也是很苦恼，改了好几个下午的bug就是找不到真正的问题所在，下面先看一个错误：Error: could not assemble transaction: ProposalResponsePayloads do not match - proposal response: version:1 response:......
Hyperledger Fabric v1.3 单机多节点Kafka SSL部署指南
"本文档是关于部署Hyperledger Fabric v1.3的详细指南，特别强调在单台机器上建立多节点Kafka集群，并且所有服务都启用了SSL认证。" 在Hyperledger Fabric v1.3的部署过程中，关键点包括环境规划、节点设置以及开启...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值