> For the complete documentation index, see [llms.txt](https://docs.motif.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motif.finance/specification/bitcoinpod-overview/stateless-vs-stateful.md). # Stateless vs Stateful BitcoinPods can function in 2 modes: 1. A **stateful** BitcoinPod holds funds directly within the Bitcoin address deployed as the BOD, ensuring native control. Applications can enforce custom bitcoin scripts for deploying the BitcoinPod as well as arbitrary valiation logic, making it a playground for financial applications like staking, lending, stablecoin, prediction markets and others. 2. A **stateless** BitcoinPod operates more like EigenPods, where the funds are staked in an external protocol but are locked to the BitcoinPod address as the designated withdrawal destination. The funds are not directly within the BOD address during staking but become accessible to it only at the time of unbonding. This mode introduces additional flexibility by enabling interactions with staking protocols while preserving accountability of the BOD as the final authority on fund access. This enables native restaking for AVSs on Eigenlayer. --- # 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.motif.finance/specification/bitcoinpod-overview/stateless-vs-stateful.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.