> 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/sequencer-consensus.md).

# Sequencer Consensus

{% hint style="info" %}

## 📜 **TL;DR:**

* This approach addresses key PoS vulnerabilities: weak subjectivity and censorship attacks.
* Forged chains would be invalidated by the state proofs on the Bitcoin network.
* Integration with the Bitcoin network validates the blockchain and helps maintain integrity even under attack.
  {% endhint %}

{% hint style="success" %}

## 👀 Sneak Peek WIP

*The Hemi Network uses a hybrid of Proof-of-Stake (PoS) and Proof-of-Proof (PoP) to secure its blockchain.*
{% endhint %}

***

## 🌐 **Overview**

The Hemi Network utilizes the Bitcoin-Secure Sequencer (BSS), a type of Proof-of-Stake (PoS) node, to achieve consensus, or agreement, on the network’s status. By leveraging the Bitcoin blockchain, the Hemi Network decentralizes its security measures, reducing reliance on internal network validators.

***

{% hint style="success" %}

## 👀 Sneak Peek WIP

***Enhanced Consensus Mechanism***

*The network combines traditional PoS with Proof-of-Proof (PoP), creating a more secure and robust consensus mechanism than standard PoS systems.*
{% endhint %}

***

## 🛠️ **How?**

⛓️ It incorporates state proofs from the Bitcoin network to validate the Hemi blockchain, ensuring the network's history cannot be easily altered or falsified.

🛡️ The hybrid model provides a unique defense against majority stake attacks, a common vulnerability in pure PoS networks.

🔐 In the event of an overwhelming attack, the network can offload transactions to the Bitcoin network, ensuring continuous operation and security.


---

# 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/sequencer-consensus.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.