# Block Validation

#### Block Commitment Verification Process

In this process, each follower is synchronized with the encrypted transactions and their respective order commitments. This synchronization allows each member of the cluster to build the block similarly to the leader. The following steps outline the block commitment verification process:

#### Block Commitment Verification Process Documentation

Since each follower is synchronized with leader's encrypted transactions and respective order commitments, this enables them to build the block similarly to the leader. The following steps outline the block commitment verification process:

<figure><img src="/files/3bmgls7o9ecACCKjieoM" alt=""><figcaption><p>Block Validation Flow</p></figcaption></figure>

1. **Initiating the Build**:
   * Upon receiving the build block request, the leader initiates the build function.
   * The leader propagates the close message to all followers, prompting them to close their blocks and begin building.
2. **Submitting Block to Rollup Operator**:
   * The rollup operator requests a block from the leader.
   * The leader submits the block to the rollup operator.
3. **Generating Block Commitments**:
   * The leader and followers generate a block commitment based on the encrypted transactions and order commitments.
   * This process occurs in parallel across all members of the cluster.
4. **Submitting Block Commitment by Leader**:
   * The leader creates a task and submits its block commitment to ValidationServiceManager contract, triggering an event that followers listen to.
5. **Submitting Block Commitment by Followers**:
   * The followers submit their block commitments as a respond to the same task.
6. **Commitment Validation**:
   * ValidationServiceManager contract aggregates commitments from all members of the cluster.
   * It validates the commitments by comparing them with the leader's block commitment through a smart contract.
   * Rewards are determined based on the validation results.

This process ensures that block commitments are accurately validated.

**Validation Scenarios**

* **Scenario 1: Majority Coincidence**
  * If the majority of the followers' commitments coincide with the leader's commitment, the leader's commitment is considered valid.
  * The leader is rewarded.
* **Scenario 2: Majority Discrepancy**
  * If the majority of the followers' commitments do not coincide with the leader's commitment, the leader's commitment is considered invalid.
  * The leader is not rewarded.

**Assumptions**

* There is no slashing of the tx. orderer in this flow as of now, regardless of the result of the evaluation of block commitments.
* It is assumed that all members of the cluster, both followers and the leader, are motivated to earn fees and thus will not act maliciously.

This process ensures that the block commitments are verified in a decentralized manner, promoting fairness and accuracy in the blockchain network.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.theradius.xyz/overview/internal-secure-block-building-sbb/tx.-orderer-cluster/liveness/block-validation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.