# Validators - Overview

### Overview

Validators play a critical role in the Proof-of-Stake (PoS) networks as they are responsible for maintaining the integrity and security of the network. They do this by compiling and validating transactions, then proposing and voting on new blocks to be added to the chain.

In contrast to batching transactions, Sui follows a [causal-ordering approach](https://docs.sui.io/learn/sui-compared#causal-order-vs-total-order) to handle and execute transactions individually. In other words, if the objects in two transactions are entirely distinct from each other, the order in which they get processed becomes irrelevant.&#x20;

By adopting this method, Sui is able to parallelize transactions with non-shared objects in a ["multi-lane" approach](https://docs.sui.io/learn/sui-compared#suis-approach-to-validating-new-transactions), which results in a remarkable improvement in throughput and a reduction in latency. Additionally, each validator can scale itself horizontally (via worker nodes) and increase its transaction through-put by adding more computing power, allowing them to to achieve highly efficient unit economics with cost scaling linearly with network activity.&#x20;

Sui adopts a Delegated Proof-of-Stake (DPoS) consensus mechanism to identify the validators who manage the network and their corresponding voting rights. These validators are motivated to participate in an honest manner because they receive a percentage of the transaction fees, rewards for staking, and penalties in the form of lost stake and staking rewards for any wrongful conduct.

Despite [Sui's different approach to state](https://docs.sui.io/devnet/learn/sui-compared), the fundamentals behind running a validator node remain the same, adhering to several key principles. Here are a few of the most important ones:

1. **Reliability**: A good validator operator must have a reliable infrastructure to prevent downtime and ensure that blocks are produced and validated regularly.
2. **Security**: The security of the network is of utmost importance, and a good validator operator must take all necessary measures to secure its validator nodes, including using secure hardware, implementing firewalls, and following best practices for network security.
3. **Performance**: Operators must allocate sufficient computational resources and network bandwidth to validate blocks and produce new blocks in a timely manner.
4. **Compliance**: A good validator operator must comply with the rules and regulations of the network, including any economic and technical requirements for validators.
5. **Communication**: Good validator operators must have clear and open communication with the network stakeholders, including other validators, developers, and users. This includes transparent reporting of performance metrics and adherence to consensus protocols.
6. **Transparency:** Good validator operators must be transparent about their operations, including their ownership, infrastructure, and policies for handling stake.
7. **Stakeholder alignment**: Good validator operators must align their interests with those of the network stakeholders and act in the best interests of the network as a whole.

By sticking to these principles, a validator operator can build trust with network stakeholders, contribute to the stability and security of the network, and help drive the success of the PoS network.
