implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers major types of peer; there are two other roles a peer can adopt: Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes responsibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers types of peer; there are two other roles a peer can adopt: • Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes respon- sibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers major types of peer; there are two other roles a peer can adopt: Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes responsibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers types of peer; there are two other roles a peer can adopt: • Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes respon- sibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers types of peer; there are two other roles a peer can adopt: • Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes respon- sibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers major types of peer; there are two other roles a peer can adopt: Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes responsibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers major types of peer; there are two other roles a peer can adopt: Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes responsibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers types of peer; there are two other roles a peer can adopt: • Leader peer. When an organization has multiple peers in a channel, a leader peer is a node which takes respon- sibility for distributing transactions have static leader selection, and those with dynamic leader selection. For the static set, zero or more peers can be configured as leaders. For the dynamic set, one peer will be elected leader by the set

you wish to inspect its contents. Configuring Leader Election Note This section is included as a general reference for understanding the leader election settings when adding organizations to a network network after the initial channel configuration has completed. This sample defaults to dynamic leader election, which is set for all peers in the network in peer-base.yaml. Newly joining peers are bootstrapped that they receive blocks from the ordering service: 1. To utilize static leader mode, configure the peer to be an organization leader: CORE_PEER_GOSSIP_USELEADERELECTION=false CORE_PEER_GOSSIP_ORGLEADER=true

wish to inspect its contents. 3.3.10 Configuring Leader Election Note: This section is included as a general reference for understanding the leader election settings when adding organizations to a network network after the initial channel configuration has completed. This sample defaults to dynamic leader election, which is set for all peers in the network in peer-base.yaml. Newly joining peers are bootstrapped that they receive blocks from the ordering service: 1. To utilize static leader mode, configure the peer to be an organization leader: CORE_PEER_GOSSIP_USELEADERELECTION=false CORE_PEER_GOSSIP_ORGLEADER=true