> For the complete documentation index, see [llms.txt](https://whitepaper.anttime.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.anttime.net/tokenomics/time-coin/time-blockchain/consensus-mechanism.md).

# Consensus Mechanism

<figure><img src="/files/2L7ZHamMnuq311KPlxvm" alt=""><figcaption></figcaption></figure>

The TIME Blockchain has adopted the PoA (Proof of Authority) consensus algorithm to further strengthen the ecosystem. By using ANTTIME, individuals or organizations can produce TIME by leveraging time as an absolute asset. After undergoing the verification process of governance, they can join as TIME Provers, who serve as validators. Individuals or organizations holding 10 million TIME coins can become node validators and members of the Governance Council. The allocation of these positions may vary based on countries and populations.

<figure><img src="/files/OruUZPzxzSk7KJWpZwqE" alt=""><figcaption></figcaption></figure>

✅ **Consensus Algorithm: Proof of Authority**

✅ **Transaction Processing Speed: 4,000 tps (transactions per second)**

✅ **Block Generation Period: 1 seconds**

✅ **Openness: Verified node validators can participate in the consensus process.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.anttime.net/tokenomics/time-coin/time-blockchain/consensus-mechanism.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.