> For the complete documentation index, see [llms.txt](https://docs.nomic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomic.io/network/signer.md). # Signer Validating on Nomic means you partake in the Bitcoin signing process of the funds in the Bitcoin decentralized custody. It is very important that you run a signer. You can run the signer with: ``` nomic signer ``` This will automatically generate a Bitcoin extended private key and store it at `~/.nomic-stakenet-3/signer/xpriv`. It will also prompt you to submit your public key to the network so you can be added to the multisig. {% hint style="danger" %} **KEEP THIS KEY SAFE** - similar to your validator private key, it is important to be mindful of this key so that it is never lost or stolen. {% endhint %} Leave this process running, it will automatically sign Bitcoin transactions that the network wants to create. In the future, we hope for the community to come up with alternative types of signers which provide for extra security, by e.g. airgapping keys, using HSMs, or prompting the user for an encryption key. ### Circuit Breaker The signer process will automatically halt signing if, over the past 24 hours, the signatory set has changed too much, or if too much Bitcoin is being withdrawn from the bridge. These parameters are tunable: ``` nomic signer --max-sigset-change-rate Limits the maximum allowed signatory set change within 24 hours The Total Variation Distance between a day-old signatory set and the newly-proposed signatory set may not exceed this value [default: 0.04] --max-withdrawal-rate Limits the fraction of the total reserve that may be withdrawn within the trailing 24-hour period [default: 0.04] ``` Tweaking these parameters is a decision that requires careful thought. A future release will integrate these circuit breaker checks into the protocol itself. --- # 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.nomic.io/network/signer.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.