> For the complete documentation index, see [llms.txt](https://docs.bits.financial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bits.financial/protocol-overview/security-and-custody.md).
# Security and Custody
The Bits Protocol prioritizes security and custody to ensure user assets remain protected. Every BITS token is backed 1:1 by verifiable Bitcoin deposits, stored either in secure vaults on the Bitcoin mainnet or in audited smart contracts for wrapped tokens like wBTC and cbBTC. Assets are not rehypothecated, meaning they are not reused for other purposes or exposed to additional risks.
Yield is generated through the Core Network's Dual Staking, which avoids slashing penalties and preserves the principal under various conditions. A multichain orchestrator handles deposits and redemptions across networks, ensuring accurate token issuance and preventing duplicates. All operations are on-chain, transparent, and auditable, with proof of reserves available at every step.
---
# 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://docs.bits.financial/protocol-overview/security-and-custody.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.