> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/custody-and-security/what-is-a-multisignature-wallet.md). # What is a Multisignature Wallet? **Multisignature** (multisig) is a security mechanism that involves multiple private keys to authorize a Bitcoin transaction. Instead of a single private key controlling the transaction, multisig requires two or more private keys to sign off on a transaction before it can be executed. This adds an extra layer of security to prevent unauthorized access and potential theft of funds. While it's true that the principles of Bitcoin emphasize individual control of one's private keys, there are still valid reasons to use a service like Blink's Custodial Mode. Custodial wallets can offer additional security measures such as multisig, which can provide an extra layer of protection for users' funds. Additionally, using a managed wallet can provide peace of mind for users who may be less experienced with managing their own private keys or who simply prefer the convenience and ease of use that it can offer. Ultimately, the choice of wallet comes down to individual preferences and risk tolerance. **Note:** The multisig cold storage described above applies to Blink's Custodial Mode. In Non-Custodial Mode, you hold your own keys via the Spark protocol and your funds are not held in Blink's multisig system. --- # 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://faq.blink.sv/custody-and-security/what-is-a-multisignature-wallet.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.