The crypto-config.yaml file contains information only about the new organization, sufficient to generate certificates and signing keys:

PeerOrgs: 
  # ExportingEntityOrg 
  - Name: ExportingEntityOrg 
    Domain: exportingentityorg.trade.com 
    EnableNodeOUs: true 
    Template: 
      Count: 1 
    Users: 
     Count: 1 

As we can see, the specification is identical to the ones we defined for our initial four organizations, except that the MSP name and organization domain reflect the nature of the exporting entity organization. To generate the crypto material just for this organization, run the cryptogen command as in Chapter 5, Exposing Network Assets and Transactions, but this time using the configuration file defined in the add_orgs folder:

cryptogen generate --config=./add_org/crypto-config.yaml 

The output is saved to crypto-config/peerOrganizations, where you will see a folder named exportingentityorg.trade.com in addition to the existing organization's folders. This folder contains the keys and certificates for our new organization.