What is the crypto-config.yaml Configuration File used in BYFN (Build Your First Network)?

The crypto-config.yaml Configuration File provides settings on how to generate private keys and public certificates for network entities: order and peer organizations.

Here is the default copy of crypto-config.yaml provided in BYFN:

# Copyright IBM Corp. All Rights Reserved.

# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
  - Name: Orderer
    Domain: example.com
    Specs:
      - Hostname: orderer

# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
  # ---------------------------------------------------------------------------
  # Org1
  # ---------------------------------------------------------------------------
  - Name: Org1
    Domain: org1.example.com
    EnableNodeOUs: true
    Template:
      Count: 2
    Users:
      Count: 1
  # ---------------------------------------------------------------------------
  # Org2: See "Org1" for full specification
  # ---------------------------------------------------------------------------
  - Name: Org2
    Domain: org2.example.com
    EnableNodeOUs: true
    Template:
      Count: 2
    Users:
      Count: 1

As you can see, the crypto-config.yaml file defines 1 orderer organization: orderer.example.com, and 2 peer organizations: org1.example.com and org2.example.com. Each organization has 2 peers with template names of peer0.* and peer1.*, plus 1 user. By default, each peer organization will an admin user, Admin@org1.example.com.

⇒ "cryptogen" Command - Generate Keys and Certificates

⇐ Build the BYFN Network Manually

⇑ Hyperledger Fabric Sample Networks

⇑⇑ Hyperledger Tutorials