> For the complete documentation index, see [llms.txt](https://docs-launchpad.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-launchpad.energyweb.org/ewc-ecosystem/energy-web-chain/system-architecture/proof-of-authority-consensus-mechanism.md).

# Proof-of-Authority Consensus Mechanism

In a centralized system, such as a bank or a broker, a designated authority or central operating system would be in charge of adding transactions or information to the system, making sure that each transaction is trustworthy, up to date with the whole system, and does not duplicate previous transactions.

In contrast, public blockchains are decentralized, peer-to-peer systems that have no central authority or oversight like this. Designated actors are responsible for processing transactions, creating new blocks and maintaining the integrity and history of previous blocks.

**The system for determining these actors and how they are selected is called a** [**consensus mechanism**](https://ethereum.org/en/developers/docs/consensus-mechanisms/)**.** These mechanisms determine the process of who can confirm transactions and create new blocks on the blockchain and the protocol for how they do so. Because there is no central oversight, consensus needs to be designed in a way that prevents or disincentivizes malicious or uninformed actors from corrupting the integrity of the chain. 

There are many consensus algorithms. You may have heard of some widely used ones like [Proof-of-Work](https://ethereum.org/en/developers/docs/consensus-mechanisms/#proof-of-work) or [Proof-of-Stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/#proof-of-stake'). Each mechanism has its own way of determining who is eligible to process transactions and create new blocks, and how how actors are selected to do so.

**The Energy Web Chain uses the Proof-of-Authority (PoA) consensus mechanism.** 

 All consensus mechanisms have disadvantages and advantages and are chosen based on the purpose and use case of the blockchain it will be serving.[ Read more about why Energy Web employs the Proof-of-Authority mechanisms.](https://docs.energyweb.org/ewc-validator-documentation/ewc-governance/proof-of-authority-consensus-mechanism)


---

# 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://docs-launchpad.energyweb.org/ewc-ecosystem/energy-web-chain/system-architecture/proof-of-authority-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.