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

# æternity Consensus Protocol

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>aeternity Consensus</strong></td><td><a href="/developer-documentation/protocol/consensus.md">æternity consensus protocol</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FO7MHc7XJYKrtCX2zPCz5%2Fflip-30deg-gradient2.svg?alt=media&amp;token=9a5fcdda-f853-495e-a65b-ac9c4272af37">flip-30deg-gradient2.svg</a></td></tr></tbody></table>

The æternity blockchain uses a modified version of the Bitcoin-NG (Next Generation) consensus protocol, designed to significantly improve scalability and transaction throughput while maintaining security. Unlike traditional blockchain protocols that combine leader election and transaction processing in a single block, Bitcoin-NG separates these functions: key blocks handle leader election through proof-of-work mining, while micro blocks, created by the elected leader, contain transactions. This innovative approach allows æternity to achieve higher transaction speeds (approximately 120 transactions per second) and shorter confirmation times (around 3 seconds) compared to traditional blockchain architectures, all while preserving decentralization and security.

Our consensus protocol documentation provides detailed technical specifications of this implementation, covering Bitcoin-NG's adaptation for æternity, the handling of coinbase rewards at different block heights, fundamental consensus mechanisms, and the protocol's coin locking features for participation in governance and delegation.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Bitcoin-NG for æternity</td><td><a href="/developer-documentation/protocol/consensus/bitcoin-ng.md">Bitcoin-NG for æternity</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FO7MHc7XJYKrtCX2zPCz5%2Fflip-30deg-gradient2.svg?alt=media&amp;token=9a5fcdda-f853-495e-a65b-ac9c4272af37">flip-30deg-gradient2.svg</a></td></tr><tr><td>Coins Locking</td><td><a href="/developer-documentation/protocol/consensus/locking.md">Coins locking</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FU6AxxjQIzLuS9z4AwiGP%2F15deg-gradient.svg?alt=media&amp;token=a2520256-1072-43f8-9a8d-3681276494bd">15deg-gradient.svg</a></td></tr><tr><td>Coinbase at height</td><td><a href="/developer-documentation/protocol/consensus/coinbase.md">Coinbase at height</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FFg8uXb2tgWcUjB3yscps%2Fflip-30deg-gradient.svg?alt=media&amp;token=7011595e-bad7-4b5e-926e-501080d42820">flip-30deg-gradient.svg</a></td></tr></tbody></table>


---

# 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.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components/aeternity-consensus-protocol.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.