> For the complete documentation index, see [llms.txt](https://block-convey.gitbook.io/block-convey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://block-convey.gitbook.io/block-convey/blockchain-consensus-mechanisms/proof-of-authority-consensus.md).

# Proof of Authority Consensus

 

Proof of Authority (PoA) is a reputation- based consensus algorithm that introduces a practical and efficient solution for blockchain networks (especially the private ones). The term was proposed in 2017 by Ethereum co-founder and former CTO Gavin Wood.

The PoA consensus algorithm leverages the value of identities, which means that block validators are not [*staking*](https://academy.binance.com/en/articles/what-is-staking) coins but their own reputation instead. Therefore, PoA blockchains are secured by the validating nodes that are arbitrarily selected as trustworthy entities.

The Proof of Authority model relies on a limited number of block validators, and this is what makes it a highly scalable system. Blocks and transactions are verified by pre-approved participants, who act as moderators of the system.

PoA consensus algorithm may be applied in a variety of scenarios and is deemed a high-value option for logistical [*applications. When it comes to supply chains, for example, PoA is considered an*](https://academy.binance.com/en/glossary/supply-chain) effective and reasonable solution.

The Proof of Authority model enables companies to maintain their privacy while availing the benefits of blockchain technology. Microsoft Azure is another example where the PoA is being implemented. In a few words, the Azure platform provides solutions for private networks with a system that does not require a native currency like the ether ‘gas’ since there is no need for mining.


---

# 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:

```
GET https://block-convey.gitbook.io/block-convey/blockchain-consensus-mechanisms/proof-of-authority-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.