Wallets and identity

We've already seen how identity is central to multi-party transactions; the transaction input is signed by the transaction proposer, and the transaction responses are signed by the endorsing organizations. Moreover, we're going to see how a user's identity associates them with a role in their organization, which in turn determines how they can access resources in the network.

Using an identity

Because of the central role that identity plays in a Hyperledger Fabric network, it makes sense that the first thing an application must do is select an identity to use. Let's look at an example:

Figure 7.7: A wallet stores a user's identity for interaction with the network

In Figure 7.7, we can see how organizations A, B, and C use a channel to form a blockchain network. Organization A owns a set of infrastructure components for use in this network channel, namely Peers 1, 2, and 3 and a certificate authority CA1. Similarly...