In this section, we will evolve the network further to realize requirement #2. Requirement #2 wants the producer organization O1 to execute private transactions and communications with O3 (retail organization 3), as they have agreed on certain private discount rates and payments terms.

Administrators from the founder organization (O5) define a new consortium between the producer organization (O1) and a second retail organization (O3). Consortium definitions are defined in the network configuration (NC05). One of the organizations (O1 or O5) can define a new channel (C2) for the new consortium (X2). Channel (C2) configuration resides in the channel configuration (CCon2). You may observe that the channel configuration for C2 resides in CCon2, and is separate from Channel-C1's configuration (CCon1). Both channel configurations are separate from the network configuration (NC05). Hence, only O1 and O3 have rights over C2, and O5 has no rights over Channel-C2. O5 only offers a resource (orderer service – Ord O5) to channel (C2).

The organization (O3) adds a peer (P3) to the channel (C2) and has a different ledger (L2). The scope of the ledger is confined to the channel, hence, Channel-C1 has ledger L1, and Channel-C2 has ledger L2. Chaincode SC2 is installed and initiated on Channel-C2, and organization O3's application (O3App3) uses Channel-C2 to invoke transactions against chaincode SC2.