# ZEDXION Consensus

Consensus refers to the agreement process between nodes in a network. The nodes must agree on which transactions to include in the next block on the chain before these transactions are committed.

There are 2 aspects to the process - the actual consensus mechanism to add transactions to blocks, and Sybil protection and validator incentives.

### Sybil protection and incentives via delegated proof of stake

ZEDXION uses delegated Proof of Stake (dPoS) to provide Sybil protection and align the validator incentives.

In order to participate in securing the network consensus, a node operator must stake a minimum required amount of ZEDX tokens (currently set at 10,000 ZEDX). Becoming a validator on ZEDXION is permissionless, meaning that a node operator just needs to satisfy certain technical requirements. The need to stake ZEDX ensures that an entity cannot create multiple seemingly distinct validators without incurring a significant cost. Hence, the Sybil protection. Currently, the maximum number of validators on ZEDXION is 100.

The validator who publishes a block agreed upon during a given consensus round is rewarded by the network protocol in newly minted ZEDX tokens. They also receive the fees users paid for the transactions included into the block.

Over time, validators can expect to publish a share of blocks equal to their share of the overall stake. Since ZEDX uses dPoS, a validator can increase their share by attracting ZEDX tokens from delegators. The mechanics of delegation on ZEDX are discussed in more detail on the [following page](/general/learn-about-the-fuse-platform/fuse-network-blockchain/validators-and-delegation.md).

Validators who violate the consensus rules (by, for instance, not revealing random numbers) can expect their stake (including the delegators' contribution) to be frozen. This provides a strong incentive for validators to behave in the desired manner.

### Consensus Model

ZEDXION initially began with the AuRa (Authority Round) consensus mechanism developed by Parity to append blocks to the ZEDXION blockchain. This mechanism is also known for its use on the xDAI network.

In the AuRa model, validators took turns signing blocks. A signed block was broadcast to all validators, and if the majority agreed on its validity, it was added to the chain. A new block was added every 5 seconds, regardless of whether it contained any transactions. Within this model, transactions on ZEDXION were considered finalized after a single block confirmation.

However, at block 100, the ZEDXION network transitioned to a Proof of Stake (PoS) mechanism. Now, validators are selected based on the amount of staked tokens in the network, maintaining high transaction processing speeds but with enhanced security and decentralization.

#### Current Consensus Parameters

• Transition Block: **100**

• Block Generation Time: **5 seconds**

• Post-Transition Mechanism: **Proof of Stake (PoS)**

• Reward Contract Address: **0xd483605703A18Ce5CDac692B60E41c922a8A3b8E**

The PoS model provides greater decentralization, as validators are now chosen based on their stake rather than on a rotational basis as in the AuRa model. This shift supports stable network growth and reliability while remaining fast and cost-effective for users and developers alike.


---

# 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.zedscan.net/general/learn-about-the-fuse-platform/fuse-network-blockchain/fuse-consensus.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.
