Please enable JavaScript.
Coggle requires JavaScript to display documents.
Local Association, Hyperledger Framework - Coggle Diagram
-
Hyperledger Framework
configtx.yaml contains all of the information related to the configuration of the network structure.
configtx.yaml file is used for all your channel configuration needs. This file is used in conjunction with the configtxlator tool
Organizations section is where we add and define the organizations who want to participate on the network.Every organization must define values according to each key in the following list
- Name
- MSP ID and Path
- Policies (optional)
- Anchor peer, which declares the list of peers an organization will expose to support the cross-organization gossip protocol
Orderer add & define specific configuration details for orderers that will run on the network.
- MUST provide a list of domain addresses (and their endpoints).
- Need to choose between either Solo or Kafka, by specifying the ordererType
- Can specify within configtx.yaml parameters such as maximum block size or the maximum time to wait before cutting a block.
Application of configtx is where we define our ACL, policies, and capabilities.
We can then allow our channels to reference these application level descriptions to create custom, application-specific configurations for their channels.
Profiles section of configtx define the details of either the network or the channel we want to create on the network and is used to create the network artifacts
crypto-config is used for development purposes only. It contains all of the crypto-certificates related to (MSPs) and (CAs) of organizations. It is also useful for quick templating of certificates' generation in development environments.
To turn a user into an administrator, we can simply add its public certificate to the admincerts section of the MSP folder, and it will be recognized as such.
-
-
-
docker-compose file is creates container definitions, and also provides easy source for deploying a network in one command.
docker-compose is a great tool for creating multiple containers in an environment that is deployed on a single host, but not so much for a multiple-host, multiple-organization, decentralized network (due to admin-only related governance roadblocks).
These container definitions handle
- Port configuration
- Establishment of dependencies
- Environment variables (in regard to the specified component)
- Pathing for crypto-certificates
- Database establishment and its configuration
- Volumes and mapping.
-
-
Network artifacts we are referring to the initial configuration-related files that we generate at the start of a network. configuration .tx files (e.g., ChannelName.tx), the Genesis block, and the anchor peer transactions.
crypto-config.yaml allows to define templated information that structures how we can generate proper x509 certificates for all identifiable nodes across the network (orderers, orgs, peers, CA, etc.), mostly at the organization level.
crypto-config.yaml is dependent on cryptogen for certificate generation. The output result of combining cryptogen with crypto-config.yaml is the crypto-config folder.