> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/operate/protocol-bonds/bond-faq.md). # Bond FAQ Short answers about protocol bonds under PoX-5, with links to the guides that cover each in full. ## How long is a protocol bond? 12 reward cycles, 25,200 Bitcoin blocks, roughly six months. The term is fixed for every bond. ## Can I hold more than one bond, or a bond and an STX-only stake? No to both. A Stacks principal holds one position at a time. A registration that overlaps an existing bond fails with `ERR_ALREADY_REGISTERED` (u9), and one that overlaps an STX-only stake fails with `ERR_ALREADY_STAKED` (u19). A position that ends before the new one starts can roll into it. The rule is keyed on the Stacks address, not on your Bitcoin keys, so the same Bitcoin keys can lock BTC for later bonds. ## Can I lock BTC on L1 and sBTC in the same bond? No. A registration is either native BTC, as up to 10 lock outputs on Bitcoin, or sBTC held by the contract. Each lock output can commit its own unlock height, as long as every one is at or above the bond's minimum. ## Can I add BTC after registering? No. Commit the full amount when you register. Nothing in pox-5 adds BTC to an existing bond position. ## What am I paid in? Rewards are paid in sBTC: miner BTC is auto-bridged to sBTC for distribution. If you supplied a Bitcoin payout address and your signer-manager supports it, as the reference signer-manager and compatible ones do, your share is withdrawn to native BTC on L1 when it is claimed. The payout address travels in `signer-calldata` to your signer-manager. See [How you are paid](/operate/staking-stx/stack-with-a-pool.md#how-you-are-paid). ## When can I register, and when does registration close? Registration opens once the bond is set up, which happens within the two reward cycles before it starts. It closes when the prepare phase before the bond's start begins, at least 100 Bitcoin blocks before the start height. See [Opening a Bond Position](/operate/protocol-bonds/opening-a-bond-position.md). ## Can I exit my bond early? Yes, during the reward phase of any cycle, which excludes its last 100 Bitcoin blocks (the prepare phase). * **Native BTC bond.** Call `announce-l1-early-exit` from your own Stacks address; no contract or other party can call it for you. You stop earning from that point, then spend your BTC back through the early-exit branch with a co-signature from the early-exit signer. Your STX stays locked until the bond's original end. * **sBTC bond.** Withdraw with `unstake-sbtc`. See [Ending or Changing a Bond Position](/operate/protocol-bonds/ending-or-changing-a-bond-position.md). ## What if my registration fails? See [Bond Troubleshooting](/operate/protocol-bonds/bond-troubleshooting.md). If you funded the bond's checked lock address, a failed registration does not cost you the BTC: it stays spendable by you through the timelock path. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stacks.co/operate/protocol-bonds/bond-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.