fabric-SDK-go初探

最新推荐文章于 2022-09-02 15:50:24 发布
最新推荐文章于 2022-09-02 15:50:24 发布
阅读量1.6k 收藏 3
点赞数
分类专栏： Go fabric
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_44336181/article/details/119114578
版权
Go 同时被 2 个专栏收录
17 篇文章 2 订阅
订阅专栏
fabric
4 篇文章 0 订阅
订阅专栏

1. 环境安装

本教程不会详细解释 Hyperledger Fabric ，可访问其官方文档，

本文参照CHAINHERO，在Mac OS上实践，Hyperledger Fabric 框架与 Mac OS X、Windows 和其他 Linux 发行版兼容。

环境安装可参考fabric2.x环境搭建
请确保安装好了docker，go，git等环境

2.打造咱们的第一个区块链网络

为了docker构建区块链网络，我们将使用构建将处理不同角色的虚拟计算机。Hyperledger Fabric 需要大量证书来确保整个端到端流程（TSL、身份验证、签名块……）的加密。这些文件的创建需要一点时间，为了直接解决问题的核心，本文参考的教程已经fixtures在此存储库的文件夹中为准备好了所有这些。

按照我们的存储库命名，src在您的文件夹中创建一个新目录GOPATH：

mkdir -p $GOPATH/src/github.com/chainHero/heroes-service && \
cd $GOPATH/src/github.com/chainHero/heroes-service

要获取fixtures文件夹，您可以遵循此命令行，它将安装并使用 subversion 从该存储库中获取文件夹。或者从 Github下载zip 文件并仅提取fixtures文件夹。

brew install subversion 

cd $GOPATH/src/github.com/chainHero/heroes-service 

svn checkout https://github.com/chainHero/heroes-service/branches/v1.1.0/fixtures 

rm -rf fixtures/.svn

注：如果是Linux

apt -y subversion && \
cd $GOPATH/src/github.com/chainHero/heroes-service && \
svn checkout https://github.com/chainHero/heroes-service/branches/v1.1.0/fixtures &&
rm -rf fixtures/.svn

为了检查网络是否工作，我们将使用docker-compose同时启动或停止所有容器。进入fixtures文件夹，然后运行：

cd $GOPATH/src/github.com/chainHero/heroes-service/fixtures && \
docker-compose up -d

在这里插入图片描述

此时能看到fabric网络已经启动

打开一个新终端运行：
docker ps
在这里插入图片描述
可以看到：两个对等节点，一个排序节点和一个 CA 容器。您已经成功地创建了一个新网络，可以与 SDK 一起使用。要停止网络返回上一个终端，按下Ctrl+C并等待所有容器停止。

  • 提示：当网络停止时，所有使用的容器仍然可以访问。例如，这对于检查日志非常有用。您可以使用docker ps -a. 为了清理这些容器，您需要删除它们，docker rm $(docker ps -aq)或者如果您使用了一个docker-compose文件，请转到该文件所在的位置并运行docker-compose down.

  • 提示：您可以docker-compose在后台运行该命令以保持提示。要做到这一点，使用参数-d，像这样：docker-compose up -d。要停止容器，请在所在的同一文件夹中运行docker-compose.yaml命令：（docker-compose stop或docker-compose down在所有容器停止后进行清理）。

3.使用Fabric SDK Go

3.1 配置文件

我们的应用程序需要很多参数，尤其是 Fabric 组件的地址来进行通信。我们将把所有东西都放在一个新的配置文件中，Fabric SDK Go 配置和我们的自定义参数。目前，我们只会尝试使 Fabric SDK Go 使用默认链码：

cd $GOPATH/src/github.com/chainHero/heroes-service && \
vi config.yaml

name: "heroes-service-network"
#
# Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
#
version: 1.0.0

#
# The client section used by GO SDK.
#
client:

  # Which organization does this application instance belong to? The value must be the name of an org
  # defined under "organizations"
  organization: org1

  logging:
    level: info

  # Global configuration for peer, event service and orderer timeouts
  # if this this section is omitted, then default values will be used (same values as below)
#  peer:
#    timeout:
#      connection: 10s
#      response: 180s
#      discovery:
#        # Expiry period for discovery service greylist filter
#        # The channel client will greylist peers that are found to be offline
#        # to prevent re-selecting them in subsequent retries.
#        # This interval will define how long a peer is greylisted
#        greylistExpiry: 10s
#  eventService:
#    # Event service type (optional). If not specified then the type is automatically
#    # determined from channel capabilities.
#    type: (deliver|eventhub)
    # the below timeouts are commented out to use the default values that are found in
    # "pkg/fab/endpointconfig.go"
    # the client is free to override the default values by uncommenting and resetting
    # the values as they see fit in their config file
#    timeout:
#      connection: 15s
#      registrationResponse: 15s
#  orderer:
#    timeout:
#      connection: 15s
#      response: 15s
#  global:
#    timeout:
#      query: 180s
#      execute: 180s
#      resmgmt: 180s
#    cache:
#      connectionIdle: 30s
#      eventServiceIdle: 2m
#      channelConfig: 30m
#      channelMembership: 30s
#      discovery: 10s
#      selection: 10m

  # Root of the MSP directories with keys and certs.
  cryptoconfig:
    path: ${GOPATH}/src/github.com/chainHero/heroes-service/fixtures/crypto-config

  # Some SDKs support pluggable KV stores, the properties under "credentialStore"
  # are implementation specific
  credentialStore:
    path: /tmp/heroes-service-store

    # [Optional]. Specific to the CryptoSuite implementation used by GO SDK. Software-based implementations
    # requiring a key store. PKCS#11 based implementations does not.
    cryptoStore:
      path: /tmp/heroes-service-msp

   # BCCSP config for the client. Used by GO SDK.
  BCCSP:
    security:
     enabled: true
     default:
      provider: "SW"
     hashAlgorithm: "SHA2"
     softVerify: true
     level: 256

  tlsCerts:
    # [Optional]. Use system certificate pool when connecting to peers, orderers (for negotiating TLS) Default: false
    systemCertPool: false

    # [Optional]. Client key and cert for TLS handshake with peers and orderers
    client:
      keyfile:
      certfile:

#
# [Optional]. But most apps would have this section so that channel objects can be constructed
# based on the content below. If an app is creating channels, then it likely will not need this
# section.
#
channels:
  # name of the channel
  chainhero:
    # Required. list of orderers designated by the application to use for transactions on this
    # channel. This list can be a result of access control ("org1" can only access "ordererA"), or
    # operational decisions to share loads from applications among the orderers.  The values must
    # be "names" of orgs defined under "organizations/peers"
    # deprecated: not recommended, to override any orderer configuration items, entity matchers should be used.
    # orderers:
    #  - orderer.example.com

    # Required. list of peers from participating orgs
    peers:
      peer0.org1.hf.chainhero.io:
        # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
        # have the chaincode installed. The app can also use this property to decide which peers
        # to send the chaincode install request. Default: true
        endorsingPeer: true

        # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
        # installed. The app can also use this property to decide which peers to send the
        # chaincode install request. Default: true
        chaincodeQuery: true

        # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
        # queryBlock(), queryTransaction(), etc. Default: true
        ledgerQuery: true

        # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
        # produce events but the app typically only needs to connect to one to listen to events.
        # Default: true
        eventSource: true

      peer1.org1.hf.chainhero.io:

    policies:
      #[Optional] options for retrieving channel configuration blocks
      queryChannelConfig:
        #[Optional] min number of success responses (from targets/peers)
        minResponses: 1
        #[Optional] channel config will be retrieved for these number of random targets
        maxTargets: 1
        #[Optional] retry options for query config block
        retryOpts:
          #[Optional] number of retry attempts
          attempts: 5
          #[Optional] the back off interval for the first retry attempt
          initialBackoff: 500ms
          #[Optional] the maximum back off interval for any retry attempt
          maxBackoff: 5s
          #[Optional] he factor by which the initial back off period is exponentially incremented
          backoffFactor: 2.0


#
# list of participating organizations in this network
#
organizations:
  org1:
    mspid: org1.hf.chainhero.io
    cryptoPath: peerOrganizations/org1.hf.chainhero.io/users/{userName}@org1.hf.chainhero.io/msp
    peers:
      - peer0.org1.hf.chainhero.io
      - peer1.org1.hf.chainhero.io

    # [Optional]. Certificate Authorities issue certificates for identification purposes in a Fabric based
    # network. Typically certificates provisioning is done in a separate process outside of the
    # runtime network. Fabric-CA is a special certificate authority that provides a REST APIs for
    # dynamic certificate management (enroll, revoke, re-enroll). The following section is only for
    # Fabric-CA servers.
    certificateAuthorities:
      - ca.org1.hf.chainhero.io

#
# List of orderers to send transaction and channel create/update requests to. For the time
# being only one orderer is needed. If more than one is defined, which one get used by the
# SDK is implementation specific. Consult each SDK's documentation for its handling of orderers.
#
orderers:
  orderer.hf.chainhero.io:
    url: localhost:7050

    # these are standard properties defined by the gRPC library
    # they will be passed in as-is to gRPC client constructor
    grpcOptions:
      ssl-target-name-override: orderer.hf.chainhero.io
      # These parameters should be set in coordination with the keepalive policy on the server,
      # as incompatible settings can result in closing of connection.
      # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
      keep-alive-time: 0s
      keep-alive-timeout: 20s
      keep-alive-permit: false
      fail-fast: false
      # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
      allow-insecure: false

    tlsCACerts:
      # Certificate location absolute path
      path: ${GOPATH}/src/github.com/chainHero/heroes-service/fixtures/crypto-config/ordererOrganizations/hf.chainhero.io/tlsca/tlsca.hf.chainhero.io-cert.pem
#
# List of peers to send various requests to, including endorsement, query
# and event listener registration.
#
peers:
  peer0.org1.hf.chainhero.io:
    # this URL is used to send endorsement and query requests
    url: localhost:7051
    # eventUrl is only needed when using eventhub (default is delivery service)
    eventUrl: localhost:7053

    grpcOptions:
      ssl-target-name-override: peer0.org1.hf.chainhero.io
      # These parameters should be set in coordination with the keepalive policy on the server,
      # as incompatible settings can result in closing of connection.
      # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
      keep-alive-time: 0s
      keep-alive-timeout: 20s
      keep-alive-permit: false
      fail-fast: false
      # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
      allow-insecure: false

    tlsCACerts:
      # Certificate location absolute path
      path: ${GOPATH}/src/github.com/chainHero/heroes-service/fixtures/crypto-config/peerOrganizations/org1.hf.chainhero.io/tlsca/tlsca.org1.hf.chainhero.io-cert.pem

  peer1.org1.hf.chainhero.io:
    # this URL is used to send endorsement and query requests
    url: localhost:8051
    # eventUrl is only needed when using eventhub (default is delivery service)
    eventUrl: localhost:8053

    grpcOptions:
      ssl-target-name-override: peer1.org1.hf.chainhero.io
      # These parameters should be set in coordination with the keepalive policy on the server,
      # as incompatible settings can result in closing of connection.
      # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
      keep-alive-time: 0s
      keep-alive-timeout: 20s
      keep-alive-permit: false
      fail-fast: false
      # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
      allow-insecure: false

    tlsCACerts:
      # Certificate location absolute path
      path: ${GOPATH}/src/github.com/chainHero/heroes-service/fixtures/crypto-config/peerOrganizations/org1.hf.chainhero.io/tlsca/tlsca.org1.hf.chainhero.io-cert.pem

#
# Fabric-CA is a special kind of Certificate Authority provided by Hyperledger Fabric which allows
# certificate management to be done via REST APIs. Application may choose to use a standard
# Certificate Authority instead of Fabric-CA, in which case this section would not be specified.
#
certificateAuthorities:
  ca.org1.hf.chainhero.io:
    url: http://localhost:7054
    # Fabric-CA supports dynamic user enrollment via REST APIs. A "root" user, a.k.a registrar, is
    # needed to enroll and invoke new users.
    httpOptions:
      verify: false
    registrar:
      enrollId: admin
      enrollSecret: adminpw
    # [Optional] The optional name of the CA.
    caName: ca.org1.hf.chainhero.io
    tlsCACerts:
      # Certificate location absolute path
      path: ${GOPATH}/src/github.com/chainHero/heroes-service/fixtures/crypto-config/peerOrganizations/org1.hf.chainhero.io/ca/ca.org1.hf.chainhero.io-cert.pem

entityMatchers:
  peer:
    - pattern: (\w*)peer0.org1.hf.chainhero.io(\w*)
      urlSubstitutionExp: localhost:7051
      eventUrlSubstitutionExp: localhost:7053
      sslTargetOverrideUrlSubstitutionExp: peer0.org1.hf.chainhero.io
      mappedHost: peer0.org1.hf.chainhero.io

    - pattern: (\w*)peer1.org1.hf.chainhero.io(\w*)
      urlSubstitutionExp: localhost:8051
      eventUrlSubstitutionExp: localhost:8053
      sslTargetOverrideUrlSubstitutionExp: peer1.org1.hf.chainhero.io
      mappedHost: peer1.org1.hf.chainhero.io

  orderer:
    - pattern: (\w*)orderer.hf.chainhero.io(\w*)
      urlSubstitutionExp: localhost:7050
      sslTargetOverrideUrlSubstitutionExp: orderer.hf.chainhero.io
      mappedHost: orderer.hf.chainhero.io

  certificateAuthorities:
    - pattern: (\w*)ca.org1.hf.chainhero.io(\w*)
      urlSubstitutionExp: http://localhost:7054
      mappedHost: ca.org1.hf.chainhero.io

配置文件也可以在这里找到： config.yaml

3.2初始化

我们添加一个名为的新文件夹blockchain，该文件夹将包含与网络通信的整个接口。我们将仅在此文件夹中看到 Fabric SDK Go。

mkdir $GOPATH/src/github.com/chainHero/heroes-service/blockchain

现在，我们添加一个名为的新 go 文件setup.go：

vi $GOPATH/src/github.com/chainHero/heroes-service/blockchain/setup.go

package blockchain

import (
	"fmt"
	mspclient "github.com/hyperledger/fabric-sdk-go/pkg/client/msp"
	"github.com/hyperledger/fabric-sdk-go/pkg/client/resmgmt"
	"github.com/hyperledger/fabric-sdk-go/pkg/common/errors/retry"
	"github.com/hyperledger/fabric-sdk-go/pkg/common/providers/msp"
	"github.com/hyperledger/fabric-sdk-go/pkg/core/config"
	"github.com/hyperledger/fabric-sdk-go/pkg/fabsdk"
	"github.com/pkg/errors"
)

// FabricSetup implementation
type FabricSetup struct {
	ConfigFile      string
	OrgID           string
	OrdererID	string
	ChannelID       string
	ChainCodeID     string
	initialized     bool
	ChannelConfig   string
	ChaincodeGoPath string
	ChaincodePath   string
	OrgAdmin        string
	OrgName         string
	UserName        string
	admin           *resmgmt.Client
	sdk             *fabsdk.FabricSDK
}

// Initialize reads the configuration file and sets up the client, chain and event hub
func (setup *FabricSetup) Initialize() error {

	// Add parameters for the initialization
	if setup.initialized {
		return errors.New("sdk already initialized")
	}

	// Initialize the SDK with the configuration file
	sdk, err := fabsdk.New(config.FromFile(setup.ConfigFile))
	if err != nil {
		return errors.WithMessage(err, "failed to create SDK")
	}
	setup.sdk = sdk
	fmt.Println("SDK created")

	// The resource management client is responsible for managing channels (create/update channel)
	resourceManagerClientContext := setup.sdk.Context(fabsdk.WithUser(setup.OrgAdmin), fabsdk.WithOrg(setup.OrgName))
	if err != nil {
		return errors.WithMessage(err, "failed to load Admin identity")
	}
	resMgmtClient, err := resmgmt.New(resourceManagerClientContext)
	if err != nil {
		return errors.WithMessage(err, "failed to create channel management client from Admin identity")
	}
	setup.admin = resMgmtClient
	fmt.Println("Ressource management client created")

	// The MSP client allow us to retrieve user information from their identity, like its signing identity which we will need to save the channel
	mspClient, err := mspclient.New(sdk.Context(), mspclient.WithOrg(setup.OrgName))
	if err != nil {
		return errors.WithMessage(err, "failed to create MSP client")
	}
	adminIdentity, err := mspClient.GetSigningIdentity(setup.OrgAdmin)
	if err != nil {
		return errors.WithMessage(err, "failed to get admin signing identity")
	}
	req := resmgmt.SaveChannelRequest{ChannelID: setup.ChannelID, ChannelConfigPath: setup.ChannelConfig, SigningIdentities: []msp.SigningIdentity{adminIdentity}}
	txID, err := setup.admin.SaveChannel(req, resmgmt.WithOrdererEndpoint(setup.OrdererID))
	if err != nil || txID.TransactionID == "" {
		return errors.WithMessage(err, "failed to save channel")
	}
	fmt.Println("Channel created")

	// Make admin user join the previously created channel
	if err = setup.admin.JoinChannel(setup.ChannelID, resmgmt.WithRetry(retry.DefaultResMgmtOpts), resmgmt.WithOrdererEndpoint(setup.OrdererID)); err != nil {
		return errors.WithMessage(err, "failed to make admin join channel")
	}
	fmt.Println("Channel joined")

	fmt.Println("Initialization Successful")
	setup.initialized = true
	return nil
}

func (setup *FabricSetup) CloseSDK() {
	setup.sdk.Close()
}

该文件可在此处获得： blockchain/setup.go
在这个阶段，只初始化了一个将与对等方、CA 和排序者通信的客户端。还创建了一个新频道并将这个对等点连接到这个频道。有关更多信息，请参阅代码中的注释。

3.3测试

为了确保客户端成功初始化了他的所有组件，我们将在启动网络的情况下进行一个简单的测试。为了做到这一点，我们需要构建 go 代码。由于我们没有任何主文件，我们必须添加一个：

cd $GOPATH/src/github.com/chainHero/heroes-service && \
vi main.go

package main

import (
	"fmt"
	"github.com/chainHero/heroes-service/blockchain"
	"os"
)

func main() {
	// Definition of the Fabric SDK properties
	fSetup := blockchain.FabricSetup{
		// Network parameters 
		OrdererID: "orderer.hf.chainhero.io",

		// Channel parameters
		ChannelID:     "chainhero",
		ChannelConfig: os.Getenv("GOPATH") + "/src/github.com/chainHero/heroes-service/fixtures/artifacts/chainhero.channel.tx",

		// Chaincode parameters
		ChainCodeID:     "heroes-service",
		ChaincodeGoPath: os.Getenv("GOPATH"),
		ChaincodePath:   "github.com/chainHero/heroes-service/chaincode/",
		OrgAdmin:        "Admin",
		OrgName:         "org1",
		ConfigFile:      "config.yaml",

		// User parameters
		UserName: "User1",
	}

	// Initialization of the Fabric SDK from the previously set properties
	err := fSetup.Initialize()
	if err != nil {
		fmt.Printf("Unable to initialize the Fabric SDK: %v\n", err)
		return
	}
	// Close SDK
	defer fSetup.CloseSDK()	
}

该文件可在此处获得： main.go

使用如下命令确保安装依赖

go mod init

go mod vendor

待依赖下载完成后，即可开始编译

cd $GOPATH/src/github.com/chainHero/heroes-service && \
go build

编译完成后会生成一个可执行的文件
在这里插入图片描述

输入命令

./heroes-service

此时就可看到
在这里插入图片描述

Demonwuwen
关注
  • 0
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
专栏目录
Fabric Sdk Go(五)
笔记|思路|总结
01-08 431
Fabric Sdk Go(五)
Hyperledger fabric2.4 fabric-SDK-GO开发
qq_28052455的博客
09-12 4322
在实际部署时，一般将Fabric SDK作为API到提供者，为上层应用或对外服务提供Fabric区块链网络底层服务。Fabric SDK本质是一个Fabric基础对象，功能的封装集合和客户端框架实现，旨在方便开发人员快速开发出符合产品业务需求的服务模块。获取 Fabric 和 Fabric CA 的客户端 SDK 包，SDK 文档可以在下面使用sdk实现创建通道，加入通道，打包链码，安装链码，升级链码等功能。
Fabric-SDK-Go
星回昭以烂的博客
06-30 4487
Fabric-SDK-Go 1.配置Fabric-SDK 1）创建config.yaml 确认 Hyperledger Fabric 基础网络环境运行没有问题后，现在我们通过创建一个新的 config.yaml 配置文件给应用程序所使用的 Fabric-SDK-Go 配置相关参数及 Fabric 组件的通信地址 进入项目的根目录中创建一个 config.yaml 文件并编辑 2）定义所需结构体 配置文件完成指定的配置信息之后，我们开始编写代码。 在项目的根目录下添加一个名为 sdkInit 的新目录，我们将
【Fabric】教程之使用GO-SDK(一）
Moooonk的博客
09-02 3247
整个目录可以分为三个部分，即fabric相关，app相关；其中app分为server后端和web前端。故创建如下文件夹：fixture、app/server和app/web。
HyperLeger Fabric SDK-go开发使用
乐观的阿锡的博客
06-18 1266
git branch -a　　 // 查看分支，不出意外的话，此时分支应该处于 release-1.4 git checkout release-1.4 // 切换到 release-1.3 版本 git branch -v git checkout release-1.4 报错过程： 进入fabric-samples 目录中的first-networkd子目录后，在使用“./byfn.sh —help”时报错： error getting endo
fabric-sdk-py:Hyperledger Fabric Python SDK
05-04
面料-SDK-Py Fabric-SDK-Py是Hyperledger Fabric SDK的Python 3.x实现！ 当前，它主要支持Fabric 1.4.x版本。前提条件该SDK需要Python3和Libssl pkgs。 如果没有，请运行以下cmd来安装必备组件： 作业系统命令Ubuntu...
fabric-java-sdk-demo.zip
09-02
《基于Fabric-Java-SDK的区块链应用实践》 在当今的数字时代，区块链技术作为一种分布式账本技术，正逐渐渗透到各个行业中。Hyperledger Fabric，作为Linux基金会主导的开源项目，是企业级区块链解决方案的重要代表...
fabric-sdk-go与GIN框架应用.pdf
03-23
fabric-sdk-go与GIN框架应用
fabric-sdk-java+ springBoot 简单invoke和query引用示例
03-11
这是一个基于spingBoot的项目,通过此项目可以实现对fabric网络的简单调用,并且可以启动一个fabric网路的服务,直接在网页上调用. 搭建流程,首先需要fabric1.4的网络， 1进入-first-network目录，修改byfn.sh中...
fabric-sdk-go.zip
04-02
go客户端
hyperledger Fabric 2.3版本使用Go SDK搭建区块浏览器
Rightstar的博客
07-24 9793
前言 作者:Rightstar 微信:Rightstar_ CSDN:https://blog.csdn.net/qq_33886316 掘金:https://juejin.cn/user/2375425082269832 最近使用fabric 的Go SDK搭建了个Go服务器,完整项目还包括链代码的调用以及相关连接配置文件,这里只给出区块链浏览器相关的构建代码。由于百度博客找的资料太少或者又是不全,分享下希望对大家有帮助。 效果图(Vue前端) 部分数据简单地模拟了下 主要功能包括可以查询最新的区块以
Hyperledger Fabric Rest API服务开发教程【含源码】
周红伟讲AI
01-29 2868
Hyperledger Fabric Rest API服务开发教程【含源码】 Hyperledger Fabric 提供了软件开发包/SDK以帮助开发者访问fabric网络 和部署在网络上的链码，但是Hyperledger Fabric官方没有提供简单易用的REST API访问接口，在这个教程里我们将学习如何利用Hyperledger Fabric的SDK 来开发REST API服务器。 ...
基于 Fabric-SDK-Go 的Web项目实战之使用Fabric-SDK-Go满足依赖
weixin_43970764的博客
01-18 3417
  作者：ChainDesk韩小东 目标 1.根据项目要求满足所需依赖 2.使用Makefiel简化项目测试 任务实现 11.2.1 安装dep工具 在运行应用程序之前，需要将 Go 源代码时行编译，但在开始编译之前，我们需要使用一个 vendor 目录来包含应用中所需的所有的依赖关系。 在我们的GOPATH中，我们有Fabric SDK Go和其他项目。 在尝试编译应用程序时，...
【区块链Fabric CA】Fabric Ca环境配置及解决go环境的坑
大帅Douk的博客
01-24 2640
参考区块链 原理、设计与应用这本书进行配置环境，但是完全按照书上进行配置，环境会报错。 本人参考此书，记录Fabric Ca 环境搭建过程 前提：已安装docker环境配置  安装Docker  Fabric网络目前依赖 Docker服务作为链码容器的支持,因此即使是本地环境运行Fabric网络,也需要在Peer节点上安装 Docker环境。推荐使用1.12或者更新的版本。  Li
使用Fabric Node SDK进行Invoke和Query
weixin_33709219的博客
09-15 526
前面的文章都是在讲解Fabric网络的搭建和ChainCode的开发，那么在ChainCode开发完毕后，我们就需要使用Fabric SDK做应用程序的开发了。官方虽然提供了Node.JS，Java，Go，Python等多种语言的SDK，但是由于整个Fabric太新了，很多SDK还不成熟和完善，所以我采用Node JS的SDK，毕竟这个是功能毕竟齐全，而且也是官方示例的时候使用的SDK。由于我从来...
Hyperledger Fabric Client SDK for Go 下载与配置
lilihli的专栏
12-26 3304
在下载之前需要确保你的系统安装了以下项目: Go 1.9DepMakeDockerDocker ComposeGit Fabric Client SDK 使用了go dep 作为版本管理工具，使用下面的命令 go get -u github.com/hyperledger/fabric-sdk-go 下载后，使用 dep ensure -update 更新第三方依赖包，结束后运行 ma
从零到壹构建基于 Fabric-SDK-Go 的Web应用之二：使用 Fabric-SDK-Go
hanxiaodong
03-05 8771
Hyperledger Fabric 提供了许多 SDK 来支持各种不同的编程语言，但是因为 Hyperledger Fabric 是使用 Golang 构建的，所以我们将使用 Go 语言来设计我们的应用程序，包括链码（智能合约）。如果您想使用其它 SDK，如 Fabric-SDK-Java，Fabric-SDK-Node等等，这些都可以通过在线文档进行学习，我们不在这里讨论。 1. 配置Fabr...
1个Fabric-sdk-go案例-访问yaml配置并创建SDK实例
qq_18807043的博客
05-14 1146
Fabric-sdk-go案例准备工作创建案例目录编写案例源程序demo1.go运行结果 准备工作 创建案例目录 config_e2e.yaml是fabric-sdk-go本身提供的一个配置文件，搜索得到，复制到案例目录。 编写案例源程序demo1.go 第18行，从当前目录读配置文件，即config_e2e.yaml 第19行，configOpt是1个函数，调用它得到1个切片backend 第20行，在切片backend中查询version，也就是config_e2e.yaml里的version 第
安装Hyperledger的Fabric的遇到的go语言坑
龙哥的世界
10-23 5325
我在使用ununtu 20 来测试区块链的超级账本Hyperledger的fabric的时候，安装fabric-samples的时候，在输入./network.sh deployCC 安装合约的时候 碰到的错误 github.com/golang/protobuf@v1.3.2: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt 百度说应该是go mod 模块相关，GO111M.
fabric-sdk-go + gin
最新发布
04-28
fabric-sdk-go和gin是两个不同的开源项目。 fabric-sdk-go是Hyperledger Fabric的一个官方SDK，它提供了一系列的API和工具，用于方便地与Fabric网络进行交互。它是基于Golang开发，具有高效、稳定和可扩展性强等...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值