mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
6007c0974c
Updated chaincode, BYFN, and all other references to example02 to use the new name ABstore. Change-Id: I04c177f9de68eb913f4384fd643aa69631143d58 Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
225 lines
9.3 KiB
YAML
225 lines
9.3 KiB
YAML
---
|
|
#
|
|
# The network connection profile provides client applications the information about the target
|
|
# blockchain network that are necessary for the applications to interact with it. These are all
|
|
# knowledge that must be acquired from out-of-band sources. This file provides such a source.
|
|
#
|
|
name: "finance-networks"
|
|
|
|
#
|
|
# Any properties with an "x-" prefix will be treated as application-specific, exactly like how naming
|
|
# in HTTP headers or swagger properties work. The SDK will simply ignore these fields and leave
|
|
# them for the applications to process. This is a mechanism for different components of an application
|
|
# to exchange information that are not part of the standard schema described below. In particular,
|
|
# the "x-type" property with the "hlfv1" value example below is used by Hyperledger Composer to
|
|
# determine the type of Fabric networks (v0.6 vs. v1.0) it needs to work with.
|
|
#
|
|
x-type: "hlfv1"
|
|
|
|
#
|
|
# Describe what the target network is/does.
|
|
#
|
|
description: "A gateway connection file for the PaperNet networks"
|
|
|
|
#
|
|
# Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
|
|
#
|
|
version: "1.0"
|
|
|
|
#
|
|
# The client section is SDK-specific. The sample below is for the node.js SDK
|
|
#
|
|
#client:
|
|
# Which organization does this application instance belong to? The value must be the name of an org
|
|
# defined under "organizations"
|
|
#organization: Org1
|
|
|
|
# Some SDKs support pluggable KV stores, the properties under "credentialStore"
|
|
# are implementation specific
|
|
#credentialStore:
|
|
# [Optional]. Specific to FileKeyValueStore.js or similar implementations in other SDKs. Can be others
|
|
# if using an alternative impl. For instance, CouchDBKeyValueStore.js would require an object
|
|
# here for properties like url, db name, etc.
|
|
#path: "/tmp/hfc-kvs"
|
|
|
|
# [Optional]. Specific to the CryptoSuite implementation. Software-based implementations like
|
|
# CryptoSuite_ECDSA_AES.js in node SDK requires a key store. PKCS#11 based implementations does
|
|
# not.
|
|
#cryptoStore:
|
|
# Specific to the underlying KeyValueStore that backs the crypto key store.
|
|
#path: "/tmp/hfc-cvs"
|
|
|
|
# [Optional]. Specific to Composer environment
|
|
#wallet: wallet-name
|
|
|
|
#
|
|
# [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
|
|
papernet:
|
|
# 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"
|
|
orderers:
|
|
- orderer.magnetocorp.com
|
|
|
|
# Required. list of peers from participating orgs
|
|
peers:
|
|
peer1.magnetocorp.com:
|
|
# [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
|
|
|
|
peer2.digibank.com:
|
|
endorsingPeer: true
|
|
chaincodeQuery: false
|
|
ledgerQuery: true
|
|
eventSource: true
|
|
|
|
# [Optional]. what chaincodes are expected to exist on this channel? The application can use
|
|
# this information to validate that the target peers are in the expected state by comparing
|
|
# this list with the query results of getInstalledChaincodes() and getInstantiatedChaincodes()
|
|
chaincodes:
|
|
# the format follows the "cannonical name" of chaincodes by fabric code
|
|
- abstore:v1
|
|
- marbles:1.0
|
|
|
|
#
|
|
# list of participating organizations in this network
|
|
#
|
|
organizations:
|
|
Org1:
|
|
mspid: magnetocorpMSP
|
|
|
|
peers:
|
|
- peer1.magnetocorp.com
|
|
|
|
# [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-magnetocorp
|
|
|
|
# [Optional]. If the application is going to make requests that are reserved to organization
|
|
# administrators, including creating/updating channels, installing/instantiating chaincodes, it
|
|
# must have access to the admin identity represented by the private key and signing certificate.
|
|
# Both properties can be the PEM string or local path to the PEM file. Note that this is mainly for
|
|
# convenience in development mode, production systems should not expose sensitive information
|
|
# this way. The SDK should allow applications to set the org admin identity via APIs, and only use
|
|
# this route as an alternative when it exists.
|
|
adminPrivateKey:
|
|
path: commercial-paper/organization/magnetocorp/users/Admin@magnetocorp/keystore/9022d671ceedbb24af3ea69b5a8136cc64203df6b9920e26f48123fcfcb1d2e9_sk
|
|
signedCert:
|
|
path: comercial-paper/organization/magnetocorp/users/Admin@magnetocorp.com/signcerts/Admin@magnetocorp.com-cert.pem
|
|
|
|
# the profile will contain public information about organizations other than the one it belongs to.
|
|
# These are necessary information to make transaction lifecycles work, including MSP IDs and
|
|
# peers with a public URL to send transaction proposals. The file will not contain private
|
|
# information reserved for members of the organization, such as admin key and certificate,
|
|
# fabric-ca registrar enroll ID and secret, etc.
|
|
Org2:
|
|
mspid: digibankMSP
|
|
peers:
|
|
- peer1.digibank.com
|
|
certificateAuthorities:
|
|
- ca-digibank
|
|
adminPrivateKey:
|
|
path: commercial-paper/organization/digibank/users/Admin@digibank.com/keystore/5a983ddcbefe52a7f9b8ee5b85a590c3e3a43c4ccd70c7795bec504e7f74848d_sk
|
|
signedCert:
|
|
path: commercial-paper/organization/digibank/users/Admin@digibank.com/signcerts/Admin@digibank.com-cert.pem
|
|
|
|
#
|
|
# 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.magnetocorp.com:
|
|
url: grpcs://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.example.com
|
|
|
|
tlsCACerts:
|
|
path: comercial-paper/organization/magnetocorp/orderer/orderer.magnetocorp.com/tlscacerts/example.com-cert.pem
|
|
|
|
#
|
|
# List of peers to send various requests to, including endorsement, query
|
|
# and event listener registration.
|
|
#
|
|
peers:
|
|
peer1.magnetocorp.com:
|
|
# this URL is used to send endorsement and query requests
|
|
url: grpcs://localhost:7051
|
|
|
|
grpcOptions:
|
|
ssl-target-name-override: peer1.magnetocorp.com
|
|
request-timeout: 120
|
|
|
|
tlsCACerts:
|
|
path: certificates/magnetocorp/magnetocorp.com-cert.pem
|
|
|
|
peer1.digibank.com:
|
|
url: grpcs://localhost:8051
|
|
grpcOptions:
|
|
ssl-target-name-override: peer1.digibank.com
|
|
tlsCACerts:
|
|
path: certificates/digibank/digibank.com-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:
|
|
url: https://localhost:7054
|
|
# the properties specified under this object are passed to the 'http' client verbatim when
|
|
# making the request to the Fabric-CA server
|
|
httpOptions:
|
|
verify: false
|
|
tlsCACerts:
|
|
path: commercial-paper/organization/magnetocorp/ca/magnetocorp.com-cert.pem
|
|
|
|
# Fabric-CA supports dynamic user enrollment via REST APIs. A "root" user, a.k.a registrar, is
|
|
# needed to enroll and invoke new users.
|
|
registrar:
|
|
- enrollId: admin
|
|
enrollSecret: adminpw
|
|
# [Optional] The optional name of the CA.
|
|
caName: ca-magnetocorp
|
|
|
|
ca-org2:
|
|
url: https://localhost:8054
|
|
httpOptions:
|
|
verify: false
|
|
tlsCACerts:
|
|
path: commercial-paper/organization/digibank/ca/digibank.com-cert.pem
|
|
registrar:
|
|
- enrollId: admin
|
|
enrollSecret: adminpw
|
|
# [Optional] The optional name of the CA.
|
|
caName: ca-digibank
|