> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/basics/what-is-a-multisig.md). # What is a multisig Fundamental explanation of a multisig wallet and its importance. A multisig is a non-custodial solution where control over assets is not exercised by a single private key, but rather by multiple private keys. It can be thought of as a safe that requires multiple unique keys to open it and move the assets. That means that even if one of the keys is compromised, the assets remain secure (no single point of failure). Squads Protocol, the autonomous finance layer on Solana, is a collection of onchain smart accounts. These smart accounts are what power Squads Multisig. Multisigs are the most widely adopted use case of smart accounts. They have been around since the early days of Bitcoin and are widely used for the purposes of self-custody of crypto assets across blockchains. Every Squad is a programmable multisig wallet at its core, which ensures that any transaction or action taken within Squads requires the approval of multiple team members. As a result, the risk of unauthorized or malicious activity is greatly reduced, as it becomes impossible for a single member to access and manipulate funds or trigger harmful transactions to the funds held within the multisig. On top of that, multi-signature technology serves as a consensus mechanism allowing teams to make decisions over their treasury (tokens, NFTs) and developer assets (programs, tokens, validators) together in a decentralized manner. --- # 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.squads.so/main/basics/what-is-a-multisig.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.