> 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/introduction/integrations.md). # BITS the Canonical Bitcoin Yield Layer The Bits Protocol is a decentralized liquid staking solution designed specifically for Bitcoin (BTC) and its wrapped variants (e.g., wBTC). By leveraging the Core Network's Dual Staking mechanism, Bits enables BTC holders to earn yield on their assets without exposing them to slashing risks. This protocol follows a Lido-inspired model, where staked assets generate rewards that are redistributed to holders, maintaining a 1:1 peg with BTC's price. The ecosystem includes the primary rebasing token (BITS), a wrapped version for DeFi integration (wBITS), and a forthcoming protocol token (qBITS). This documentation provides a comprehensive explanation of the protocol's components, mechanics, and user flows. --- # 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/introduction/integrations.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.