> For the complete documentation index, see [llms.txt](https://documents.geb.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documents.geb.network/geb-consensus/mother-consensus.md).

# Mother Consensus

GEB's Mother Consensus implements a sophisticated dual-token consensus model built on Bitcoin, featuring a unique BFT PoS mechanism that combines Aura and GRANDPA consensus algorithms through the Substrate framework.

### Detailed Analysis:

1. BFT PoS Consensus Architecture

* Aura for efficient block production
* GRANDPA for rapid finality
* Integration through Substrate framework
* Focus on throughput, security, and consistency
* Decentralization through randomized validator selection

2. Bitcoin Staking Dual-Token Model(L-BTC)

* Non-custodial Bitcoin staking through Lightning Network Layer 2
* Energy conservation principle in GEB token generation 
* Dual-token coordination between BTC and GEB tokens
* Random validator selection with minimum staking thresholds
* Secure non-custodial staking mechanism
* Time-based pledge system aligned with energy conservation

### Equity Distribution：

Two deployment mechanisms for the consensus of mothers have the following revenue distribution methods:

Participants in PoS Stake, whether validators or nominators (ordinary users staking), can only receive BTC Gas rewards

The validators in PoS Stake are the same as the validators of L-BTC (validators need to bind their EVM address). These validators can accept both user stakes from L-BTC and their own stakes, enabling them to earn GEB rewards in L-BTC Stake.

**The Mother Consensus architecture successfully integrates Bitcoin's proven security model with modern PoS mechanisms, creating a robust and efficient system. Through its dual-token model and sophisticated consensus mechanisms, it achieves a balance between security, decentralization, and performance while maintaining strong economic incentives for participants.**

### Practice:

{% content-ref url="/pages/kARRHA8MZ0mtK4ZFVvuB" %}
[Validator](/build/validator.md)
{% endcontent-ref %}

{% content-ref url="/pages/8I2bI7Imdzgwch1qXYcq" %}
[L-BTC Validator Operation](/build/validator/l-btc-validator-operation.md)
{% endcontent-ref %}

{% content-ref url="/pages/nwpuAPO983iH9hFOiX66" %}
[Stake L-BTC](/use/earn-usdgeb/stake-l-btc.md)
{% endcontent-ref %}


---

# 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://documents.geb.network/geb-consensus/mother-consensus.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.