> For the complete documentation index, see [llms.txt](https://docs.hemi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hemi.xyz/foundational-topics/the-architecture/consensus-and-security-protocols.md).

# Consensus and Security Protocols

{% hint style="info" %}

### 📜 **TL;DR:**

* Incorporates Bitcoin's security to prevent attacks, with PoP Miners embedding consensus data on the Bitcoin blockchain.
* **Rewards PoP Miners** in native tokens for strengthening consensus.
* **Utilizes Bitcoin confirmations** to ensure network integrity, achieving "Bitcoin Finality" for robust defense against reorganizations.
  {% endhint %}

***

{% hint style="success" %}

### 👀 Sneak Peek WIP

***Overview***

The Hemi Network's sequencer consensus combines **Proof-of-Stake** with **Proof-of-Proof** to address weak subjectivity and censorship attacks inherent in traditional PoS systems.

*This hybrid model prevents forged chains through state proofs on the Bitcoin network and allows legitimate sequencers to regain control in adversarial conditions, ensuring the network's resilience and security.*
{% endhint %}

***

#### 🔒 **Network Security and Finality**

* To inherit Bitcoin security, a new type of miner (a “PoP Miner”) publishes Hemi consensus information to the Bitcoin blockchain.
* After a state publication to Bitcoin, the Hemi Network’s consensus layer incorporates cryptographic proofs of these publications, with PoP Miners receiving a reward in the protocol’s native token. The network uses these proofs during fork resolution to prevent reorganizations with the full force of Bitcoin’s security.
* As they are produced, the Hemi Network’s chain segments initially receive Bitcoin confirmations, which means an attacker **would have to control increasingly large ratios of staking power to successfully affect a reorganization.**
* During normal operation, each block on the Hemi Network reaches full **“Bitcoin Finality”** **after 90 minutes, or nine Bitcoin blocks, on average**.

> At this point, it is mathematically impossible for anyone to reorganize the network without 51% attacking Bitcoin itself.


---

# 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.hemi.xyz/foundational-topics/the-architecture/consensus-and-security-protocols.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.