> For the complete documentation index, see [llms.txt](https://doc.particle.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.particle.network/particle-network/modular-l1-design/underlying-architecture/dual-staking.md).
# Dual Staking
Following a similar philosophy to AggDA, Particle Network approaches consensus by focusing on ensuring a high degree of cryptoeconomic security and accessibility.
Bootstrapping a Proof-of-Stake network can be risky, often leading to undesirable volatility affecting the network's value and stability. To solve this, the Particle Chain features a dual staking system, combining Proof-of-Stake through Tendermint with Bitcoin's native security and censorship resistance. Babylon's Bitcoin staking protocol makes this.
Dual staking leverages two distinct pools of operators: one with delegations of Particle Network's native token, and another with delegations of BTC through Babylon. Both groups are required to agree on validity individually, warranting equal participation in consensus.
A model of this nature significantly reduces pressure and security dependence on Particle Network's native token, instead bootstrapping the network through the cryptoeconomic security provided by Bitcoin staking.
---
# 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://doc.particle.network/particle-network/modular-l1-design/underlying-architecture/dual-staking.md?ask=&goal=
```
`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.