Designing and configuring a Hyperledger Fabric trade network
As you already know by now, an instance of a Hyperledger Fabric blockchain is referred to as a channel, which is a log of transactions linked to each other sequentially in a cryptographically secure manner. To design and run a blockchain application, the first step is to determine how many channels are required. For our trade application, we will use two channels, which will maintain the history of trades carried out among the different participants along with associated artifacts like letters of credit, export licenses, bills of lading, bank accounts, and shipment records.
A Fabric peer may belong to multiple channels, which maintain independent and isolated sequences of transactions and resulting datasets. A single peer may thus access ledger data from, and run transactions in, different applications (or contracts) on behalf of its owners (or clients). A channel can run multiple smart contracts, each of which...
