> 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/pox-5/actors/sbtc-signers.md). # sBTC Signers [sBTC signers](/pox-5/glossary.md#sbtc-signer-set) provide the BTC address that Stacks miners pay into for [PoX-5](/pox-5/glossary.md#pox-pox-4-pox-5-pox-6) reward collection. That address is initialized at the [hard fork](/pox-5/glossary.md#hard-fork-activation) and can later be updated by the sBTC signers without another hard fork, for example if the sBTC signing set changes. They also matter because PoX-5 rewards default to [sBTC](/pox-5/glossary.md#sbtc): miner BTC bids are routed into a smart contract, [auto-bridged](/pox-5/glossary.md#auto-bridge-sbtc) to sBTC, and distributed [weekly](/pox-5/glossary.md#weekly-rewards). Participants can opt out to receive L1 BTC, and the launch scope says that opt-out path routes through the sBTC signer set. --- # 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.stacks.co/pox-5/actors/sbtc-signers.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.