Common use of Agreement Protocol Clause in Contracts

Agreement Protocol. First we describe how PBFT achieves agreement on a unique order of requests within a single view. Figure 26.9 shows how the nodes come to an agreement on a sequence number for a client request. Informally, the protocol has these five steps: 1. The nodes receive a request and relay it to the primary. 2. The primary sends a pre-prepare-message to all backups, informing them that it wants to execute that request with the sequence number specified in the message. 3. Backups send prepare-messages to all nodes, informing them that they agree with that suggestion. 4. All nodes send commit-messages to all nodes, informing everyone that they have committed to execute the request with that sequence number. 5. They execute the request and inform the client.

Appears in 2 contracts

Sources: Byzantine Agreement With Authentication, Authenticated Agreement

Agreement Protocol. First we describe how PBFT achieves agreement on a unique order of requests within a single view. Figure 26.9 25.9 shows how the nodes come to an agreement on a sequence number for a client request. Informally, the protocol has these five steps: 1. The nodes receive a request and relay it to the primary. 2. The primary sends a pre-prepare-message to all backups, informing them that it wants to execute that request with the sequence number specified in the message. 3. Backups send prepare-messages to all nodes, informing them that they agree with that suggestion. 4. All nodes send commit-messages to all nodes, informing everyone that they have committed to execute the request with that sequence number. 5. They execute the request and inform the client.

Appears in 2 contracts

Sources: Byzantine Agreement With Authentication, Authenticated Agreement