# Tx. Orderer Cluster

**Overview**

The cryptographic approach employed by the system ensures a trustless environment for the tx. orderer operation. However, the architecture still faces the challenge of a Single Point of Failure (SPOF). To mitigate this risk, Radius adopts a distributed tx. orderer network. This network comprises multiple tx. orderers operating concurrently to ensure system reliability and continuity.

**Functionality**

In the event of a tx. orderer failure, the distributed nature of the network allows the remaining tx. orderers to continue operations without interruption. This redundancy enhances the robustness of the system against individual node failures.

**Communication and Decision making**

To ensure efficient communication and syncing among multiple nodes, Radius adopts a leader-based decision-making process. This strategy eliminates the need for consensus regarding the order and formation of blocks. It clearly outlines the roles and duties of the tx. orderers in the network, distinguishing between the leader and the followers.

**Key Benefits**

* **Reliability:** The distributed tx. orderer network significantly reduces the risk associated with a single point of failure, ensuring higher system uptime.
* **Efficiency:** By eliminating the need for consensus between network members, Radius ensures efficient decision-making among tx. orderers, leading to a swift and reliable sequencing process.
* **Scalability:** The distributed architecture allows for scalability, accommodating an increasing number of tx. orderers as the network grows.

**Conclusion**

The implementation of a distributed tx. orderer network represents a strategic approach to enhancing the reliability, scalability, and decision making efficiency of tx. orderer set. This ensures that the system remains robust against failures and maintains continuous operation.


---

# 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.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.