# Consensus

### Current phase Proof of Authority (PoA)

In a Proof of Authority system, blocks are produced by a set of validators whose identities are known and verifiable. Unlike Proof of Work, where anyone can attempt to mine a block by mobilizing computing power, PoA relies on reputation and the trust placed in a small group of authorized participants.

This choice is not a compromise; it is a deliberate technical decision for the network launch phase. A young network with little activity is more vulnerable to attacks on an open consensus mechanism than a mature network. Proof of Authentication (PoA) allows for a start under optimal conditions of stability and security, without sacrificing performance.

Advantages of PoA for this phase:

* ⚡ Fast finalization of blocks in a few secondses
* 🔋 Energy efficiency, no competition in computing power
* 🛡️ Reduced attack surface stability during network boot
* 🔧 Maintainability, corrections and updates made easier

### Proof of Stake (PoS) target phase

The migration to Proof of Stake represents the next natural step in the network's evolution. In this model, validators are selected proportionally to the amount of ZLA they have locked in the protocol for their stake.

This system, adopted by Ethereum in 2022 after several years of development, opens validation to a much larger number of participants and strengthens the decentralization of the network.

The transition will occur when Zeltra's activity and community have reached a sufficient level for open consensus to be viable and secure. There is no arbitrary date: it is the actual growth of the network that will trigger this evolution.

{% hint style="warning" %}
The staking parameters minimum amount, lock duration, reward rate, slashing conditions will be defined and submitted to governance before any migration.
{% endhint %}


---

# 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://zeltra.gitbook.io/zeltra-docs/basics/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.