> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/architecture/consensus.md).

# Consensus

At its core, the Keeta Network utilizes a Delegated Proof of Stake (dPoS) voting protocol, which allows for quick consensus while ensuring decentralization. Keeta's block validation process follows a structured five-step sequence that ensures security and efficiency.&#x20;

The process begins when a client initiates a vote on a new block(s), sending their request to multiple network representatives. These representatives respond with temporary votes, providing initial validation of the proposed blocks. The client then requests verification of all temporary votes, creating a cross-validation layer. Following this, representatives submit their permanent votes, confirming their final decision on block validity. In the final step, the client broadcasts both the validated blocks and their associated votes to the network, where they are permanently added to the blockchain.

<figure><img src="https://content.gitbook.com/content/pitcpcamWc0BKEe28I1D/blobs/LwlGTA6iR7dBTOqeTn0v/vote.jpg" alt=""><figcaption><p>Each transaction must receive a sufficient number of votes before being broadcasted to the network.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeta.com/architecture/consensus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
